Closed sbach89 closed 2 years ago
I think this is a duplicate of issue #4 that I already reported. As a workaround, what I did was add an automation that restarts the service a couple of minutes after startup and that does work, but it would be nice to get this fixed. My HASS is running on quite an old raspberry pi so possibly the timeout is too short.
Hmm it's odd because I didn't have this issue when the integration and controller were on 4.x version. I'm also running on a Celeron J1900 so it isn't exactly slow for what it's doing. Thanks for the tip.
I'm trying to recreate this issue to add in a fix, but unable to. I'm running HA and Omada both in docker containers on a NUC with a Celeron J3455. If I restart the entire box, the integration comes back fine. Restarting both individually seems to work as well.
This appears to be an issue with connectivity when the integration initially loads.
I am also running Omada and HA on docker container on the same computer. If I reboot the computer, I have seen cases that the Omada may have start after the HA, so as the integration fail. To fix that, I just need to restart the HA container. I don't recall such problem in v4 Omada.
Marking this as duplicate. We can continue conversation in #4
Integration fails after every reboot, needs to be removed and re added to enable again.
Omada Software Controller 5.0.29, Home Assistant 2021.12.10 Home Assistant TP-Link Omada Integration 0.2.0