Actions accidentally triggered on Hub reboot

[ilkeraktuna]

@BorrisTheCat

So you question is actually about this. You must have a rule which lets say fires on a "ON" event and the driver or app is incorrectly calling that when the hub reboots and the IP connection is made.

So you need to look at the rule which is being called, look at the trigger and then look at the driver or app and see when that is being called.

I was asking a generic question but when I ask it that way, it is not understood correctly , so let me explain with a specific and real example:

I am using the following integration with my PI server and a UPS:

[RELEASE] Network UPS Tools (NUT) monitor and shutdown controller (upsmon)

This driver implements a UPS monitor and shutdown controller for use with Network UPS Tools (NUT). The driver works in conjunction with a remote NUT upsd server, and provides the equivalent of NUT's upsmon for the Hubitat. In other words, it monitors the ups and shuts the hub down when the ups battery is low. The driver is available via HPM, or for direct import from GitHub here. Configuration is as shown below. [Screenshot 2023-03-22 at 22.00.30] NUT server host: The hostname or IP addr…

This driver has several states for the UPS.
Online and "On Battery" are specific states.
But when the PI is rebooted, Hub can not reach the app on PI.
So the driver reports state as "unknown"

I have 2 rules on Rule Machine.
One is for when the UPS is activated (state != Online & state!=unknown)
The other rule is for when the UPS is deactivated (state==Online)

The second rule is activated when state comes from "unknown" to "Online"
But I don't want this case to be reported.

How can I check the previous state of the UPS in Rule machine when state has changed to Online ?