Hello fellow automation enthusiasts! I’m reaching out today with a puzzling issue I’ve been facing with my Enocean setup. I’ve been using OpenHAB for a while now, and it’s been a fantastic experience overall, but this particular problem has me scratching my head. Let me walk you through what’s happening and see if anyone out there might have some insights or suggestions.
So, the setup is as follows: I’ve got an Enocean USB stick (USB300) connected to my Raspberry Pi running OpenHAB 3.0.1. I’ve installed a Switsch Nodeon 2-1-0 Enocean switch and a Z-Wave PIR sensor. By manual control, everything works flawlessly—I can toggle the switch on and off without any issues. However, when I try to automate this process using a simple rule, things start to fall apart.
Here’s the rule I’ve set up:
plaintext
rule “Motion Activated Lighting”
when
Item PIRFlurUntenGeraet_MotionAlarm changed to ON
then
logInfo(“Automation”, “Motion detected!”)
sendCommand(LichtFlurUnternGeraet_Switch, ON)
end
The logs confirm that the rule is triggered and the command is sent:
plaintext
2021-04-08 12:14:18.947 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘PIRFlurUntenGeraet_MotionAlarm’ changed from OFF to ON
2021-04-08 12:14:18.953 [INFO ] [openhab.event.ItemCommandEvent ] - Item ‘LichtFlurUnternGeraet_Switch’ received command ON
2021-04-08 12:14:18.954 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item ‘LichtFlurUnternGeraet_Switch’ predicted to become ON
2021-04-08 12:14:18.959 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item ‘LichtFlurUnternGeraet_Switch’ changed from OFF to ON
But here’s the kicker—the actual physical switch doesn’t respond. It stays off, and I’m left in the dark, both literally and figuratively. The really odd part is that if I manually trigger the rule through the OpenHAB interface, it works perfectly. It’s only when the rule is triggered by the PIR sensor that things go south.
I’ve tried a few troubleshooting steps:
- Checked the Enocean Range: The switch is only about 2 meters away from the Raspberry Pi, so range shouldn’t be an issue.
- Reset the Enocean Stick: No luck there either.
- Reviewed the Logs: The logs don’t show any errors, just the successful execution of the rule.
- Tested with a Blockly Script: Interestingly, when I replicate the functionality using a Blockly script, it works without any issues.
At this point, I’m leaning towards some sort of timing or synchronization issue, but I’m not entirely sure. Maybe there’s a delay in how the Enocean protocol handles automated commands versus manual ones? Or perhaps there’s a configuration setting I’m overlooking.
I’d love to hear from anyone who might have encountered a similar issue or has some insights into how Enocean devices handle automated commands. Your experiences could be invaluable in helping me resolve this mystery!
Cheers,
[Your Name]