-
Notifications
You must be signed in to change notification settings - Fork 21
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
Reboot caused by exception when HomeKit WiFi client apparently has zero for localIP and remoteIP #126
Comments
To fix this I forked my own version of the HomeKit server and added a test for valid IP address here. I also found additional fixes implemented by @JKoss2 in his fork which may, or may not, help with the problems reported here with loss of HomeKit pairing. I now have a branch in my own repository that I will start long-term test with (run for a week and see how things go). |
Closing as fix merged with #127 |
Reopening as this may not be fixed yet |
#129 might help with this one. Also, I see that the HomeKit library includes its own WiFi library which is also quite old. I just removed it altogether from my builds. |
Fixed in #129 |
Error creating new wifiClient in HomeKit. For some reason localIP and remoteIP are zero which leads to an exception and reboot...
The text was updated successfully, but these errors were encountered: