johnnyt Posted July 16 Share Posted July 16 (edited) I noticed that my ISY nodes for Airthings weren't getting updated today so I checked logs and found a boat load of these sequences: 2024-07-16 03:02:30.244 Thread-867 (handler_poll) udi_interface ERROR Controller:_query_all: Previous query still running 2024-07-16 03:02:30.244 Thread-867 (handler_poll) udi_interface INFO Controller:shortPoll: exit 2024-07-16 03:07:00.248 Thread-869 (handler_poll) udi_interface INFO Controller:shortPoll: enter 2024-07-16 03:07:00.248 Thread-869 (handler_poll) udi_interface INFO Controller:_query_all: enter 2024-07-16 03:07:00.248 Thread-869 (handler_poll) udi_interface ERROR Controller:_query_all: Previous query still running 2024-07-16 03:07:00.248 Thread-869 (handler_poll) udi_interface INFO Controller:shortPoll: exit 2024-07-16 03:11:30.249 Thread-870 (handler_poll) udi_interface INFO Controller:shortPoll: enter 2024-07-16 03:11:30.249 Thread-870 (handler_poll) udi_interface INFO Controller:_query_all: enter 2024-07-16 03:11:30.250 Thread-870 (handler_poll) udi_interface ERROR Controller:_query_all: Previous query still running 2024-07-16 03:11:30.250 Thread-870 (handler_poll) udi_interface INFO Controller:shortPoll: exit 2024-07-16 03:16:00.259 Thread-872 (handler_poll) udi_interface INFO Controller:shortPoll: enter 2024-07-16 03:16:00.259 Thread-872 (handler_poll) udi_interface INFO Controller:_query_all: enter While there appears to have been an update made around 2AM early this morning, the log before and after that update is just full of the above messages I did make some tweaks yesterday that included changing short poll time and doing a restart. This did result in reaching the API limit but only once, which I blamed on the restart causing some short shifting. Maybe, though, reaching the API limit (even only once) caused the problem? I've had API limit messages in the past but things always sorted themselves out assuming short poll is reasonable (I always set it above 30 X number of devices). A restart of the plug-in did fix the problem - at least for now. Airthings-C_7-16-2024_113452_AM.zip Edited July 16 by johnnyt added log file Quote Link to comment
johnnyt Posted July 19 Author Share Posted July 19 (edited) @Jimbo.Automates, it happened again overnight only this time there was no sign of API limit or any other problem. At least not to me. I had to restart the plug-in to get data updates to resume. After last time I changed log level to Debug and will send you today's log via PM. Edited July 19 by johnnyt Quote Link to comment
Jimbo.Automates Posted July 19 Share Posted July 19 Thanks, I've been traveling. I'll try to look at it this weekend.Sent from my Pixel 8 Pro using Tapatalk Quote Link to comment
johnnyt Posted July 19 Author Share Posted July 19 (edited) No problem. I noticed the messages started before midnight so I went to grab yesterday's log file from the archive and PM'ed that file too. There appears to have been some successful updates before 2AM but then things got stuck repeating the error. Thanks. Edited July 19 by johnnyt 1 Quote Link to comment
johnnyt Posted July 29 Author Share Posted July 29 It happened again the night after I installed 1.2.2 so I went in and turned on debug log level (because the reinstall returned log level to warning only) but it hasn't happened since. Maybe I needed to restart PG3, which I think I did later the next day. Anyway, all is good now. Thanks 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.