I’m currently migrating my home automation from openHAB 1 to openHAB 3.
I still try to get my head around on all the new concepts like things, channels, semantic models (equipment, points etc.) and maybe I haven’t understood them all (even after reading the documentation at least 3 times).
- Eltako FTS14 bus system: FAM14 and FGW14-USB
- PIR motion sensors attached to FTS12EM-UC
- Eltako FTS14 bus system with different actuators (FUD14/800W, FSG14/1-10V, and some more). The light actuator (a FUD14) is
- paired with the PIR (a FTS12EM)
- is configured to be controlled by a GFVS
- The setup is fine and I can control the FUD via openHAB3, the status is reported correctly.
What I would like to achieve is to “decouple” the PIRs from the light during during night time (for example after 10pm) and couple the PIRs at morning time (6am).
In my old setup with openHAB 1 I implemented this feature by using a MQTT bridge (written in Python). I configured a scheduled command which sends a telegram to the FUD14 blocking its value of 0 (respective unblock).
Reading through the EnOcean binding I found a parameter
storeValue in the
But I found no way to configure this value via the UI.
- Maybe my old solution isn’t the best way to achieve my goal. Does anyone else have an alternative solution to my problem to couple/decouple the lights from the PIR based on a schedule?
- In case my proposed solution to block the actuator at 0, how could I achieve this with openHAB3?