search

skrollme / homebridge-eveatmo

Homebridge plugin which adds a Netatmo weatherstation as HomeKit device and tries to act like Elgato Eve Room/Weather
Apache License 2.0
69 stars 7 forks source link

HomeKit connection failed completely because of empty battery of outdoor module #44

Closed x7onix closed 4 years ago

x7onix commented 4 years ago

Hi,

first of all, thanks for the good work and the plugin, did run like a charm till yesterday :). If this problem is already known, than sorry didn't find it.

I had yesterday the following Problem: I restarted my homebridge system. After the restart my HomeKit Hub marked every Accessory with "No Response". Homebridge is running on a raspberry pi. On that raspberry there are some other systems too like openhab, grafana and a postgresql server. I did some changes on openhab and as this is connected to homebridge -- my journey did begin.

What did i do:

  1. Reverting everything i did in openhab (had nothing to do with homebridge, it was just for the openhab cloud)
  2. Looking into some logs and fixing an ipv6 failure (at least this is gone forever now, as i do not have ipv6 in my home network, the fix was pretty easy -- shutting it down)
  3. Rebooted my iPad (this is the HomeKit Hub) multiple times
  4. Installing a different Version of Homebridge - Before 1.2.2 now 1.1.6
  5. Lastly, I thought "what the heck" - disconnect the bridge from my ipad and reconnect it to start over. <-- I was not able to reconnect my homebridge to my iPad with the Failure "It is not compatible"
  6. A short google told me, that one of my accessory does give "wrong" or "unusable" data to homekit and homekit then ignores the complete bridge :( n1 one apple, just ignore the one accessory and not all of it!
  7. After that i remembered that the battery of the outdoor module did die a few days ago
  8. Deleted the Plugin configuration for eveatmo in homebridge
  9. Connection between homekit and homebrigde worked again
  10. Readded the configuration of eveatmo into homebridge
  11. Connection died again
  12. Went outside and replaced the empty batteries
  13. Did take around 10 to 20 minutes -- Connection between Homekit and Homebridge worked again. Ttl is 540, so i think there are the 10 to 20 minutes coming from.

Homebridge did work fine until the restart. I think the initial value after a restart could something be like "null" which Homekit cannot handle. Btw. A module with batteries which is not reachable should get battery value of 0 and Status low 1 (but that"s my opinion :) -- at least someone would know that there is something wrong -- but i do not know what homekit allows and netatmo provides in this case :) ) I hope the next one having this problem this issue can help.

Versions:

Thanks a lot for the good work. If information is missing or you need some more, just let me know. If i can still reach it, i am going to provide it to you.

Greetings, Toni

x7onix commented 4 years ago

Sry, just saw that some issues because of this are already closed with "won't be fixed"

Still thanks for the good work :)