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. [Solved] 22337 ignoring "not between"?
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

[Solved] 22337 ignoring "not between"?

Scheduled Pinned Locked Moved Multi-System Reactor
9 Posts 2 Posters 377 Views 2 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 gwp1
    #1

    This is an old, well-established rule. It controls the ceiling fan in the LR. I don't want the fan running between the hours of 19:00 and 23:55 each evening so I have this condition:

    66427999-2bf7-4deb-9f13-96806489750d-image.png

    It's part of the larger:
    397a1bf8-5c6b-4a4c-aee9-b7cfc2999ad0-image.png

    If you look closely at the timebox rule you'll see it's set to not between and the time is definitely "between".

    Is it me or is MSR ignoring the NOT in not between?

    *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 toggledbits
      #2

      The condition time shown is 10:58:00PM. That is between 7:00pm and 11:55pm, so between would be true, and not between would be false, which it is (the condition result is false).

      What am I missing?

      Edit: if you're trying to figure out why the fan is running, it's because the Heating group is true... it's an OR between Cooling and Heating, so either being true will make the trigger overall true. The date comparison isn't even part of the logic for Heating. If the date comparison applies to both heating and cooling, it's in the wrong place, wrong logic.

      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

        The condition time shown is 10:58:00PM. That is between 7:00pm and 11:55pm, so between would be true, and not between would be false, which it is (the condition result is false).

        What am I missing?

        Edit: if you're trying to figure out why the fan is running, it's because the Heating group is true... it's an OR between Cooling and Heating, so either being true will make the trigger overall true. The date comparison isn't even part of the logic for Heating. If the date comparison applies to both heating and cooling, it's in the wrong place, wrong logic.

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

        @toggledbits The not between should fail the rule because the time IS between and the fan should NOT be operating.

        I'm using not between essentially as "except during these times".

        *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
          #4

          Did you see my edit on my original reply?

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

          G 2 Replies Last reply
          0
          • toggledbitsT toggledbits

            Did you see my edit on my original reply?

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

            @toggledbits Just now, after I hit submit - reviewing.

            *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

              Did you see my edit on my original reply?

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

              @toggledbits well, shahzbaht as a famous Orkan used to say.

              This must have been wrong over a year ago and sat there dormant because of warmer seasons. Crazy timing, just after I updated to the latest release.

              Changed or to and at the topmost level and the fan has, indeed, stopped.

              I posted hoping an extra set of eyes would see... something... and you did. Thank you for your rapid response and infinite patience, Patrick.

              *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
              1
              • G gwp1

                @toggledbits well, shahzbaht as a famous Orkan used to say.

                This must have been wrong over a year ago and sat there dormant because of warmer seasons. Crazy timing, just after I updated to the latest release.

                Changed or to and at the topmost level and the fan has, indeed, stopped.

                I posted hoping an extra set of eyes would see... something... and you did. Thank you for your rapid response and infinite patience, Patrick.

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

                @gwp1 Just changing to AND at the top level probably isn't right, either, I think, as that would require both Heating and Cooling to be true at the same instant... can they? Should they? If not, that date condition needs to moved to the top level and the rest restructured accordingly.

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

                G 2 Replies Last reply
                0
                • toggledbitsT toggledbits

                  @gwp1 Just changing to AND at the top level probably isn't right, either, I think, as that would require both Heating and Cooling to be true at the same instant... can they? Should they? If not, that date condition needs to moved to the top level and the rest restructured accordingly.

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

                  @toggledbits Thanks for surfacing that. I fell asleep mulling this last night. Based on my Comments within the ruleset it looks like I'd originally intended for this timebox to only impact Cooling, at which point everything is actually WAI.

                  I am going to need to adjust this if I want the timebox to impact BOTH Heating and Cooling, you're right.

                  *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

                    @gwp1 Just changing to AND at the top level probably isn't right, either, I think, as that would require both Heating and Cooling to be true at the same instant... can they? Should they? If not, that date condition needs to moved to the top level and the rest restructured accordingly.

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

                    @toggledbits

                    This seems more appropriate. The timebox AND the OR group for Heating vs Cooling with the individual Heating and Cooling groups nested within.

                    f9a1a1ce-99a4-4b90-b325-7b916c0f357b-image.png

                    Edited with the updated version.

                    *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 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
                      31

                    • Error After Upgrade
                      G
                      gwp1
                      0
                      4
                      103

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

                    • 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
                      918

                    • 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