Event Listener

[rlkoshak (Rich Koshak)]

Automation/Orchestration Design Patterns

As a guy who’s written code for a living for 35+ years, I appreciate the “mother of all rules” post on the wiki and the discussions here which use groups for reduce lines of code. But I’ve not seen too much on doing systematic coordination/orchestration of automation events and design patterns of logic for same. So, I offer the following. This starts with my particular use case involving a Light in my kitchen. There’s a switch in the room to control the light, as well as a motion sensor whi…

This is the original posting and perhaps a little complex for your needs.

A Proxy Item is just an Item not bound to anything. So you would have:

items

Switch HallwayCommand { tcp=">[ON:10.5.1.6:3040:'MAP(90.map)'],>[OFF:10.5.1.6:3040:'MAP(90.map)'] " }
Switch HallwayUpdate { tcp="<[10.5.1.6:3040:'MAP(m90.map)']" }
Switch HallwayProxy

Rules

// when the proxy receives a command, send it to the device
rule "HallwayProxy received command"
when
    Item HallwayProxy received command
then
    HallwayCommand.sendCommand(HallwayProxy.state)
end

// when the Update Item receives a command, update the Proxy
rule "HallwayUpdate received command"
when
    Item HallwayUpdate received command
then
    HallwayProxy.postUpdate(HallwayUpdate.state)
end

Put HallwayProxy on your sitemap and only use HallwayProxy in the rest of your rules.