wildoracle
commented
6 months ago Here's the log that downloaded by activating "debug logging" in the integration:
Closed wildoracle closed 6 months ago
wildoracle
commented
6 months ago Here's the log that downloaded by activating "debug logging" in the integration:
brg468
commented
6 months ago It looks like you're having network issues. The logs you posted show a lot of issues connecting to the media player integration as well.
wildoracle
commented
6 months ago It looks like you're having network issues. The logs you posted show a lot of issues connecting to the media player integration as well.
You're correct that I'm having issues with the media player integration, but I have no other network issues (that I know of). Could you elaborate on what you're seeing in the logs that leads you to believe it's my network and not the media player integration itself?
brg468
commented
6 months ago I'm not expert on this stuff but you have Wyze throwing:
raise ClientConnectorError(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host api.wyzecam.com:443 ssl:default [Try again]and the media player at the same time throwing
(Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f730441d010>: Failed to establish a new connection: [Errno -3] Try again'))
They are using different libraries, but maybe the media player issue is blocking the aiohttp connection? Have you tried disabling the media players that are causing issues and see if that allows Wyze to load? Just a guess but worth a try.
wildoracle
commented
6 months ago I'm not expert on this stuff but you have Wyze throwing:
raise ClientConnectorError(req.connection_key, exc) from exc aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host api.wyzecam.com:443 ssl:default [Try again]and the media player at the same time throwing
(Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f730441d010>: Failed to establish a new connection: [Errno -3] Try again'))They are using different libraries, but maybe the media player issue is blocking the aiohttp connection? Have you tried disabling the media players that are causing issues and see if that allows Wyze to load? Just a guess but worth a try.
Thanks, I don't use the media player for anything else, so not sure what else I need to disable?
wildoracle
commented
6 months ago Wyze still is failing to set up. I can hit Reload and sometimes it works sometimes not. UPDATE: Cleaned out some overprotective security firewall settings on my Unifi router, and seems to have eliminated many of the log issues related to APIs not being able to connect, etc. I will turn back on security settings that I need and see what fixes this issue. I should probably close this issue now.
MattRK
commented
3 months ago I just wanted to add that I also experienced this issue. It turned out to be my network settings, specifically my DNS settings. I use AdGuard DNS resolvers (similar to PiHole) and by default it rate limits clients to 20 lookups/sec. As noted in case #441, this integration (or Wyze in general) performs an excessive number of DNS queries. I believe this is why the integration would only load the first 5 to 10 devices in my account before throwing the above referenced "Cannot connect to host" errors. As soon as I changed the rate limit in AdGuard to 0 (AKA unlimited), the integration loaded everything perfectly with no errors/warnings.
wildoracle
commented
3 months ago Thanks - I also use AdGuard on my LAN, and I've been experimenting with it as the possible source for troubles with my Google Chromecast devices. I'll probably just use it as a manually set DNS for specific devices and computers rather than using AdGuard for the whole subnet and then exempting or changing settings for specific devices.
Describe the bug Wyze integration going offline, not loading properly, when it DOES work, several individual Wyze devices go offline even though they are accessible via the Wyze app.
To Reproduce Steps to reproduce the behavior:
Expected behavior I expected all my Wyze devices to be available without errors.
System configuration System: VM in Synology Core 2024.3.2 Supervisor 2024.03.1 Operating System 12.1 Frontend 20240307.0 WyzeApi Version: How can I find this??
home-assistant.log