search

jfarmer08 / homebridge-wyze-smart-home

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

Error getting devices: Error: ENOENT: no such file or directory #201

Open JGRR48 opened 6 months ago

JGRR48 commented 6 months ago

Not connecting.

Error getting devices: Error: ENOENT: no such file or directory, open '/var/lib/hoobs/hoobs/persist/wyze-d1b53a32-18ea-5e98-a534-7082d59c47c0.json'

Plugin Config:

"platform": "WyzeSmartHome", "name": "Wyze", "refreshInterval": 60000, "username": "USER, "password": "PWRD", "keyId": "ID", "apiKey": "KEY, "mfaCode": "YOUR_2FA_AUTHENTICATION_PIN", "filterDeviceTypeList": [ "OutdoorPlug", "Plug" ], "filterByMacAddressList": [ "MAC_ADDRESS_1", "MAC_ADDRESS_2" ]

Screenshots:

Environment:

github-actions[bot] commented 6 months ago

Message that will be displayed on users' first issue

carTloyal123 commented 4 months ago

@JGRR48 is this resolved with the latest update to the plugin?

JGRR48 commented 4 months ago

Nope - just updated and still getting: ENOENT: no such file or directory, open '/var/lib/hoobs/hoobs/persist/wyze-d1b53a32-18ea-5e98-a534-7082d59c47c0.json'

On Sat, Feb 17, 2024 at 9:43 AM carTloyal123 @.***> wrote:

@JGRR48 https://github.com/JGRR48 is this resolved with the latest update to the plugin?

— Reply to this email directly, view it on GitHub https://github.com/jfarmer08/homebridge-wyze-smart-home/issues/201#issuecomment-1950266655, or unsubscribe https://github.com/notifications/unsubscribe-auth/BEV6FSHL7HR5I7UGYFJJESDYUDT27AVCNFSM6AAAAABAVTGE5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJQGI3DMNRVGU . You are receiving this because you were mentioned.Message ID: @.***>

jfarmer08 commented 4 months ago

Are there any errors in the logs?

jfarmer08 commented 4 months ago

Can you try and add this to your config? "persistPath":"/var/lib/hoobs/hoobs"

xtcoops-yyc commented 3 months ago

I am getting the same error and have tried the above solution of adding "persistPath":"/var/lib/hoobs/hoobs" to the config. I also cleared the Bridge cache, HOOBS cache, completely removed the bridge and reinstalled, AND I disabled and re-enabled 2FA. Nothing has worked. @jfarmer08 any guidance?

jfarmer08 commented 3 months ago

2fa is not supported. You have to use apiKey with any of the latest releases.

Thanks Allen :)

On Mon, Mar 18, 2024 at 6:18 PM xtcoops-yyc @.***> wrote:

I am getting the same error and have tried the above solution of adding "persistPath":"/var/lib/hoobs/hoobs" to the config. I also cleared the Bridge cache, HOOBS cache, completely removed the bridge and reinstalled, AND I disabled and re-enabled 2FA. Nothing has worked. @jfarmer08 https://github.com/jfarmer08 any guidance?

— Reply to this email directly, view it on GitHub https://github.com/jfarmer08/homebridge-wyze-smart-home/issues/201#issuecomment-2005278381, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEKHFBYCWLYJ3QHPRZGGA7TYY5Y3TAVCNFSM6AAAAABAVTGE5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBVGI3TQMZYGE . You are receiving this because you were mentioned.Message ID: @.***>

xtcoops-yyc commented 3 months ago

2fa is not supported. You have to use apiKey with any of the latest releases. Thanks Allen :) … On Mon, Mar 18, 2024 at 6:18 PM xtcoops-yyc @.> wrote: I am getting the same error and have tried the above solution of adding "persistPath":"/var/lib/hoobs/hoobs" to the config. I also cleared the Bridge cache, HOOBS cache, completely removed the bridge and reinstalled, AND I disabled and re-enabled 2FA. Nothing has worked. @jfarmer08 https://github.com/jfarmer08 any guidance? — Reply to this email directly, view it on GitHub <#201 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEKHFBYCWLYJ3QHPRZGGA7TYY5Y3TAVCNFSM6AAAAABAVTGE5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBVGI3TQMZYGE . You are receiving this because you were mentioned.Message ID: @.>

I am using the apiKey and ID already, I will try removing the 2fa from config. You may want to update your README if that is the case as it says nothing about API Keys or 2FA being taken off.

Update: removing 2fa/mfa from the config results in the same error.