I think at this point we can confirm that ipv6 stack enabled causes the problem. Hopefully it will be fixed in the future.
Since the moment of disabling it (few days so far) — home app works perfectly, no disconnections all great
Thanks
1 Like
Thanks vlas for the update and confirmation. But how would that setup work for a dockerized environment? I’m running the latest 3.1.0-M2 docker image on my Synology NAS in host mode and struggle to understand how the ipv6 stack could be disabled in such a setup?
Never mind…I disabled it within Synology NAS, let’s see…
Fortunately this wont be a problem in 3.1.0.M3 as the PR eugen committed has been merged which fixes it in my docker environment without touching ipv6 stack.
2 Likes
Deactivating IPv6 for my entire Raspberry Pi solved the issue for me!
Do you know if there’s a way to run the bundle:refresh command from a Rule (or something else that can be scheduled to run regularly) on systems that don’t include openhab-cli (e.g. Mac)? At the moment I’m just manually entering the command in the Karaf console from time to time, but would be nice to be able to schedule it to run.
Looks like .M3 has solved the problem - my homekit binding has been responding perfectly ever since the update, no need for bundle:refresh.
What did you configured? I am using openhab M3 in a docker environment and if I disable “Use openHAB mDNS service” then the HomeKit could not connect to openHab. If it is enabled, everything works. But my test is not long enough to say, that everything is working fine.
I didn’t change my configuration at all from M2 to M3 (or indeed from 3.0.1 to 3.1.0.M2), so it’s just on the default setup for HomeKit. The default in my setup appears to be “Use openHAB mDNS service” set to off.
please make sure you have configured correct ip address in homekit binding setting. it should the ip address / interface which is accessible from outside or via docker ingress
I can confirm same issue on RasPi/ openHAB3 setup, no docker container.
the challenge with “no response” error is that it is very generic error and could have a number of total different root causes, from network issue, additional homekit bridges like apple tv, to actual issue with homekit add on.
Olaf, was it working before on other /older version of homekit binding? does it works sometime or you always have “no response”?
I just upgraded to openhab 3.1.0m3 , homekit snapshot of today, and turned ipv6 off. I will report back if I get the disconnect error again.
I played around a little bit, and can say, that it is not really working on my end. If I enable the “Use openHAB mDNS service” then it is working about 24h. If I disable it, it is only working till the container gets restarted. Then I have to enable “Use openHAB mDNS service” and disable it again, then it is running until the next container restart. I think that must be something with mdns, because I can see it in my mdns Browser App. Am I doing something wrong? I put in the Main IP address of my Raspberry Pi (so 192.168.20.10), the Container is using network mode host and even a bundle restart did not work for me. Any ideas?
Is there a definitive fix for the HomeKit add on seemingly disconnecting and leaving the accessories in a ‘no response’ state? I’ve disabled all elements of IP6 from the openHAB server and also turned it off on my router. I’m still having this issue occur every hour or so. I can kickstart it again by simply changing the port number that the HomeKit add on works on, I don’t have to restart the bundle or clear pairings.
Has anyone any idea how I can get it to be more stable? Apologies, I know this has been discussed previously, but I’m still none the wiser as to the best way to resolve it.
@alaub81 yes, it sounds like mDNS issue. what you see in the mdns browser app before you restart (when it doesnot work) and after the restart, when it works? do you see _hap services and openHAB there? what is the ip and port stored in that record?
@Jorggs please check with mdns browser app, e.g. discovery app as describe here HomeKit Add-on - System Integrations | openHAB
maybe it still binds to your ipv6
@Jorggs that probably means that IPv6 is not disabled completely. In my case since the moment of turning off it in the kernel – no issues at all.
After a restart it seems, that no mDNS is started for HomeKit. So I try to explain what I found out.
Lets start with a fresh start of my openhab container. My HomeKit Configuration looks like this:
My mDNS Browser looks like this after everything is started fresh in _hap._tcp.
So no HomeKit Entry for openhab. I checked if HomeKit port is online with netstat, and yes it is. and on the right interface:
# netstat -an | grep 9124
tcp6 0 0 :::9124 :::* LISTEN
so no problem here. in openhab client, bundle:list shows that HomeKit is running as well.
So looks like no mDNS publishing is done.
Next step is to activate Use openHAB mDNS service and saving it:
And now, in mDNS Browser there is a new entry and HomeKit gets a Connection to openhab.
But with that option enabled, it works only for 24h. So that’s why I have to disable the option again:
and then mDNS Browser shows this:
and then everything works fine until the next restart of the container or with openhab cli with bundle:restart "HomeKit ID"
So seems, that with the disabled option there is no mDNS Service started at openhab start. Hope my explanation will help out a bit.
@yfre If you need more information, just ask me.
Hi, I have IPv6 turned off in the kernel as this was what I’d thought was causing the problem, but alas not.
thank you. very interesting. i will try to re-produce it on my site.
what is especially interesting is the label “openHAB (2)” on the screenshot number 4. (2) is added automatically by mDNS if there is already a service with the name openHAB. but in you case, it is the only one.