Just updated today from 87.1->88.1. I run HassIO and I think I have a quite nice home automation using mostly ZHA stuff. After starting 88.1 I had problems with Osram Smart Plugs; they just stopped working. I was able to solve that with ZHA network management reconfigure feature.
Biggest change for me is battery charge entities has disappeared
Now I see the battery charge as ZHA attribute. I do not know was this a target but it once again was a change which was not so welcome to me. I had a nice Grafana view to follow the charge level and it does not work anymore. Any Idea how to get that attribute to show as “grafana entity”?
Add one more to the list here. I am having this exact same issue with my zha.* attributes after upgrading from hassio .95 to .96. The zigbee sensors are working otherwise (ie binaryband other states are updating), but the zha device entity that contains battery level is ‘unavailable’. This also broke my battery level templates like the op.
In case it helps, all was working fine before the update, and all my other devices are unaffected (zwave, mqtt, and serial sensors).
Thanks for the head’s up tube0013. In that case I (and likely many others) will have to come up with some way to check batteries. Any ideas on how to go about this?
ZHA - ZHA entities are being removed and battery sensors are being added. We have been asked several times to remove the ZHA domain entities because they do not follow the HA standards. They were originally used to show device online / offline status, rssi, lqi and last seen. They were eventually expanded to hold battery information as well because many Zigbee devices have several power configuration clusters. Online and offline handling, rssi, lqi last seen and the handling of device availability have all been moved to the device object and battery information has been split back out into its own sensor. Any users that created template sensors that leveraged the data in the ZHA entities will be affected by this change. (@dmulcahey - #24909) (zha docs)
Thank you for the very fast reply… beat my research speed. I just read through the breaking changes (more carefully this time… all the way to the bottom lol) and saw that. Now that I know I checked and sure enough the new battery sensors did show up in my zha integrations page. I’ll just have to spend some time renaming those new battery sensor entities and editing my template sensors to match. No big deal.
However it brings up a second question in my mind: What about all the other attributes? For example how would we make use of RSSI?
I just tested and of course zha.entityname.attributes.rssi won’t work. I ask just for knowledge, since I don’t currently use any other attributes in my automations. However if I did, I’d like to know how.
Yes I can see the attributes are there (in the integrations page). There are no entities in the registry to access those values though… or at least I don’t know where to find/enable them. I searched dev/states and nothing.
Thank you again for the reply. It helps knowing what is going on and that there is a solution in the works. Last night I thought I was going crazy, because I just finished dealing with another issue that had similar behavior (issues with persistent USB serial).
