preventing "thread seems to have ended unexpectedly"

[willemd]

I have a plugin that runs data collection every minute. Heartbeat is set to 30 seconds, since that is the max according to the wiki, and therefore every other heartbeat is skipped before data collection is starting again.

Sometimes the data collection, due to timeouts, runs longer than a minute and then I get the message "thread seems to have ended unexpectedly", I guess because a new call from heartbeat is started before the old one has finished.

The plugin continues normally after this error, so it is more like a warning, but anyway: How to avoid? Can I test whether the previous call has finished? Or should I just ignore?

[jvdz]

The only way to avoid this is to have the heartbeat end timely and run the data retrieval part asynchronously.
There are a couple of plugins that use this method, and details can be found here: https://github.com/domoticz/domoticz/bl ... hreaded.py

The other option is to limit the time that website api call is allowed to take, when this long process only happens occasionally.

[willemd]

Thanks,

I now "solved" it by setting a "stillbusy" flag on the start and resetting it when finished. If the next heartbeat starts it checks that flag and skips if true, with a maximum number of skips set.