hart2hart Posted November 26, 2023 Share Posted November 26, 2023 Been getting getting error messages on node server for at least a week. Thought it might resolve but it has not. Quote Link to comment
hart2hart Posted November 27, 2023 Author Share Posted November 27, 2023 @Goose66 The error is: There was an error connecting to the Schlage service. Please check the log files and correct the issue before restarting the nodeserver. Quote Link to comment
Goose66 Posted November 27, 2023 Share Posted November 27, 2023 My Schlage node server is currently working. Just restarted to verify. Please send a log package. Quote Link to comment
hart2hart Posted November 27, 2023 Author Share Posted November 27, 2023 4 hours ago, Goose66 said: My Schlage node server is currently working. Just restarted to verify. Please send a log package. Log sent. Thanks Quote Link to comment
Solution Goose66 Posted November 28, 2023 Solution Share Posted November 28, 2023 I see a "failed due to bad credentials" in your log four or five times over the course of the day. But it always succeeds a minute later on the next longpoll. I actually got one of these today myself. Based on the timing (the few in your log are exactly one hour apart) it appears to me that the oAuth token is expiring before automatically refreshed, so the pyschlage library just refreshes it on the next call. I will put it in the To-do for the node server to remove the warning message from the PG3 dashboard, but since the node server remains functional (it's just a warning), you can just ignore these errors for now. 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.