-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[homekit] Binding stops working after a couple of days #9773
Comments
I have the very same issue using a Raspberry Pi 3 Model B. Around 20 HomeKit devices (most of them DIY thermometers and Sonoff switches) and an Apple TV 4 ("HD"). Here's the output from
Also, some general system info:
|
It happened again yesterday. So approx. four days since my original posting. Same stack trace as shown above. |
Not going to post every time this happens (I promise this will be the last time). But this morning it happened again, and there were some loosely time related warnings immediately preceeding the stack trace. I believe they are not related because those warnings have been reported in another issue. But I wanted to share the info anyway.
As usual, a restart of the homekit binding fixed the Home App / Siri. |
Happened again today. I'm going to work around this by restarting OpenHAB at a fixed time (every day at 3:00 AM for now) until this issue is actually fixed. |
I have the same problem. ConcurrentModificationException as well as the HomeKit stopping to work issue. I'm using the official 3.0.0 release. I think the problem startet somewhere around 3.0.0M4 or M5. |
Same problem here! |
There is an open issue at the jmDNS repository |
This issue has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/homekit-jmdns-concurrent-modification-exception/115410/1 |
For the moment I am using a simple cron to detect the corrupted state of the bundle to restart it periodically. Not a beauty, but it minimizes the impact... Adjust to your likings. OpenHab is my only homekit bridge at home so I can detect the faulty state by detecting the missing
|
Same issue here! Thanks for posting your cron job as workaround |
@sebiJo No problem! FYI I changed the script as the interactive cli didn't work in a cron job. Now it does. |
This issue has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/homekit-no-response-error-on-all-openhab-items/118200/2 |
This issue has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/homekit-no-response-error-on-all-openhab-items/118200/4 |
This issue has been mentioned on openHAB Community. There might be relevant details there: |
Deactivating IPv6 for my entire Raspberry Pi helped! |
Unfortunately the issue still exists in 3.1.0-SNAPSHOT Build 2294 (to which I updated on 2021-03-30). The stack trace appeared approx. 1 week after the update and the Homekit-Binding stopped working. Following the advice of @sebiJo I have now disabled IPv6 on the Mac mini's ethernet interface & Wifi (although Wifi is off anyway) and will see how that goes. |
This issue has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/need-to-reset-homekit-pairing-at-every-launch/13542/72 |
Disabling IPv6 does not seem to help on my Mac. It took two weeks but the binding stopped working again yesterday. |
Same issue on 3.1M3, rasPi, IPv6 disabled, both on using its own and using OpenHABs mDNS - still, after some hours, all homekit items are flagged as non responding. openhab-cli console -p XXXXX bundle:restart org.openhab.io.homekit helps. logs: Last login: Sun Apr 25 13:18:36 on ttys000 The default interactive shell is now zsh. The programs included with the Debian GNU/Linux system are free software; Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent ############################################################################### Ip = 192.168.2.12Release = Raspbian GNU/Linux 10 (buster)Kernel = Linux 5.10.17-v7l+Platform = Raspberry Pi 4 Model B Rev 1.2Uptime = 2 day(s). 1:24:56CPU Usage = 0% avg over 4 cpu(s) (4 core(s) x 1 socket(s))CPU Load = 1m: 0.00, 5m: 0.00, 15m: 0.00Memory = Free: 2.60GB (69%), Used: 1.18GB (31%), Total: 3.78GBSwap = Free: 2.58GB (100%), Used: 0.00GB (0%), Total: 2.58GBRoot = Free: 21.50GB (77%), Used: 6.25GB (23%), Total: 28.98GBUpdates = 7 apt updates available.Sessions = 1 session(s)Processes = 125 running processes of 32768 maximum processes###############################################################################
___ ___ ___ ___ | | | | / \ | __ ) () ____ ___ Looking for a place to get started? Check out 'sudo openhabian-config' and the openhabian@OpenHabian:~ $ openhab-cli showlods Unrecognised command: showlods Possible commands: openhabian@OpenHabian:~ $ openhab-cli showlogs ==> /var/log/openhab/audit.log <== ==> /var/log/openhab/events.log <== ==> /var/log/openhab/openhab.log <== ==> /var/log/openhab/audit.log <== ==> /var/log/openhab/events.log <== ==> /var/log/openhab/openhab.log <== Logging in as openhab
2021-04-27 14:28:35.758 [DEBUG] [rver.impl.http.impl.AccessoryHandler] - Exception caught in web handler |
This issue has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/homekit-no-response-error-on-all-openhab-items/118200/104 |
@kaikreuzer Did OH 3.1 ship with jmdns 3.5.7? Where can we see this info? |
Yes, you can check on the openHAB console like this:
|
This issue has been mentioned on openHAB Community. There might be relevant details there: https://community.openhab.org/t/homekit-no-response-error-on-all-openhab-items/118200/153 |
@jewesta this bug report is almost 2 years old and there were several improvements in the homekit binding |
@yfre I've been using 3.3.0 Release for quite a while now and the problem is gone. Yes, I am confident that we can close this issue. Thanks a lot for keeping track! 👍 |
Current Behavior
I am using the Homekit binding to make approx. 50 openHAB items available for control via Siri. After a seemingly random amount of time - mostly a couple of days - the binding stops working. The symptoms are that the Home app flags all items with "no response".
We have two HomePods and an Apple TV. All three are listed as Homekit hubs in the Home app settings. We tried to reboot the device shown as "connected" (as opposed to "standby") in the Home app settings when the problem occurred. But that didn't help.
If I check Karaf console, I can see that a ConcurrentModificationException has been logged. The following is an abbreviated copy & paste of my Karaf console output spanning approx two weeks and showing two consecutive incidents. Although I am not 100% sure that the Exception is directly related to the issue it was there every time I checked the server after Homekit stopped working. As can be seen I can correct the issue if I just restart the binding. Seconds later all Homekit items become responsive again.
Steps to Reproduce (for Bugs)
Unfortunately this issue seems to happen at random. I do not know of a way to reproduce it at will.
Your Environment
Here is the output of the Karaf "info" command:
I am currently running the 3.1.0-SNAPSHOT of openHAB, but I had this issue with the milestones (and I believe the 3.0 release) as well. It is hard to tell as the milestones sometimes got released faster than the issue usually appears.
As can be seen on the Karaf output the system I am running openHAB on is a mac Mini 2012 running macOS Catalina. The system is used exclusively for openHAB.
The text was updated successfully, but these errors were encountered: