Diggerules

@Goose66 eISY PG3x ver 3.3.21 IoX 5.9.1 Schlage 3.2.4 I went though that last post they had and it seemed their fix was due to a PG3X problem, I tested that script and it returned saying my system was good. I can start a new thread if you prefer but the problems started as soon as I upgraded to 5.9.1. Schlage had an upgrade to 3.2.4 available prior to the upgrade, but it upgraded on it's own after the system update. But with the above it looks like it having trouble with the Schlage modules within the plugin.

Hi @skunkiechris, I am curious if you figured anything out. I had 4 older (2018ish) bulbs that were working great with the devlist but one of them finally gave up and died recently. I just picked up a new bulb and I am seeing the same error that you list above. The other 3 older bulbs are still working properly and reporting status.

Hi@Goose66, I am seeing the same symptoms as @tjmeiner reported. After upgrading to 5.9.1 the node stays in a disconnected status. I attempted to delete and reinstall in a different slot with no change. However according to the debug log it looks like it can't find the module pyschlage. Any suggestions on what to try? 2025-08-12 23:04:56.494 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2025-08-12 23:04:56.495 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026262_6/main.py", line 9, in <module> 2025-08-12 23:04:56.495 MainThread udi_interface ERROR udi_interface:write: from schlagens import SchlageNS 2025-08-12 23:04:56.495 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026262_6/schlagens/__init__.py", line 5, in <module> 2025-08-12 23:04:56.495 MainThread udi_interface ERROR udi_interface:write: from .schlagens import SchlageNS, NS_VERSION_STRING, NS_NAME 2025-08-12 23:04:56.495 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026262_6/schlagens/schlagens.py", line 14, in <module> 2025-08-12 23:04:56.496 MainThread udi_interface ERROR udi_interface:write: from .nodes import Lock 2025-08-12 23:04:56.496 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026262_6/schlagens/nodes.py", line 11, in <module> 2025-08-12 23:04:56.496 MainThread udi_interface ERROR udi_interface:write: import pyschlage 2025-08-12 23:04:56.496 MainThread udi_interface ERROR udi_interface:write: ModuleNotFoundError 2025-08-12 23:04:56.496 MainThread udi_interface ERROR udi_interface:write: : 2025-08-12 23:04:56.496 MainThread udi_interface ERROR udi_interface:write: No module named 'pyschlage'

@firstone I just updated to 3.2.18. Same results when clicking the Authenticate button. It takes me to the account selection screen. When I select my gmail account I get the "This app is blocked" "This app tried to access sensitive info in your Google Account. To keep your account safe, Google blocked this access."

I am on PG3x Version 3.2.17. I had seen the note in the config settings saying "Google authenitcation is not working right now so as a temporary workaround, token needs to be generated using a desktop." So I thought the button didn't work anymore and I had to generate it. Thanks for taking at look at it @firstone

I am struggling with configuring the authentication properly since the Authentication button doesn't work. I have enabled the google calendar API on my account. Tried creating both an API key as well as creating a OAuth 2.0 Client IDs with the settings that home assistant requires. I was unable to get either to work and still get the "Not authenticated or invalid authentication" banner. I am unsure of what to set as the key name in the custom parameters. Potentially this is all I am missing or messing up. All the posts I can find talk about the calendar settings, but brush over the authentication settings. Hopefully I am just missing something silly, but any help is appreciated. Thanks!