-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Homebridge crashes when neato servers can’t be reached #33
Comments
Not sure what it is actually, but I guess somethings not up and running when I try to start that specific homebridge instance after a reboot. I have it now waiting for two minutes after reboot and it works. |
This has happened before. It's likely on the Neato server end. |
Thanks for raising this issue. Fixed in v0.6.3 |
Last update broke everything, on startup the plugin overrides the error but then also removes both my Neato from HomeKit and from my automations. |
Your neato and homebridge where on or offline? |
Both Neatos were online, I installed the update and did a sudo reboot to see what happens. My Neato homebridge instance started now as expected where it failed before but kicked both robots out of HomeKit. Maybe it’s just me but I have the feeling that the DNS error in the log might me due to something not yet ready networking wise. On the other hand all other plugins that rely on accessing some external API work without problems. Went back to 0.6.2 where I have to do a restart after booting but at least it won’t delete my automations till then. |
Should be the same issue as #44 and will be fixed with the change to a dynamic platform. |
So this is really weird. When I restart my Pi the neato plugin throws the following error protocol. If I restart the service a few minutes later everything suddenly works fine. Any idea what this might be causing? (Credentials edited)
The text was updated successfully, but these errors were encountered: