Closed pergolafabio closed 1 year ago
ok, tested again, and indeed add-on crashes again , never noticed it before
I seem to experience this also after a few hours.
It starts with 'CLOCK' Timeout and eventually the add-on stops working till restarted.
I'm on version 0.4.2
As a workaround - I'm trying to figure out how to get a heart-beart from the add-on. Perhaps with a mqtt topic that publishes "uptime" or such every minute or so. Then an automation on HA can fire if there was no update in x amount of minutes and then restart the addon.
Good idea for now, keep us posted
I think I got a workable workaround.
I created a MQTT Binary Sensor, which monitors 'riscopanel/alarm/status'. I use the force_update option in the config. Then with a template trigger looking at last_changed attribute I fire service: hassio.addon_restart if it exceeds a predetermined value e.g. 30 seconds
I changed the script to grab the add-on container name with a template, that should the container name change with an update it will continue to work.
So far it has worked very well. I have not had a unresponsive alarm from HA since implementing. Fingers crossed....
Describe the bug
Hi @vanackej , i had the error before also in the past, sure if its the same now, but i use the proxy method, when i take out the UTP cable or my network is down for a little white, it never reconnects again, i see a continues loop like below
I attached the logs, copy/pasted from where i took out the network cable
Seems also at the bottom of the log, it crashed the add-on, i think this is the first time i see this The logs are starting when i took out the cable
thnx for looking into it!
Configuration
Logs