Odianosen25
commented
1 year ago Hello @herrmannj,
As for the MQTT plugin, it can behave you way you said via a configuration “force_start” and you can see it here https://appdaemon.readthedocs.io/en/latest/CONFIGURE.html#mqtt. It actually says it was added for what you said.
On the other hand, we unfortunately for now don’t support it in HASS, but can be fixed. Will look into it thanks
Background:
i run some raspberry pi "remote". There runs AD (docker) and the raspi are connected via HASS AD plugin to a central HASS instance (other machine within the network). This way, the remote systems provide their own intelligence to control (heating, ventilation, ...) which is maintained even if the network or the central HASS instance is not available. For this case, fallback routines are programmed and the systems continue to run and control in a limited but functional mode
Problem:
In the event of a power failure, the remote systems each have a UPS and continue to run for some time. If the power fails for a longer period of time, the remote systems shut down and start automatically when the power is restored. In this state, AD waits (according to the documentation) for the connection to the central HASS instance before starting the apps. In case the central instance cannot be reached (because secondary errors may occur, network down, HASS does not start), the fallback routines cannot become active because the apps will not start.
Is the described (start) behavior correct?
Is there a way to "force" the start of the apps - even if neither HASS nor the MQTT broker can be reached by AD?