Hi. First off this is an unsupported version of HS 2026.5.2 so happy to be told it's that.
Currently running latest-26130-3d2a489a on a Debian Buster bare metal VM.
I've been working on moving away from OpenLuup completely and up until now have been using some virtual switches t manage things like 'Is there anyone home'
I have a binary sensor in HA that provides the same thing
binary_sensor.someone_home which appears in MSR as
hass>binary_sensor_someone_home
HA shows on or off. MSR shows true or false
All fine. The odd thing happened after an update of HA and a restart.
From HA
13:07:04 it turned off
13:07:11 it turned on
However that does not appear to have been reflected in MSR which turned all the heating and so on off as it is supposed to do, and I got all my notifications as I should.
Here's a huge log section (sorry) as I wanted to show how MSR identifies that HA is up and running at 12:07:08 (Zulu) but triggers the 'There's no one here' at 12:07:17 some 6 seconds after HA updated to on.
Checking in the interface MSR said the status was 'False' while HA stated 'On'
rule-mkwk2fwa.dval:[{"id":1,"container":2,"value":3,"serial":92,"tss":93,"tsc":93},"rule-mkwk2fwa","rules",{"id":1,"serial":4,"triggers":5,"constraints":21,"expressions":24,"name":25,"react_set":26,"react_reset":88,"ruleset":91},16,{"type":6,"id":7,"op":8,"conditions":9,"editor_version":20},"group","trig","and",[10],{"id":11,"type":12,"data":13},"condmkwk2fwa","entity",{"entity":14,"attribute":15,"op":16,"value":17},"hass>person_rachel_matthews","x_hass.state","change",[18,19],null,"not_home",25351,{"type":6,"id":22,"op":8,"conditions":23},"cons",[],{},"Rachel is on the move",{"id":27,"actions":28,"rule":1,"editor_version":87,"set":61},"rule-mkwk2fwa:S",[29,35,62,83],{"id":30,"type":31,"data":32},"24kv27go","setvar",{"var":33,"value":34},"g_CurrentHour","${{int(strftime(\"%H\", time()))}}",{"id":36,"type":6,"actions":37,"constraints":46},"rule-mkwk2fwa:S-24kv7qgg",[38],{"id":39,"type":12,"data":40},"24kv4y1v",{"entity":41,"action":42,"args":43},"hass>system","x_hass_system.call_service",{"service":44,"data":45},"notify.alexa_media","{\n\"message\":\"Good ${{g_Greeting}} Chris. , Rachel has left the ${{g_rachel_last_area}} zone and is in transit \",\n\"data\":{\"type\":\"announce\", \"method\":\"speak\"},\n\"target\":[\"media_player.everywhere\"]\n}",{"id":47,"name":48,"type":6,"op":8,"conditions":49,"editor_version":20},"rule-mkwk2fwa:S-24kv7qgg-cons","Group Constraints Copy",[50,55],{"id":51,"type":52,"data":53},"cond24kv89zv","comment",{"comment":54},"Should speak only when I'm home",{"id":56,"type":12,"data":57},"cond24kv7qgh",{"entity":58,"attribute":59,"op":60,"value":61},"mqqt>catman_iphone","binary_sensor.state","=",true,{"id":63,"type":6,"actions":64,"constraints":72},"rule-mkwk2fwa:S-24kv2lon",[65],{"id":66,"type":67,"data":68},"28xz6paf","notify",{"method":69,"message":70,"profile":71},"Telegram","Rachel has left the ${{g_rachel_last_area}} zone and is in transit","default",{"id":73,"name":48,"type":6,"op":8,"conditions":74,"editor_version":20},"rule-mkwk2fwa:S-24kv2lon-cons",[75,79],{"id":76,"type":52,"data":77},"cond24kvlpae",{"comment":78},"Should telegram while I am away",{"id":80,"type":12,"data":81},"cond24kvkyz7",{"entity":58,"attribute":59,"op":60,"value":82},false,{"id":84,"type":52,"data":85},"24kv7hvk",{"comment":86},"Enter comment text",25314,{"id":89,"actions":90,"rule":1,"set":82},"rule-mkwk2fwa:R",[],"rs-l5sdq41x",2,1779017869959]
rule-mkwk2fwa.json:{"id":"rule-mkwk2fwa","container":"rules","value":{"id":"rule-mkwk2fwa","serial":16,"triggers":{"type":"group","id":"trig","op":"and","conditions":[{"id":"condmkwk2fwa","type":"entity","data":{"entity":"hass>person_rachel_matthews","attribute":"x_hass.state","op":"change","value":[null,"not_home"]}}],"editor_version":25351},"constraints":{"type":"group","id":"cons","op":"and","conditions":[]},"expressions":{},"name":"Rachel is on the move","react_set":{"id":"rule-mkwk2fwa:S","actions":[{"id":"24kv27go","type":"setvar","data":{"var":"g_CurrentHour","value":"${{int(strftime(\"%H\", time()))}}"}},{"id":"rule-mkwk2fwa:S-24kv7qgg","type":"group","actions":[{"id":"24kv4y1v","type":"entity","data":{"entity":"hass>system","action":"x_hass_system.call_service","args":{"service":"notify.alexa_media","data":"{\n\"message\":\"Good ${{g_Greeting}} Chris. , Rachel has left the ${{g_rachel_last_area}} zone and is in transit \",\n\"data\":{\"type\":\"announce\", \"method\":\"speak\"},\n\"target\":[\"media_player.everywhere\"]\n}"}}}],"constraints":{"id":"rule-mkwk2fwa:S-24kv7qgg-cons","name":"Group Constraints Copy","type":"group","op":"and","conditions":[{"id":"cond24kv89zv","type":"comment","data":{"comment":"Should speak only when I'm home"}},{"id":"cond24kv7qgh","type":"entity","data":{"entity":"mqqt>catman_iphone","attribute":"binary_sensor.state","op":"=","value":true}}],"editor_version":25351}},{"id":"rule-mkwk2fwa:S-24kv2lon","type":"group","actions":[{"id":"28xz6paf","type":"notify","data":{"method":"Telegram","message":"Rachel has left the ${{g_rachel_last_area}} zone and is in transit","profile":"default"}}],"constraints":{"id":"rule-mkwk2fwa:S-24kv2lon-cons","name":"Group Constraints Copy","type":"group","op":"and","conditions":[{"id":"cond24kvlpae","type":"comment","data":{"comment":"Should telegram while I am away"}},{"id":"cond24kvkyz7","type":"entity","data":{"entity":"mqqt>catman_iphone","attribute":"binary_sensor.state","op":"=","value":false}}],"editor_version":25351}},{"id":"24kv7hvk","type":"comment","data":{"comment":"Enter comment text"}}],"rule":"rule-mkwk2fwa","editor_version":25314,"set":true},"react_reset":{"id":"rule-mkwk2fwa:R","actions":[],"rule":"rule-mkwk2fwa","set":false},"ruleset":"rs-l5sdq41x"},"serial":2,"tss":1779017869959,"tsc":1779017869959}
rule-mkwlg11o.dval:[{"id":1,"container":2,"value":3,"serial":92,"tss":93,"tsc":93},"rule-mkwlg11o","rules",{"id":1,"serial":4,"triggers":5,"constraints":20,"expressions":23,"name":24,"react_set":25,"react_reset":88,"ruleset":91},5,{"type":6,"id":7,"op":8,"conditions":9,"editor_version":19},"group","trig","and",[10],{"id":11,"type":12,"data":13},"condmkwk2fwa","entity",{"entity":14,"attribute":15,"op":16,"value":17},"hass>person_rachel_matthews","x_hass.state","change",[18],"not_home",25351,{"type":6,"id":21,"op":8,"conditions":22},"cons",[],{},"Rachel has arrived",{"id":26,"actions":27,"rule":1,"editor_version":87,"set":65},"rule-mkwlg11o:S",[28,33,39,66,83],{"id":29,"type":30,"data":31},"24kvboht","script",{"expr":32},"g_rachel_last_area = getEntity(\"hass>person_rachel_matthews\").attributes['x_hass'].state",{"id":34,"type":35,"data":36},"24kvbohu","setvar",{"var":37,"value":38},"g_CurrentHour","${{int(strftime(\"%H\", time()))}}",{"id":40,"type":6,"actions":41,"constraints":50},"rule-mkwlg11o:S-rule-mkwlg11o-24kvbohv",[42],{"id":43,"type":12,"data":44},"24kvbohw",{"entity":45,"action":46,"args":47},"hass>system","x_hass_system.call_service",{"service":48,"data":49},"notify.alexa_media","{\n\"message\":\"Good ${{g_Greeting}} Chris. , Rachel has arrived in the ${{g_rachel_last_area}} zone.\",\n\"data\":{\"type\":\"announce\", \"method\":\"speak\"},\n\"target\":[\"media_player.everywhere\"]\n}",{"id":51,"name":52,"type":6,"op":8,"conditions":53,"editor_version":19},"24kvbohv-cons","Group Constraints Copy",[54,59],{"id":55,"type":56,"data":57},"cond24kv89zv","comment",{"comment":58},"Should speak only when I'm home",{"id":60,"type":12,"data":61},"cond24kv7qgh",{"entity":62,"attribute":63,"op":64,"value":65},"mqqt>catman_iphone","binary_sensor.state","=",true,{"id":67,"type":6,"actions":68,"constraints":76},"rule-mkwlg11o:S-rule-mkwlg11o-24kvbohx",[69],{"id":70,"type":71,"data":72},"24kvbohy","notify",{"method":73,"message":74,"profile":75},"Telegram","Rachel has arrived in the ${{g_rachel_last_area}} zone.","default",{"id":77,"name":52,"type":6,"op":8,"conditions":78,"editor_version":19},"24kvbohx-cons",[79],{"id":80,"type":12,"data":81},"cond24kvmzfp",{"entity":62,"attribute":63,"op":64,"value":82},false,{"id":84,"type":56,"data":85},"24kvbohz",{"comment":86},"Enter comment text",25314,{"id":89,"actions":90,"rule":1,"set":82},"rule-mkwlg11o:R",[],"rs-l5sdq41x",1,1770023368433]
rule-mkwlg11o.json:{"id":"rule-mkwlg11o","container":"rules","value":{"id":"rule-mkwlg11o","serial":5,"triggers":{"type":"group","id":"trig","op":"and","conditions":[{"id":"condmkwk2fwa","type":"entity","data":{"entity":"hass>person_rachel_matthews","attribute":"x_hass.state","op":"change","value":["not_home"]}}],"editor_version":25351},"constraints":{"type":"group","id":"cons","op":"and","conditions":[]},"expressions":{},"name":"Rachel has arrived","react_set":{"id":"rule-mkwlg11o:S","actions":[{"id":"24kvboht","type":"script","data":{"expr":"g_rachel_last_area = getEntity(\"hass>person_rachel_matthews\").attributes['x_hass'].state"}},{"id":"24kvbohu","type":"setvar","data":{"var":"g_CurrentHour","value":"${{int(strftime(\"%H\", time()))}}"}},{"id":"rule-mkwlg11o:S-rule-mkwlg11o-24kvbohv","type":"group","actions":[{"id":"24kvbohw","type":"entity","data":{"entity":"hass>system","action":"x_hass_system.call_service","args":{"service":"notify.alexa_media","data":"{\n\"message\":\"Good ${{g_Greeting}} Chris. , Rachel has arrived in the ${{g_rachel_last_area}} zone.\",\n\"data\":{\"type\":\"announce\", \"method\":\"speak\"},\n\"target\":[\"media_player.everywhere\"]\n}"}}}],"constraints":{"id":"24kvbohv-cons","name":"Group Constraints Copy","type":"group","op":"and","conditions":[{"id":"cond24kv89zv","type":"comment","data":{"comment":"Should speak only when I'm home"}},{"id":"cond24kv7qgh","type":"entity","data":{"entity":"mqqt>catman_iphone","attribute":"binary_sensor.state","op":"=","value":true}}],"editor_version":25351}},{"id":"rule-mkwlg11o:S-rule-mkwlg11o-24kvbohx","type":"group","actions":[{"id":"24kvbohy","type":"notify","data":{"method":"Telegram","message":"Rachel has arrived in the ${{g_rachel_last_area}} zone.","profile":"default"}}],"constraints":{"id":"24kvbohx-cons","name":"Group Constraints Copy","type":"group","op":"and","conditions":[{"id":"cond24kvmzfp","type":"entity","data":{"entity":"mqqt>catman_iphone","attribute":"binary_sensor.state","op":"=","value":false}}],"editor_version":25351}},{"id":"24kvbohz","type":"comment","data":{"comment":"Enter comment text"}}],"rule":"rule-mkwlg11o","editor_version":25314,"set":true},"react_reset":{"id":"rule-mkwlg11o:R","actions":[],"rule":"rule-mkwlg11o","set":false},"ruleset":"rs-l5sdq41x"},"serial":1,"tss":1770023368433,"tsc":1770023368433}
catman@openluup:~/reactor/storage/rules$ exit
logout
Connection to 192.168.70.249 closed.
catman@ChrisMBP2021 ~ % ./NotVera
** WARNING: connection is not using a post-quantum key exchange algorithm.
** This session may be vulnerable to "store now, decrypt later" attacks.
** The server may need to be upgraded. See https://openssh.com/pq.html
Linux openluup 4.19.0-20-amd64 #1 SMP Debian 4.19.235-1 (2022-03-17) x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon May 18 12:13:38 2026 from 192.168.70.69
cdcatman@openluup:~$ cd reactor/lo
locales/ logs/
catman@openluup:~$ cd reactor/logs/
catman@openluup:~/reactor/logs$ ls
console.log hass_config.json hass_services-2025-11-1.json hass_services-2026-1-0.json hass_services-2026-5-2.json reactor.log reactor.log.4 vera-user_data-initial.json
device_32 hass_device_registry.json hass_services-2025-11-2.json hass_services-2026-1-1.json hass_services.json reactor.log.1 reactor.log.5
e hass_entity_registry.json hass_services-2025-11-3.json hass_services-2026-4-2.json hass_sources.json reactor.log.2 unhandled.json
hass_area_registry.json hass_integrations.json hass_services-2025-7-2.json hass_services-2026-4-4.json hass_states.json reactor.log.3 vera-status-initial.json
catman@openluup:~/reactor/logs$ less reactor.log
catman@openluup:~/reactor/logs$ tail reactor.log
[latest-26130]2026-05-19T12:20:08.296Z <httpapi:INFO> httpapi#1 API request from ::ffff:192.168.70.249: GET /api/v1/netstatus
[latest-26130]2026-05-19T12:21:03.391Z <httpapi:INFO> httpapi#1 API request from ::ffff:192.168.70.249: GET /api/v1/netstatus
[latest-26130]2026-05-19T12:21:08.729Z <Rule:INFO> Rule#rule-mova0cpn re-evaluating local variable L_Cinema_Light_Level for dependency notification from ValueSensor#hass>sensor_cinema_multi_sensor_illuminance
[latest-26130]2026-05-19T12:21:08.734Z <Rule:INFO> Rule#rule-mova0cpn requesting eval for changed dependent locals Array(1) ["L_Cinema_Light_Level"]
[latest-26130]2026-05-19T12:22:03.501Z <httpapi:INFO> httpapi#1 API request from ::ffff:192.168.70.249: GET /api/v1/netstatus
[latest-26130]2026-05-19T12:22:08.614Z <Rule:INFO> Rule#rule-mova0cpn re-evaluating local variable L_Cinema_Light_Level for dependency notification from ValueSensor#hass>sensor_cinema_multi_sensor_illuminance
[latest-26130]2026-05-19T12:22:08.624Z <Rule:INFO> Rule#rule-mova0cpn requesting eval for changed dependent locals Array(1) ["L_Cinema_Light_Level"]
[latest-26130]2026-05-19T12:23:03.590Z <httpapi:INFO> httpapi#1 API request from ::ffff:192.168.70.249: GET /api/v1/netstatus
[latest-26130]2026-05-19T12:23:08.503Z <Rule:INFO> Rule#rule-mova0cpn re-evaluating local variable L_Cinema_Light_Level for dependency notification from ValueSensor#hass>sensor_cinema_multi_sensor_illuminance
[latest-26130]2026-05-19T12:23:08.506Z <Rule:INFO> Rule#rule-mova0cpn requesting eval for changed dependent locals Array(1) ["L_Cinema_Light_Level"]
catman@openluup:~/reactor/logs$ less reactor.log
[latest-26130]2026-05-19T12:07:17.946Z <Rule:INFO> Cyrus Stream Vol+ (rule-ml9yjy9z in Living Room) starting rule state evaluation; because predicate-state-changed Predicate#rule-ml9yjy9z/trig
[latest-26130]2026-05-19T12:07:17.947Z <Rule:INFO> Cyrus Stream Vol+ (rule-ml9yjy9z in Living Room) evaluated; rule state transition from RESET to 'SET'
[latest-26130]2026-05-19T12:07:17.961Z <Rule:INFO> Cyrus Stream Vol- (rule-ml9ylxw3 in Living Room) starting rule state evaluation; because predicate-state-changed Predicate#rule-ml9ylxw3/trig
[latest-26130]2026-05-19T12:07:17.962Z <Rule:INFO> Cyrus Stream Vol- (rule-ml9ylxw3 in Living Room) evaluated; rule state transition from RESET to 'SET'
[latest-26130]2026-05-19T12:07:17.995Z <Engine:INFO> Enqueueing "Heating Control Mode is Home<RESET>" (rule-l680lif2:R)
[latest-26130]2026-05-19T12:07:17.996Z <Engine:INFO> Enqueueing "House Mode is Home<RESET>" (rule-l5sdqazh:R)
[latest-26130]2026-05-19T12:07:17.997Z <Engine:INFO> Enqueueing "Cyrus Stream Play / Pause<SET>" (rule-ml9y0xqo:S)
[latest-26130]2026-05-19T12:07:17.997Z <Engine:INFO> Enqueueing "Cyrus Stream Vol+<SET>" (rule-ml9yjy9z:S)
[latest-26130]2026-05-19T12:07:17.998Z <Engine:INFO> Enqueueing "Cyrus Stream Vol-<SET>" (rule-ml9ylxw3:S)
[latest-26130]2026-05-19T12:07:18.000Z <Engine:NOTICE> Starting reaction Heating Control Mode is Home<RESET> (rule-l680lif2:R)
[latest-26130]2026-05-19T12:07:18.000Z <Engine:INFO> Engine#1 perform power_switch.off on Entity#hass>input_boolean_heating_mode with { } by reaction Heating Control Mode is Home<RESET> (rule-l680lif2:R) step 1
[latest-26130]2026-05-19T12:07:18.000Z <HassController:INFO> HassController#hass perform power_switch.off on Entity#hass>input_boolean_heating_mode with { }
[latest-26130]2026-05-19T12:07:18.001Z <HassController:INFO> HassController#hass service homeassistant.turn_off target data is { } (empty), assuming default entity target
[latest-26130]2026-05-19T12:07:18.001Z <HassController:INFO> HassController#hass: sending payload for power_switch.off on Entity#hass>input_boolean_heating_mode action: { "type": "call_service", "service_data": { }, "domain": "homeassistant", "service": "turn_off", "target": { "entity_id": "input_boolean.heating_mode" } }
[latest-26130]2026-05-19T12:07:18.017Z <Engine:NOTICE> Starting reaction House Mode is Home<RESET> (rule-l5sdqazh:R)
[latest-26130]2026-05-19T12:07:18.018Z <Engine:INFO> House Mode is Home<RESET> all actions completed.
[latest-26130]2026-05-19T12:07:18.074Z <Engine:NOTICE> Starting reaction Cyrus Stream Play / Pause<SET> (rule-ml9y0xqo:S)
[latest-26130]2026-05-19T12:07:18.076Z <Engine:INFO> Engine#1 perform x_hass.call_service on Entity#hass>text_living_room_remote_ir_code_to_send with { "service": "text.set_value", "data": "{ \"value\": \"BfcG9wZ8A+ABAeABDRP3BvcGfAN8A/cG9wb///cG9wZ8A+ABAeABDRP3BvcGfAN8A/cG9wb///cG9wZ8A+ABAeABDQv3BvcGfAN8A/cG9wY=\" }" } by reaction Cyrus Stream Play / Pause<SET> (rule-ml9y0xqo:S) step 1
[latest-26130]2026-05-19T12:07:18.076Z <HassController:INFO> HassController#hass perform x_hass.call_service on Entity#hass>text_living_room_remote_ir_code_to_send with { "service": "text.set_value", "data": "{ \"value\": \"BfcG9wZ8A+ABAeABDRP3BvcGfAN8A/cG9wb///cG9wZ8A+ABAeABDRP3BvcGfAN8A/cG9wb///cG9wZ8A+ABAeABDQv3BvcGfAN8A/cG9wY=\" }" }
[latest-26130]2026-05-19T12:07:18.077Z <HassController:INFO> HassController#hass: sending payload for x_hass.call_service on Entity#hass>text_living_room_remote_ir_code_to_send action: { "type": "call_service", "service_data": { "value": "BfcG9wZ8A+ABAeABDRP3BvcGfAN8A/cG9wb///cG9wZ8A+ABAeABDRP3BvcGfAN8A/cG9wb///cG9wZ8A+ABAeABDQv3BvcGfAN8A/cG9wY=" }, "domain": "text", "service": "set_value", "target": { "entity_id": "text.living_room_remote_ir_code_to_send" } }
[latest-26130]2026-05-19T12:07:18.090Z <Engine:NOTICE> Starting reaction Cyrus Stream Vol+<SET> (rule-ml9yjy9z:S)
[latest-26130]2026-05-19T12:07:18.091Z <Engine:INFO> Engine#1 perform x_hass.call_service on Entity#hass>text_living_room_remote_ir_code_to_send with { "service": "text.set_value", "data": "{ \"value\": \"BXsDewP3BkABAXsD4AUBBfcG9wZ7A+ABAQf//3sDewP3BkABAXsD4AUBBfcG9wZ7A+ABAQf//3sDewP3BkABAXsD4AUBD/cG9wZ7A3sDewN7A3sDewM=\" }" } by reaction Cyrus Stream Vol+<SET> (rule-ml9yjy9z:S) step 1
[latest-26130]2026-05-19T12:07:18.092Z <HassController:INFO> HassController#hass perform x_hass.call_service on Entity#hass>text_living_room_remote_ir_code_to_send with { "service": "text.set_value", "data": "{ \"value\": \"BXsDewP3BkABAXsD4AUBBfcG9wZ7A+ABAQf//3sDewP3BkABAXsD4AUBBfcG9wZ7A+ABAQf//3sDewP3BkABAXsD4AUBD/cG9wZ7A3sDewN7A3sDewM=\" }" }
[latest-26130]2026-05-19T12:07:18.092Z <HassController:INFO> HassController#hass: sending payload for x_hass.call_service on Entity#hass>text_living_room_remote_ir_code_to_send action: { "type": "call_service", "service_data": { "value": "BXsDewP3BkABAXsD4AUBBfcG9wZ7A+ABAQf//3sDewP3BkABAXsD4AUBBfcG9wZ7A+ABAQf//3sDewP3BkABAXsD4AUBD/cG9wZ7A3sDewN7A3sDewM=" }, "domain": "text", "service": "set_value", "target": { "entity_id": "text.living_room_remote_ir_code_to_send" } }
[latest-26130]2026-05-19T12:07:18.093Z <Engine:NOTICE> Starting reaction Cyrus Stream Vol-<SET> (rule-ml9ylxw3:S)
[latest-26130]2026-05-19T12:07:18.093Z <Engine:INFO> Engine#1 perform x_hass.call_service on Entity#hass>text_living_room_remote_ir_code_to_send with { "service": "text.set_value", "data": "{ \"value\": \"AXoD4AEBA/EGegPgBQEF8QbxBnoDgAFACQP//3oD4AEBQBHgBQEP8QbxBnoDegN6A3oD8QZ6Aw==\" }" } by reaction Cyrus Stream Vol-<SET> (rule-ml9ylxw3:S) step 1
[latest-26130]2026-05-19T12:07:18.094Z <HassController:INFO> HassController#hass perform x_hass.call_service on Entity#hass>text_living_room_remote_ir_code_to_send with { "service": "text.set_value", "data": "{ \"value\": \"AXoD4AEBA/EGegPgBQEF8QbxBnoDgAFACQP//3oD4AEBQBHgBQEP8QbxBnoDegN6A3oD8QZ6Aw==\" }" }
[latest-26130]2026-05-19T12:07:18.111Z <HassController:INFO> HassController#hass: sending payload for x_hass.call_service on Entity#hass>text_living_room_remote_ir_code_to_send action: { "type": "call_service", "service_data": { "value": "AXoD4AEBA/EGegPgBQEF8QbxBnoDgAFACQP//3oD4AEBQBHgBQEP8QbxBnoDegN6A3oD8QZ6Aw==" }, "domain": "text", "service": "set_value", "target": { "entity_id": "text.living_room_remote_ir_code_to_send" } }
[latest-26130]2026-05-19T12:07:18.113Z <Rule:INFO> Rule#rule-l5sdqazh reaction rule-l5sdqazh:R completed
This is hardly the end of the world as HA restarting is rare and I simply hit refresh on the entity in MSR but is this some kind of race condition or something that needs addressing?
Hoping I've given enough data to make it sensible
C
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.
I have a couple of rules that has group reactions with empty conditions. I notice, in particular on one that's called every 5 secs, that it was not working. I added an empty comment as condition and it started working again.
I don't know if saving was enough to "reset" it, but I'm reporting anyway. No errors in the logs, but the MQTT message was not published, so I had an easy path to check the rule.
I have others like these, but not easy to test. @toggledbits maybe some stuck status data? (I restarted a couple of times after the last update). Thanks.
TL;DR: Format of data in storage directory will soon change. Make sure you are backing up the contents of that directory in its entirety, and you preserve your backups for an extended period, particularly the backup you take right before upgrading to the build containing this change (date of that is still to be determined, but soon). The old data format will remain readable (so you'll be able to read your pre-change backups) for the foreseeable future.
In support of a number of other changes in the works, I have found it necessary to change the storage format for Reactor objects in storage at the physical level.
Until now, plain, standard JSON has been used to store the data (everything under the storage directory). This has served well, but has a few limitations, including no real support for native JavaScript objects like Date, Map, Set, and others. It also is unable to store data that contains "loops" — objects that reference themselves in some way.
I'm not sure exactly when, but in the not-too-distant future I will publish a build using the new data format. It will automatically convert existing JSON data to the new format. For the moment, it will save data in both the new format and the old JSON format, preferring the former when loading data from storage. I have been running my own home with this new format for several months, and have no issues with data loss or corruption.
A few other things to know:
If you are not already backing up your storage directory, you should be. At a minimum, back this directory up every time you make big changes to your Rules, Reactions, etc.
Your existing JSON-format backups will continue to be readable for the long-term (years). The code that loads data from these files looks for the new file format first (which will have a .dval suffix), and if not found, will happily read (and convert) a same-basenamed .json file (i.e. it looks for ruleid.dval first, and if it doesn't find it, it tries to load ruleid.json). I'll publish detailed instructions for restoring from old backups when the build is posted (it's easy).
The new .dval files are not directly human-readable or editable as easily as the old .json files. A new utility will be provided in the tools directory to convert .dval data to .json format, which you can then read or edit if you find that necessary. However, that may not work for all future data, as my intent is to make more native JavaScript objects directly storable, and many of those objects cannot be stored in JSON.
You may need to modify your backup tools/scripts to pick up the new files: if you explicitly name .json files (rather than just specifying the entire storage directory) in your backup configuration, you will need to add .dval files to get a complete, accurate backup. I don't think this will be an issue for any of you; I imagine that you're all just backing up the entire contents of storage regardless of format/name, that is the safest (and IMO most correct) way to go (if that's not what you're doing, consider changing your approach).
The current code stores the data in both the .dval form and the .json form to hedge against any real-world problems I don't encounter in my own use. Some future build will drop this redundancy (i.e. save only to .dval form). However, the read code for the .json form will remain in any case.
This applies only to persistent storage that Reactor creates and controls under the storage tree. All other JSON data files (e.g. device data for Controllers) are unaffected by this change and will remain in that form. YAML files are also unaffected by this change.
This thread is open for any questions or concerns.
Hi,
I'm on Docker/NAs (latest-26011-c621bbc7) with Zwave js ui (last version).
I have set the 'Location' for each device in the Z-Wave JS UI dashboard, I cannot find this information among the Entity Attributes in the Reactor. I tried and the result is an empty array []. It seems the 'Location' metadata from Z-Wave JS is not being mapped to a standard attribute in Reactor. Location is equale to Rooms for me. When comparing this to the Vera or Ezlo Controller, Reactor automatically creates Room Icons also in the Reactor Dashboard and places the various devices under those room categories.
This is a very convenient way to keep the dashboard organized and quickly find lights to turn off with a click (especially when something isn't switched off as expected for me:) ).
Is there a way to map the Z-Wave JS UI 'Location' attribute and a dashboard organization, just like it does with Vera/Ezlo?
Thanks in advance for all the great tips you've shared
I use Virtual Entity Controller virtual switches which I turn on via webhooks from other applications. Once a switch triggers and turns on, I can then activate associated rules.
I would like each virtual switch to automatically turn off after a configurable time (e.g., 5 seconds, 10 seconds).
Is there a better way to achieve this auto-off behavior instead of creating a separate rule for each switch that uses the 'Condition must be sustained for' option to turn it off?
With a large number of these switches (and the associated turn-off rules), I'm checking to see if there is a simpler approach.If not, could this be a feature request to add an auto-off timer directly to the virtual switches.
Thanks
Reactor (Multi-hub) latest-26011-c621bbc7
VirtualEntityController v25356
Synology Docker
I've had similar problems before, but now this issue has resurfaced. Using build 26011 on Docker.
As I copied one old rule as a "template" for a similar new rule, where I have multiple conditions using changes operator (from any to any, and with delay reset of 900), these conditions do not detect change in attributes. Even if I manually reset the rule, reset delay timers do not restart.
If I do a new rule from scratch, and do not copy/import anything old, the same conditions work properly. Also, if I modify copied rule's conditions (put a random number to "from" & "to" fields), then save, and after that remove those modifications, rule begins to function normally. Just editing e.g. delay reset value does not do any good in this context.
@toggledbits, I can DM logs & related rule files to you, if you just send me instructions.
Looking at using Home Assistant for the first time, either on a Home Assistant Green, their own hardware or buying a cheap second hand mini PC.
Sounds like Home Assistant OS is linux based using Docker for HA etc.
Would I also be able to install things like MSR as well on their OS ? On the same box?
Thanks.
Having been messing around with some stuff I worked a way to self trigger some tests that I wanted to do on the HA <> MSR integration
This got me wondering if there's an entity that changes state / is exposed when a configured controller goes off line? I can't see one but thought it might be hidden or something?
Cheers
C
Set reaction triggering wrong z-wave device
Multi-System Reactor
19
Posts
2
Posters
1.4k
Views
2
Watching
-
Good afternoon,
I've been having an issue where a rule that is supposed to trigger my front porch lights when motion is detected, is instead turning on our holiday soffit lighting. They are one z-wave entry appart. It's been driving me crazy trying to figure out what is triggering the lights to come on, because I haven't been able to find any rule that would trigger it, and the logs don't indicate any mention of that specific entity being turned on.The device that it's turning on is:
Soffit Outlets
zwavejs>136-0
false
6:48:32 PMThe device that it should be turning on is:
Front Porch Lights
zwavejs>137-0
false
6:47:09 PM
I've switched the entry to use the HAAS entry to stop it, but I'd like to know why it's triggering an entry one entity off.
This could also explain some issues I've been having with Zwave entries not working properly for some time.
I'm running Reactor (Multi-hub) latest-26011-c621bbc7 in Docker/Portainer.
ZWaveJSController [0.1.25139]Yes, it's no theory. I was able to confirm it by activating the action to turn on the zwave-137-0, and zwave-136-0 came on, and 137-0 did not. Once I determined that was happening, I found events for zwave-137-0 in the logs at the time it was zwave-136-0 was coming on.
Edit: I could not find events for zwave-136-0 coming on, so that initially left me stumped.
-
Here's a better output of the logs. I was providing output from Proxmox, which is awful for copying text.
root@docker:/home/tmorgenthaler/reactor/logs# cat reactor.* | grep 137-0 | grep zwavejs | grep T22:29 [latest-26011]2026-01-30T22:29:00.005Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing power_switch.on on Front Porch Lights (Switch#zwavejs>137-0) with { } [latest-26011]2026-01-30T22:29:00.918Z <ZWaveJSController:5:ZWaveJSController.js:966> ZWaveJSController#zwavejs handling node event statistics updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-30T22:29:01.169Z <ZWaveJSController:5:ZWaveJSController.js:966> ZWaveJSController#zwavejs handling node event statistics updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-30T22:29:02.240Z <ZWaveJSController:5:ZWaveJSController.js:966> ZWaveJSController#zwavejs handling node event statistics updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-30T22:29:02.241Z <ZWaveJSController:5:ZWaveJSController.js:966> ZWaveJSController#zwavejs handling node event value updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-30T22:29:02.241Z <ZWaveJSController:5:ZWaveJSController.js:966> ZWaveJSController#zwavejs handling node event value updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-30T22:29:02.241Z <ZWaveJSController:5:ZWaveJSController.js:1270> ZWaveJSController#zwavejs setting Switch#zwavejs>137-0.x_zwave_values.Binary_Switch_targetValue to true [latest-26011]2026-01-30T22:29:02.241Z <ZWaveJSController:5:ZWaveJSController.js:1255> ZWaveJSController#zwavejs updating attribute power_switch.state with { "entity": "137-0", "impl": { "valueId": "37:currentValue:" } } [latest-26011]2026-01-30T22:29:02.242Z <ZWaveJSController:5:ZWaveJSController.js:1166> ZWaveJSController#zwavejs _apply_value entity Switch#zwavejs>137-0 power_switch.state [latest-26011]2026-01-30T22:29:02.242Z <ZWaveJSController:5:ZWaveJSController.js:1179> ZWaveJSController#zwavejs handling Switch#zwavejs>137-0 power_switch.state by { "valueId": "37:currentValue:" } with { "endpoint": 0, "commandClass": 37, "commandClassName": "Binary Switch", "property": "currentValue", "propertyName": "currentValue", "ccVersion": 2, "metadata": { "type": "boolean", "readable": true, "writeable": false, "label": "Current value" }, "value": true, "__endp": { "power_switch.state": { "entity": "137-0", "impl": { "valueId": "37:currentValue:" } } } } [latest-26011]2026-01-30T22:29:02.242Z <ZWaveJSController:5:ZWaveJSController.js:1270> ZWaveJSController#zwavejs setting Switch#zwavejs>137-0.x_zwave_values.Binary_Switch_currentValue to true [latest-26011]2026-01-30T22:29:02.491Z <ZWaveJSController:5:ZWaveJSController.js:966> ZWaveJSController#zwavejs handling node event statistics updated entity Switch#zwavejs>137-0 root@docker:/home/tmorgenthaler/reactor/logs# cat reactor.* | grep 136-0 | grep zwavejs | grep T22:29 root@docker:/home/tmorgenthaler/reactor/logs#This was the timestamp for when that particular rule was triggering. As you can see, the 137-0 entity has several entries for that timestamp, but 136-0 does not, yet I've been able to replicate that is what is occuring.
-
Please go to the Entities list, find entity
zwavejs>137-0, open its detail panel, and copy-paste the output from the Copy Attributes button here (as text, no screen shots). -
Please go to the Entities list, find entity
zwavejs>137-0, open its detail panel, and copy-paste the output from the Copy Attributes button here (as text, no screen shots).@toggledbits said in Set reaction triggering wrong z-wave device:
Please go to the Entities list, find entity zwavejs>137-0, open its detail panel, and copy-paste the output from the Copy Attributes button here (as text, no screen shots).
I've providing a link as text file. I got a warning about the number of characters when I tried to paste into the reply directly.
-
OK. Everything checks out there. I would upgrade to the latest ZWaveJSController -- it looks like you are a release behind. That version added logging for what is actually sent to ZWaveJS, which may be instructive. But restarting for that update and rebuilding the state data may resolve the issue (you've probably done the former, I assume, but the latter is less obvious), so we're changing the conditions of the test. But let's see what happens when you upgrade, and then see what the log entries look like if the behavior is the same, because it sure looks like ZWaveJSController has it correct.
-
I wasn't sure if I was on the correct release or not. Does the Docker image include the Zwave release in the pull?
said in Set reaction triggering wrong z-wave device:
I wasn't sure if I was on the correct release or not. Does the Docker image include the Zwave release in the pull?
Never mind. It's says it does not in your documentation.
I updated to v25304 and restarted Reactor. I'll run some tests now.
-
said in Set reaction triggering wrong z-wave device:
I wasn't sure if I was on the correct release or not. Does the Docker image include the Zwave release in the pull?
Never mind. It's says it does not in your documentation.
I updated to v25304 and restarted Reactor. I'll run some tests now.
said in Set reaction triggering wrong z-wave device:
I updated to v25304 and restarted Reactor. I'll run some tests now.
Alright, it still seems to be doing the same thing. I'm tailing the zwavejs log, and pressing the button for the Set Reaction. I see it pushing the command for 137-0, however, the soffit lights (136-0) are coming on.
root@docker:/home/tmorgenthaler/reactor/logs# tail -f zwavejs.log | grep 137-0 [latest-26011]2026-01-31T20:25:01.008Z <ZWaveJSController:5:ZWaveJSController.js:1237> ZWaveJSController#zwavejs updating attribute power_switch.state with { "entity": "137-0", "impl": { "valueId": "37:currentValue:" } } [latest-26011]2026-01-31T20:25:01.008Z <ZWaveJSController:5:ZWaveJSController.js:1148> ZWaveJSController#zwavejs _apply_value entity Switch#zwavejs>137-0 power_switch.state [latest-26011]2026-01-31T20:25:01.008Z <ZWaveJSController:5:ZWaveJSController.js:1161> ZWaveJSController#zwavejs handling Switch#zwavejs>137-0 power_switch.state by { "valueId": "37:currentValue:" } with { "endpoint": 0, "commandClass": 37, "commandClassName": "Binary Switch", "property": "currentValue", "propertyName": "currentValue", "ccVersion": 2, "metadata": { "type": "boolean", "readable": true, "writeable": false, "label": "Current value", "stateful": true, "secret": false }, "value": true, "__endp": { "power_switch.state": { "entity": "137-0", "impl": { "valueId": "37:currentValue:" } } } } [latest-26011]2026-01-31T20:25:01.009Z <ZWaveJSController:5:ZWaveJSController.js:1252> ZWaveJSController#zwavejs setting Switch#zwavejs>137-0.x_zwave_values.Binary_Switch_currentValue to true [latest-26011]2026-01-31T20:25:01.104Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event statistics updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-31T20:25:15.710Z <ZWaveJSController:INFO> ZWaveJSController#zwavejs performing power_switch.on on Front Porch Lights (Switch#zwavejs>137-0) with { } [latest-26011]2026-01-31T20:25:15.973Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event statistics updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-31T20:25:16.125Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event value updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-31T20:25:16.125Z <ZWaveJSController:5:ZWaveJSController.js:1252> ZWaveJSController#zwavejs setting Switch#zwavejs>137-0.x_zwave_values.Binary_Switch_targetValue to true [latest-26011]2026-01-31T20:25:16.125Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event value updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-31T20:25:16.126Z <ZWaveJSController:5:ZWaveJSController.js:1237> ZWaveJSController#zwavejs updating attribute power_switch.state with { "entity": "137-0", "impl": { "valueId": "37:currentValue:" } } [latest-26011]2026-01-31T20:25:16.126Z <ZWaveJSController:5:ZWaveJSController.js:1148> ZWaveJSController#zwavejs _apply_value entity Switch#zwavejs>137-0 power_switch.state [latest-26011]2026-01-31T20:25:16.126Z <ZWaveJSController:5:ZWaveJSController.js:1161> ZWaveJSController#zwavejs handling Switch#zwavejs>137-0 power_switch.state by { "valueId": "37:currentValue:" } with { "endpoint": 0, "commandClass": 37, "commandClassName": "Binary Switch", "property": "currentValue", "propertyName": "currentValue", "ccVersion": 2, "metadata": { "type": "boolean", "readable": true, "writeable": false, "label": "Current value", "stateful": true, "secret": false }, "value": true, "__endp": { "power_switch.state": { "entity": "137-0", "impl": { "valueId": "37:currentValue:" } } } } [latest-26011]2026-01-31T20:25:16.126Z <ZWaveJSController:5:ZWaveJSController.js:1252> ZWaveJSController#zwavejs setting Switch#zwavejs>137-0.x_zwave_values.Binary_Switch_currentValue to true [latest-26011]2026-01-31T20:25:16.224Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event statistics updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-31T20:25:33.510Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event statistics updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-31T20:25:33.661Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event value updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-31T20:25:33.661Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event value updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-31T20:25:33.662Z <ZWaveJSController:5:ZWaveJSController.js:1252> ZWaveJSController#zwavejs setting Switch#zwavejs>137-0.x_zwave_values.Binary_Switch_targetValue to false [latest-26011]2026-01-31T20:25:33.666Z <ZWaveJSController:5:ZWaveJSController.js:1237> ZWaveJSController#zwavejs updating attribute power_switch.state with { "entity": "137-0", "impl": { "valueId": "37:currentValue:" } } [latest-26011]2026-01-31T20:25:33.666Z <ZWaveJSController:5:ZWaveJSController.js:1148> ZWaveJSController#zwavejs _apply_value entity Switch#zwavejs>137-0 power_switch.state [latest-26011]2026-01-31T20:25:33.666Z <ZWaveJSController:5:ZWaveJSController.js:1161> ZWaveJSController#zwavejs handling Switch#zwavejs>137-0 power_switch.state by { "valueId": "37:currentValue:" } with { "endpoint": 0, "commandClass": 37, "commandClassName": "Binary Switch", "property": "currentValue", "propertyName": "currentValue", "ccVersion": 2, "metadata": { "type": "boolean", "readable": true, "writeable": false, "label": "Current value", "stateful": true, "secret": false }, "value": false, "__endp": { "power_switch.state": { "entity": "137-0", "impl": { "valueId": "37:currentValue:" } } } } [latest-26011]2026-01-31T20:25:33.666Z <ZWaveJSController:5:ZWaveJSController.js:1252> ZWaveJSController#zwavejs setting Switch#zwavejs>137-0.x_zwave_values.Binary_Switch_currentValue to false [latest-26011]2026-01-31T20:25:33.760Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event statistics updated entity Switch#zwavejs>137-0I also see the results of turning off the device from HAAS in the ZWaveJS logs.
Here are the entries for the devices in HAAS from ZwaveJS-UI
Screenshot 2026-01-31 at 3.29.10 PMI've also creating an attirbutes text file for 136-0. Maybe something is funky in that entry.
-
Here are some logs of me turning the entities on and off from HAAS.
root@docker:/home/tmorgenthaler/reactor/logs# tail -f zwavejs.log | grep 13'[6-7]'-0 [latest-26011]2026-01-31T20:37:00.403Z <ZWaveJSController:5:ZWaveJSController.js:1148> ZWaveJSController#zwavejs _apply_value entity Switch#zwavejs>136-0 power_switch.state [latest-26011]2026-01-31T20:37:00.403Z <ZWaveJSController:5:ZWaveJSController.js:1161> ZWaveJSController#zwavejs handling Switch#zwavejs>136-0 power_switch.state by { "valueId": "37:currentValue:" } with { "endpoint": 0, "commandClass": 37, "commandClassName": "Binary Switch", "property": "currentValue", "propertyName": "currentValue", "ccVersion": 2, "metadata": { "type": "boolean", "readable": true, "writeable": false, "label": "Current value", "stateful": true, "secret": false }, "value": true, "__endp": { "power_switch.state": { "entity": "136-0", "impl": { "valueId": "37:currentValue:" } } } } [latest-26011]2026-01-31T20:37:00.403Z <ZWaveJSController:5:ZWaveJSController.js:1252> ZWaveJSController#zwavejs setting Switch#zwavejs>136-0.x_zwave_values.Binary_Switch_currentValue to true [latest-26011]2026-01-31T20:37:00.648Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event statistics updated entity Switch#zwavejs>136-0 [latest-26011]2026-01-31T20:37:18.529Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event statistics updated entity Switch#zwavejs>136-0 [latest-26011]2026-01-31T20:37:18.553Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event value updated entity Switch#zwavejs>136-0 [latest-26011]2026-01-31T20:37:18.553Z <ZWaveJSController:5:ZWaveJSController.js:1252> ZWaveJSController#zwavejs setting Switch#zwavejs>136-0.x_zwave_values.Binary_Switch_targetValue to false [latest-26011]2026-01-31T20:37:18.559Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event value updated entity Switch#zwavejs>136-0 [latest-26011]2026-01-31T20:37:18.559Z <ZWaveJSController:5:ZWaveJSController.js:1237> ZWaveJSController#zwavejs updating attribute power_switch.state with { "entity": "136-0", "impl": { "valueId": "37:currentValue:" } } [latest-26011]2026-01-31T20:37:18.559Z <ZWaveJSController:5:ZWaveJSController.js:1148> ZWaveJSController#zwavejs _apply_value entity Switch#zwavejs>136-0 power_switch.state [latest-26011]2026-01-31T20:37:18.559Z <ZWaveJSController:5:ZWaveJSController.js:1161> ZWaveJSController#zwavejs handling Switch#zwavejs>136-0 power_switch.state by { "valueId": "37:currentValue:" } with { "endpoint": 0, "commandClass": 37, "commandClassName": "Binary Switch", "property": "currentValue", "propertyName": "currentValue", "ccVersion": 2, "metadata": { "type": "boolean", "readable": true, "writeable": false, "label": "Current value", "stateful": true, "secret": false }, "value": false, "__endp": { "power_switch.state": { "entity": "136-0", "impl": { "valueId": "37:currentValue:" } } } } [latest-26011]2026-01-31T20:37:18.560Z <ZWaveJSController:5:ZWaveJSController.js:1252> ZWaveJSController#zwavejs setting Switch#zwavejs>136-0.x_zwave_values.Binary_Switch_currentValue to false [latest-26011]2026-01-31T20:37:18.779Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event statistics updated entity Switch#zwavejs>136-0 [latest-26011]2026-01-31T20:37:25.647Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event statistics updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-31T20:37:25.803Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event value updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-31T20:37:25.803Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event value updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-31T20:37:25.804Z <ZWaveJSController:5:ZWaveJSController.js:1252> ZWaveJSController#zwavejs setting Switch#zwavejs>137-0.x_zwave_values.Binary_Switch_targetValue to true [latest-26011]2026-01-31T20:37:25.808Z <ZWaveJSController:5:ZWaveJSController.js:1237> ZWaveJSController#zwavejs updating attribute power_switch.state with { "entity": "137-0", "impl": { "valueId": "37:currentValue:" } } [latest-26011]2026-01-31T20:37:25.808Z <ZWaveJSController:5:ZWaveJSController.js:1148> ZWaveJSController#zwavejs _apply_value entity Switch#zwavejs>137-0 power_switch.state [latest-26011]2026-01-31T20:37:25.808Z <ZWaveJSController:5:ZWaveJSController.js:1161> ZWaveJSController#zwavejs handling Switch#zwavejs>137-0 power_switch.state by { "valueId": "37:currentValue:" } with { "endpoint": 0, "commandClass": 37, "commandClassName": "Binary Switch", "property": "currentValue", "propertyName": "currentValue", "ccVersion": 2, "metadata": { "type": "boolean", "readable": true, "writeable": false, "label": "Current value", "stateful": true, "secret": false }, "value": true, "__endp": { "power_switch.state": { "entity": "137-0", "impl": { "valueId": "37:currentValue:" } } } } [latest-26011]2026-01-31T20:37:25.809Z <ZWaveJSController:5:ZWaveJSController.js:1252> ZWaveJSController#zwavejs setting Switch#zwavejs>137-0.x_zwave_values.Binary_Switch_currentValue to true [latest-26011]2026-01-31T20:37:25.898Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event statistics updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-31T20:37:29.297Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event statistics updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-31T20:37:29.447Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event value updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-31T20:37:29.448Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event value updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-31T20:37:29.448Z <ZWaveJSController:5:ZWaveJSController.js:1252> ZWaveJSController#zwavejs setting Switch#zwavejs>137-0.x_zwave_values.Binary_Switch_targetValue to false [latest-26011]2026-01-31T20:37:29.453Z <ZWaveJSController:5:ZWaveJSController.js:1237> ZWaveJSController#zwavejs updating attribute power_switch.state with { "entity": "137-0", "impl": { "valueId": "37:currentValue:" } } [latest-26011]2026-01-31T20:37:29.453Z <ZWaveJSController:5:ZWaveJSController.js:1148> ZWaveJSController#zwavejs _apply_value entity Switch#zwavejs>137-0 power_switch.state [latest-26011]2026-01-31T20:37:29.453Z <ZWaveJSController:5:ZWaveJSController.js:1161> ZWaveJSController#zwavejs handling Switch#zwavejs>137-0 power_switch.state by { "valueId": "37:currentValue:" } with { "endpoint": 0, "commandClass": 37, "commandClassName": "Binary Switch", "property": "currentValue", "propertyName": "currentValue", "ccVersion": 2, "metadata": { "type": "boolean", "readable": true, "writeable": false, "label": "Current value", "stateful": true, "secret": false }, "value": false, "__endp": { "power_switch.state": { "entity": "137-0", "impl": { "valueId": "37:currentValue:" } } } } [latest-26011]2026-01-31T20:37:29.453Z <ZWaveJSController:5:ZWaveJSController.js:1252> ZWaveJSController#zwavejs setting Switch#zwavejs>137-0.x_zwave_values.Binary_Switch_currentValue to false [latest-26011]2026-01-31T20:37:29.547Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event statistics updated entity Switch#zwavejs>137-0 -
I also just noticed that if I performed an action from the Entities page in MSR fr 137-0, it's turning on 136-0 in HAAS. If I turn on 136-0 through entities, it's turning on 137-0 in HAAS. It would appear these devices are somehow switching actions, despite everything showing what they are.
-
Here are some logs of me turning the entities on and off from HAAS.
root@docker:/home/tmorgenthaler/reactor/logs# tail -f zwavejs.log | grep 13'[6-7]'-0 [latest-26011]2026-01-31T20:37:00.403Z <ZWaveJSController:5:ZWaveJSController.js:1148> ZWaveJSController#zwavejs _apply_value entity Switch#zwavejs>136-0 power_switch.state [latest-26011]2026-01-31T20:37:00.403Z <ZWaveJSController:5:ZWaveJSController.js:1161> ZWaveJSController#zwavejs handling Switch#zwavejs>136-0 power_switch.state by { "valueId": "37:currentValue:" } with { "endpoint": 0, "commandClass": 37, "commandClassName": "Binary Switch", "property": "currentValue", "propertyName": "currentValue", "ccVersion": 2, "metadata": { "type": "boolean", "readable": true, "writeable": false, "label": "Current value", "stateful": true, "secret": false }, "value": true, "__endp": { "power_switch.state": { "entity": "136-0", "impl": { "valueId": "37:currentValue:" } } } } [latest-26011]2026-01-31T20:37:00.403Z <ZWaveJSController:5:ZWaveJSController.js:1252> ZWaveJSController#zwavejs setting Switch#zwavejs>136-0.x_zwave_values.Binary_Switch_currentValue to true [latest-26011]2026-01-31T20:37:00.648Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event statistics updated entity Switch#zwavejs>136-0 [latest-26011]2026-01-31T20:37:18.529Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event statistics updated entity Switch#zwavejs>136-0 [latest-26011]2026-01-31T20:37:18.553Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event value updated entity Switch#zwavejs>136-0 [latest-26011]2026-01-31T20:37:18.553Z <ZWaveJSController:5:ZWaveJSController.js:1252> ZWaveJSController#zwavejs setting Switch#zwavejs>136-0.x_zwave_values.Binary_Switch_targetValue to false [latest-26011]2026-01-31T20:37:18.559Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event value updated entity Switch#zwavejs>136-0 [latest-26011]2026-01-31T20:37:18.559Z <ZWaveJSController:5:ZWaveJSController.js:1237> ZWaveJSController#zwavejs updating attribute power_switch.state with { "entity": "136-0", "impl": { "valueId": "37:currentValue:" } } [latest-26011]2026-01-31T20:37:18.559Z <ZWaveJSController:5:ZWaveJSController.js:1148> ZWaveJSController#zwavejs _apply_value entity Switch#zwavejs>136-0 power_switch.state [latest-26011]2026-01-31T20:37:18.559Z <ZWaveJSController:5:ZWaveJSController.js:1161> ZWaveJSController#zwavejs handling Switch#zwavejs>136-0 power_switch.state by { "valueId": "37:currentValue:" } with { "endpoint": 0, "commandClass": 37, "commandClassName": "Binary Switch", "property": "currentValue", "propertyName": "currentValue", "ccVersion": 2, "metadata": { "type": "boolean", "readable": true, "writeable": false, "label": "Current value", "stateful": true, "secret": false }, "value": false, "__endp": { "power_switch.state": { "entity": "136-0", "impl": { "valueId": "37:currentValue:" } } } } [latest-26011]2026-01-31T20:37:18.560Z <ZWaveJSController:5:ZWaveJSController.js:1252> ZWaveJSController#zwavejs setting Switch#zwavejs>136-0.x_zwave_values.Binary_Switch_currentValue to false [latest-26011]2026-01-31T20:37:18.779Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event statistics updated entity Switch#zwavejs>136-0 [latest-26011]2026-01-31T20:37:25.647Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event statistics updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-31T20:37:25.803Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event value updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-31T20:37:25.803Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event value updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-31T20:37:25.804Z <ZWaveJSController:5:ZWaveJSController.js:1252> ZWaveJSController#zwavejs setting Switch#zwavejs>137-0.x_zwave_values.Binary_Switch_targetValue to true [latest-26011]2026-01-31T20:37:25.808Z <ZWaveJSController:5:ZWaveJSController.js:1237> ZWaveJSController#zwavejs updating attribute power_switch.state with { "entity": "137-0", "impl": { "valueId": "37:currentValue:" } } [latest-26011]2026-01-31T20:37:25.808Z <ZWaveJSController:5:ZWaveJSController.js:1148> ZWaveJSController#zwavejs _apply_value entity Switch#zwavejs>137-0 power_switch.state [latest-26011]2026-01-31T20:37:25.808Z <ZWaveJSController:5:ZWaveJSController.js:1161> ZWaveJSController#zwavejs handling Switch#zwavejs>137-0 power_switch.state by { "valueId": "37:currentValue:" } with { "endpoint": 0, "commandClass": 37, "commandClassName": "Binary Switch", "property": "currentValue", "propertyName": "currentValue", "ccVersion": 2, "metadata": { "type": "boolean", "readable": true, "writeable": false, "label": "Current value", "stateful": true, "secret": false }, "value": true, "__endp": { "power_switch.state": { "entity": "137-0", "impl": { "valueId": "37:currentValue:" } } } } [latest-26011]2026-01-31T20:37:25.809Z <ZWaveJSController:5:ZWaveJSController.js:1252> ZWaveJSController#zwavejs setting Switch#zwavejs>137-0.x_zwave_values.Binary_Switch_currentValue to true [latest-26011]2026-01-31T20:37:25.898Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event statistics updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-31T20:37:29.297Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event statistics updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-31T20:37:29.447Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event value updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-31T20:37:29.448Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event value updated entity Switch#zwavejs>137-0 [latest-26011]2026-01-31T20:37:29.448Z <ZWaveJSController:5:ZWaveJSController.js:1252> ZWaveJSController#zwavejs setting Switch#zwavejs>137-0.x_zwave_values.Binary_Switch_targetValue to false [latest-26011]2026-01-31T20:37:29.453Z <ZWaveJSController:5:ZWaveJSController.js:1237> ZWaveJSController#zwavejs updating attribute power_switch.state with { "entity": "137-0", "impl": { "valueId": "37:currentValue:" } } [latest-26011]2026-01-31T20:37:29.453Z <ZWaveJSController:5:ZWaveJSController.js:1148> ZWaveJSController#zwavejs _apply_value entity Switch#zwavejs>137-0 power_switch.state [latest-26011]2026-01-31T20:37:29.453Z <ZWaveJSController:5:ZWaveJSController.js:1161> ZWaveJSController#zwavejs handling Switch#zwavejs>137-0 power_switch.state by { "valueId": "37:currentValue:" } with { "endpoint": 0, "commandClass": 37, "commandClassName": "Binary Switch", "property": "currentValue", "propertyName": "currentValue", "ccVersion": 2, "metadata": { "type": "boolean", "readable": true, "writeable": false, "label": "Current value", "stateful": true, "secret": false }, "value": false, "__endp": { "power_switch.state": { "entity": "137-0", "impl": { "valueId": "37:currentValue:" } } } } [latest-26011]2026-01-31T20:37:29.453Z <ZWaveJSController:5:ZWaveJSController.js:1252> ZWaveJSController#zwavejs setting Switch#zwavejs>137-0.x_zwave_values.Binary_Switch_currentValue to false [latest-26011]2026-01-31T20:37:29.547Z <ZWaveJSController:5:ZWaveJSController.js:948> ZWaveJSController#zwavejs handling node event statistics updated entity Switch#zwavejs>137-0@tamorgen said in Set reaction triggering wrong z-wave device:
Here are some logs of me turning the entities on and off from HAAS.
You've shown here all stuff from ZWaveController, not HassController...? I don't think that would be helpful here anyway, because it would only show the HA entity IDs, and HA doesn't embed ZWave node numbers in their entity names. You would have to go look at the device in HA to confirm the node numbers. In HA's UI, go to Settings > Integrations > ZWave > Devices. Find the device you think is your Front Porch Lights switch, and click it. In the Device Info area, there's a Z-Wave Info heading with an arrow — click the arrow to expose the node number.
You said you updated ZWaveJSController, but it's still not showing me the expected log data. Can you confirm that in the startup messages for Reactor, ZWaveJSController reports it is version as 25304. If not, your update was not successful.
You can also go back to the ZWave-jS UI and command node 137 on from there, and see which device ZWave-JS switches. If it's the same device that Reactor switches, your Z-Wave nodes or HA devices are incorrectly identified.
What is clear in the Reactor logs so far is that ZWave node 137 is being told to do something, and ZWave node 137 responds back that it received the command its values changed. Nowhere along the way do the logs mention 136. If there was something wrong with what ZWaveJSController was commanding ZWaveJS to do, I would expect it log that it was performing an action on 137, but then gets update reports from 136, and that's not what is happening. I can also see in your Z-Wave data that node 137 is named "Front Porch Lights" at the node itself, which is consistent with the Reactor entity name, so Reactor/ZWaveJSController thinks it is doing the right thing.
I would start looking at the root, which is the ZWaveJS-UI, and make sure that node 137 is really your porch lights and you can command them on and off from there. If that's not the case, change the device name in Z-WaveJS UI, and then make sure the names in both HA and Reactor for nodes 136 and 137 match that data. Right now, it appears they do not.
-
@tamorgen said in Set reaction triggering wrong z-wave device:
Here are some logs of me turning the entities on and off from HAAS.
You've shown here all stuff from ZWaveController, not HassController...? I don't think that would be helpful here anyway, because it would only show the HA entity IDs, and HA doesn't embed ZWave node numbers in their entity names. You would have to go look at the device in HA to confirm the node numbers. In HA's UI, go to Settings > Integrations > ZWave > Devices. Find the device you think is your Front Porch Lights switch, and click it. In the Device Info area, there's a Z-Wave Info heading with an arrow — click the arrow to expose the node number.
You said you updated ZWaveJSController, but it's still not showing me the expected log data. Can you confirm that in the startup messages for Reactor, ZWaveJSController reports it is version as 25304. If not, your update was not successful.
You can also go back to the ZWave-jS UI and command node 137 on from there, and see which device ZWave-JS switches. If it's the same device that Reactor switches, your Z-Wave nodes or HA devices are incorrectly identified.
What is clear in the Reactor logs so far is that ZWave node 137 is being told to do something, and ZWave node 137 responds back that it received the command its values changed. Nowhere along the way do the logs mention 136. If there was something wrong with what ZWaveJSController was commanding ZWaveJS to do, I would expect it log that it was performing an action on 137, but then gets update reports from 136, and that's not what is happening. I can also see in your Z-Wave data that node 137 is named "Front Porch Lights" at the node itself, which is consistent with the Reactor entity name, so Reactor/ZWaveJSController thinks it is doing the right thing.
I would start looking at the root, which is the ZWaveJS-UI, and make sure that node 137 is really your porch lights and you can command them on and off from there. If that's not the case, change the device name in Z-WaveJS UI, and then make sure the names in both HA and Reactor for nodes 136 and 137 match that data. Right now, it appears they do not.
@toggledbits said in Set reaction triggering wrong z-wave device:
. Can you confirm that in the startup messages for Reactor, ZWaveJSController reports it is version as 25304
Yes, it shows up as 0.1.25304
So, you seemed to have hit it. There is a disagreement in the names in the Z-wave JS integration and the Z-Wave JS UI naming. I'm not sure how or when that happened, since I haven't touched the naming of these in at least 2 years.
The device that is 136 is truly the Front Porch Sconces. Everywhere in the HA dashboards when I click on the binary switch, it does turn it on. Same with 137 being the Soffit Lights.
It would seem it's getting the names from the ZwaveJS UI values, since they seemed to be off. I've gone ahead and renamed them in ZwaveJS UI to reflect the values in ZwaveJS. How do I get ZWaveJSController to update the names? They still show up as the incorrect name. I went ahead and restarted MSR, and the old naming is till persistent.
-
Reactor only changes the entity name when the entity is first created. From there on, it sticks, no matter what the underlying hub does. To change the name, hit the "Rename" button on the entity in the detail pane (see your latest screen shots).
Also future note. When posting log snippets, please don't use
grepor other filtering. Find the lines of interest, and post 20-25 of context before and as much context after as is relevant. Not all relevant log messages may contain the string you are searching for. -
Reactor only changes the entity name when the entity is first created. From there on, it sticks, no matter what the underlying hub does. To change the name, hit the "Rename" button on the entity in the detail pane (see your latest screen shots).
Also future note. When posting log snippets, please don't use
grepor other filtering. Find the lines of interest, and post 20-25 of context before and as much context after as is relevant. Not all relevant log messages may contain the string you are searching for.Thank you. Perhaps the non-updating of the name was the root cause of my issue all along.
-
The name is incorrect at ZWave-JS (on the node itself) if that's the case, so to keep your sanity later, make sure you go all the way back to the source and work your way forward from there.
-
The name is incorrect at ZWave-JS (on the node itself) if that's the case, so to keep your sanity later, make sure you go all the way back to the source and work your way forward from there.
@toggledbits said in Set reaction triggering wrong z-wave device:
The name is incorrect at ZWave-JS (on the node itself) if that's the case, so to keep your sanity later, make sure you go all the way back to the source and work your way forward from there.
I renamed the devices on the ZWave-JS UI, so i won't have the problem going forward. I'm still not sure how this all happened, as I did not experience this problem in years past. The only thing I can think of is there was some sort of glitch in an upgrade. I know I had to restore the Z-Wave JS UI to an earlier version back in October because of a change they made that broke window coverings, so perhaps during that restore something went wonky.
