search

jfarmer08 / homebridge-wyze-smart-home

Wyze Smart Home plugin for Homebridge.
MIT License
93 stars 14 forks source link

Most wyze devices stopped responding logs full of errors. #211

Closed Andy589 closed 4 months ago

Andy589 commented 5 months ago

Describe Your Problem: All wyze products I have except for the switches stopped working. I had not changed anything for months. My wife received an email from wyze stating that her password was reset because of suspicious activity. I updated synology, homebridge, plugin, reboot several times, changed wyze password, api token and updated homebridge and no change. Logs are full of errors and I don't know what they mean. Was working flawlessly for months.

Logs:

[2/2/2024, 9:33:56 PM] [Wyze] Error, logging in and trying again [2/2/2024, 9:33:56 PM] [Wyze] Request failed: AxiosError: Request failed with status code 403 [2/2/2024, 9:33:56 PM] [Wyze] Response PerformRequest ([object Object]): "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=\"1px\">\nRequest blocked.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: xV-oplX0RmQnYiQ774XQ2sJpOAs484svI4LE523vMBBLOqP-Ok0AtA==\n
\n
\n
\n" [2/2/2024, 9:33:56 PM] [Wyze] Error getting devices: AxiosError: Request failed with status code 403 [2/2/2024, 9:34:57 PM] [Wyze] Error: access token is error at WyzeAPI._performRequest (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:132:15) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WyzeAPI.request (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:80:14) at WyzeAPI.getObjectList (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:234:20) at WyzeSmartHome.refreshDevices (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:101:26) at WyzeSmartHome.runLoop (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:90:9) [2/2/2024, 9:34:57 PM] [Wyze] Error, refreshing access token and trying again [2/2/2024, 9:34:57 PM] [Wyze] Error, logging in and trying again [2/2/2024, 9:34:57 PM] [Wyze] Request failed: AxiosError: Request failed with status code 403 [2/2/2024, 9:34:57 PM] [Wyze] Response PerformRequest ([object Object]): "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=\"1px\">\nRequest blocked.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: PcEGns9LNlnv8JJF-fQZemJ19wC9jNx8rU5P4ldzyCxgGkJaD9nWmA==\n
\n
\n
\n" [2/2/2024, 9:34:57 PM] [Wyze] Error getting devices: AxiosError: Request failed with status code 403 [2/2/2024, 9:35:57 PM] [Wyze] Error: access token is error at WyzeAPI._performRequest (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:132:15) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WyzeAPI.request (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:80:14) at WyzeAPI.getObjectList (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:234:20) at WyzeSmartHome.refreshDevices (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:101:26) at WyzeSmartHome.runLoop (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:90:9) [2/2/2024, 9:35:57 PM] [Wyze] Error, refreshing access token and trying again [2/2/2024, 9:35:57 PM] [Wyze] Error, logging in and trying again [2/2/2024, 9:35:57 PM] [Wyze] Request failed: AxiosError: Request failed with status code 403 [2/2/2024, 9:35:57 PM] [Wyze] Response PerformRequest ([object Object]): "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=\"1px\">\nRequest blocked.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: _LjF9RAtXkXulPgx75hplM6IAghhzkEwL7A_nWqcMdPWnKHgH_5h2A==\n
\n
\n
\n" [2/2/2024, 9:35:57 PM] [Wyze] Error getting devices: AxiosError: Request failed with status code 403 [2/2/2024, 9:36:58 PM] [Wyze] Error: access token is error at WyzeAPI._performRequest (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:132:15) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WyzeAPI.request (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:80:14) at WyzeAPI.getObjectList (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:234:20) at WyzeSmartHome.refreshDevices (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:101:26) at WyzeSmartHome.runLoop (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:90:9) [2/2/2024, 9:36:58 PM] [Wyze] Error, refreshing access token and trying again [2/2/2024, 9:36:58 PM] [Wyze] Error, logging in and trying again [2/2/2024, 9:36:58 PM] [Wyze] Request failed: AxiosError: Request failed with status code 403 [2/2/2024, 9:36:58 PM] [Wyze] Response PerformRequest ([object Object]): "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=\"1px\">\nRequest blocked.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: VfjsVIQRhyP4dOiyIzva7n2vEc2v9NKrRtlcRka7M_Adim-7wNt4pw==\n
\n
\n
\n" [2/2/2024, 9:36:58 PM] [Wyze] Error getting devices: AxiosError: Request failed with status code 403 [2/2/2024, 9:37:58 PM] [Wyze] Error: access token is error at WyzeAPI._performRequest (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:132:15) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WyzeAPI.request (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:80:14) at WyzeAPI.getObjectList (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:234:20) at WyzeSmartHome.refreshDevices (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:101:26) at WyzeSmartHome.runLoop (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:90:9) [2/2/2024, 9:37:58 PM] [Wyze] Error, refreshing access token and trying again [2/2/2024, 9:37:58 PM] [Wyze] Error, logging in and trying again [2/2/2024, 9:37:59 PM] [Wyze] Request failed: AxiosError: Request failed with status code 403 [2/2/2024, 9:37:59 PM] [Wyze] Response PerformRequest ([object Object]): "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=\"1px\">\nRequest blocked.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: 4R_E9U1olo5gx7GBhanSYco6BO1vyITNXRUkl03W3IaWI9qUUYoVXQ==\n
\n
\n
\n" [2/2/2024, 9:37:59 PM] [Wyze] Error getting devices: AxiosError: Request failed with status code 403 WARNING couldn't map socket coming from remote address ::ffff:10.11.12.254:59740 at local address ::ffff:10.11.12.254 to a interface! [2/2/2024, 9:38:40 PM] [homebridge-wyze-smart-home] This plugin generated a warning from the characteristic 'On': characteristic value expected boolean and received undefined. See https://homebridge.io/w/JtMGR for more info. [2/2/2024, 9:38:40 PM] [homebridge-wyze-smart-home] This plugin generated a warning from the characteristic 'On': characteristic value expected boolean and received undefined. See https://homebridge.io/w/JtMGR for more info. WARNING couldn't map socket coming from remote address ::ffff:10.11.12.254:59744 at local address ::ffff:10.11.12.254 to a interface! WARNING couldn't map socket coming from remote address ::ffff:10.11.12.254:59748 at local address ::ffff:10.11.12.254 to a interface! WARNING couldn't map socket coming from remote address ::ffff:10.11.12.254:59752 at local address ::ffff:10.11.12.254 to a interface! WARNING couldn't map socket coming from remote address ::ffff:10.11.12.254:59754 at local address ::ffff:10.11.12.254 to a interface! WARNING couldn't map socket coming from remote address ::ffff:10.11.12.254:59756 at local address ::ffff:10.11.12.254 to a interface! WARNING couldn't map socket coming from remote address ::ffff:10.11.12.254:59758 at local address ::ffff:10.11.12.254 to a interface! WARNING couldn't map socket coming from remote address ::ffff:10.11.12.254:59760 at local address ::ffff:10.11.12.254 to a interface! WARNING couldn't map socket coming from remote address ::ffff:10.11.12.254:59762 at local address ::ffff:10.11.12.254 to a interface! WARNING couldn't map socket coming from remote address ::ffff:10.11.12.254:59764 at local address ::ffff:10.11.12.254 to a interface! WARNING couldn't map socket coming from remote address ::ffff:10.11.12.254:59766 at local address ::ffff:10.11.12.254 to a interface! WARNING couldn't map socket coming from remote address ::ffff:10.11.12.254:59768 at local address ::ffff:10.11.12.254 to a interface! WARNING couldn't map socket coming from remote address ::ffff:10.11.12.254:59770 at local address ::ffff:10.11.12.254 to a interface! WARNING couldn't map socket coming from remote address ::ffff:10.11.12.254:59772 at local address ::ffff:10.11.12.254 to a interface! [2/2/2024, 9:38:40 PM] [homebridge-wyze-smart-home] This plugin generated a warning from the characteristic 'On': characteristic value expected boolean and received undefined. See https://homebridge.io/w/JtMGR for more info. WARNING couldn't map socket coming from remote address ::ffff:10.11.12.254:59774 at local address ::ffff:10.11.12.254 to a interface! WARNING couldn't map socket coming from remote address ::ffff:10.11.12.254:59776 at local address ::ffff:10.11.12.254 to a interface! WARNING couldn't map socket coming from remote address ::ffff:10.11.12.254:59780 at local address ::ffff:10.11.12.254 to a interface! WARNING couldn't map socket coming from remote address ::ffff:10.11.12.254:59782 at local address ::ffff:10.11.12.254 to a interface! WARNING couldn't map socket coming from remote address ::ffff:10.11.12.254:59784 at local address ::ffff:10.11.12.254 to a interface! WARNING couldn't map socket coming from remote address ::ffff:10.11.12.254:59786 at local address ::ffff:10.11.12.254 to a interface! WARNING couldn't map socket coming from remote address ::ffff:10.11.12.254:59788 at local address ::ffff:10.11.12.254 to a interface! [2/2/2024, 9:38:40 PM] [homebridge-wyze-smart-home] This plugin generated a warning from the characteristic 'On': characteristic value expected boolean and received undefined. See https://homebridge.io/w/JtMGR for more info. WARNING couldn't map socket coming from remote address ::ffff:10.11.12.254:59790 at local address ::ffff:10.11.12.254 to a interface! WARNING couldn't map socket coming from remote address ::ffff:10.11.12.254:59808 at local address ::ffff:10.11.12.254 to a interface! [2/2/2024, 9:38:43 PM] [homebridge-wyze-smart-home] This plugin generated a warning from the characteristic 'On': characteristic value expected boolean and received undefined. See https://homebridge.io/w/JtMGR for more info. [2/2/2024, 9:38:43 PM] [homebridge-wyze-smart-home] This plugin generated a warning from the characteristic 'On': characteristic value expected boolean and received undefined. See https://homebridge.io/w/JtMGR for more info. [2/2/2024, 9:38:58 PM] [Homebridge UI] Homebridge restart request received [2/2/2024, 9:38:58 PM] [Homebridge UI] UI / Bridge settings have not changed; only restarting Homebridge process [2/2/2024, 9:38:58 PM] [Homebridge UI] Sending SIGTERM to Homebridge [2/2/2024, 9:38:58 PM] Got SIGTERM, shutting down Homebridge... [2/2/2024, 9:38:58 PM] Got SIGTERM, shutting down child bridge process... [2/2/2024, 9:38:59 PM] [Wyze] Error: access token is error at WyzeAPI._performRequest (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:132:15) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WyzeAPI.request (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:80:14) at WyzeAPI.getObjectList (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:234:20) at WyzeSmartHome.refreshDevices (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:101:26) at WyzeSmartHome.runLoop (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:90:9) [2/2/2024, 9:38:59 PM] [Wyze] Error, refreshing access token and trying again [2/2/2024, 9:38:59 PM] [Wyze] Error, logging in and trying again [2/2/2024, 9:38:59 PM] [Wyze] Request failed: AxiosError: Request failed with status code 403 [2/2/2024, 9:38:59 PM] [Wyze] Response PerformRequest ([object Object]): "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=\"1px\">\nRequest blocked.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: BOEoGbtIis7nArNqvIvRmhGjJwcDrqOGDWV-1PvhGcoEjusq10mbgA==\n
\n
\n
\n" [2/2/2024, 9:38:59 PM] [Wyze] Error getting devices: AxiosError: Request failed with status code 403 [2/2/2024, 9:39:03 PM] [HB Supervisor] Homebridge Process Ended. Code: 143, Signal: null [2/2/2024, 9:39:08 PM] [HB Supervisor] Restarting Homebridge... [2/2/2024, 9:39:08 PM] [HB Supervisor] Starting Homebridge with extra flags: -I -P /volume1/homebridge/node_modules --strict-plugin-resolution [2/2/2024, 9:39:08 PM] [HB Supervisor] Started Homebridge v1.7.0 with PID: 22462 [2/2/2024, 9:39:09 PM] Loaded config.json with 0 accessories and 2 platforms. [2/2/2024, 9:39:09 PM] Loaded 0 cached accessories from cachedAccessories. [2/2/2024, 9:39:09 PM] --- [2/2/2024, 9:39:09 PM] Loaded plugin: homebridge-wyze-smart-home@0.5.37-alpha.7 [2/2/2024, 9:39:09 PM] Registering platform 'homebridge-wyze-smart-home.WyzeSmartHome' [2/2/2024, 9:39:09 PM] --- [2/2/2024, 9:39:09 PM] Loading 2 platforms... [2/2/2024, 9:39:09 PM] [Wyze] Initializing WyzeSmartHome platform... [2/2/2024, 9:39:09 PM] [Wyze] Initializing child bridge 0E:28:8E:C6:2B:52 Setup Payload: X-HM://0024GOI5W17XT Enter this code with your HomeKit app on your iOS device to pair with Homebridge:

┌────────────┐     

└────────────┘

[2/2/2024, 9:39:09 PM] Homebridge v1.7.0 (HAP v0.11.1) (Homebridge 9B5C) is running on port 51702. Failed to create listener for avahi-daemon server state. The system will not be notified about restarts of avahi-daemon and will therefore stay undiscoverable in those instances. Error message: Error: No such interface found [2/2/2024, 9:39:09 PM] [Wyze] Launched child bridge with PID 22477 [2/2/2024, 9:39:09 PM] Registering platform 'homebridge-wyze-smart-home.WyzeSmartHome' [2/2/2024, 9:39:09 PM] [Wyze] Loaded homebridge-wyze-smart-home v0.5.37-alpha.7 child bridge successfully [2/2/2024, 9:39:09 PM] Loaded 21 cached accessories from cachedAccessories.0E288EC62B52. [2/2/2024, 9:39:09 PM] Homebridge v1.7.0 (HAP v0.11.1) (Wyze) is running on port 33901. Failed to create listener for avahi-daemon server state. The system will not be notified about restarts of avahi-daemon and will therefore stay undiscoverable in those instances. Error message: Error: No such interface found WARNING couldn't map socket coming from remote address ::ffff:10.11.12.254:46092 at local address ::ffff:10.11.12.254 to a interface! [2/2/2024, 9:39:10 PM] [Wyze] Error: access token is error at WyzeAPI._performRequest (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:132:15) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WyzeAPI.request (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:80:14) at WyzeAPI.getObjectList (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:234:20) at WyzeSmartHome.refreshDevices (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:101:26) at WyzeSmartHome.runLoop (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:90:9) [2/2/2024, 9:39:10 PM] [Wyze] Error, refreshing access token and trying again [2/2/2024, 9:39:10 PM] [Wyze] Error, logging in and trying again [2/2/2024, 9:39:10 PM] [Wyze] Request failed: AxiosError: Request failed with status code 403 [2/2/2024, 9:39:10 PM] [Wyze] Response PerformRequest ([object Object]): "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=\"1px\">\nRequest blocked.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: 4bl_jYYsPu9xtK4I0yGxhSzoPw5Zh6zbgH2qai2WWqjuasWyDE-ETA==\n
\n
\n
\n" [2/2/2024, 9:39:10 PM] [Wyze] Error getting devices: AxiosError: Request failed with status code 403 WARNING couldn't map socket coming from remote address ::ffff:10.11.12.254:59858 at local address ::ffff:10.11.12.254 to a interface! [2/2/2024, 9:39:11 PM] [homebridge-wyze-smart-home] This plugin generated a warning from the characteristic 'On': characteristic value expected boolean and received undefined. See https://homebridge.io/w/JtMGR for more info. [2/2/2024, 9:39:11 PM] [homebridge-wyze-smart-home] This plugin generated a warning from the characteristic 'On': characteristic value expected boolean and received undefined. See https://homebridge.io/w/JtMGR for more info. [2/2/2024, 9:39:27 PM] [Wyze] Restarting child bridge... [2/2/2024, 9:39:27 PM] Got SIGTERM, shutting down child bridge process... [2/2/2024, 9:39:32 PM] [Wyze] Child bridge process ended [2/2/2024, 9:39:32 PM] [Wyze] Process Ended. Code: 143, Signal: null [2/2/2024, 9:39:39 PM] [Wyze] Restarting Process... [2/2/2024, 9:39:40 PM] [Wyze] Launched child bridge with PID 22691 [2/2/2024, 9:39:40 PM] Registering platform 'homebridge-wyze-smart-home.WyzeSmartHome' [2/2/2024, 9:39:40 PM] [Wyze] Loaded homebridge-wyze-smart-home v0.5.37-alpha.7 child bridge successfully [2/2/2024, 9:39:40 PM] Loaded 21 cached accessories from cachedAccessories.0E288EC62B52. [2/2/2024, 9:39:40 PM] Homebridge v1.7.0 (HAP v0.11.1) (Wyze) is running on port 33901. Failed to create listener for avahi-daemon server state. The system will not be notified about restarts of avahi-daemon and will therefore stay undiscoverable in those instances. Error message: Error: No such interface found [2/2/2024, 9:39:40 PM] [Wyze] Error: access token is error at WyzeAPI._performRequest (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:132:15) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WyzeAPI.request (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:80:14) at WyzeAPI.getObjectList (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:234:20) at WyzeSmartHome.refreshDevices (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:101:26) at WyzeSmartHome.runLoop (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:90:9) [2/2/2024, 9:39:40 PM] [Wyze] Error, refreshing access token and trying again [2/2/2024, 9:39:40 PM] [Wyze] Error, logging in and trying again [2/2/2024, 9:39:41 PM] [Wyze] Request failed: AxiosError: Request failed with status code 403 [2/2/2024, 9:39:41 PM] [Wyze] Response PerformRequest ([object Object]): "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=\"1px\">\nRequest blocked.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: VqRs1JIitPpqsRwQXKNn_ZuplAxIY0R7AX7nqyWesQ_0mnJKI_qG4Q==\n
\n
\n
\n" [2/2/2024, 9:39:41 PM] [Wyze] Error getting devices: AxiosError: Request failed with status code 403 [2/2/2024, 9:39:41 PM] [homebridge-wyze-smart-home] This plugin generated a warning from the characteristic 'On': characteristic value expected boolean and received undefined. See https://homebridge.io/w/JtMGR for more info. [2/2/2024, 9:39:41 PM] [homebridge-wyze-smart-home] This plugin generated a warning from the characteristic 'On': characteristic value expected boolean and received undefined. See https://homebridge.io/w/JtMGR for more info. [2/2/2024, 9:40:41 PM] [Wyze] Error: access token is error at WyzeAPI._performRequest (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:132:15) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WyzeAPI.request (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:80:14) at WyzeAPI.getObjectList (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:234:20) at WyzeSmartHome.refreshDevices (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:101:26) at WyzeSmartHome.runLoop (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:90:9) [2/2/2024, 9:40:41 PM] [Wyze] Error, refreshing access token and trying again [2/2/2024, 9:40:41 PM] [Wyze] Error, logging in and trying again [2/2/2024, 9:40:41 PM] [Wyze] Request failed: AxiosError: Request failed with status code 403 [2/2/2024, 9:40:41 PM] [Wyze] Response PerformRequest ([object Object]): "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=\"1px\">\nRequest blocked.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: 2qnfJlveq2p4stsIjUohd5wX2gVq0tlYQPVvYkwFkDUSmfLVA_nrhA==\n
\n
\n
\n" [2/2/2024, 9:40:41 PM] [Wyze] Error getting devices: AxiosError: Request failed with status code 403 [2/2/2024, 9:41:36 PM] [Homebridge UI] Changes to config.json saved. [2/2/2024, 9:41:38 PM] [Wyze] Restarting child bridge... [2/2/2024, 9:41:38 PM] Got SIGTERM, shutting down child bridge process... [2/2/2024, 9:41:42 PM] [Wyze] Error: access token is error at WyzeAPI._performRequest (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:132:15) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WyzeAPI.request (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:80:14) at WyzeAPI.getObjectList (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:234:20) at WyzeSmartHome.refreshDevices (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:101:26) at WyzeSmartHome.runLoop (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:90:9) [2/2/2024, 9:41:42 PM] [Wyze] Error, refreshing access token and trying again [2/2/2024, 9:41:42 PM] [Wyze] Error, logging in and trying again [2/2/2024, 9:41:42 PM] [Wyze] Request failed: AxiosError: Request failed with status code 403 [2/2/2024, 9:41:42 PM] [Wyze] Response PerformRequest ([object Object]): "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=\"1px\">\nRequest blocked.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: iI3NXrvK213RgCbMmPRAqT67i-42OSCaBKjJfOsZ7PP7Y3v_q-p0eg==\n
\n
\n
\n" [2/2/2024, 9:41:42 PM] [Wyze] Error getting devices: AxiosError: Request failed with status code 403 [2/2/2024, 9:41:43 PM] [Wyze] Child bridge process ended [2/2/2024, 9:41:43 PM] [Wyze] Process Ended. Code: 143, Signal: null [2/2/2024, 9:41:50 PM] [Wyze] Restarting Process... [2/2/2024, 9:41:50 PM] [Wyze] Launched child bridge with PID 23354 [2/2/2024, 9:41:50 PM] Registering platform 'homebridge-wyze-smart-home.WyzeSmartHome' [2/2/2024, 9:41:50 PM] [Wyze] Loaded homebridge-wyze-smart-home v0.5.37-alpha.7 child bridge successfully [2/2/2024, 9:41:50 PM] Loaded 21 cached accessories from cachedAccessories.0E288EC62B52. [2/2/2024, 9:41:51 PM] Homebridge v1.7.0 (HAP v0.11.1) (Wyze) is running on port 33901. Failed to create listener for avahi-daemon server state. The system will not be notified about restarts of avahi-daemon and will therefore stay undiscoverable in those instances. Error message: Error: No such interface found [2/2/2024, 9:41:51 PM] [Wyze] Error: access token is error at WyzeAPI._performRequest (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:132:15) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WyzeAPI.request (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:80:14) at WyzeAPI.getObjectList (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:234:20) at WyzeSmartHome.refreshDevices (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:101:26) at WyzeSmartHome.runLoop (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:90:9) [2/2/2024, 9:41:51 PM] [Wyze] Error, refreshing access token and trying again [2/2/2024, 9:41:51 PM] [Wyze] Error, logging in and trying again [2/2/2024, 9:41:51 PM] [Wyze] Request failed: AxiosError: Request failed with status code 403 [2/2/2024, 9:41:51 PM] [Wyze] Response PerformRequest ([object Object]): "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=\"1px\">\nRequest blocked.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: INPoKivh1kojOUoKRGIc-vjVYxiqqjb3R3HMp50zGP96COP3NVBXLw==\n
\n
\n
\n" [2/2/2024, 9:41:51 PM] [Wyze] Error getting devices: AxiosError: Request failed with status code 403 WARNING couldn't map socket coming from remote address ::ffff:10.11.12.254:59898 at local address ::ffff:10.11.12.254 to a interface! [2/2/2024, 9:41:52 PM] [homebridge-wyze-smart-home] This plugin generated a warning from the characteristic 'On': characteristic value expected boolean and received undefined. See https://homebridge.io/w/JtMGR for more info. [2/2/2024, 9:41:52 PM] [homebridge-wyze-smart-home] This plugin generated a warning from the characteristic 'On': characteristic value expected boolean and received undefined. See https://homebridge.io/w/JtMGR for more info. [2/2/2024, 9:42:52 PM] [Wyze] Error: access token is error at WyzeAPI._performRequest (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:132:15) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WyzeAPI.request (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:80:14) at WyzeAPI.getObjectList (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:234:20) at WyzeSmartHome.refreshDevices (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:101:26) at WyzeSmartHome.runLoop (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:90:9) [2/2/2024, 9:42:52 PM] [Wyze] Error, refreshing access token and trying again [2/2/2024, 9:42:52 PM] [Wyze] Error, logging in and trying again [2/2/2024, 9:42:52 PM] [Wyze] Request failed: AxiosError: Request failed with status code 403 [2/2/2024, 9:42:52 PM] [Wyze] Response PerformRequest ([object Object]): "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=\"1px\">\nRequest blocked.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: ZW42MT3i1IEa1j64jSYHoD-Ppxthz4721PjWsa7Pj6K880d-e6MbLw==\n
\n
\n
\n" [2/2/2024, 9:42:52 PM] [Wyze] Error getting devices: AxiosError: Request failed with status code 403 [2/2/2024, 9:43:52 PM] [Wyze] Error: access token is error at WyzeAPI._performRequest (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:132:15) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WyzeAPI.request (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:80:14) at WyzeAPI.getObjectList (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:234:20) at WyzeSmartHome.refreshDevices (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:101:26) at WyzeSmartHome.runLoop (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:90:9) [2/2/2024, 9:43:52 PM] [Wyze] Error, refreshing access token and trying again [2/2/2024, 9:43:52 PM] [Wyze] Error, logging in and trying again [2/2/2024, 9:43:52 PM] [Wyze] Request failed: AxiosError: Request failed with status code 403 [2/2/2024, 9:43:52 PM] [Wyze] Response PerformRequest ([object Object]): "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=\"1px\">\nRequest blocked.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: LnUCij9NwRnKZltkxefCv8a8tqOpjw7Pqa9YRsMbFjttmSNSBXGlGw==\n
\n
\n
\n" [2/2/2024, 9:43:52 PM] [Wyze] Error getting devices: AxiosError: Request failed with status code 403 [2/2/2024, 9:44:53 PM] [Wyze] Error: access token is error at WyzeAPI._performRequest (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:132:15) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WyzeAPI.request (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:80:14) at WyzeAPI.getObjectList (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:234:20) at WyzeSmartHome.refreshDevices (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:101:26) at WyzeSmartHome.runLoop (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:90:9) [2/2/2024, 9:44:53 PM] [Wyze] Error, refreshing access token and trying again [2/2/2024, 9:44:53 PM] [Wyze] Error, logging in and trying again [2/2/2024, 9:44:53 PM] [Wyze] Request failed: AxiosError: Request failed with status code 403 [2/2/2024, 9:44:53 PM] [Wyze] Response PerformRequest ([object Object]): "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=\"1px\">\nRequest blocked.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: EPJXadU8CaBKKRPmY6nA7Foafc9cf8rxv1jaY-rLxMxHkCHzXfTA==\n
\n
\n
\n" [2/2/2024, 9:44:53 PM] [Wyze] Error getting devices: AxiosError: Request failed with status code 403 [2/2/2024, 9:44:58 PM] [homebridge-wyze-smart-home] This plugin generated a warning from the characteristic 'On': characteristic value expected boolean and received undefined. See https://homebridge.io/w/JtMGR for more info. [2/2/2024, 9:44:58 PM] [homebridge-wyze-smart-home] This plugin generated a warning from the characteristic 'On': characteristic value expected boolean and received undefined. See https://homebridge.io/w/JtMGR for more info. [2/2/2024, 9:45:50 PM] [homebridge-wyze-smart-home] This plugin generated a warning from the characteristic 'On': characteristic value expected boolean and received undefined. See https://homebridge.io/w/JtMGR for more info. [2/2/2024, 9:45:50 PM] [homebridge-wyze-smart-home] This plugin generated a warning from the characteristic 'On': characteristic value expected boolean and received undefined. See https://homebridge.io/w/JtMGR for more info. [2/2/2024, 9:45:53 PM] [Wyze] Error: access token is error at WyzeAPI._performRequest (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:132:15) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WyzeAPI.request (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:80:14) at WyzeAPI.getObjectList (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:234:20) at WyzeSmartHome.refreshDevices (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:101:26) at WyzeSmartHome.runLoop (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:90:9) [2/2/2024, 9:45:53 PM] [Wyze] Error, refreshing access token and trying again [2/2/2024, 9:45:53 PM] [Wyze] Error, logging in and trying again [2/2/2024, 9:45:53 PM] [Wyze] Request failed: AxiosError: Request failed with status code 403 [2/2/2024, 9:45:53 PM] [Wyze] Response PerformRequest ([object Object]): "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=\"1px\">\nRequest blocked.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: 7D6kzpvIUayDcXOHbuZJWi1V9YQx070b68W2oY6cCFJl5Z9lODZ6PQ==\n
\n
\n
\n" [2/2/2024, 9:45:53 PM] [Wyze] Error getting devices: AxiosError: Request failed with status code 403 [2/2/2024, 9:46:54 PM] [Wyze] Error: access token is error at WyzeAPI._performRequest (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:132:15) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WyzeAPI.request (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:80:14) at WyzeAPI.getObjectList (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:234:20) at WyzeSmartHome.refreshDevices (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:101:26) at WyzeSmartHome.runLoop (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:90:9) [2/2/2024, 9:46:54 PM] [Wyze] Error, refreshing access token and trying again [2/2/2024, 9:46:54 PM] [Wyze] Error, logging in and trying again [2/2/2024, 9:46:54 PM] [Wyze] Request failed: AxiosError: Request failed with status code 403 [2/2/2024, 9:46:54 PM] [Wyze] Response PerformRequest ([object Object]): "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=\"1px\">\nRequest blocked.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: NtZxLz-gEa_JSEu-ydzF1V2oakWZJQ1HOLXxLL4R6KgjRz2caJd-hQ==\n
\n
\n
\n" [2/2/2024, 9:46:54 PM] [Wyze] Error getting devices: AxiosError: Request failed with status code 403 [2/2/2024, 9:47:54 PM] [Wyze] Error: access token is error at WyzeAPI._performRequest (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:132:15) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WyzeAPI.request (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:80:14) at WyzeAPI.getObjectList (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:234:20) at WyzeSmartHome.refreshDevices (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:101:26) at WyzeSmartHome.runLoop (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:90:9) [2/2/2024, 9:47:54 PM] [Wyze] Error, refreshing access token and trying again [2/2/2024, 9:47:55 PM] [Wyze] Error, logging in and trying again [2/2/2024, 9:47:55 PM] [Wyze] Request failed: AxiosError: Request failed with status code 403 [2/2/2024, 9:47:55 PM] [Wyze] Response PerformRequest ([object Object]): "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=\"1px\">\nRequest blocked.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: h6SNFvBQJG4VMhMr5j8vG6z6N_9_U0tUnFGA1CpZVqIDPK8dBHyb9g==\n
\n
\n
\n" [2/2/2024, 9:47:55 PM] [Wyze] Error getting devices: AxiosError: Request failed with status code 403 [2/2/2024, 9:48:55 PM] [Wyze] Error: access token is error at WyzeAPI._performRequest (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:132:15) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WyzeAPI.request (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:80:14) at WyzeAPI.getObjectList (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:234:20) at WyzeSmartHome.refreshDevices (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:101:26) at WyzeSmartHome.runLoop (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:90:9) [2/2/2024, 9:48:55 PM] [Wyze] Error, refreshing access token and trying again [2/2/2024, 9:48:55 PM] [Wyze] Error, logging in and trying again [2/2/2024, 9:48:55 PM] [Wyze] Request failed: AxiosError: Request failed with status code 403 [2/2/2024, 9:48:55 PM] [Wyze] Response PerformRequest ([object Object]): "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=\"1px\">\nRequest blocked.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: k9LVsKhvmChUqDt1aHarbuCs4bem6AigDLsZLorFQ-LPk1UecbzdlQ==\n
\n
\n
\n" [2/2/2024, 9:48:55 PM] [Wyze] Error getting devices: AxiosError: Request failed with status code 403 [2/2/2024, 9:49:56 PM] [Wyze] Error: access token is error at WyzeAPI._performRequest (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:132:15) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WyzeAPI.request (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:80:14) at WyzeAPI.getObjectList (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:234:20) at WyzeSmartHome.refreshDevices (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:101:26) at WyzeSmartHome.runLoop (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:90:9) [2/2/2024, 9:49:56 PM] [Wyze] Error, refreshing access token and trying again [2/2/2024, 9:49:56 PM] [Wyze] Error, logging in and trying again [2/2/2024, 9:49:56 PM] [Wyze] Request failed: AxiosError: Request failed with status code 403 [2/2/2024, 9:49:56 PM] [Wyze] Response PerformRequest ([object Object]): "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=\"1px\">\nRequest blocked.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: d56KOwbiIq0n49kh4wy7HFm6FsYwUd1U3p3woeDYCIVRXUvHW8w5qg==\n
\n
\n
\n" [2/2/2024, 9:49:56 PM] [Wyze] Error getting devices: AxiosError: Request failed with status code 403 [2/2/2024, 9:50:56 PM] [Wyze] Error: access token is error at WyzeAPI._performRequest (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:132:15) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WyzeAPI.request (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:80:14) at WyzeAPI.getObjectList (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:234:20) at WyzeSmartHome.refreshDevices (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:101:26) at WyzeSmartHome.runLoop (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:90:9) [2/2/2024, 9:50:56 PM] [Wyze] Error, refreshing access token and trying again [2/2/2024, 9:50:56 PM] [Wyze] Error, logging in and trying again [2/2/2024, 9:50:56 PM] [Wyze] Request failed: AxiosError: Request failed with status code 403 [2/2/2024, 9:50:56 PM] [Wyze] Response PerformRequest ([object Object]): "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=\"1px\">\nRequest blocked.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: Az3j6JVoR38ipYPYhmoKCyiTKYWSzI1wEOjK0EuuxhGSaIyPO-bj6A==\n
\n
\n
\n" [2/2/2024, 9:50:56 PM] [Wyze] Error getting devices: AxiosError: Request failed with status code 403 [2/2/2024, 9:51:57 PM] [Wyze] Error: access token is error at WyzeAPI._performRequest (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:132:15) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WyzeAPI.request (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:80:14) at WyzeAPI.getObjectList (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:234:20) at WyzeSmartHome.refreshDevices (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:101:26) at WyzeSmartHome.runLoop (/volume1/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:90:9) [2/2/2024, 9:51:57 PM] [Wyze] Error, refreshing access token and trying again [2/2/2024, 9:51:57 PM] [Wyze] Error, logging in and trying again [2/2/2024, 9:51:57 PM] [Wyze] Request failed: AxiosError: Request failed with status code 403 [2/2/2024, 9:51:57 PM] [Wyze] Response PerformRequest ([object Object]): "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=\"1px\">\nRequest blocked.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: GzHMnzKIWXrZHTWD2ZCHWGxqZpZhIY7i_QhWAUhRTodMULn582ksDw==\n
\n
\n
\n" [2/2/2024, 9:51:57 PM] [Wyze] Error getting devices: AxiosError: Request failed with status code 403

Show the Homebridge logs here, remove any sensitive information.

Plugin Config:

Show your Homebridge config.json here, remove any sensitive information.
"name": "Wyze",
"username": "",
"password": "",
"keyId": "",
"apiKey": " ",
"refreshInterval": 60000,
"hms": false,
"showAdvancedOptions": false,
"apiLogEnabled": false,
"logLevel": "none",
"lowBatteryPercentage": 30,
"excludeMacAddress": false,
"excludedeviceType": false,
"_bridge": {
    "username": "",
    "port": 33901
},
"platform": "WyzeSmartHome"

}

Screenshots:

Environment:

OS Synology DSM

Hostname wds220 User homebridge Node.js Version v20.9.0

github-actions[bot] commented 5 months ago

Message that will be displayed on users' first issue

AwesomeTaylor commented 5 months ago

Hello - just to add that I'm having the same issue on my end also with 2 Wyze smart plugs.

Farmer APIKey and KEYID
[2/2/2024, 11:05:25 PM] [Wyze] Request failed: Error: Request failed with status code 403
[2/2/2024, 11:05:25 PM] [Wyze] Response PerformRequest (Forbidden): "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<HTML><HEAD><META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\n<TITLE>ERROR: The request could not be satisfied</TITLE>\n</HEAD><BODY>\n<H1>403 ERROR</H1>\n<H2>The request could not be satisfied.</H2>\n<HR noshade size=\"1px\">\nRequest blocked.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n<PRE>\nGenerated by cloudfront (CloudFront)\nRequest ID: ELV8ToUQ_vZN9KNZeURyuyuqX6eKxLhIOU4qtE8FHgW9IpVhcYJC8Q==\n</PRE>\n<ADDRESS>\n</ADDRESS>\n</BODY></HTML>"
holocronology commented 5 months ago

Same.

shsussman commented 5 months ago

Yep same exact thing. I thought maybe Wyze security had banned my IP but nope.

2/3/2024, 1:38:56 PM] [Wyze] Error: SUCCESS at WyzeAPI._performRequest (/var/lib/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:132:15) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WyzeAPI.request (/var/lib/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:80:14) at WyzeAPI.getObjectList (/var/lib/homebridge/node_modules/homebridge-wyze-smart-home/src/wyze-api/src/index.js:234:20) at WyzeSmartHome.refreshDevices (/var/lib/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:101:26) at WyzeSmartHome.runLoop (/var/lib/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:90:9) [2/3/2024, 1:38:56 PM] [Wyze] Error, refreshing access token and trying again [2/3/2024, 1:38:57 PM] [Wyze] Error, logging in and trying again [2/3/2024, 1:38:57 PM] [Wyze] Request failed: AxiosError: Request failed with status code 403 [2/3/2024, 1:38:57 PM] [Wyze] Response PerformRequest ([object Object]): "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\nERROR: The request could not be satisfied\n\n

403 ERROR

\n

The request could not be satisfied.

\n<HR noshade size=\"1px\">\nRequest blocked.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n
\nGenerated by cloudfront (CloudFront)\nRequest ID: g_yKI5MSP6feNGQvs285McKnaxzS4bGe2tzuo6e6uwNpSd_HsCEG5g==\n
\n
\n
\n" [2/3/2024, 1:38:57 PM] [Wyze] Error getting devices: AxiosError: Request failed with status code 403

ejoliet commented 4 months ago

Same problem here - hope is not same NEST story we had with HASS where they shutdown cloud third party access. Watching this thread. 

[2/3/2024, 12:53:56 PM] [Wyze] Error, logging in and trying again
Farmer APIKey and KEYID
[2/3/2024, 12:53:56 PM] [Wyze] Request failed: Error: Request failed with status code 403
[2/3/2024, 12:53:56 PM] [Wyze] Response PerformRequest (Forbidden): "<!DOCTYPE HTML PUBLIC \"-//W3C//DTD HTML 4.01 Transitional//EN\" \"http://www.w3.org/TR/html4/loose.dtd\">\n<HTML><HEAD><META HTTP-EQUIV=\"Content-Type\" CONTENT=\"text/html; charset=iso-8859-1\">\n<TITLE>ERROR: The request could not be satisfied</TITLE>\n</HEAD><BODY>\n<H1>403 ERROR</H1>\n<H2>The request could not be satisfied.</H2>\n<HR noshade size=\"1px\">\nRequest blocked.\nWe can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.\n<BR clear=\"all\">\nIf you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.\n<BR clear=\"all\">\n<HR noshade size=\"1px\">\n<PRE>\nGenerated by cloudfront (CloudFront)\nRequest ID: xxx\n</PRE>\n<ADDRESS>\n</ADDRESS>\n</BODY>

my config.json has the 'mfaCode' key/value pair:


    "name": "Wyze",
    "username": "xxx",
    "password": "xxx",
    "keyId": "<...>",
    "apiKey": "<..>",
    "refreshInterval": 180000,
    "hms": false,
    "showAdvancedOptions": true,
    "apiLogEnabled": false,
    "logLevel": "info",
    "lowBatteryPercentage": 30,
    "excludeMacAddress": false,
    "excludedeviceType": false,
    "_bridge": {
        "username": "<...>",
        "port": NNNN
    },
    "mfaCode": "nnnnnn",
    "platform": "WyzeSmartHome"
}```
shsussman commented 4 months ago

Check here --> https://github.com/jfarmer08/homebridge-wyze-smart-home/issues/208

The temp fix that requires you to alter line 131 in index.js... that works. At least until the plugin gets a proper update.

ejoliet commented 4 months ago

Check here --> #208

The temp fix that requires you to alter line 131 in index.js... that works. At least until the plugin gets a proper update.

Thanks!!! Ok, i've updated line 131 mentioned. I also had to use delete /var/lib/homebridge/persist/wize-.. files, add new mfaCode, restart bridge. Seems to get back my 'switch' in homekit now and now error. Camera UI next with wyze-bridge in HASS. Different problem but probably similar fix :-( Thanks.

Andy589 commented 4 months ago

Check here --> #208

The temp fix that requires you to alter line 131 in index.js... that works. At least until the plugin gets a proper update.

This worked, thank you. I'm going to close this so the other thread can hopefully take over and a more permanent solution can be found later. :)