@ int_ua, probably upower service wasn't running: systemctl start upower.service or systemctl enable upower.service will start it for a session or permanently. upower -e as shown in my screenshot will then list (enumerate) power devices and upower -i /org/freedesktop/UPower/devices/battery_bq27200_0 will show actual battery data like charging/discharging status, native path in the filesystem etc.

Interesting, there we have another link to the actual device. But either way only reads out battery status. For charging, the known failure with musb modules at first boot occurs on my setup too, but shutdown -r now does the trick. With that workaround at hand, it's a low-priority bug I'd say.