UPDATE: Not deprecated. See below. Cache purge fixed the problem.
I received the 3.1.0 update of
openHAB last Monday (Raspbian) and I noticed the
System started rule trigger has been deprecated. I have seen multiple threads discussing this. I thought I would start a new thread to hopefully bring back this key (for me) rule trigger.
I live in a hot, dry, windy area susceptible to wildfires. My power utility will cut my power multiple times per year based on their own reasoning, and we’re approaching the time of year where it could be cut multiple times per month. I have UPSs in place and I initiate bash scripts that issue graceful shutdowns to the boxes prior to the UPS battery depleting. As part of the shutdown, I have
OFF smart switches that are connected to the boxes and other equipment. The thinking here is that I’d much rather cause damage to a smart switch in the case of a power restoration surge, as opposed to damaging the computers. You can tell me that UPSs are designed to protect the equipment from a surge but I can tell you that is simply not the case in lower end UPSs.
openHAB on a RPi and it is not connected to a smart switch. Again, more cost effective to replace a RPi than my other equipment.
Now power is restored and the RPi boots on its own and begins to restore my internal environment. That is unfortunately no longer the case because of the
System started deprecation. I need remote access to my home internal network as I travel for work. Hopefully you can see how problematic this is for this scenario. I’m assuming the thought process was to go with Persistence on startup but that is counter intuitive for me.
Yes, I can schedule health checks in the rules but there are also times when I want a device to be off and there’s no programmatic way to convey that easily in the rules.
Hopefully I’ve made a strong case to bring this feature back otherwise I have to move away from