Hi all,
I’m running Openhab 2.5M2 on an Ubuntu MiniITX machine with a fairly high count of connected devices. The setup was usually quite reliable with the 2.5M1, but creates a lot of headache since 2.5M2…
Rule which worked before do not trigger anymore, even if the contents are more than simple.
AN example of the last rule not firing:
Alexa changes the Item “Vacuum” to ON:
Switch Vacuum "Vacuum" ["Switchable"] { expire="1m,OFF" }
This can be observed in the logs:
2019-08-17 11:07:25.760 [ome.event.ItemCommandEvent] - Item ‘Vacuum’ received command ON
2019-08-17 11:07:25.774 [vent.ItemStateChangedEvent] - Vacuum changed from OFF to ON
The rule which listens for received commands of “Vacuum”, however, does not trigger, the logs do not show the logError-output:
import java.util.concurrent.locks.ReentrantLock
val ReentrantLock lock_echoVacuum = new ReentrantLock()
rule "Echo Vacuum"
when
Item Vacuum received command
then
logError("Vacuum", "Rule triggered")
lock_echoVacuum.lock()
try {
if (receivedCommand == ON) {
xiaomi_Robot_actionControl.sendCommand("vacuum")
} else if (receivedCommand == OFF && xiaomi_Robot_actionControl.state != "pause") {
xiaomi_Robot_actionControl.sendCommand("pause")
} else if (receivedCommand == OFF && xiaomi_Robot_actionControl.state == "pause") {
xiaomi_Robot_actionCommand.sendCommand("dock")
}
} finally {
lock_echoVacuum.unlock()
}
end
This, however, is just an example. After restarting openhab, it may be random other rules that are not working anymore, rules not working before the restart may be fine again. The general setting is always the same, the item changes in openhab, bute the rule doesn’t react.
I’ve cleared cache multiple times after restart, restarted openhab and the machine multiple times - no change (Except for a changing set of not working rules).
During startup, the log shows the known error messages of mqtt binding not being able to parse the zigbee2mqtt messages correctly, which is not related to this issue. Besides that, nothing related to the rules.
As I’ve followed the recent bugs & workarounds for the Milestone build, I’ve even tried to increase the org.quartz.threadPool.threadCount in quarz.properties to 30, to no avail.
Any help would be highly appreciated!
Thanks,
Chris