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. MSR if you have only one system
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

MSR if you have only one system

Scheduled Pinned Locked Moved Multi-System Reactor
11 Posts 5 Posters 568 Views 5 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.
  • CatmanV2C Offline
    CatmanV2C Offline
    CatmanV2
    wrote on last edited by
    #1

    As above really

    Watching the MSR threads. Is there a benefit / should I look to move to MSR if I only have (and likely at this point only intend to have) one system (i.e. OpenLuup)

    Just curious, really

    C

    The Ex-Vera abuser know as CatmanV2.....

    1 Reply Last reply
    0
    • 3 Offline
      3 Offline
      3rdStng
      wrote on last edited by
      #2

      My vote is yes. I was/am running Vera, which we all know is slow and gets bogged down at times. Moving my Reactor for Vera off to its own docker was a huge performance lift in the Vera. I continued to move all of my scenes off next. I now have a Hubitat and Vera, but each are only there for control of the device itself. All my scenes, schedules, modes, etc. are all managed and run by MSR.

      1 Reply Last reply
      1
      • CatmanV2C Offline
        CatmanV2C Offline
        CatmanV2
        wrote on last edited by
        #3

        Yep, that makes sense.

        Except I don't have Vera. Everything I have is running in Reactor on an Intel NUC with OpenLuup on Debian....

        C

        The Ex-Vera abuser know as CatmanV2.....

        1 Reply Last reply
        0
        • 3 Offline
          3 Offline
          3rdStng
          wrote on last edited by
          #4

          I just noticed your signature line. That's funny. I realize you don't have Vera. For me though, getting all the routines and everything vendor neutral has made it super simple for me to move/migrate devices between hubs. And the family doesn't know. My only hold up right now is an easy to use and easy to configure dashboard. But I've got a plan for that. Just need to do a bulk migration one day of a group of sensors. I look forward to the day that MSR has its Dashboard running.

          MatohlM 1 Reply Last reply
          1
          • toggledbitsT Offline
            toggledbitsT Offline
            toggledbits
            wrote on last edited by toggledbits
            #5

            If you are using openLuup as a single system, that resolves many of the performance issues of the Vera itself (it makes an acceptable radio for the devices it can support, as we all know). There are pros and cons to moving to MSR in this kind of scenario.

            You are bridged, meaning there is a socket-based tunnel between the Vera and openLuup to get the Vera devices into openLuup. If you introduce MSR into the equation, then there are three possibilities: (1) you configure MSR to talk to the Vera directly, in which case MSR brings the Vera devices in and lets you run the rules, etc., but it can't see the openLuup devices (only relevant if there are other plugins/devices on openLuup that you need access to from MSR); (2) you configure MSR to talk to openLuup, in which case you have all of your Vera and openLuup devices available in MSR, but MSR is talking to the Vera devices over a bridge to openLuup that is talking to the Vera devices over the bridge to Vera (bridge to a bridge, not very efficient); (3) you connect MSR to both, in which case you have all the devices from both like #2, with the option of talking to the Vera devices more directly, but confusion may set in because all of the Vera devices will appear as both the native Vera entities and bridged openLuup entities -- every Vera device is listed in MSR once for its appearance on Vera and again for its appearance in openLuup.

            The biggest con to staying on the Reactor plugin (for Vera/openLuup) is that I have no further development planned for it. As new features go into MSR, I have no plans to "back port" them into R4V. As Vera is "walking dead", so is every Vera plugin, including R4V.

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

            CatmanV2C 1 Reply Last reply
            0
            • 3 3rdStng

              I just noticed your signature line. That's funny. I realize you don't have Vera. For me though, getting all the routines and everything vendor neutral has made it super simple for me to move/migrate devices between hubs. And the family doesn't know. My only hold up right now is an easy to use and easy to configure dashboard. But I've got a plan for that. Just need to do a bulk migration one day of a group of sensors. I look forward to the day that MSR has its Dashboard running.

              MatohlM Offline
              MatohlM Offline
              Matohl
              wrote on last edited by
              #6

              @3rdstng I have walked the HA route instead of Openluup. Vera for the devices that are supported by it and HA for the ones that are not supported by Vera. I have connected MSR directly to Vera and the same for HA to Vera which means I see them twice in MSR as described above which could sometimes lead to some confusion. However, I use MSR for all the rules and HA for its very flexible dashboards and support to devices that are not (and will not be) supported by Vera.

              1 Reply Last reply
              0
              • toggledbitsT toggledbits

                If you are using openLuup as a single system, that resolves many of the performance issues of the Vera itself (it makes an acceptable radio for the devices it can support, as we all know). There are pros and cons to moving to MSR in this kind of scenario.

                You are bridged, meaning there is a socket-based tunnel between the Vera and openLuup to get the Vera devices into openLuup. If you introduce MSR into the equation, then there are three possibilities: (1) you configure MSR to talk to the Vera directly, in which case MSR brings the Vera devices in and lets you run the rules, etc., but it can't see the openLuup devices (only relevant if there are other plugins/devices on openLuup that you need access to from MSR); (2) you configure MSR to talk to openLuup, in which case you have all of your Vera and openLuup devices available in MSR, but MSR is talking to the Vera devices over a bridge to openLuup that is talking to the Vera devices over the bridge to Vera (bridge to a bridge, not very efficient); (3) you connect MSR to both, in which case you have all the devices from both like #2, with the option of talking to the Vera devices more directly, but confusion may set in because all of the Vera devices will appear as both the native Vera entities and bridged openLuup entities -- every Vera device is listed in MSR once for its appearance on Vera and again for its appearance in openLuup.

                The biggest con to staying on the Reactor plugin (for Vera/openLuup) is that I have no further development planned for it. As new features go into MSR, I have no plans to "back port" them into R4V. As Vera is "walking dead", so is every Vera plugin, including R4V.

                CatmanV2C Offline
                CatmanV2C Offline
                CatmanV2
                wrote on last edited by
                #7

                @toggledbits said in MSR if you have only one system:

                If you are using openLuup as a single system, that resolves many of the performance issues of the Vera itself (it makes an acceptable radio for the devices it can support, as we all know). There are pros and cons to moving to MSR in this kind of scenario.

                You are bridged, meaning there is a socket-based tunnel between the Vera and openLuup to get the Vera devices into openLuup. If you introduce MSR into the equation, then there are three possibilities: (1) you configure MSR to talk to the Vera directly, in which case MSR brings the Vera devices in and lets you run the rules, etc., but it can't see the openLuup devices (only relevant if there are other plugins/devices on openLuup that you need access to from MSR); (2) you configure MSR to talk to openLuup, in which case you have all of your Vera and openLuup devices available in MSR, but MSR is talking to the Vera devices over a bridge to openLuup that is talking to the Vera devices over the bridge to Vera (bridge to a bridge, not very efficient); (3) you connect MSR to both, in which case you have all the devices from both like #2, with the option of talking to the Vera devices more directly, but confusion may set in because all of the Vera devices will appear as both the native Vera entities and bridged openLuup entities -- every Vera device is listed in MSR once for its appearance on Vera and again for its appearance in openLuup.

                The biggest con to staying on the Reactor plugin (for Vera/openLuup) is that I have no further development planned for it. As new features go into MSR, I have no plans to "back port" them into R4V. As Vera is "walking dead", so is every Vera plugin, including R4V.

                Thanks. That last paragraph is the only one that seems to apply, unless for 'Vera', I read Z-Way-Server?

                The last paragraph is compelling. I assume there's not conflict runnin MSR and Reactor together?

                C

                The Ex-Vera abuser know as CatmanV2.....

                toggledbitsT 1 Reply Last reply
                0
                • CatmanV2C CatmanV2

                  @toggledbits said in MSR if you have only one system:

                  If you are using openLuup as a single system, that resolves many of the performance issues of the Vera itself (it makes an acceptable radio for the devices it can support, as we all know). There are pros and cons to moving to MSR in this kind of scenario.

                  You are bridged, meaning there is a socket-based tunnel between the Vera and openLuup to get the Vera devices into openLuup. If you introduce MSR into the equation, then there are three possibilities: (1) you configure MSR to talk to the Vera directly, in which case MSR brings the Vera devices in and lets you run the rules, etc., but it can't see the openLuup devices (only relevant if there are other plugins/devices on openLuup that you need access to from MSR); (2) you configure MSR to talk to openLuup, in which case you have all of your Vera and openLuup devices available in MSR, but MSR is talking to the Vera devices over a bridge to openLuup that is talking to the Vera devices over the bridge to Vera (bridge to a bridge, not very efficient); (3) you connect MSR to both, in which case you have all the devices from both like #2, with the option of talking to the Vera devices more directly, but confusion may set in because all of the Vera devices will appear as both the native Vera entities and bridged openLuup entities -- every Vera device is listed in MSR once for its appearance on Vera and again for its appearance in openLuup.

                  The biggest con to staying on the Reactor plugin (for Vera/openLuup) is that I have no further development planned for it. As new features go into MSR, I have no plans to "back port" them into R4V. As Vera is "walking dead", so is every Vera plugin, including R4V.

                  Thanks. That last paragraph is the only one that seems to apply, unless for 'Vera', I read Z-Way-Server?

                  The last paragraph is compelling. I assume there's not conflict runnin MSR and Reactor together?

                  C

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

                  @catmanv2 said in MSR if you have only one system:

                  unless for 'Vera', I read Z-Way-Server?

                  Not sure what you mean here.

                  There is no problem running the Reactor for Vera plugin on a Vera or openLuup and running MSR in parallel with it.

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

                  CatmanV2C 1 Reply Last reply
                  0
                  • toggledbitsT toggledbits

                    @catmanv2 said in MSR if you have only one system:

                    unless for 'Vera', I read Z-Way-Server?

                    Not sure what you mean here.

                    There is no problem running the Reactor for Vera plugin on a Vera or openLuup and running MSR in parallel with it.

                    CatmanV2C Offline
                    CatmanV2C Offline
                    CatmanV2
                    wrote on last edited by
                    #9

                    @toggledbits

                    Typed earlier:

                    'You are bridged, meaning there is a socket-based tunnel between the Vera and openLuup to get the Vera devices into openLuup.'

                    Should I read z-way-server for Vera as I don't have a Vera any more?

                    C

                    The Ex-Vera abuser know as CatmanV2.....

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

                      I don't know how the openLuup ZWay integration works, I don't use it, but if it communicates via a socket with openLuup, then yes, tunnel-to-tunnel. At least its within the same system, though.

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

                      therealdbT 1 Reply Last reply
                      1
                      • toggledbitsT toggledbits

                        I don't know how the openLuup ZWay integration works, I don't use it, but if it communicates via a socket with openLuup, then yes, tunnel-to-tunnel. At least its within the same system, though.

                        therealdbT Offline
                        therealdbT Offline
                        therealdb
                        wrote on last edited by
                        #11

                        @toggledbits said in MSR if you have only one system:

                        I don't know how the openLuup ZWay integration works

                        It's using polling via HTTP.

                        --
                        On a mission to automate everything.

                        My MS Reactor contrib
                        My Luup Plug-ins

                        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
                          139

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

                        • Error After Upgrade
                          G
                          gwp1
                          0
                          4
                          105

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

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

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

                        • Links to MSR from HA
                          Tom_DT
                          Tom_D
                          0
                          1
                          91

                        • Set Reaction > Script Action
                          wmarcolinW
                          wmarcolin
                          0
                          11
                          437

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

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

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

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