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. every X days field uneditable
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
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
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
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 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
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor

every X days field uneditable

Scheduled Pinned Locked Moved Multi-System Reactor
11 Posts 3 Posters 583 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.
  • G Offline
    G Offline
    gwp1
    wrote on last edited by
    #1

    Wasn't able to create a Mantis ticket on this.

    Attempted to add a month range to a ruleset and it seems the first field every X days is not editable. The rest are fine.

    msr_field_unselectable.png

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

    *HASS 2025.6.0
    w/ ZST10-700 fw 7.18.3

    *Prod MSR in docker/portainer
    MSR: latest-25139-fbd67abc
    MQTTController: 25139
    ZWave Controller: 25139

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

      Set hours to zero first.

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

      G 1 Reply Last reply
      0
      • toggledbitsT toggledbits

        Set hours to zero first.

        G Offline
        G Offline
        gwp1
        wrote on last edited by gwp1
        #3

        @toggledbits Ok, that opened it up - thank you.

        Maybe I'm using this incorrectly, however. I want to create a ruleset that is only in effect from October thru March annually between certain hours each day during that period.

        2200 - 0600 ET daily, 10/01 - 03/31 annually.

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

        *HASS 2025.6.0
        w/ ZST10-700 fw 7.18.3

        *Prod MSR in docker/portainer
        MSR: latest-25139-fbd67abc
        MQTTController: 25139
        ZWave Controller: 25139

        toggledbitsT 1 Reply Last reply
        0
        • G gwp1

          @toggledbits Ok, that opened it up - thank you.

          Maybe I'm using this incorrectly, however. I want to create a ruleset that is only in effect from October thru March annually between certain hours each day during that period.

          2200 - 0600 ET daily, 10/01 - 03/31 annually.

          toggledbitsT Offline
          toggledbitsT Offline
          toggledbits
          wrote on last edited by toggledbits
          #4

          @gwp1 said in every X days field uneditable:

          I want to create a ruleset that is only in effect from October thru March annually

          Actually, you want to create a Rule. A RuleSet is a collection of Rules.

          Now, I have to read between the lines of your problem description a bit here, but I'm thinking you mean that you want a rule to trigger once per day from October to March? If that's the case, an Interval is not the way to go, IMO. I would use two Date/Time conditions in an AND group. The first condition would constrain the dates (i.e. "between 1 October and 1 April", assuming you want it to trigger throughout March"), and the second "after 00:00" (assuming you keep the default Follow output mode on the condition and its parent group). The second condition will only trigger once per day, whenever it can (i.e. if the system is down at midnight, it will trigger as soon as it comes back up).

          0401c845-9338-4a7d-a205-71a068db6ee2-image.png

          If you want the trigger to happen at some other time of day, say 10am, just put that in the Date/Time after condition instead of midnight.

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

          G 1 Reply Last reply
          0
          • toggledbitsT toggledbits

            @gwp1 said in every X days field uneditable:

            I want to create a ruleset that is only in effect from October thru March annually

            Actually, you want to create a Rule. A RuleSet is a collection of Rules.

            Now, I have to read between the lines of your problem description a bit here, but I'm thinking you mean that you want a rule to trigger once per day from October to March? If that's the case, an Interval is not the way to go, IMO. I would use two Date/Time conditions in an AND group. The first condition would constrain the dates (i.e. "between 1 October and 1 April", assuming you want it to trigger throughout March"), and the second "after 00:00" (assuming you keep the default Follow output mode on the condition and its parent group). The second condition will only trigger once per day, whenever it can (i.e. if the system is down at midnight, it will trigger as soon as it comes back up).

            0401c845-9338-4a7d-a205-71a068db6ee2-image.png

            If you want the trigger to happen at some other time of day, say 10am, just put that in the Date/Time after condition instead of midnight.

            G Offline
            G Offline
            gwp1
            wrote on last edited by
            #5

            @toggledbits I incorrectly correctly used ruleset as there will be a couple/three rules 🙂

            So if I want it on between two specific times I would update what you show to

            391940ce-4c22-4e91-94c2-00c7d215bfb6-image.png

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

            *HASS 2025.6.0
            w/ ZST10-700 fw 7.18.3

            *Prod MSR in docker/portainer
            MSR: latest-25139-fbd67abc
            MQTTController: 25139
            ZWave Controller: 25139

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

              Yes, this should work. Just be aware that since your second condition spans midnight, the rule will set at midnight on 10/1 and reset at midnight on 4/1.

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

              G 1 Reply Last reply
              0
              • toggledbitsT toggledbits

                Yes, this should work. Just be aware that since your second condition spans midnight, the rule will set at midnight on 10/1 and reset at midnight on 4/1.

                G Offline
                G Offline
                gwp1
                wrote on last edited by
                #7

                @toggledbits what would be a better approach to ensuring it starts at 2200 EDT on 10/01 and runs thru 0600 03/31?

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

                *HASS 2025.6.0
                w/ ZST10-700 fw 7.18.3

                *Prod MSR in docker/portainer
                MSR: latest-25139-fbd67abc
                MQTTController: 25139
                ZWave Controller: 25139

                tunnusT 1 Reply Last reply
                0
                • G gwp1

                  @toggledbits what would be a better approach to ensuring it starts at 2200 EDT on 10/01 and runs thru 0600 03/31?

                  tunnusT Offline
                  tunnusT Offline
                  tunnus
                  wrote on last edited by
                  #8

                  @gwp1 just using one date/time condition and adding start & stop times to the first condition?

                  Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT

                  G 1 Reply Last reply
                  0
                  • tunnusT tunnus

                    @gwp1 just using one date/time condition and adding start & stop times to the first condition?

                    G Offline
                    G Offline
                    gwp1
                    wrote on last edited by
                    #9

                    @tunnus would that not create the condition of starting at 2200 on 10/01 and staying on until 0600 04/01?

                    That's not what I'm after. I'm after a daily window of hours for those months.

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

                    *HASS 2025.6.0
                    w/ ZST10-700 fw 7.18.3

                    *Prod MSR in docker/portainer
                    MSR: latest-25139-fbd67abc
                    MQTTController: 25139
                    ZWave Controller: 25139

                    tunnusT 1 Reply Last reply
                    0
                    • G gwp1

                      @tunnus would that not create the condition of starting at 2200 on 10/01 and staying on until 0600 04/01?

                      That's not what I'm after. I'm after a daily window of hours for those months.

                      tunnusT Offline
                      tunnusT Offline
                      tunnus
                      wrote on last edited by tunnus
                      #10

                      @gwp1 you wrote "ensuring it starts at 2200 EDT on 10/01 and runs thru 0600 03/31?" so I got an impression you really wanted continuous operation. But if that's not the case, then why wouldn't those two conditions you showed in a screenshot (post #5) work? Have you tested that rule?

                      Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT

                      G 1 Reply Last reply
                      0
                      • tunnusT tunnus

                        @gwp1 you wrote "ensuring it starts at 2200 EDT on 10/01 and runs thru 0600 03/31?" so I got an impression you really wanted continuous operation. But if that's not the case, then why wouldn't those two conditions you showed in a screenshot (post #5) work? Have you tested that rule?

                        G Offline
                        G Offline
                        gwp1
                        wrote on last edited by
                        #11

                        @tunnus yes, the rule is working and @toggledbits indicated as such (that it would work) but he raised a potential issue regarding the crossing of midnight that I was asking about there being a better approach.

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

                        *HASS 2025.6.0
                        w/ ZST10-700 fw 7.18.3

                        *Prod MSR in docker/portainer
                        MSR: latest-25139-fbd67abc
                        MQTTController: 25139
                        ZWave Controller: 25139

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


                        Recent Topics

                        • Gradually turn on lights.
                          G
                          gwp1
                          0
                          4
                          132

                        • Stop the MSR by an external switch on Hubitat.
                          wmarcolinW
                          wmarcolin
                          0
                          1
                          30

                        • Error After Upgrade
                          G
                          gwp1
                          0
                          4
                          103

                        • Reset attribute value of entity in event handler
                          R
                          RHCPNG
                          0
                          5
                          201

                        • Need help figuring out how to delay a reset on reaction
                          G
                          gwp1
                          0
                          22
                          925

                        • Way to search for rules (rule state) in other rules
                          T
                          tamorgen
                          0
                          3
                          99

                        • Links to MSR from HA
                          Tom_DT
                          Tom_D
                          0
                          1
                          90

                        • Set Reaction > Script Action
                          wmarcolinW
                          wmarcolin
                          0
                          11
                          433

                        • Wiring Samotech SM308-S into light fitting
                          akbooerA
                          akbooer
                          0
                          2
                          146

                        • Errors after updating to MQTTController build 25139
                          toggledbitsT
                          toggledbits
                          0
                          6
                          236

                        • 🎉 My very first MSR controller: OpenSprinkler
                          therealdbT
                          therealdb
                          5
                          13
                          917

                        • Advice reqeusted to migrate MSR from Bare Metal to Container
                          T
                          tamorgen
                          0
                          5
                          260
                        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