Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
G
Topic thumbnail image
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Upgrade Issues
T
Topic thumbnail image
Multi-System Reactor
Logon screen timeout
G
Noticing since 170 that the lock screen doesn't switch to the logon prompt but, rather, stays on the active UI until such time as you go to click something within it. Then it jumps to the login screen. Brave browser Brave 1.92.139 (Official Build) (arm64) Chromium: 150.0.7871.114
Multi-System Reactor
[MSR] Copy&past of actions and/or drag&drop between set/reset
therealdbT
Hey @toggledbits One thing that bothers me while doing work on new systems/new features, is that I cannot copy&paste actions, and I cannot drag&drop between set and resets. #1 is for when I want to copy an action between different rules opened in two separate browser windows, while #2 is when I just need to flip a bunch of actions in the reset, or move some logic back and forth. Both will be appreciated, but I understand the technical challenges. Thanks!
Multi-System Reactor
Upgrade advice - upgrade from aarch64 to ARM64 image
T
I'm currently on version 26011. I understand that the aarch64 image is no longer supported. So, I therefore need to update to the ARM64 image. Can anyone possibly suggest how I update my docker compose.yaml file (see below). Ideally I'd like to keep my existing reactions etc. rather than start from scratch. # Multi-System Reactor template docker-compose.yml (version 22160) # # Change the lines indicated by "DO"... # services: reactor: container_name: reactor environment: # DO change the TZ: line to set your local time zone. # See valid TZ list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones TZ: GB # # DO NOT change this path. Your directory location is in "source" below. REACTOR_DATA_PREFIX: /var/reactor # DO change the image below to the one you are using (e.g. armv7l or aarch64 for RPi 4) image: toggledbits/reactor:latest-aarch64 restart: "always" expose: - 8111 ports: - 8111:8111 volumes: # DO change the /home/username/reactor below to the directory you created for # your local data; DO NOT change the /var/reactor part - /home/pi/docker/reactor:/var/reactor - /etc/localtime:/etc/localtime:ro tmpfs: /tmp
Multi-System Reactor
Alexa for MSR, any interest?
MikeReadingtonM
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Telegram notification broke with latest update
3
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Phantom device, “INFO” appears
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Mode Status NULL
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[RESOLVED] HTTP query failing after version 26177
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Question about the find function
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[Answered] OK to remove old json files?
3
Topic thumbnail image
Multi-System Reactor
Deprecation Announcement: 32-bit ARM *docker* images
toggledbitsT
If you are using the armv7l docker image, the OpenJS Foundation that publishes node is no longer producing 32-bit builds as of v24. That means the last supported LTS version of node for armv7l is v22, which will go End-of-Life in May 2027. Therefore, the Reactor armv7l image is now deprecated and will only be produced until node v22 goes EOL, and I will not publish armv7l images beyond that date. If you are running an RPi 3 or earlier with Reactor, you are on this image, and will need to upgrade hardware to a 64-bit model and use the arm64 image. If you need help getting it done, ask in this category.
Multi-System Reactor
[Solved] build 26150 - engine not starting
G
@toggledbits I pulled the image (well, Watchtower did) and within minutes the whole system went offline. The log looks like it ends with 26143. [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mkahsmgf/26qq82mw-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lqyfljfi/22f8on0t-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lsb61rw8/24oenqi2-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/rule-lrh58he0:S-1c00gfib-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1c00dylr-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1nam9w5u-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miuh2qqi/22ls4lql-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1vj8sdfc-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1qanz01x-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/24lq19p6-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mk0o8iox/23oy468y-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miscg2h3/rule-miscg2h3:S-22gmbq1c-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrfjke/238p0old-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-m7ccsso5/re-m7ccsso5-1r0myjxa-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/19nl9wq2-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3xk9t-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3vv5m-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/re-ln7j2nqp-22mx9lzd-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/22mx87c8-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-licneppy/1mzwe7ht-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ml3194ih/25jqt1j4-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrg7kf/227hshak-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13ua1p95-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13uagam7-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x4cbv-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x2fyl-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-lscjrws1/238p5c22-cons [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lbwr0jvq/1xkczf03-cons [latest-26143]2026-05-31T15:23:44.547Z <Structure:NOTICE> Structure Structure#1 stopped [latest-26143]2026-05-31T15:23:44.547Z <app:NOTICE> Closing APIs... [latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: closing... [latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: disconnecting from "192.168.1.23#82" (1001 service closing) [latest-26143]2026-05-31T15:23:44.548Z <httpapi:NOTICE> HTTP API closing... [latest-26143]2026-05-31T15:23:44.549Z <wsapi:NOTICE> wsapi: server closed [latest-26143]2026-05-31T15:23:44.549Z <httpapi:INFO> HTTP server closed. [latest-26143]2026-05-31T15:23:44.549Z <app:NOTICE> Stopping timers... [latest-26143]2026-05-31T15:23:44.551Z <app:null> Shutdown complete, process ID 1 [latest-26143]2026-05-31T15:23:44.551Z <app:null> Closing logs... [latest-26143]2026-05-31T15:23:44.551Z <default:null> Closing log I can SSH to the VM. Alas, I do not have the previous image for 26143 as I'm a little too quick sometimes on housekeeping.
Multi-System Reactor
http request action & digest auth
tunnusT
I’m using the HTTP Request action in MSR and need to authenticate against an endpoint that uses HTTP Digest authentication. Now that endpoint was changed to use SHA-256 in digest auth, so I would like to know if MSR supports it, or is it limited to MD5-based digest auth?
Multi-System Reactor
Cloning actions in reactions does not work
tunnusT
With build 26140 (on Docker) I'm not able to clone any actions in reactions. Using Chrome if it has any relevance.
Multi-System Reactor
Has ping command been removed?
tunnusT
Topic thumbnail image
Multi-System Reactor
ReferenceError with Home Assistant data & build 26140
tunnusT
Topic thumbnail image
Multi-System Reactor
Integrations and 'Loaded'
CatmanV2C
Thanks again for the recent release. One thing I wanted to ask about integrations and their 'loaded' condition: Is there something similar that applies to the entire controller? So if I have (for example) a helper in HA that is used to trigger an automation in MSR, is it possible to effectively exclude it until MSR is 'happy' that HA is stable and its values can be trusted? This, actually goes back to the issue I had. I've got a use case where a 30 second delay from triggering is a bit of a PITA (sustained for...) and was just wondering if there's a way of knowing that 'native' HA functions are working correctly. Probably asking wrong, or it's hideously obvious, but... TIA C
Multi-System Reactor

Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation

Scheduled Pinned Locked Moved Multi-System Reactor
1 Posts 1 Posters 1 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G Online
    G Online
    gwp1
    wrote last edited by gwp1
    #1

    Within a single rule evaluation pass, two mutually-exclusive Set Reaction condition groups both evaluated as TRUE and fired conflicting actions — one issuing cover.close, the other issuing cover.open — to the same entity, roughly 19ms apart. Both commands were dispatched to Home Assistant and both succeeded, with the later cover.open command effectively overriding the intended cover.close result and the blind staring at me like "what."

    Environment
    Rule: MBath Redux (rule-2c0ih079, folder: Blinds - Defers (Switchbot))
    Target entity: cover.blind_tilt_5d (via HassController)
    Conflicting groups: Privacy Close (-10) [HIGHEST PRIORITY] vs. Default/Open - No Deferral

    Set Reaction groups within a rule are configured to be mutually exclusive via their condition logic — each subgroup of "Default/Open - No Deferral" explicitly requires Master Bath lights is FALSE, while "Privacy Close (-10)" requires Master Bath lights is TRUE. These conditions reference the same Rule State and should not be able to evaluate as true simultaneously within one rule pass. Only one group should fire per evaluation.

    3b26f348-e95b-4929-8403-df0445839d15-image.png bd941b36-9461-4612-a56f-60085dd9c2fa-image.png 1dcf1bb5-27ba-43e6-ba05-12ee59934ed9-image.png ee5135ed-2a4e-4700-b476-aca70a34c032-image.png 83f1b565-2d73-4032-962f-ed7c52c40dc8-image.png 7a2e638b-e51d-4d91-b5bd-fdb040dcc770-image.png a992b3a0-4252-4b16-a544-674417ea7444-image.png

    Actual Behavior

    Both groups fired in the same evaluation cycle, dispatching opposing commands to the same cover entity within 19-35ms of each other. The cover.open command completed after cover.close, resulting in the blind ending up open when Privacy Close conditions (interpreted at time of trigger) should have closed it.

    Relevant Log Excerpt
    Yep. I even pulled logs.
    (40 lines: 20 before and 20 after the conflicting group evaluations at 00:06:17.410–17.630)

    [latest-26193]2026-08-03T00:06:14.658Z <ZWaveJSController:5:ZWaveJSController.js:890> ZWaveJSController#zwavejs handling event message
    [latest-26193]2026-08-03T00:06:14.658Z <ZWaveJSController:5:ZWaveJSController.js:954> ZWaveJSController#zwavejs handling event { "source": "node", "event": "value updated", "nodeId": 50, "args": { "commandClassName": "Multilevel Switch", "commandClass": 38, "endpoint": 0, "property": "targetValue", "newValue": 99, "prevValue": 99, "propertyName": "targetValue" } }
    [latest-26193]2026-08-03T00:06:14.658Z <ZWaveJSController:5:ZWaveJSController.js:966> ZWaveJSController#zwavejs handling node event value updated entity Light#zwavejs>50-0
    [latest-26193]2026-08-03T00:06:14.658Z <ZWaveJSController:5:ZWaveJSController.js:976> ZWaveJSController#zwavejs node value updated: { "source": "node", "event": "value updated", "nodeId": 50, "args": { "commandClassName": "Multilevel Switch", "commandClass": 38, "endpoint": 0, "property": "targetValue", "newValue": 99, "prevValue": 99, "propertyName": "targetValue" } }
    [latest-26193]2026-08-03T00:06:14.658Z <ZWaveJSController:5:ZWaveJSController.js:1230> ZWaveJSController#zwavejs update node 50 value "0:38:targetValue:" data { "source": "node", "event": "value updated", "nodeId": 50, "args": { "commandClassName": "Multilevel Switch", "commandClass": 38, "endpoint": 0, "property": "targetValue", "newValue": 99, "prevValue": 99, "propertyName": "targetValue" } }
    [latest-26193]2026-08-03T00:06:14.659Z <ZWaveJSController:5:ZWaveJSController.js:1245> ZWaveJSController#zwavejs updating attributes for node 50 value "0:38:duration:"={ "value": 0, "unit": "seconds" }: Array(0) []
    [latest-26193]2026-08-03T00:06:14.659Z <ZWaveJSController:5:ZWaveJSController.js:1270> ZWaveJSController#zwavejs setting Light#zwavejs>50-0.x_zwave_values.Multilevel_Switch_duration to { "value": 0, "unit": "seconds" }
    [latest-26193]2026-08-03T00:06:14.659Z <ZWaveJSController:5:ZWaveJSController.js:1245> ZWaveJSController#zwavejs updating attributes for node 50 value "0:38:targetValue:"=99: Array(0) []
    [latest-26193]2026-08-03T00:06:14.659Z <ZWaveJSController:5:ZWaveJSController.js:1270> ZWaveJSController#zwavejs setting Light#zwavejs>50-0.x_zwave_values.Multilevel_Switch_targetValue to 99
    [latest-26193]2026-08-03T00:06:14.711Z <ZWaveJSController:5:ZWaveJSController.js:890> ZWaveJSController#zwavejs handling event message
    [latest-26193]2026-08-03T00:06:14.711Z <ZWaveJSController:5:ZWaveJSController.js:954> ZWaveJSController#zwavejs handling event { "source": "controller", "event": "statistics updated", "statistics": { "messagesTX": 6218, "messagesRX": 13874, "messagesDroppedRX": 0, "NAK": 0, "CAN": 0, "timeoutACK": 0, "timeoutResponse": 0, "timeoutCallback": 0, "messagesDroppedTX": 0, "backgroundRSSI": { "channel0": { "current": -97, "average": -93 }, "channel1": { "current": -107, "average": -106 }, "channel2": { "current": -107, "average": -106 }, "channel3": { "current": -86, "average": -91 }, "timestamp": 1785715559933 } } }
    [latest-26193]2026-08-03T00:06:14.762Z <ZWaveJSController:5:ZWaveJSController.js:890> ZWaveJSController#zwavejs handling event message
    [latest-26193]2026-08-03T00:06:14.762Z <ZWaveJSController:5:ZWaveJSController.js:954> ZWaveJSController#zwavejs handling event { "source": "node", "event": "statistics updated", "nodeId": 50, "statistics": { "commandsTX": 85, "commandsRX": 108, "commandsDroppedRX": 0, "commandsDroppedTX": 0, "timeoutResponse": 0, "lastSeen": "2026-08-03T00:06:14.713Z", "rtt": 68, "rssi": -61, "lwr": { "protocolDataRate": 2, "repeaters": Array(1) [89], "rssi": -60, "repeaterRSSI": Array(1) [127] } } }
    [latest-26193]2026-08-03T00:06:14.762Z <ZWaveJSController:5:ZWaveJSController.js:966> ZWaveJSController#zwavejs handling node event statistics updated entity Light#zwavejs>50-0
    [latest-26193]2026-08-03T00:06:14.962Z <ZWaveJSController:5:ZWaveJSController.js:890> ZWaveJSController#zwavejs handling event message
    [latest-26193]2026-08-03T00:06:14.962Z <ZWaveJSController:5:ZWaveJSController.js:954> ZWaveJSController#zwavejs handling event { "source": "controller", "event": "statistics updated", "statistics": { "messagesTX": 6218, "messagesRX": 13875, "messagesDroppedRX": 0, "NAK": 0, "CAN": 0, "timeoutACK": 0, "timeoutResponse": 0, "timeoutCallback": 0, "messagesDroppedTX": 0, "backgroundRSSI": { "channel0": { "current": -97, "average": -93 }, "channel1": { "current": -107, "average": -106 }, "channel2": { "current": -107, "average": -106 }, "channel3": { "current": -86, "average": -91 }, "timestamp": 1785715559933 } } }
    [latest-26193]2026-08-03T00:06:15.093Z <Engine:INFO> Resuming reaction MBR Lamp ON (80%)/Repeat Conditions (re-mho04vm7-re-m7b73nz7-re-m6dz6200-1q2f02r5) from step 4
    [latest-26193]2026-08-03T00:06:15.093Z <Engine:INFO> MBR Lamp ON (80%)/Repeat Conditions all actions completed.
    [latest-26193]2026-08-03T00:06:15.106Z <Engine:NOTICE> Starting reaction MBR Lamp ON (80%) (re-mho04vm7)
    [latest-26193]2026-08-03T00:06:15.109Z <Engine:INFO> MBR Lamp ON (80%) all actions completed.
    [latest-26193]2026-08-03T00:06:17.410Z <Rule:INFO> MBath (AI generated) (rule-2c0ih079 in Blinds - Defers (Switchbot)) starting rule state evaluation; because predicate-state-changed Predicate#rule-2c0ih079/trig
    [latest-26193]2026-08-03T00:06:17.410Z <Rule:INFO> MBath (AI generated) (rule-2c0ih079 in Blinds - Defers (Switchbot)) evaluated; rule state transition from RESET to 'SET'
    [latest-26193]2026-08-03T00:06:17.414Z <Engine:INFO> Enqueueing reaction "MBath (AI generated)<SET>" (rule-2c0ih079:S)
    [latest-26193]2026-08-03T00:06:17.414Z <Engine:NOTICE> Starting reaction MBath (AI generated)<SET> (rule-2c0ih079:S)
    [latest-26193]2026-08-03T00:06:17.426Z <Engine:NOTICE> Starting reaction MBath (AI generated)<SET>/Privacy Close (-10) [HIGHEST PRIORITY] (rule-2c0ih079:S-grp2c0k359i)
    [latest-26193]2026-08-03T00:06:17.426Z <Engine:INFO> MBath (AI generated)<SET>/Privacy Close (-10) [HIGHEST PRIORITY] all actions completed.
    [latest-26193]2026-08-03T00:06:17.426Z <Engine:INFO> Enqueueing reaction "Blinds MBthR Close" (re-kx6addmw)
    [latest-26193]2026-08-03T00:06:17.439Z <Engine:INFO> Resuming reaction MBath (AI generated)<SET> (rule-2c0ih079:S) from step 2
    [latest-26193]2026-08-03T00:06:17.441Z <Engine:NOTICE> Starting reaction Blinds MBthR Close (re-kx6addmw)
    [latest-26193]2026-08-03T00:06:17.441Z <Engine:INFO> Engine#1 perform cover.close on Entity#hass>cover_blind_tilt_5d with {  } by reaction Blinds MBthR Close (re-kx6addmw) step 1
    [latest-26193]2026-08-03T00:06:17.441Z <HassController:INFO> HassController#hass perform cover.close on Entity#hass>cover_blind_tilt_5d with {  }
    [latest-26193]2026-08-03T00:06:17.442Z <HassController:INFO> HassController#hass: sending payload for cover.close on Entity#hass>cover_blind_tilt_5d action: { "type": "call_service", "service_data": {  }, "domain": "cover", "service": "close_cover", "target": { "entity_id": "cover.blind_tilt_5d" } }
    [latest-26193]2026-08-03T00:06:17.442Z <Engine:NOTICE> Starting reaction MBath (AI generated)<SET>/Default/Open - No Deferral (rule-2c0ih079:S-rule-2c0ih079-2c0ih07a)
    [latest-26193]2026-08-03T00:06:17.442Z <Engine:INFO> MBath (AI generated)<SET>/Default/Open - No Deferral all actions completed.
    [latest-26193]2026-08-03T00:06:17.442Z <Engine:INFO> Enqueueing reaction "Blinds MBthR Open" (re-lz20b071)
    [latest-26193]2026-08-03T00:06:17.456Z <Engine:INFO> Resuming reaction MBath (AI generated)<SET> (rule-2c0ih079:S) from step 7
    [latest-26193]2026-08-03T00:06:17.456Z <Engine:INFO> MBath (AI generated)<SET> all actions completed.
    [latest-26193]2026-08-03T00:06:17.460Z <Engine:NOTICE> Starting reaction Blinds MBthR Open (re-lz20b071)
    [latest-26193]2026-08-03T00:06:17.460Z <Engine:INFO> Engine#1 perform cover.open on Entity#hass>cover_blind_tilt_5d with {  } by reaction Blinds MBthR Open (re-lz20b071) step 1
    [latest-26193]2026-08-03T00:06:17.460Z <HassController:INFO> HassController#hass perform cover.open on Entity#hass>cover_blind_tilt_5d with {  }
    [latest-26193]2026-08-03T00:06:17.461Z <HassController:INFO> HassController#hass: sending payload for cover.open on Entity#hass>cover_blind_tilt_5d action: { "type": "call_service", "service_data": {  }, "domain": "cover", "service": "open_cover", "target": { "entity_id": "cover.blind_tilt_5d" } }
    [latest-26193]2026-08-03T00:06:17.461Z <Rule:INFO> Rule#rule-2c0ih079 reaction rule-2c0ih079:S completed
    [latest-26193]2026-08-03T00:06:17.584Z <HassController:INFO> HassController#hass action cover.close({  }) on Entity#hass>cover_blind_tilt_5d succeeded
    [latest-26193]2026-08-03T00:06:17.584Z <Engine:INFO> Resuming reaction Blinds MBthR Close (re-kx6addmw) from step 2
    [latest-26193]2026-08-03T00:06:17.584Z <Engine:INFO> Blinds MBthR Close all actions completed.
    [latest-26193]2026-08-03T00:06:17.595Z <HassController:INFO> HassController#hass action cover.open({  }) on Entity#hass>cover_blind_tilt_5d succeeded
    [latest-26193]2026-08-03T00:06:17.595Z <Engine:INFO> Resuming reaction Blinds MBthR Open (re-lz20b071) from step 2
    [latest-26193]2026-08-03T00:06:17.595Z <Engine:INFO> Blinds MBthR Open all actions completed.
    [latest-26193]2026-08-03T00:06:17.630Z <Engine:INFO> Resuming reaction MBath Lights ON (re-lwbbelj4) from step 3
    [latest-26193]2026-08-03T00:06:17.630Z <Engine:INFO> Engine#1 perform dimming.set on Light#zwavejs>50-0 with { "level": 0.4 } by reaction MBath Lights ON (re-lwbbelj4) step 3
    [latest-26193]2026-08-03T00:06:17.630Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing dimming.set on Master Bath Lights (Light#zwavejs>50-0) with { "level": 0.4 }
    [latest-26193]2026-08-03T00:06:17.630Z <ZWaveJSController:5:ZWaveJSController.js:2332> ZWaveJSController#zwavejs def { "endpoint": 0, "commandClass": 38, "property": "currentValue", "propertyKey": (undefined), "impl": Array(1) [{ "valueId": "+targetValue:", "value": { "expr": "max( 0, min( 99, round( 100 * ( parameters.level ?# 0 ), 0 ) ) )" } }] }
    [latest-26193]2026-08-03T00:06:17.630Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs action dimming.set set node 50 endpoint 0 value 38:targetValue: = 40
    [latest-26193]2026-08-03T00:06:17.630Z <ZWaveJSController:5:ZWaveJSController.js:2009> ZWaveJSController#zwavejs _set_value(50,0,38,targetValue,(undefined),40)
    

    My interpretation... which we all know how that can be lol:

    • Line 00:06:17.426: "Privacy Close (-10) [HIGHEST PRIORITY]" group's conditions evaluate true → enqueues Blinds MBthR Close.
    • Line 00:06:17.442, only 16ms later: "Default/Open - No Deferral" group's conditions also evaluate true in the same rule pass → enqueues Blinds MBthR Open.
    • Both groups reference the same Master Bath lights Rule State with opposite required values (is TRUE vs. is FALSE), and both should not have been able to pass simultaneously.
    • Both cover.close and cover.open service calls were dispatched to Home Assistant for the same entity (cover.blind_tilt_5d), 19ms apart, and both were reported as succeeded (00:06:17.584 and 00:06:17.595 respectively).
    • Because cover.open was issued and acknowledged after cover.close, it effectively overrode the intended close action — consistent with the observed real-world behavior (blind did not end up closed).
    • Impact

    Any rule with multiple Set Reaction groups intended to be mutually exclusive can silently issue conflicting device commands within the same evaluation pass, with the outcome determined by non-deterministic command-arrival order rather than rule logic. This makes the rule's actual behavior unpredictable despite condition logic that appears correctly exclusive when reviewed in the UI.

    I thought Set Reaction groups were expected to stop after the first match (if/elseif semantics) - OR are all groups are intended to evaluate independently every pass? If independent evaluation is by design, please give me some guidance on enforcing mutual exclusivity (or a built-in "stop after first match" option). My other option is back to multiple rules just for this one little thing the blinds have to do.

    *Hubitat C-7 2.5.1.142
    *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

    *HAOS
    Core 2026.7.4
    w/ HA Connect ZWA-2
    FW: v1.1
    SDK: v7.23.1

    *Prod MSR in docker/portainer
    MSR: latest-26193-8dd8f854
    MQTTController: 25139
    ZWave Controller: 25139

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    Recent Topics

    • Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
      G
      gwp1
      0
      1
      1

    • Reactor (Multi-System/Multi-Hub) Announcements
      toggledbitsT
      toggledbits
      5
      147
      126.7k

    • Upgrade Issues
      toggledbitsT
      toggledbits
      0
      8
      55

    • openLuup console disappeared - 500 - Internal Server Error
      A
      a-lurker
      0
      2
      143

    • Logon screen timeout
      G
      gwp1
      0
      5
      167

    • [MSR] Copy&past of actions and/or drag&drop between set/reset
      toggledbitsT
      toggledbits
      0
      9
      310

    • Upgrade advice - upgrade from aarch64 to ARM64 image
      toggledbitsT
      toggledbits
      0
      4
      181

    • Alexa for MSR, any interest?
      CatmanV2C
      CatmanV2
      2
      4
      313

    • Ezlo Paid Subscription for Vera Cloud Services
      therealdbT
      therealdb
      4
      2
      438

    • [RESOLVED] Telegram notification broke with latest update
      CatmanV2C
      CatmanV2
      0
      11
      766

    • [RESOLVED] Phantom device, “INFO” appears
      toggledbitsT
      toggledbits
      0
      2
      167
    Powered by NodeBB | Contributors
    Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • Unsolved