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

kfxo

@kfxo
[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
80
Topics
6
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Integrate UPS with MSR
    K kfxo

    @toggledbits said in Integrate UPS with MSR:

    Fixed now, 22152 build of NUTController available for download.

    Confirmed fixed. Thanks.

    Multi-System Reactor

  • Integrate UPS with MSR
    K kfxo

    @toggledbits

    Getting this error in the log when restarting Reactor after performing the installation steps for NUT controller. I am on Reactor 22149 installed on Ubuntu in Docker.

    [latest-22149]2022-06-01T16:54:36.344Z <Structure:INFO> Structure#1 loading controller interface nut (NUTController)
    [latest-22149]2022-06-01T16:54:36.345Z <Controller:CRIT> Controller: failed to load nut implementation /var/reactor/ext/NUTController/NUTController.js: [TypeError]TypeError: Incompatible base version; is 22125, requires at least 22145
    [latest-22149]2022-06-01T16:54:36.346Z <Controller:CRIT> TypeError: Incompatible base version; is 22125, requires at least 22145
    TypeError: Incompatible base version; is 22125, requires at least 22145
        at Function.requires (/opt/reactor/server/lib/Controller.js:327:19)
        at Object.<anonymous> (/var/reactor/ext/NUTController/NUTController.js:9:53)
        at Module._compile (node:internal/modules/cjs/loader:1103:14)
        at Object.Module._extensions..js (node:internal/modules/cjs/loader:1157:10)
        at Module.load (node:internal/modules/cjs/loader:981:32)
        at Function.Module._load (node:internal/modules/cjs/loader:822:12)
        at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:168:29)
        at ModuleJob.run (node:internal/modules/esm/module_job:197:25)
        at async Promise.all (index 0)
        at async ESMLoader.import (node:internal/modules/esm/loader:337:24)
    [latest-22149]2022-06-01T16:54:36.346Z <Structure:ERR> Structure#1 controller nut (NUT) skipped, implementation could not be loaded.
    

    edit: Fixed in build 22152. See below.

    Multi-System Reactor

  • Integrate UPS with MSR
    K kfxo

    @toggledbits said in Integrate UPS with MSR:

    I use NUT on Linux (and I have a Reactor controller for it that I can publish). I know nothing about it on Windows.

    I would be interested in trying out the NUT controller if you publish.

    Multi-System Reactor

  • Strange MSR behaviours after NAS reboots
    K kfxo

    @snowman said in Strange MSR behaviours after NAS reboots:

    Interestingly, everything seems to be working like it should even if I don't do anything. Which is weird.

    So everything ends up working but the visual errors persist? It would be unsettling seeing all those errors even though it works fine.

    Software

  • Strange MSR behaviours after NAS reboots
    K kfxo

    My guess would be that home assistant is still loading when MSR starts and MSR is not seeing all the entities initially.

    Software

  • Urgent Help MSR stopped running
    K kfxo

    Not sure what else to try as you already commented out the Influx. Maybe back up your MSR files and try a fresh install.

    Multi-System Reactor

  • Urgent Help MSR stopped running
    K kfxo

    The logs dont say anything else? If not I dont know and you might have to wait for @toggledbits

    Multi-System Reactor

  • Urgent Help MSR stopped running
    K kfxo

    Maybe the logs will have a clue? The other day I moved HA to a new computer and MSR was trying to connect to the old machine and MSR would not load. Sure enough the logs indicated that MSR could not connect to HA. Fixed that and all was well.

    Multi-System Reactor

  • Re-number on OpenLuup
    K kfxo

    Is it marked as failed in z-wave (z-way?) server? If you can reset the device without excluding it, I think you can use the replace failed node operation on the z-way server control section.

    General Discussion

  • Is it possible for MSR to act on Nest hello (doorbell pressed)?
    K kfxo

    This is off topic to the original post so maybe it should be moved but it is directed towards the Home Assistant event_targets discussed above.

    I defined an event_target in my system for emulated roku that looks like this:

        event_targets:
          "LR_Emulated_Roku_Home_Keypress":
            name: "LR Emulated Roku Home Keypress"
            capabilities:
              - button
            events:
              - event:
                  event_type: "roku_command"
                  data:
                    source_name: "LR_Roku"
                    type: "keypress"
                    key: "Home"
                response:
                  "button.since":
                    expr: "time()"
                  "button.state": true
    

    This works great, detects the event and stores the time and True in the respective button entity attributes. However upon restarting MSR the values of the button entity attributes clear to null (e.g. button.since=null).

    Is this expected behavior or should these values be maintained on restart?

    Multi-System Reactor

  • Is it possible for MSR to act on Nest hello (doorbell pressed)?
    K kfxo

    I was messing around with this and I think there is an indentation issue starting at line 8. See below for what indentation worked for me.

          event_targets:    # this section starts the event-receiving entities
            "my_virtual_entity_id":     # Assign an ID to your entity; each entity must have a unique ID
              name: "My Entity Name"   # This is optional but recommended, so you have a friendly name
              capabilities:  # define an array of capabilities to be modified by the event
                - capability_name    # first capability
                - capability_name    # second, etc., as many as you need, but always at least ONE
              events:  # define an array of events that modify capability attributes on the entity
                - event:  # start of an event; each element of the events array begins this way
                    event_type: "type of HomeAssistant event"
                    data:  # optional section, if further matching to the event data is required
                      data_field: "data_value"    # data field to be checked/matched to data_value
                      data_field: "data_value"    # as many as you need, but each data_field must be unique
                  response:  # begin the (required) response section for handling the event
                    "capability.attribute":
                      expr: "expression"   # expression to get attribute value from event data
                      # repeat "capability.attribute" section for all attributes modified by the event
    
    Multi-System Reactor

  • Is it possible for MSR to act on Nest hello (doorbell pressed)?
    K kfxo

    It appears from the Nest- Home Assistant docs that the doorbell generates a nest_event (doorbell_chime). Unfortunately I do not believe there is any way for MSR to see these events. I have brought this up previously with respect to Emulated Roku. My work around is to use a native HA automation to detect the event and trigger a helper object that MSR can see, in my case I place the text of the event in a input_text helper which MSR can see.

    Multi-System Reactor

  • Change in Plans (Don't Panic)
    K kfxo

    @toggledbits said in Change in Plans (Don't Panic):

    Maybe once I get the ZWaveJS interface fleshed out

    Curious about progress on this. I was just messing around with ZwaveJS today and was thinking of utilizing it to move all my zwave devices from openluup+zway to HA+ZwaveJS. Obviously a direct ZwaveJS interface to MSR would be optimal.

    Also is there any plans of a tool that might allow us to swap an entity reference in the rules? Moving zwave devices to ZwaveJS would require going through all MSR rules one by one and remapping to reference the ZwaveJS entity instead of the openluup entity.

    Multi-System Reactor

  • Universal Remote Control
    K kfxo

    @catmanv2 I have been keeping an eye on this project. Looks promising. I hope they deliver.

    General Discussion

  • Let's talk about MSR-provided Virtual Devices... NOT!
    K kfxo

    I could definitely see it being useful for dashboards and also if an integrated controller does not provide the ability to create a virtual device.

    Multi-System Reactor

  • Let's talk about MSR-provided Virtual Devices... NOT!
    K kfxo

    @toggledbits So what would be the difference between MSR provided Virtual Devices and expressionless variables? Do you envision interacting with the virtual devices in MSR? Right now I use expressionless variables whenever I need to keep track of some value and I have no intention of needing to modify the value outside of logic. I use virtual devices both in openluup and HA when I intend to physically interact to change the value (or I have no other way of getting the value into MSR..cough cough HA event data generated by integrations that are not reflected in entities). I guess I am not seeing why MSR would need Virtual Devices to act as data containers when MSR already has data containers with expressionless variables.

    Multi-System Reactor

  • Moving to Docker
    K kfxo

    There is a post from me above in this thread (sorry don't know how to link specific post) that explains how I got it to work. Have you tried that? I think the issue is synology gui does not support the correct type of volumes and you have to ssh into synology and run the correct docker command to set it up.

    Docker

  • Moving to Docker
    K kfxo

    I think I had this same issue. If you copy the files in cmh-ludl from an existing openluup install into ' /OpenLuup/openluup-env' it should start right up.

    Docker

  • MSR on Synology without Docker
    K kfxo

    I am using virtual machine manager on synology to host a Debian 10 VM. Works well.

    Multi-System Reactor

  • Feature Request: Hass service call action
    K kfxo

    @toggledbits Success! When pasting into Notepad++ I had to edit the line endings to (LF) and I also had to change the ID from "hass>media_player.lr_mibox" to "hass>media_player_lr_mibox".

    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