TUhl01 Posted January 12, 2024 Author Posted January 12, 2024 Believe so. The log shows polling. This error happens randomly.
Goose66 Posted January 12, 2024 Posted January 12, 2024 Appears to be periodic REST call failure that I’m not handling gracefully. Since it’s an authorization error it’s also posting the notification that’s never getting cleared. if you can turn on debug logging and capture more info, I can release a new version that ignores the periodic error.
TUhl01 Posted January 12, 2024 Author Posted January 12, 2024 Attached is the debug log and a clip of the error section for your review. debug.logFetching info...
TUhl01 Posted January 16, 2024 Author Posted January 16, 2024 Is this error going to be resolved. Have not heard anything since submitting the debug log.
tlightne Posted January 17, 2024 Posted January 17, 2024 @TUhl01 Did you send the log to the developer?? That is the best way to make sure they get it...
TUhl01 Posted January 17, 2024 Author Posted January 17, 2024 On 1/17/2024 at 1:39 AM, tlightne said: @TUhl01 Did you send the log to the developer?? That is the best way to make sure they get it... Expand The information is included in this thread. Look above.
tlightne Posted January 17, 2024 Posted January 17, 2024 @TUhl01 I see it but that does not mean the developer is aware it is there. Not all developers babysit this forum. Just trying to help you out.
TUhl01 Posted January 17, 2024 Author Posted January 17, 2024 In the post, he was the person that asked for this.
Solution Goose66 Posted January 17, 2024 Solution Posted January 17, 2024 I've had put in a note to fix it in next release. But as I mentioned, it is a non-fatal connection error very infrequently returned from the Schlage API the plugin uses, and the data is updated on the next poll. But it adds the notification when the error occurs. So even though it's logged as a warning and the plugin recovers on the next poll, the notification just hangs out until you clear it. Shouldn't cause any issues in the operation of the plugin.
TUhl01 Posted January 17, 2024 Author Posted January 17, 2024 On 1/17/2024 at 2:50 AM, Goose66 said: I've had put in a note to fix it in next release. But as I mentioned, it is a non-fatal connection error very infrequently returned from the Schlage API the plugin uses, and the data is updated on the next poll. But it adds the notification when the error occurs. So even though it's logged as a warning and the plugin recovers on the next poll, the notification just hangs out until you clear it. Shouldn't cause any issues in the operation of the plugin. Expand Thanks - Topic Closed
Recommended Posts