Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. Change instruction in Dome DMS01 device
[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
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
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
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.
Multi-System Reactor
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Can't customize home page
G
I foolishly let my system wipe all cookies this morning and with it my settings for my MSR home page. Once logged back in I can no longer remove errant panes nor is the + available to add new ones. Brave Browser v1.80.122 (Jul 16, 2025) What have I done?! Will check other browsers on my M1. UPDATE: Safari exhibits same behaviour. I've tried both sans last-four public key entry and with - no change.
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
Multi-System Reactor
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor

Change instruction in Dome DMS01 device

Scheduled Pinned Locked Moved Multi-System Reactor
8 Posts 2 Posters 475 Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • wmarcolinW Offline
    wmarcolinW Offline
    wmarcolin
    wrote on last edited by
    #1

    Hi,

    I do not know the community can help but here is the request 😁.

    I have a Dome DMS01 device to have sound alerts. To operate it has an APP installed, Dome Chime that calls one of 10 types of sounds by a panel.

    9ae09d5f-f41c-4515-bd2f-81c2cb72b646-image.png

    d5dff783-16f1-4ed5-888d-11c0ff5d204d-image.png

    To use it with Reactor, I had to create a scene for each sound, which Reactor calls and triggers the sound/chime. I would like to check if there is a way to make this call directly from MSR, without going through this ugly scene path.

    I already changed the configuration variable, but it only changes what is stored in the Vera, it doesn't change the data in the device, so it doesn't change the bell.

    024a8634-c43f-461e-9a86-d5c1df56c8b2-image.png

    When using the reconfiguration instruction (x_vera_svc_micasaverde_com_HaDevice1. Reconfigure), it shows an error message and does not make the change.

    d58bb0e3-eaea-4600-86d3-d3a93bbde385-image.png

    Manual info: http://manuals-backend.z-wave.info/make.php?lang=en&sku=DMS01&cert=ZC10-17015372

    In short, I want to do in the MSR the same thing that this APP does.

    If anyone can help, I appreciate.

    1 Reply Last reply
    0
    • toggledbitsT Offline
      toggledbitsT Offline
      toggledbits
      wrote on last edited by toggledbits
      #2

      OK. So first, you're not telling us how your Vera scene works, so I can't be more detailed in the reply here, but...

      Changing VariablesSet does nothing on the device immediately.

      The usual way to change configuration parameters on the fly (on both Vera and in MSR) is to use a direct ZWave send data with the necessary byte string for setting configuration parameters. This goes immediately to the device, as opposed to modifying the state variable (directly or via the UI) which won't do anything until the device is next configured.

      In MSR, use the zwave_network.send_data action on Vera device #1, which is on the ZWave network parent device for all ZWave devices on Vera (search your MSR entities for the entity with ID device_1). You need to know the ZWave node number (not device number) of the Dome Chime, and the a configuration parameter format (again, no info about how you did it in your scene, so I can't be more detailed here). The general form of the data to be sent for setting a configuration variable is: x70 4 n s b... where the x70 is the Zwave configuration command class, 4 is the set command, n is the parameter number (0-255), s is the number of bytes in the value (1, 2 or 4), and b... is one, two or four byte values separated by a space (just like the rest of it). So, for example, to set parameter 5 to the single byte value 10, you would send x70 4 5 1 10.

      84a438bd-25c2-4d1b-8dae-30da9f883ae1-image.png

      Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

      wmarcolinW 1 Reply Last reply
      1
      • toggledbitsT toggledbits

        OK. So first, you're not telling us how your Vera scene works, so I can't be more detailed in the reply here, but...

        Changing VariablesSet does nothing on the device immediately.

        The usual way to change configuration parameters on the fly (on both Vera and in MSR) is to use a direct ZWave send data with the necessary byte string for setting configuration parameters. This goes immediately to the device, as opposed to modifying the state variable (directly or via the UI) which won't do anything until the device is next configured.

        In MSR, use the zwave_network.send_data action on Vera device #1, which is on the ZWave network parent device for all ZWave devices on Vera (search your MSR entities for the entity with ID device_1). You need to know the ZWave node number (not device number) of the Dome Chime, and the a configuration parameter format (again, no info about how you did it in your scene, so I can't be more detailed here). The general form of the data to be sent for setting a configuration variable is: x70 4 n s b... where the x70 is the Zwave configuration command class, 4 is the set command, n is the parameter number (0-255), s is the number of bytes in the value (1, 2 or 4), and b... is one, two or four byte values separated by a space (just like the rest of it). So, for example, to set parameter 5 to the single byte value 10, you would send x70 4 5 1 10.

        84a438bd-25c2-4d1b-8dae-30da9f883ae1-image.png

        wmarcolinW Offline
        wmarcolinW Offline
        wmarcolin
        wrote on last edited by wmarcolin
        #3

        @toggledbits Hola Patrick
        The scene is a pretty simple thing, I call the APP and tell it from 1 to 10 which sound I want to run.

        5347d860-4f05-453b-bd63-2f4be2cddb93-image.png

        fa59bbfa-dfa4-4a78-b294-32470e5d47e5-image.png

        Now I think my error is in one detail of your instruction "You need to know the ZWave node number (not device number) of the Dome Chime". I am using the device number, your student master doesn't know where to find the node number 😞

        9d08bb23-5e1f-4224-a29d-0daaa9b1b2af-image.png

        1 Reply Last reply
        0
        • toggledbitsT Offline
          toggledbitsT Offline
          toggledbits
          wrote on last edited by toggledbits
          #4

          The ZWave node number can be found in MSR on the Entities screen, just go to the device, click the device name to open its details, and look for zwave_device.node_id

          You may need a little delay between setting the config parameter and turning the device on, too. Commands to devices are asynchronous, so MSR isn't waiting for the command to finish on the Vera. It just sends it and moves on.

          Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

          wmarcolinW 1 Reply Last reply
          0
          • toggledbitsT toggledbits

            The ZWave node number can be found in MSR on the Entities screen, just go to the device, click the device name to open its details, and look for zwave_device.node_id

            You may need a little delay between setting the config parameter and turning the device on, too. Commands to devices are asynchronous, so MSR isn't waiting for the command to finish on the Vera. It just sends it and moves on.

            wmarcolinW Offline
            wmarcolinW Offline
            wmarcolin
            wrote on last edited by
            #5

            @toggledbits

            Well, the NodeID I know as AltID, so I used the correct number.

            0bcf2aea-d0fa-40c5-ab32-1b0a72a73b9f-image.png

            But no effect, I can't change parameter 5.

            So I decided to go back and use our good Reactor, and look at the error screen that is popping up.

            a795cc11-05d0-4726-9330-aae9aaa96c98-image.png

            According to this more technical manual we are sending the correct parameters: https://cache-m2.smarthome.com/manuals/12026-manual.pdf

            1 Reply Last reply
            0
            • toggledbitsT Offline
              toggledbitsT Offline
              toggledbits
              wrote on last edited by toggledbits
              #6

              In your first post, you had a screen shot with a configuration error for the device. That may prevent it being configured and cause the 400 error you are seeing. You need to square the device away first using the "Device Options" in the Vera UI. Once you can get it configured without errors, then try your tests again.

              Wait... no you're using the wrong device for the Send Data. You MUST use ZWave Network device #1. Remember my instructions... find the entity with ID device_1. On Vera Reactor, you must do the same, using the device "ZWave (#1)".

              Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

              wmarcolinW 1 Reply Last reply
              1
              • toggledbitsT toggledbits

                In your first post, you had a screen shot with a configuration error for the device. That may prevent it being configured and cause the 400 error you are seeing. You need to square the device away first using the "Device Options" in the Vera UI. Once you can get it configured without errors, then try your tests again.

                Wait... no you're using the wrong device for the Send Data. You MUST use ZWave Network device #1. Remember my instructions... find the entity with ID device_1. On Vera Reactor, you must do the same, using the device "ZWave (#1)".

                wmarcolinW Offline
                wmarcolinW Offline
                wmarcolin
                wrote on last edited by wmarcolin
                #7

                @toggledbits YOU ARE A GENIUS!

                Direct command is not to the device, it is to ZWave#1

                845ff716-4f72-4da2-8d49-2714e88c0e30-image.png

                Another case closed for Super Patrick!!! Now fun for me, after 3 years I get rid of the ugly way of using the scenes to mediate the configuration of the bells.

                1 Reply Last reply
                2
                • toggledbitsT Offline
                  toggledbitsT Offline
                  toggledbits
                  wrote on last edited by
                  #8

                  No special powers, no cape. Just trying to make good of all the hours spent figuring things out... I can't get that time back, but I can share what it taught me.

                  Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                  1 Reply Last reply
                  1
                  • toggledbitsT toggledbits locked this topic on
                  Reply
                  • Reply as topic
                  Log in to reply
                  • Oldest to Newest
                  • Newest to Oldest
                  • Most Votes


                  Recent Topics

                  • [Reactor] Help with screne controller cycling logic
                    therealdbT
                    therealdb
                    0
                    3
                    74

                  • Stop the MSR by an external switch on Hubitat.
                    wmarcolinW
                    wmarcolin
                    0
                    4
                    182

                  • [Reactor] Variables not updating correctly in latest-25201-2aa18550
                    tunnusT
                    tunnus
                    0
                    22
                    597

                  • Expose MSR entities
                    CatmanV2C
                    CatmanV2
                    0
                    11
                    134

                  • Comment in Globa Expressions
                    CrilleC
                    Crille
                    1
                    2
                    132

                  • Little Bobby tables...
                    CatmanV2C
                    CatmanV2
                    0
                    3
                    110

                  • Home Assistant Voice TTS is Easy
                    CatmanV2C
                    CatmanV2
                    0
                    3
                    166

                  • Play Audio through Home Assistant Voice Unit
                    toggledbitsT
                    toggledbits
                    1
                    1
                    103

                  • Home Assistant Voice
                    CatmanV2C
                    CatmanV2
                    0
                    21
                    782

                  • Unofficial thread for compatibility
                    tunnusT
                    tunnus
                    2
                    1
                    107

                  • Gradually turn on lights.
                    toggledbitsT
                    toggledbits
                    0
                    21
                    979

                  • Reactor (Multi-System/Multi-Hub) Announcements
                    toggledbitsT
                    toggledbits
                    5
                    123
                    56.1k
                  Powered by NodeBB | Contributors
                  Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                  • Login

                  • Don't have an account? Register

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