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.
H

HansW

@HansW
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
Do you Matter?
akbooerA
Is anyone using the Matter protocol to connect devices?
General Discussion
Caution: zwave-js-ui docker 11.4.0 is broken
toggledbitsT
About 20 hours ago, the author of zwave-js-ui posted build 11.4.0 of that product, and it contains an error and won't start (at all) under docker. The author is aware and working on a fix. In the meanwhile, stick with 11.3.1 or earlier. Ref: Issue 4401
Software
Shelly Wall Display XL
therealdbT
I don't know if you guys are into dashboards, but I am. For a second home I tried the Shelly Wall Display 2, and while not so big, it worked well over the summer. Since we're remodeling our house, I just swapped my old Fire Tablet (with its own problems) with two new Shelly Wall Display XL. I just removed the standard firmware, and I added mine (https://github.com/dbochicchio/ShellyElevate), forked from https://github.com/RapierXbox/ShellyElevate I just managed to support buttons (this thing has 4 of them) and it's all auto-discovered by Home Assistant and accessible via Reactor. I also have a new build in the works with support for buttons inside HA. I added a bonus Javascript interface sending events (screen/screensaver status, buttons, motion) to automatically drive the dashboard (all doing in HTML+Javascript and monitoring Reactor's variable). This specifical thing excluded, go get one of them, the device has a decent CPU for HA dashboards and blends wonderfully in the decor.
Hardware
Handling Dead Entities and Renamed Entities
PablaP
Hello all.. been a minute! I recently rebuilt my Z wave network and migrated to a new z wave stick. In order to prevent any downtime I kept my original z wave network up and ran a docker version of Z Wave JS UI with my new controller. This way I could add device by device without having any devices down. I finally moved all the devices over to my new stick today. The final step was to migrate everything from my Docker instance of Z Wave JS UI to the HA add-on of Z Wave JS UI. However during this migration some of the names didn't populate correctly which I later managed to import back into Z Wave JS UI. The issue was in Reactor it is stuck on the default names and the entities are not updating. I removed the controller from Reactor, restarted, hard refreshed, and added the controller back however the new entity names have not updated. Also it seems like the old entities from my previous instance of Z Wave JS UI are lingering and not being marked as dead (I believe a certain amount of time needs to lapse before they're marked as dead in Reactor). My goal is to basically purge all the entities for the 'ZWaveJS' controller in Reactor so it can pull all the updated entity names and only the entities that exist in Z Wave JS UI. I cannot find a quick way to do this, I know entities can be deleted one by one, but with over 100 entities this would take long I am guessing that if I added the controller with a new name in in the Reactor config it would pull the updated entities and names but I think that would break my rules since the entity IDs would change (I made sure to name all the entities the exact same as they were previously to prevent this issue).
Multi-System Reactor
Strange behavior for MQTT templates using payload and attributes
therealdbT
Topic thumbnail image
Multi-System Reactor
[MSR] reactor-mqtt-contrib package for additional MQTT templates
therealdbT
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only). Anyway, here's my reactor-mqtt-contrib package: https://github.com/dbochicchio/reactor-mqtt-contrib Simply download yaml files (everything or just the ones you need) and you're good to go. I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them. The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression. Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests
Multi-System Reactor
HA 2025.9.4 Supported Yet?
CatmanV2C
Tangentially did I miss 2025.9.4 getting blessed in MSR? I've been holding off Cheers C
Multi-System Reactor
The reaction stopped working (Google Nest max playing a video)
F
Topic thumbnail image
Multi-System Reactor
Rule Set UI bug - RESOLVED
3
Topic thumbnail image
Multi-System Reactor
[Reactor] Copy&Paste of Rules
therealdbT
I don't know if I'm the only one, but managing more than one Reactor installs, the need to have some sort of copy&paste for rules has grown on me. While I understand the technical challenges, I'm wondering if a "god mode" where I could copy the raw JSON rule and paste it into another rule could be an advanced, flag only feature that could benefit power users. I know I can copy the JSON file and proceed, but I must stop Reactor and when doing maintenance, it's more clicks to do. Just an idea
Multi-System Reactor
[Reactor] Help with screne controller cycling logic
therealdbT
I’ve added a couple of Shelly Wave i4 as scene controllers and I’m planning to add more, since I can just use standard buttons instead of battery-powered scene controllers, which also looks better aesthetically. That said, I’m struggling to figure out how to write a simple rule that cycles between states every time I press a button. Example: Light 1 ON → OFF, then Light 2 ON → OFF. The part I can’t get right is handling the case where Light 1 or Light 2 might already be ON independently of the rule. Maybe it’s just too much sun and relaxation clouding my brain, but any hint would be appreciated.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor
Expose MSR entities
CatmanV2C
Probably a really dumb question. Currently I am using the owntracks_sensor for tracking phones being in region in MSR and it works great. Digging around with Home Assistant and toying with some dashboards, is there any way of exposing that sensor to HA trivially? I could set MSR to trip a virtual switch in OpenLuup which can then be exposed to HA (with all my other Vera devices) but that feels a bit in-elegant if I can do it directly. Any thoughts? Apologies if the ask is not clear/ TIA C
Multi-System Reactor
Comment in Globa Expressions
Tom_DT
I have several Global Expressions that are set by a rule so the definition area is blank. I'd like to add a comment in this area that explains what is setting the value. Commenting in this area breaks the remote setting. Any way to document what is setting the GE?
Multi-System Reactor
Little Bobby tables...
CatmanV2C
...is back.... https://arstechnica.com/google/2025/08/researchers-use-calendar-events-to-hack-gemini-control-smart-home-gadgets/?utm_source=facebook&utm_medium=social&utm_campaign=dhfacebook&utm_content=null&fbclid=IwY2xjawMBq-pleHRuA2FlbQIxMQABHlSqIalzbz1IxcJFzlw8GBE6nC3FwvxcHgR370nJhogU6JjqbmRxG-lysqgh_aem_lx9XboYFKw9tpHnedGQKUA C
General Discussion
Home Assistant Voice TTS is Easy
toggledbitsT
Topic thumbnail image
Home Assistant
Play Audio through Home Assistant Voice Unit
toggledbitsT
Topic thumbnail image
Home Assistant
Home Assistant Voice
CatmanV2C
Has anyone had a play with the local voice control for HA? I've got one on order because... https://www.home-assistant.io/voice-pe/ C
Home Assistant
Unofficial thread for compatibility
tunnusT
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well. As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API. Updates: (the latest versions first in the list) OK: build "latest-25264-2fbe9217" with Hubitat C-8 platform v. 2.4.3.123
Multi-System Reactor
About
Posts
21
Topics
4
Shares
0
Groups
0
Followers
0
Following
1

Posts

Recent Best Controversial

  • Move Reactor from Docker to Home assistant plugin
    H HansW

    @toggledbits I installed the reactor plugin on the advice in the manual,

    Could you please give me an advice here?

    Warm regards,

    Hans

    Multi-System Reactor

  • Move Reactor from Docker to Home assistant plugin
    H HansW

    I just installed the Reactor plugin for home assistant and tried to move my configuration by copying the reactor-data files to the same location in the home assistant files. Unfortunately this does not work.

    I tried rebooting, restarting but the reactor in home assistant stays clean. I tried adding some rules, they do stick but I soo no difference in the reactor-files.

    I guess I am missing something very obvious???

    No idea what however.... So I would appreciate some pointers.

    Warm regards

    Hans

    Multi-System Reactor

  • MSR UI not working on iPhone
    H HansW

    Aha, problem solved! Hitting the menu icon in the right top corner toggles the screen.

    Multi-System Reactor

  • MSR UI not working on iPhone
    H HansW

    Hey guys,

    is there a bug in the UI of MSR (and also in the history pane of HASS btw) or do I have an issue with my iPhone? Or am I the only iPhone 12 min user which seems unlikely.

    I cannot use MSR on my iPhone, the right pane does not show up on the screen, just the left pane. This is the same on chrome and safari, also when I hold the phone horizontally.

    I can simulate this on the MacBook when I crop the safari window.

    Multi-System Reactor

  • Device information in string or array
    H HansW

    Thanks a lot for your elaborate answer and explanation @toggledbits! I do appreciate this and it helps me further, also with other issues, to make better use of your wonderful tool! I was not aware of this ${{ }} construction and I have no idea from which language this syntax is but I guess it forces the bit in between to be evaluated.

    Anyway, it solved the problem! Thanks a lot!!

    Multi-System Reactor

  • Device information in string or array
    H HansW

    Thanks @toggledbits , the variables I showed you in my earlier post and I corrected them zo they evaluate properly now into a string DeviceTrackerMessage which holds the friendly name of the devices offline, separated with comma's. As a string it does not have "" around it.

    My rule has a lot of Entity Attribute checks of all devices checked on x_hass.state <> home and combined into an OR.

    Then as a constraint I check the Variable Value DeviceTrackerMessage <> ""

    And then the Set Reaction holds:

    Entity Action hass>system x_hass_system.call_service with service: notify.my_device and the data: holding
    { "title": "Some devices failed: ", "message": XXXXX }

    Where on the position of XXXX I tried all I could think of.

    I know the rule might not be perfect yet but just testing the Set Reaction should generate a message. When replacing the XXXX with "test" I get a message.

    Also I tried adding a variable called JSONString and populating that using to JSON but I cannot get the result to look like a JSON string nor to work.

    Hope this helps.....

    Multi-System Reactor

  • Device information in string or array
    H HansW

    Thanks again for your help @toggledbits. I had been looking at the wrong place (in HASS) for the entities but your pointer was a great help also for other uses of reactor. The expressions are working like a charm now.

    Still having trouble getting the JSON correct using the Variable though. I am using the x_hass_system.call_service and whatever I try it fails.

    The string looks like:
    { "title": "The following devices fail: ", "message": XXXX } Where at the location of the XXXX I probably need a trick to insert the DeviceTrackerMessage with surrounding double quotes but I don't have a clue.

    I even tried building the JSON into a global variable but it looks like the escape characters do not work or maybe I overlook something obvious.

    Multi-System Reactor

  • Device information in string or array
    H HansW

    Well, I have been trying to use the above example to get a message reporting LAN connectivity failure of devices in my network.

    So I have set up an array with devices the Global expressions named DeviceTrackerList:

    ['hass>device_tracker_airport_time_capsule_van_hw','hass>device_tracker_airport_time_capsule_van_hw','hass>device_tracker_akita','hass>device_tracker_altherma_lan_adapter','hass>device_tracker_ap_bijkeuken' etc] 
    

    Then I run into problems defining the loop into a variable DeviceTrackerNotHome:

    each id in DeviceTrackerList:getEntity( id).state == not_home ? id: null
    

    Which returns the entire list. I have tried a few dozen of other options but either the entire list or an empty list is returned. Obviously my .state does not do the trick but what is the correct syntax to use here? (And where could I have found that myself?...)

    Then the next step is to use the names of the failing devices in a message.

    My last global variable is named DeviceTrackerMessage and holds

    join(each id in DeviceTrackerNotHome:getEntity(id).name, ', ')
    

    which returns a nice list of friendly names but I have no idea how to use that in my message.

    I expected { "message": {DeviceTrackerMessage} } to work but it did not and all other attempts to construct something failed as well.

    So I do hope someone can help here to point out to me what is probably obvious but difficult for a novice user to see. 🙂

    Multi-System Reactor

  • Sending HASS notifications from MSR
    H HansW

    @toggledbits said in Sending HASS notifications from MSR:

    and sys_system from the capabilities

    Thanks, that did it!

    Multi-System Reactor

  • Sending HASS notifications from MSR
    H HansW

    @toggledbits Well, I have 21257 running now but still no hass>system entity... Only hass>controller. Should I enable something somewhere?

    Multi-System Reactor

  • Sending HASS notifications from MSR
    H HansW

    @toggledbits said in Sending HASS notifications from MSR:

    It should be 21257

    Thanks. It turns out that to upgrade a container on a QNAP you need to delete the old container first, than delete the image (which is locally stored as well) through the image menu and after that you can create a new image which will than all the real latest from the docker hub. Just specifying to get it from docker hub like I did the first time did not work, it used the locally stored image anyway.

    Multi-System Reactor

  • Sending HASS notifications from MSR
    H HansW

    @toggledbits And as an addition question on this new feature, is there any way to get for instance the friendly name of the trigger into the parameter section? I have for instance 9 doors which I would like to combine into one rule where, if one of them opens or closes, I get a message which tells me which door was opened/closed. It is not a big deal of course, I could easily have 9 rules but still would be nice also for other situations reporting temperatures and such.

    Multi-System Reactor

  • Sending HASS notifications from MSR
    H HansW

    @toggledbits, I tried but the hass>system entity is not there. I do have a hass>controller entity but no action to choose from. I am running your container on a qnap though so maybe selecting the latest build had no effect since you didn't rebuild that version? Or I did not manage to update the image in the right way. What I did was stopping the image, creating a new one using the latest-genereric-amd64 build and than starting that new image. It reports: Reactor (Multi-hub) latest-21243-a5028fc

    Multi-System Reactor

  • Sending HASS notifications from MSR
    H HansW

    @toggledbits holy cow, you are fast! I am going to try this out!

    Multi-System Reactor

  • Sending HASS notifications from MSR
    H HansW

    Yes I mean HASS native push messages to my iPhone. I would ;ike to stay with MSR for my automation instead of diving into the complexity of HASS automation, templates and blueprints but the notify action of MSR is limited to alert, email, prowl, pushover, syslog, callmebot and telegram. I would like to use the native messages and its different interruption levels

    Multi-System Reactor

  • Sending HASS notifications from MSR
    H HansW

    Hello anyone,

    is there a simple trick to send native HASS notifications from MSR? I guess I could call a scene or something with some parameters but I have little experience so would need some clear pointers on this. Thanks in advance!

    Multi-System Reactor

  • Error importing backup from vera
    H HansW

    Thank, I will give it a spin and see where it leads me too!

    Multi-System Reactor

  • Error importing backup from vera
    H HansW

    I am trying to get rid of my Vera and moving to HA on Qnap.

    It has been quite a challenge up to now especial since I have a NX584 so needed to set up a separate Pi for that but I keep on it.

    My NX584 used to set the house modes and your reactor took care of the lights and the heating.

    The house modes were nice although I would have preferred something more fancy like:

    At home daylight
    At home dark
    At home alarm on
    Away alarm on

    Multi-System Reactor

  • Error importing backup from vera
    H HansW

    Aha, I should have been able to figure that out myself but I had no idea that option existed. Thanks anyway, I just imported the file and it worked!

    Thanks for your excellent work, your software is very intuitive as compared to others.

    Is there any advice or good practice for replacing the vera house modes?

    Multi-System Reactor

  • Error importing backup from vera
    H HansW

    Aha, thanks for your swift response! Any pointer to which file(s) to use? There are a few hundred of them and multiple with Reactor in the name..

    Multi-System Reactor
  • Login

  • Don't have an account? Register

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