-
-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Somfy Homekit controller connection lost #93891
Comments
Hey there @Jc2k, @bdraco, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) homekit_controller documentation |
Do you have any other (non Bluetooth) devices with homekit_controller that are working? If this is the beta, my guess is it's the python upgrade. But @bdraco has a lot of homekit stuff so surprised he's not having troubles if it was that. Can you post debug logs? Enable debug level for aiohomekit. |
Which ones of those are WiFi/Ethernet? |
Somfy: ethernet
does that help? btw, I forgot to mention I also hard booted the Somfy Tahoma box to see if it would reconnect, but no change there |
All good here. No idea whats going on with this one. Probably need a |
exactly what do I do for that? also, and it might be coincidence, but the last 2 days, I relied completely on the homekit controller because the Cloud connection to Somfy was down. It worked flawlessly before the Beta.... should I maybe delete the connection and try re-setup? |
I've never seen a homekit_controller bug that was fixed be re-doing the setup, and sometimes we just end up with 2 bugs to fix 😆 |
I had it temporarily disabled, re-enabled it now and restarting.... fingers crossed.. nope, didnt help ;-( |
I'm adding some more logging in Jc2k/aiohomekit#290 |
changelog: Jc2k/aiohomekit@2.6.3...2.6.4 mostly additional logging to help track down #93891
changelog: Jc2k/aiohomekit@2.6.3...2.6.4 mostly additional logging to help track down #93891
changelog: Jc2k/aiohomekit@2.6.3...2.6.4 mostly additional logging to help track down #93891
with b3 and pr installed I now see thisnusing aiohomekit:debug :
which doesn't really offer a lot more info I fear? this seems to be new to me:
|
Is the ip address correct? |
And you have censored the port, but can you test it's open? curl --verbose http://ip:port Should do it |
no.... connection refused. the ip address is correct though and I have no idea why it uses the port it does. I did notice that after rebooting the Tahoma box, it got another portnumber, on the same ip address |
The port number is often random. On the Aqara hubs it changes at least once a day. So it changing is not that interesting, at least on its own. Does the curl command work? What output do you get? |
That doesn’t look like the b3 message. I don’t think b3 is done yet |
just so I do the right thing, you mean as I do for the py-spy's? https://community.home-assistant.io/t/instructions-to-install-py-spy-on-haos/480473 |
If it's the right place "which hass" will return the path to the hass binary. If it returns nothing you are in the wrong place. I think that command gets you into the OS, but not the container where HA lives. |
Your'e right, thats not it... it needed the second command also: docker exec -it homeassistant /bin/bash
and, after having installed tcpdump I see this:
using this in system monitor:
so should I replace that in the command maybe?
it does not seem to hold a lot of info though 2nd run a bit longer, after having rebooted the switch. running that arp -a command now does reveal the box:
so that at least is something |
Yes |
You can also use https://apps.apple.com/us/app/discovery-dns-sd-browser/id305441017 to verify which port is being published via mdns |
this is what I see on b4 now:
uncensored... notice the 192.168.1.72 address, which is a bit of a surprise, as I dont have that... |
That's consistent with the curl failure. So looking like a zeroconf problem (try the app @bdraco said) or a network problem. |
Discovery gives me Somfy TaHoma._hap._tcp.local. gateway-1236-2325-6238.local:32127 c# = 21 |
Can you post the output of this (from your ha container ideally) ip route get 192.168.1.59 |
|
Does it have any IPv6 addresses? |
Just a wild guess but maybe they broke ipv4. We don’t have IPv6 support yet. Asyncio has happy eyeballs built into it now so it shouldn’t be too hard to add if we need to do that. |
Where do you want me to check, I've given you all that is returned in both that app and in HA log Would this be related btw, new python? #84387 (comment) Somehow that is the bigger change in 2023.6 and really all that changed (since nothing else related to HomeKit was, nor were my devices ) |
If that would be a solution here, 'we need to do that ' ;-) How could we be positive in that regard ? Guess I could roll back to 2022.5 for quick check ( if that wouldn't kill Db stuff etc) |
You could try that curl command for all the addresses returned by the discovery app, to see if it's responding on ipv6. |
this is returning:
|
Check the |
that would be
? I cant get anything else but
so im probably doing it wrong.. |
I'm on my phone right now but if you look up "curl link local address" you might get some ideas. Eg I can see things like "http://[fe80::fa81:1aff:fe5b:c759%25eth0]:12345/" But use the right interface and port. |
the address is a direct copy the Discovery.app and I read I had to 'escape' the en0 using %25. trein it with only % too, no luck |
Earlier you mentioned enp2s0, why is it en0 now? |
that is what is listed in the discovery app, and which data I copied. but let me test that. ---update its futile:
dont think Ive found the right syntax yet... |
No I think you have, and your device isn't listening on ipv6 after all. Unless the port has changed while we have been talking. |
no I checked before I entered the commands |
Fixed! |
Did you try or do anything else besides upgrade? There are other somfy users struggling. |
No, upgrading to .1 was all my system needed. Shall we close here? Thx again! |
The problem
as title
no way to reinstall, connection keeps 'trying'
reloading either Overkiz, or Homekit controller does not solve
device Tahoma Box is readily available on the network, at the correct ip address listed in the error, and cloud connection via the Overkiz intergration is functional, as is the native Somfy app
What version of Home Assistant Core has the issue?
2023.6 beta 0
What was the last working version of Home Assistant Core?
2023.5.x
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Overkiz Homekit controller
Link to integration documentation on our website
https://www.home-assistant.io/integrations/homekit_controller/ https://www.home-assistant.io/integrations/overkiz/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
The text was updated successfully, but these errors were encountered: