Callback that terminates with no Reason

Third party integrations AppDaemon
1

Hi all,
I have an app that has a callback that runs for a long time (about an hour, used to fullfill some tanks).
Until last summer It works correctly. Now I’m testing It for next summer but the app terminates after about 10minutes. Was introduced a timeout or something?
There’s a way to set a loglevel that shows who is triggering the terminate signal?appdaemon

Thanks

2

Hello @Fraschi, although you may have been able to make this work in the past, a callback should never run for more than a few seconds. You end up with thread starvation and there is no guarantees how your AppDaemon instance is going to behave when you have a callback executing for that long. I don’t know if there were any changes that limit a callback to 10-minutes but there is no reason that a callback should run for that long. Instead of trying to fix the issue with the callback being cancelled, I would focus on refactoring the app so that the callback runs very quickly.

3

It was due to disconnection from HA, didn’t know from which version but AppDaemon fails connecting in https both via IP and via domain name. Solved by using http in connunication between HA and appdaemon (same machine).