So I’m seeing this, I was originally thinking it was because I was running it on a rasp pi but maybe it’s something else so I wanted more exposure.
events.log
2017-04-26 09:02:16.678 [ItemStateChangedEvent ] - Goodbye changed from NULL to ON
2017-04-26 09:02:16.743 [ItemCommandEvent ] - Item 'Goodbye' received command ON
2017-04-26 09:02:40.351 [ItemCommandEvent ] - Item 'BathroomLight_Switch' received command OFF
2017-04-26 09:02:40.497 [ItemStateChangedEvent ] - BathroomLight_Switch changed from ON to OFF
2017-04-26 09:02:40.514 [ItemCommandEvent ] - Item 'BedroomLight_Dimmer' received command OFF
And if I look in the logs that logInfo is printed that same time the actions start to happen so it’s as if the rule is queued up or waiting for a while before executing. How are rules executed, could it be another rule that’s blocking this one? Is there a debug I can turn on to see more info about this?
openhab.log
2017-04-26 09:02:16.737 [INFO ] [impl.connections.SubscriptionManager] - Publishing changes for 1871676262
2017-04-26 09:02:40.248 [INFO ] [.eclipse.smarthome.model.script.FILE] - Leaving
2017-04-26 09:02:40.603 [INFO ] [impl.connections.SubscriptionManager] - Publishing changes for 170787487
2017-04-26 09:02:40.789 [INFO ] [impl.connections.SubscriptionManager] - Publishing changes for 841937049
The simple rule
rule "Goodbye"
when
Item Goodbye received command
then
logInfo("FILE", "Leaving")
sendCommand(BathroomLight_Switch, OFF)
sendCommand(BedroomLight_Dimmer, OFF)
sendCommand(Cabinet_Lights, OFF)
sendCommand(DiningLight_Dimmer, OFF)
sendCommand(EntryLight_Switch, OFF)
sendCommand(HallwayLight_Switch, OFF)
sendCommand(IslandLights_Dimmer, OFF)
sendCommand(FireplaceLeftLight_Color, 0)
sendCommand(FireplaceRightLight_Color, 0)
sendCommand(LivingRoomLight_Color, 0)
sendCommand(MudroomLight_Switch, ON)
end