hi,
first a little bit of history, what might be interesting:
i have a couple of aqara temperature zigbee sensors for quite a while, connected via sonoff usb stick and zigbe2mqtt over mosquito.
one of the “oldest” and (most important) stopped working after 2 years, i thought about battery. As it is my outdoor sensor and it was raining, i could have been replaced battery earlies after a couple of weeks off time. usually i have to replace batteries and instantly sensors coming back, or additionally i have to push with zigbee2mqtt permit join and pressing paring button on sensor for some seconds… for all sensor this works quite good, sometimes i have to wait a couple of hours beeing available again. same this time. my outdoor sensor came back in z2m, good and stable lqi >150 . after some days sensor was off again. quite strange at it drops from stable 150lqi. i was curious device has some misfunctions over the time (it´s rainsheltered, but exposed to air moisture and outdoor temperatures), but anyhow. so i had redo paring with zig2mqtt, it came back again and since then it worked for some weeks until i was unavailable again? grrr… due to rainy days it took once again at least 2 weeks for taking care of that sensor
but now the strange things happend!
as it was not longer unavailable in hassio overall i realized this sensor (or device) was not longer in my zig2mqtt device list? such things never happend to my 2 years and aprox. 150 zigbee devices?
i had NO udpates in meantime for HASSIO, zigbee etc. (latest update in Sept, but now prob started in end of Oct/begin of Nov…), i had just “restarted” zig2mqtt integration manually (instead of rebooting hole decice as i had done usually)
ok so i tryied first to reboot of my hole raspi system, but this dit not helped either: device still lost in z2m!
so in a dry timesplot, i does an device reapairing as usual and device came back to zigbe2 , stable aprox 150 lqi, nearly 100% battery (and all names of device and all related single entities of that device do have exact the old names, whats good, because is not not the default z2m usually creates it, so it remembers “some how” and had not created “new” device id?) showing states, mosquito shows all sensors (temp, battery etc.) i can access history from entities search in hasio and from mosquito device page.
BUT in all dashboards and automations it´s broken! even simple entity cards showing sensor as “Entity not found”
and all integrations and automations etc, what uses that entities showing similar errors…
i created new entity card and it shows it well… so i started “replacing” the same entity in cards and it works now (unfortunately this entity i have on nearly all of my dashbards, automations etc.), quite anoying…
question(s):
- how could a whole device get lost in zig2mqtt? usually if devices physically broke or run out of power, they still appear in device list of z2m for years until manually deleted? is my z2m installation unstable or corrupted?
- why are all entities (with same names) not available after recreation of device in dashboards only? some how internal ids not matching anymore or what? because history and device pages are showing it alive and recording in the same history of last two years?
quite strange? i´m a little bit afraid about the stability and safety of my data and installation?
note. i had downloaded via HACS “Plotly Graph Card v3.3.5”, but this wa at 8st nov
could i do somehow a healing of that entity, or do i have to “reenter” this entitys in all my dashboards and automations manually, what is literally not a change anyhow just reasigning the same entity again? maybe some caching in hassio folders, or deleting some files what will be reacteated be restart of hassio an all will be good? so any fency developers hacks to heal this?
some help is apreciated!
thanx in advance
br
Frank
ps: edited. entity is shown anyhow as broken…
