Closed Geczy closed 4 months ago
after updating i now get this error
[2/13/2024, 4:42:18 PM] [WyzeSmartHome] Error: Potentially recoverable error during request
at WyzeAPI._performRequest (/homebridge/node_modules/homebridge-wyze-smart-home/node_modules/wyze-api/src/index.js:150:13)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at WyzeAPI.request (/homebridge/node_modules/homebridge-wyze-smart-home/node_modules/wyze-api/src/index.js:86:14)
at WyzeAPI.getObjectList (/homebridge/node_modules/homebridge-wyze-smart-home/node_modules/wyze-api/src/index.js:304:20)
at WyzeSmartHome.refreshDevices (/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:102:26)
at WyzeSmartHome.runLoop (/homebridge/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:91:9)
[2/13/2024, 4:42:18 PM] [WyzeSmartHome] Error, refreshing access token and trying again
Did you change your password and apikeys at the same time
no i didn't change a single thing lol, it just happened randomly
I'm having this problem as well. Just set up homebridge, and the Wyze products worked for a day....
as soon as I updated from v0.5.42 to v0.5.44, I receive the similar messages ... result: fails API login
4/02/2024, 11:54:33] [Wyze] Initializing WyzeSmartHome platform... [14/02/2024, 11:54:36] [Wyze] Error: Potentially recoverable error during request at WyzeAPI._performRequest (/usr/local/lib/node_modules/homebridge-wyze-smart-home/node_modules/wyze-api/src/index.js:150:13) at processTicksAndRejections (node:internal/process/task_queues:95:5) at WyzeAPI.request (/usr/local/lib/node_modules/homebridge-wyze-smart-home/node_modules/wyze-api/src/index.js:86:14) at WyzeAPI.getObjectList (/usr/local/lib/node_modules/homebridge-wyze-smart-home/node_modules/wyze-api/src/index.js:304:20) at WyzeSmartHome.refreshDevices (/usr/local/lib/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:102:26) at WyzeSmartHome.runLoop (/usr/local/lib/node_modules/homebridge-wyze-smart-home/src/WyzeSmartHome.js:91:9) [14/02/2024, 11:54:36] [Wyze] Error, refreshing access token and trying again [14/02/2024, 11:54:46] [Wyze] Error, logging in and trying again [14/02/2024, 11:54:47] [Wyze] Request failed: AxiosError: Request failed with status code 400 ... rolled back to v0.5.42 but still get the error messages from that version ...
[14/02/2024, 12:18:26] [Wyze] Error getting devices: TypeError: devices is not iterable [14/02/2024, 12:19:27] [Wyze] Error getting devices: TypeError: devices is not iterable [14/02/2024, 12:20:27] [Wyze] Error getting devices: TypeError: devices is not iterable [14/02/2024, 12:21:28] [Wyze] Error getting devices: TypeError: devices is not iterable ...
I have now disabled the plug-in until all resolved.
I was getting the same "Potentially recoverable error". Found I was logged out at Wyze with too many retries. Even after disabling the plugin and waiting, I still wasn't able to get into the Wyze website with my authentication. After 15 minutes, when I tried to log in I was told that I failed Captch (even though I was never presented with one). I changed my password, and that got me back in. I updated the password in Homebridge and made sure the API ID and key were still active. They are. Got the error on next try, but now it seems to be working. I did set the retry timer in the configuration up to several minutes, to make lockout less likely. FIngers crossed.
@Geczy is this resolved in the latest versions?
Closing in favor of #216
UPDATE: 2024-0216 reset password, deleted and reset API ID/Key, upgraded to latest ver (v0.5.44) and it now works with no errors.
On Sat, Feb 17, 2024 at 11:29 AM carTloyal123 @.***> wrote:
Closing in favor of #216 https://github.com/jfarmer08/homebridge-wyze-smart-home/issues/216
— Reply to this email directly, view it on GitHub https://github.com/jfarmer08/homebridge-wyze-smart-home/issues/221#issuecomment-1950263189, or unsubscribe https://github.com/notifications/unsubscribe-auth/BDLJ5ZGQ7HSYYBY7R74LOMLYUDSG5AVCNFSM6AAAAABDHJPYHOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJQGI3DGMJYHE . You are receiving this because you commented.Message ID: @.***>
looks like a simple issue that needs a fix, not sure why it happened all of a sudden