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. Replacing SiteSensor Plugin (Vera) with MSR
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

Replacing SiteSensor Plugin (Vera) with MSR

Scheduled Pinned Locked Moved Multi-System Reactor
91 Posts 7 Posters 18.1k Views 6 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.
  • ElcidE Offline
    ElcidE Offline
    Elcid
    wrote on last edited by
    #67
    This post is deleted!
    1 Reply Last reply
    0
    • ElcidE Elcid

      so to set temp expression should be ambient_api[0].lastData.tempinf

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

      @elcid Whadya know, that did the trick. Interesting to a noob like me how the original Site Sensor in Vera uses response[1].lastData.tempif and that works just fine.

      *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

      ElcidE 1 Reply Last reply
      0
      • G Offline
        G Offline
        gwp1
        wrote on last edited by
        #69

        @toggledbits QQ on the OWM built-in: is there a means by which to render it inactive until I need to call it? The way I work my Site Sensors is the one for OWM stays deactivated until the one for Ambient throws null at which point the OWM turns on, carrying the load until Ambient throws real data back out there again (at which time OWM shuts back off.)

        This saves wasted calls to the API for OWM.

        *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 toggledbitsT 2 Replies Last reply
        0
        • G gwp1

          @toggledbits QQ on the OWM built-in: is there a means by which to render it inactive until I need to call it? The way I work my Site Sensors is the one for OWM stays deactivated until the one for Ambient throws null at which point the OWM turns on, carrying the load until Ambient throws real data back out there again (at which time OWM shuts back off.)

          This saves wasted calls to the API for OWM.

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

          @gwp1 Put a constraint for the OWM rule, something like "ambient == null"?

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

          G 1 Reply Last reply
          0
          • G gwp1

            @elcid Whadya know, that did the trick. Interesting to a noob like me how the original Site Sensor in Vera uses response[1].lastData.tempif and that works just fine.

            ElcidE Offline
            ElcidE Offline
            Elcid
            wrote on last edited by
            #71

            @gwp1 vera uses lua, which arrays count from 1
            MSR uses javascript which counts from 0

            1 Reply Last reply
            1
            • tunnusT tunnus

              @gwp1 Put a constraint for the OWM rule, something like "ambient == null"?

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

              @tunnus That would work if I were creating the OWM like I've created the Ambient expressions and ruleset. But @toggledbits has OWM built-in, controlled by reactor.yaml config file. The frequency of calls to the API is configured there in minutes and it creates an entity in the Entities list. As I understand it, the entity is always refreshed data-wise by the frequency of the calls set in reactor.yaml.

              *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

              G 1 Reply Last reply
              0
              • G gwp1

                @toggledbits QQ on the OWM built-in: is there a means by which to render it inactive until I need to call it? The way I work my Site Sensors is the one for OWM stays deactivated until the one for Ambient throws null at which point the OWM turns on, carrying the load until Ambient throws real data back out there again (at which time OWM shuts back off.)

                This saves wasted calls to the API for OWM.

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

                @gwp1 said in Replacing SiteSensor Plugin (Vera) with MSR:

                @toggledbits QQ on the OWM built-in: is there a means by which to render it inactive until I need to call it?

                No. Controllers can only be switched on and off via configuration.

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

                  @tunnus That would work if I were creating the OWM like I've created the Ambient expressions and ruleset. But @toggledbits has OWM built-in, controlled by reactor.yaml config file. The frequency of calls to the API is configured there in minutes and it creates an entity in the Entities list. As I understand it, the entity is always refreshed data-wise by the frequency of the calls set in reactor.yaml.

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

                  @gwp1I got this all working, Ambient's API and OWM's API all dumping to global expressions.

                  ambient_api
                  ambient_temp
                  ambient_windspeed
                  ambient_windgust
                  ambient_solarradiation

                  openwxmap_api
                  openwxmap_temp
                  openwxmap_windspeed
                  openwxmap_windgust

                  Everything is glorious. I've planned for when the Ambient API drops (they were having big ol' issues today and into the evening now) it returns a NULL and I flip my HVAC control over to OWM API.

                  Except... Reactor gets very angry.

                  angry reactor.png

                  Now it's entirely possible this is on me - so let's review:
                  HVAC has three master rulesets, Cooling, Heating, and Neutral. You'll notice I've broken out the rules into Ambient vs OWM.

                  ambient cooling master.png

                  The triggers for OWM include a "when Ambient returns NULL" clause, if you will.

                  These are my two "Site Sensors" in MSR:

                  ambient site sensor.png OWM site sensor.png

                  This, too, works as intended with OWM sitting idle until Ambient goes "null" and then OWM starts making API calls and populating the global expressions with data.

                  In real world usage today/this evening the switch happens flawlessly. Where the angry Reactor comes in is after the switch happens. My confusion is around why any ruleset referencing the Ambient data (via global expressions) as a trigger suddenly has all the compile errors, throttling because update rates exceed 60/minute, etc. My expectation is that the "null" will blank the triggers in the ruleset and, since the ruleset is not triggered, it will go dormant until triggered again.

                  Where have I lost my way?

                  *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

                    @gwp1I got this all working, Ambient's API and OWM's API all dumping to global expressions.

                    ambient_api
                    ambient_temp
                    ambient_windspeed
                    ambient_windgust
                    ambient_solarradiation

                    openwxmap_api
                    openwxmap_temp
                    openwxmap_windspeed
                    openwxmap_windgust

                    Everything is glorious. I've planned for when the Ambient API drops (they were having big ol' issues today and into the evening now) it returns a NULL and I flip my HVAC control over to OWM API.

                    Except... Reactor gets very angry.

                    angry reactor.png

                    Now it's entirely possible this is on me - so let's review:
                    HVAC has three master rulesets, Cooling, Heating, and Neutral. You'll notice I've broken out the rules into Ambient vs OWM.

                    ambient cooling master.png

                    The triggers for OWM include a "when Ambient returns NULL" clause, if you will.

                    These are my two "Site Sensors" in MSR:

                    ambient site sensor.png OWM site sensor.png

                    This, too, works as intended with OWM sitting idle until Ambient goes "null" and then OWM starts making API calls and populating the global expressions with data.

                    In real world usage today/this evening the switch happens flawlessly. Where the angry Reactor comes in is after the switch happens. My confusion is around why any ruleset referencing the Ambient data (via global expressions) as a trigger suddenly has all the compile errors, throttling because update rates exceed 60/minute, etc. My expectation is that the "null" will blank the triggers in the ruleset and, since the ruleset is not triggered, it will go dormant until triggered again.

                    Where have I lost my way?

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

                    @gwp1 I get similar throttling warnings as you do when rules are not able to get values they used to get (via API), but at least you can eliminate those "invalid reference" errors using the following expression structure:

                    Screenshot 2021-09-16 at 11.44.01.png

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

                    G 1 Reply Last reply
                    0
                    • tunnusT tunnus

                      @gwp1 I get similar throttling warnings as you do when rules are not able to get values they used to get (via API), but at least you can eliminate those "invalid reference" errors using the following expression structure:

                      Screenshot 2021-09-16 at 11.44.01.png

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

                      @tunnus Pardon my ignorance but where do I utilize this structure?

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

                        I don't recommend using if statements. There are coalescing operators to make the deferencing through the structures easier and tidier when null is a possibility. See the documentation

                        Also your API Sensor OpenWxMap would be better without the Interval condition and applying pulse output mode (condition options) on the null test.

                        As for the throttling, I would comb through all of your rules and reactions to see if you have any left-over Set Variable or other actions that would change the value of any of the subject variables. Something seems to be competing with what you've shown here.

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

                        G tunnusT 2 Replies Last reply
                        0
                        • toggledbitsT toggledbits

                          I don't recommend using if statements. There are coalescing operators to make the deferencing through the structures easier and tidier when null is a possibility. See the documentation

                          Also your API Sensor OpenWxMap would be better without the Interval condition and applying pulse output mode (condition options) on the null test.

                          As for the throttling, I would comb through all of your rules and reactions to see if you have any left-over Set Variable or other actions that would change the value of any of the subject variables. Something seems to be competing with what you've shown here.

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

                          @toggledbits I'm not understanding Pulse vs Interval. That trigger is intended to be how often it queries the API (yes, five minutes is aggressive - I'll pull that back once this is all working.)

                          There's nothing writing to those variables as they never existed prior to just a day or two ago when I reopened this project of migrating off of Vera's Site Sensors.

                          Now, there are a slew of rulesets READING from those. That's where my confusion lies, also. In my mind, if it reads the data and it doesn't match the trigger criteria it should just stop until the data changes again, no?

                          For instance, the Fountain ruleset is complaining. But it's only set to read from Ambient API values - it should be done until there's Ambient data.

                          Screen Shot 2021-09-16 at 10.18.09 AM.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
                            #79

                            It's just an alternate way of doing things. I'm not a fan of Interval conditions, and view them as a necessary evil, so I try to remove their use whenever alternate functionality accomplishes the same.

                            The big problem you have here overall is that, currently, global variables changing does not drive rule evaluations. I think this came up in the other thread. Just because your Ambient fetch rule is updating ambient_api does not mean that ambient_temp is being updated in that same instant (that depends on how you are setting it, which you haven't shown us), and just because ambient_temp changes (no matter how you set it) doesn't mean that "Fountain via Ambient API" suddenly wakes up and checks it. This may simply be a current limitation of global variables as implemented that needs to be reviewed.

                            Another issue I see here is simply one of structure. If you've got "Fountain via Ambient" and "Fountain via OpenWxMap", then I assert you're making your life harder. It would be better to have a current_temp rule that itself decides if it is going to use Ambient or OpenWxMap, and the "Fountain" rule (singular) has no idea where that data came from and doesn't care.

                            current_temp = isnull( ambient_api?.whatever?[0] ) ? openwxapi?.whatever?[0].temperature :
                                ambient_api.whatever[0].temperature
                            

                            Also, even if everything operated to your assumptions, you have a race condition. There's an instant while the first OpenWxMap fetch is occurring that the query data from a previous query of hours, days, weeks, or months ago may be used, and that may cause reactions you don't intend until the OpenWxMap fetch succeeds and the data is updated. This is a side-effect of your goal of avoiding continuous OWM calls. There are workarounds, but the issue is moot at this point because the entire thing doesn't work like you think it does.

                            The implementation decision to not have global variables drive rule evaluation occurred early on. There were issues that prevented it, but since then, the rule evaluation algorithm has changed substantially. I'd need to study and test if this can be changed to work well under the new order. I agree it would be "better" (work more like expected) if rules could respond to global variable changes, but there are many opportunities for logic loops and other issues in doing that, so figuring that out and how to maintain control of the system and give the user meaningful feedback about such errors may not be a small task. (So I'm saying, I won't fix it today. Tomorrow's not looking good either.)

                            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
                            1
                            • toggledbitsT toggledbits

                              It's just an alternate way of doing things. I'm not a fan of Interval conditions, and view them as a necessary evil, so I try to remove their use whenever alternate functionality accomplishes the same.

                              The big problem you have here overall is that, currently, global variables changing does not drive rule evaluations. I think this came up in the other thread. Just because your Ambient fetch rule is updating ambient_api does not mean that ambient_temp is being updated in that same instant (that depends on how you are setting it, which you haven't shown us), and just because ambient_temp changes (no matter how you set it) doesn't mean that "Fountain via Ambient API" suddenly wakes up and checks it. This may simply be a current limitation of global variables as implemented that needs to be reviewed.

                              Another issue I see here is simply one of structure. If you've got "Fountain via Ambient" and "Fountain via OpenWxMap", then I assert you're making your life harder. It would be better to have a current_temp rule that itself decides if it is going to use Ambient or OpenWxMap, and the "Fountain" rule (singular) has no idea where that data came from and doesn't care.

                              current_temp = isnull( ambient_api?.whatever?[0] ) ? openwxapi?.whatever?[0].temperature :
                                  ambient_api.whatever[0].temperature
                              

                              Also, even if everything operated to your assumptions, you have a race condition. There's an instant while the first OpenWxMap fetch is occurring that the query data from a previous query of hours, days, weeks, or months ago may be used, and that may cause reactions you don't intend until the OpenWxMap fetch succeeds and the data is updated. This is a side-effect of your goal of avoiding continuous OWM calls. There are workarounds, but the issue is moot at this point because the entire thing doesn't work like you think it does.

                              The implementation decision to not have global variables drive rule evaluation occurred early on. There were issues that prevented it, but since then, the rule evaluation algorithm has changed substantially. I'd need to study and test if this can be changed to work well under the new order. I agree it would be "better" (work more like expected) if rules could respond to global variable changes, but there are many opportunities for logic loops and other issues in doing that, so figuring that out and how to maintain control of the system and give the user meaningful feedback about such errors may not be a small task. (So I'm saying, I won't fix it today. Tomorrow's not looking good either.)

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

                              @toggledbits Firstly, there is no "Fountain via OWM" as it's missing one of the metrics I use to drive that stupid thing.

                              Secondly - yes, if global variables do not drive rule evaluations then this whole idea is moot. I was hoping to pull Site Sensors out of Vera at long last. It appears, at least taking the path I did, that this is not viable.

                              Regarding how I have ambient_api set:

                              ambient api capture.png

                              That populates the rest of the global expressions:

                              ambient expressions.png

                              I need to think thru this some more if Global Expressions will not work as triggers. Has to be a way to present those datapoints as triggers like I've done with the Vera Site Sensors.

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

                                Give me a couple of days to see what I can noodle out on this. So far, things are looking like they're going the right direction, but sometimes you get >80% of the way before realizing you've painted yourself into a corner and need to take a different approach. Stay tuned!

                                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
                                0
                                • G Offline
                                  G Offline
                                  gwp1
                                  wrote on last edited by
                                  #82

                                  Preaching to the choir. As you're well aware from my previous escapades, I do tend to make things much more complicated than they need to be. I don't want you compromising your product, though, just because I am going down the wrong path. Steer me back! 🙂

                                  I would very much love to have shared elements like the outdoor temp, wind speed, and solar radiation something I can just point to. I've finally done that with HVAC, having only one master set and then pointing to them with the HVAC Ambient and HVAC OWN rulesets. Consolidation is king!

                                  *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

                                    I don't recommend using if statements. There are coalescing operators to make the deferencing through the structures easier and tidier when null is a possibility. See the documentation

                                    Also your API Sensor OpenWxMap would be better without the Interval condition and applying pulse output mode (condition options) on the null test.

                                    As for the throttling, I would comb through all of your rules and reactions to see if you have any left-over Set Variable or other actions that would change the value of any of the subject variables. Something seems to be competing with what you've shown here.

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

                                    @toggledbits Better?

                                    Screenshot 2021-09-17 at 13.46.02.png

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

                                    G 1 Reply Last reply
                                    1
                                    • tunnusT tunnus

                                      @toggledbits Better?

                                      Screenshot 2021-09-17 at 13.46.02.png

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

                                      @tunnus I'm back knocking on this again. lol

                                      I've enabled the OWM controller via reactor.yaml and this will be the dumbest question of the day, @toggledbits, but where do I see the results from it? Are new Entities created or should they appear under OWM Weather?

                                      I know I'm gonna feel like an idiot at the answer but I can take it lol

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

                                        Yeah, it creates new entities. In the Entities list, you can filter by controller. Do that. It should pop right out at you. If you want to get even more specific, filter on the wx capability, which is used by the entities that the controller publishes, and these are the entities you will want to use in rules.

                                        30aebdd4-baa1-458f-87d9-46b37de22f1d-image.png

                                        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

                                          Yeah, it creates new entities. In the Entities list, you can filter by controller. Do that. It should pop right out at you. If you want to get even more specific, filter on the wx capability, which is used by the entities that the controller publishes, and these are the entities you will want to use in rules.

                                          30aebdd4-baa1-458f-87d9-46b37de22f1d-image.png

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

                                          @toggledbits Hmmm... I'm.... not seeing the new entities at all.

                                          Mental checklist/talking out loud:

                                          • It's the same API/application key from SiteSensor in Vera and verified working.
                                          • I went with the basic config, using default location.
                                          • Restarted MSR via Tools
                                          • Key is not encased in single quotes

                                          Refresh is set to 10: for now - does MSR do an automatic call on restart?

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

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

                                          • Error After Upgrade
                                            G
                                            gwp1
                                            0
                                            4
                                            78

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

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

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

                                          • Links to MSR from HA
                                            Tom_DT
                                            Tom_D
                                            0
                                            1
                                            72

                                          • Set Reaction > Script Action
                                            wmarcolinW
                                            wmarcolin
                                            0
                                            11
                                            401

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

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

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

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