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
🎉 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
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
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
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
System Configuration Check - time is offset
F
Hi! I get this message when I'm on the status tab: System Configuration Check The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds. I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6. HA versions are: Core 2025.3.4 Supervisor 2025.03.4 Operating System 15.1 I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version. Do anyone know what I can try? Thanks in advance! Let's Be Careful Out There (Hill Street reference...) /Fanan
Multi-System Reactor
Programmatically capture HTTP Request action status code or error
therealdbT
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB. While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed. So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response. While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits Thanks!
Multi-System Reactor
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N
Hi , I'm on -Reactor (Multi-hub) latest-25067-62e21a2d -Docker on Synology NAS -ZWaveJSUI 9.31.0.6c80945 Problem with ZwaveJSUI: When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white. I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui. I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb". After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color. This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite. x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33} The "cold white" and "warm white" settings interfer with the rgb color settings. Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white. So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set. x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33 Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this? x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33} Thanks in advance.
Multi-System Reactor
Problem with simultaneous notifications.
T
Topic thumbnail image
Multi-System Reactor
Problem after upgrading to 25067
R
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem? I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Multi-System Reactor
Global expressions not always evaluated
tunnusT
Topic thumbnail image
Multi-System Reactor
[Solved] Local expression evaluation
V
Topic thumbnail image
Multi-System Reactor

Replacing SiteSensor Plugin (Vera) with MSR

Scheduled Pinned Locked Moved Multi-System Reactor
91 Posts 7 Posters 12.5k 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.
  • 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.151
    *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

    *HASS 2025.3.4
    w/ ZST10-700 fw 7.18.3

    *Prod MSR in docker/portainer
    MSR: latest-25082-3c348de6
    MQTTController: 24257
    ZWave Controller: 25082

    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.151
          *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

          *HASS 2025.3.4
          w/ ZST10-700 fw 7.18.3

          *Prod MSR in docker/portainer
          MSR: latest-25082-3c348de6
          MQTTController: 24257
          ZWave Controller: 25082

          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.151
              *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

              *HASS 2025.3.4
              w/ ZST10-700 fw 7.18.3

              *Prod MSR in docker/portainer
              MSR: latest-25082-3c348de6
              MQTTController: 24257
              ZWave Controller: 25082

              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.151
                  *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                  *HASS 2025.3.4
                  w/ ZST10-700 fw 7.18.3

                  *Prod MSR in docker/portainer
                  MSR: latest-25082-3c348de6
                  MQTTController: 24257
                  ZWave Controller: 25082

                  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.151
                      *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                      *HASS 2025.3.4
                      w/ ZST10-700 fw 7.18.3

                      *Prod MSR in docker/portainer
                      MSR: latest-25082-3c348de6
                      MQTTController: 24257
                      ZWave Controller: 25082

                      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.151
                          *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                          *HASS 2025.3.4
                          w/ ZST10-700 fw 7.18.3

                          *Prod MSR in docker/portainer
                          MSR: latest-25082-3c348de6
                          MQTTController: 24257
                          ZWave Controller: 25082

                          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.151
                              *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                              *HASS 2025.3.4
                              w/ ZST10-700 fw 7.18.3

                              *Prod MSR in docker/portainer
                              MSR: latest-25082-3c348de6
                              MQTTController: 24257
                              ZWave Controller: 25082

                              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.151
                                  *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                                  *HASS 2025.3.4
                                  w/ ZST10-700 fw 7.18.3

                                  *Prod MSR in docker/portainer
                                  MSR: latest-25082-3c348de6
                                  MQTTController: 24257
                                  ZWave Controller: 25082

                                  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.151
                                      *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                                      *HASS 2025.3.4
                                      w/ ZST10-700 fw 7.18.3

                                      *Prod MSR in docker/portainer
                                      MSR: latest-25082-3c348de6
                                      MQTTController: 24257
                                      ZWave Controller: 25082

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

                                        Did you enable the controller in its config?

                                        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
                                          #88

                                          Hang on lol. So it seems it creates the Entity as the location name, in my case "Charleston" and then the wx entities UNDER it. I should have picked that up from your screenshot with "PCT Current Weather" being the location.

                                          Only oddity.... this entry:

                                          wx.location="Melgrove (historical)"

                                          The rest of the data seems to line up just fine so that appears to be an outlier.

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

                                          *HASS 2025.3.4
                                          w/ ZST10-700 fw 7.18.3

                                          *Prod MSR in docker/portainer
                                          MSR: latest-25082-3c348de6
                                          MQTTController: 24257
                                          ZWave Controller: 25082

                                          toggledbitsT G 2 Replies Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Recent Topics

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

                                          • Errors after updating to MQTTController build 25139
                                            toggledbitsT
                                            toggledbits
                                            0
                                            2
                                            22

                                          • Set Reaction > Script Action
                                            toggledbitsT
                                            toggledbits
                                            0
                                            4
                                            37

                                          • Wiring Samotech SM308-S into light fitting
                                            F
                                            Freemanator
                                            0
                                            1
                                            16

                                          • Advice reqeusted to migrate MSR from Bare Metal to Container
                                            T
                                            tamorgen
                                            0
                                            5
                                            79

                                          • Reactor (Multi-System/Multi-Hub) Announcements
                                            toggledbitsT
                                            toggledbits
                                            5
                                            122
                                            37.3k

                                          • Z-Wave Future....
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            5
                                            165

                                          • Can´t restart or upgrade/deploy MSR
                                            toggledbitsT
                                            toggledbits
                                            0
                                            4
                                            116

                                          • [Solved] Limit HA Entity in MSR
                                            wmarcolinW
                                            wmarcolin
                                            0
                                            7
                                            239

                                          • Disaster recovery and virtualisation
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            5
                                            690

                                          • Remote access of Zwave stick from Z-wave server
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            3
                                            408
                                          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