Closed fetzu closed 2 years ago
fetzu
commented
2 years ago Additional info: the moment VeSync's API is finally reachable (for a single call apparently) is not always the time (time from start); it sometimes happens within two minutes and sometimes takes 20+ minutes.
fetzu
commented
2 years ago I took some more time to troubleshoot this, and the error was due to some exotic DNS config on my network; specifying custom DNS servers for the container fixed the issue and the plugin is able to connect and maintain its connection.
Closing this now.
Describe The Bug: When setting up the plugin in a dockerized Homebridge instance (freshly pulled oznu/homebridge:latest), the humidifier is not reachable (because the API itself seems unreachable).
Interestingly, the homebridge instance managed to reach VeSync's API at least once, and the device showed up in Homebridge (but without the ability to control). The logs (below), show that the API (smartapi.vesync.com) is not reachable.
Not sure if it matters, but:
ping: smartapi.vesync.com: Name does not resolve)Doing the same from another random docker instance or from the host machine (Synology NAS) itself resolves all three hosts (including the API).
Running an nslookup from the homebridge container's console works and returns:
To Reproduce:
Simply (re)start the homebridge instance with the homebridge-levoit-humidifiers plugin enabled and let it run for a while.
Expected behavior:
Homebridge manages to connect to VeSync's API and control the devices
Logs:
NOTE: The first part (up to
The authentication success) repeats for approximately 15 minutes. Truncated for space. The following part also repeats ad infinitum.Plugin Config:
Screenshots:
Environment:
Thanks in advance for your support :).