-
Notifications
You must be signed in to change notification settings - Fork 13
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
Local access stops randomly working #131
Comments
I have the same issue. @llavorel-somfy, @vhenriet-sfy what details can we provide that can help debug this? |
For me, it hasn't stopped working (yet), but I did notice that after a while the response time gets longer and longer. After rebooting the TaHoma Switch, reponse times are lower again. I think this was introduced with version 2024.1.4-11 , because I have not noticed it before. |
Hi @iMicknl Would you be able to share with us you Serial Number ? Are you able to detect at which date and time the disconnection occured ? |
Same here, was working fine, i had to move the box so i unplugged and since then impossible to add to homekit or home assistant or use the local api. the only thing that works is the cloud api. |
@Schwebebahn Can you email it at ? |
done |
fyi: our internet was down the last 2 days, so the box was not online. |
I have the same issue, tried to do various changes in the unifi config like disable security etc that could interfere but to no help. connection goes on and off every few minutes in the HA log. using xx.local adress and unable to connect via ip. |
We've seen this happen on two of our units now, local api refuses to connect until the Switch is power cycled |
For me the same. This was today in the domoticz log: |
@eekhoorn if you see the same in your Domoticz logs, it might be a hub problem... Do you run Domoticz and HA on the same machine? |
I've had this happen on a few units now, they refuse connections on port 8443 until rebooted, @llavorel-somfy is there any update on this? |
Same is happening to me for a few months now. |
@bellef I don't believe that's the same problem we're seeing as it's local comms to the tahoma on port 8443 that stops working for us. For your token issue you will need to make sure you are using https on the cloud API (would be on port 443 not 80) |
We've just had another unit do this. The only way to get the local API back up and running again was to power down the device for ~5 minutes and power it up again. If you did a fast power cycle it would still not connect. Just to re-iterate we have no issues with access tokens, the unit refuses any connection on port 8443. |
After some time, the Tahoma Switch Box is unavailable in my local network. Unavailable in my Home Assistant (Overkiz / Local API) and also in Apple Homekit. Can't ping and did not get an answer when asking for the version by curl, but still works with the cloud app. When I reboot the device, it works for some time. My WiFi is from UniFi, when I force the switch to connect to an other access point, it is also working for some time. So, could it be:
a) That the switch is blocking access from local network?
b) That UniFi is related to the problem?
The IP of the switch is static and all devices are in the same subnet.
The text was updated successfully, but these errors were encountered: