TUhl01 Posted January 12 Author Share Posted January 12 Believe so. The log shows polling. This error happens randomly. Link to comment
Goose66 Posted January 12 Share Posted January 12 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. Link to comment
TUhl01 Posted January 12 Author Share Posted January 12 Attached is the debug log and a clip of the error section for your review. debug.log Link to comment
TUhl01 Posted January 16 Author Share Posted January 16 Is this error going to be resolved. Have not heard anything since submitting the debug log. Link to comment
tlightne Posted January 17 Share Posted January 17 @TUhl01 Did you send the log to the developer?? That is the best way to make sure they get it... Link to comment
TUhl01 Posted January 17 Author Share Posted January 17 23 minutes ago, tlightne said: @TUhl01 Did you send the log to the developer?? That is the best way to make sure they get it... The information is included in this thread. Look above. Link to comment
tlightne Posted January 17 Share Posted January 17 @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. Link to comment
TUhl01 Posted January 17 Author Share Posted January 17 In the post, he was the person that asked for this. Link to comment
Solution Goose66 Posted January 17 Solution Share Posted January 17 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. Link to comment
TUhl01 Posted January 17 Author Share Posted January 17 12 hours ago, 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. Thanks - Topic Closed Link to comment
Recommended Posts