-
-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unknown Exception popping up every 5 seconds #124
Comments
Same here |
@Rustymage @janusn do both of you use the last released version, or the PR from @nicoinch with the new cookie method? |
@Rustymage on the top I see the commit-id from #121. You are running a test version (which you installed by hand 😉). |
Me, no never! Urm - clearly needs a little tweak if it's a test version ;) Anything from me to help/support logwise? |
I use the latest version with google access token. I am not sure how to know the version installed but I have installed through custom repository with the following URL: |
Seeing the same I think This error originated from a custom integration. Logger: custom_components.nest_protect Unknown exception. Please create an issue on GitHub with your logfile. Updates paused for 5 minutes. |
Seeing the same issue reported by Rustymage and nivek1612 here. Log message appears every 30mins but Nest Protect functionality is mostly working so seems to be a transient error. |
The same happens here. Functionality of the units (3) seems ok. The iPhone Nest app reports everything's ok. |
+1 Verified thrown by this custom component installed from this repo.
|
Using Home Assistant 2023.3.3 and seeing the same. My HA reboots a few times a day because of this error: This error originated from a custom integration. Logger: custom_components.nest_protect Unknown exception. Please create an issue on GitHub with your logfile. Updates paused for 5 minutes. |
Same issue here. HA on latest version. Integration seems to work fine though... This error originated from a custom integration. Logger: custom_components.nest_protect Unknown exception. Please create an issue on GitHub with your logfile. Updates paused for 5 minutes. |
I've implemented a fix, please let me know if this works |
Could you tell me how do I get the updated version? |
Thanks for the tips. I have updated and HA has been upped this morning by watchtower. The unknown exception still pops up around every 1.5 hours. Please consult the attached log. |
Hello Janus, I've looked at your logfile, it almost feels like the credentials are not stored and can't be retrieved/used to call the google services. Kind regards. |
You are right. I didn't change the credentials after redownloaded the plugin. In fact, I don't know how to change the credentials. Could you enlighten me? Cheers. |
Thank you very much for your help.
|
Please update to latest beta (now v0.4.0b5) and create a new issue if you face issues. |
The problem
I have got an error popping up on the log every 5 seconds. The Nest Protect Devices and entities seem working fine though.
What version of this integration (ha-nest-protect) has the issue?
0.3.10
What version of Home Assistant Core has the issue?
core-2022.11.5
Device / Model
Nest Protect (Topaz-2.9)
Diagnostics information
config_entry-nest_protect-d9d72164fb1de9ad1884f574ae28ec3c.json.txt
Home Assistant log
Logs
```2022-12-01 05:28:37.479 ERROR (MainThread) [custom_components.nest_protect] Unknown exception. Please create an issue on GitHub with your logfile. Updates paused for 5 minutes. Traceback (most recent call last): File "/config/custom_components/nest_protect/__init__.py", line 173, in _async_subscribe_for_data await entry_data.client.authenticate(entry_data.client.auth.access_token) File "/config/custom_components/nest_protect/pynest/client.py", line 187, in authenticate nest_auth = NestAuthResponse(**result) File "", line 4, in __init__ TypeError: NestAuthClaims.__init__() missing 4 required positional arguments: 'subject', 'expirationTime', 'policyId', and 'structureConstraint' 2022-12-01 05:33:37.682 ERROR (MainThread) [custom_components.nest_protect] Unknown exception. Please create an issue on GitHub with your logfile. Updates paused for 5 minutes. Traceback (most recent call last): File "/config/custom_components/nest_protect/__init__.py", line 173, in _async_subscribe_for_data await entry_data.client.authenticate(entry_data.client.auth.access_token) File "/config/custom_components/nest_protect/pynest/client.py", line 187, in authenticate nest_auth = NestAuthResponse(**result) File "", line 4, in __init__ TypeError: NestAuthClaims.__init__() missing 4 required positional arguments: 'subject', 'expirationTime', 'policyId', and 'structureConstraint' 2022-12-01 05:38:37.819 ERROR (MainThread) [custom_components.nest_protect] Unknown exception. Please create an issue on GitHub with your logfile. Updates paused for 5 minutes. Traceback (most recent call last): File "/config/custom_components/nest_protect/__init__.py", line 173, in _async_subscribe_for_data await entry_data.client.authenticate(entry_data.client.auth.access_token) File "/config/custom_components/nest_protect/pynest/client.py", line 187, in authenticate nest_auth = NestAuthResponse(**result) File "", line 4, in __init__ TypeError: NestAuthClaims.__init__() missing 4 required positional arguments: 'subject', 'expirationTime', 'policyId', and 'structureConstraint' 2022-12-01 05:43:37.958 ERROR (MainThread) [custom_components.nest_protect] Unknown exception. Please create an issue on GitHub with your logfile. Updates paused for 5 minutes. Traceback (most recent call last): File "/config/custom_components/nest_protect/__init__.py", line 173, in _async_subscribe_for_data await entry_data.client.authenticate(entry_data.client.auth.access_token) File "/config/custom_components/nest_protect/pynest/client.py", line 187, in authenticate nest_auth = NestAuthResponse(**result) File "", line 4, in __init__ TypeError: NestAuthClaims.__init__() missing 4 required positional arguments: 'subject', 'expirationTime', 'policyId', and 'structureConstraint' ```Additional information
No response
The text was updated successfully, but these errors were encountered: