Thanks for the reply and participation.
Well, some extra details:
Physically going to the sensor and resolving it (rewaking it/ repairing/ finding out the battery is good or not, then replace it if its the case) is obvisously an action to be taken.
However my point is discussing how HA could be better.
And restoring states is already a thing for some integrations. If it was chosen and coded to be.
I have 30+ zigbee battery based devices in my system. Some has a seasonal importance. I care about them more or less depending on the time of year, or don’t care at all for a time period. Also I’m prety active at improving my HA setup and I’ve being doing that for since HA 0.64, a while ago, so restarts, and reshufling things around is frequent.
All that means that with time you lose the perfectionism trait of having everything perfectly paired and working 100% all the time. Busy life.
I do restart my system often (mostly due to hacs integration updates). And also ZigBee ZHA has its share of blame to losing devices pairing from time to time.
So I’m not always sure what portion of the devices I do need to replace batteries vs just repair. ( I know, eventually I’ll have to check each one anyways one by one, physically).
But the knowledge on the state of the battery still stands.
I thought about creating a whole convoluted way of storing the information using extra helpers, automations, etc, but, but that is just a workaround of something that could be simpler. I might still do it anyways.
It’s not only zigbee devices, but I have a bunch of phones, regular tablets, kids tablets and wall mounted tablets that would benefit from that battery information sticking around on the state machine surviving HA reboots.