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
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
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
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 17.8k 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.
  • LibraSunL Offline
    LibraSunL Offline
    LibraSun
    wrote on last edited by LibraSun
    #1

    For MSR users with SiteSensor still installed back on Vera, you might want to consider letting MSR take over those duties. Here's a quick run-down of how I imported one of my SiteSensor recipes into a Rule on MSR, using OpenWeather API* as an example.

    STEP 1: Copy the Basics from Vera
    (a) Go to your Vera > Devices, locate SiteSensor (the main instance, not one of its children devices) and click ► for details then click SETTINGS.
    (b) Copy and paste (into Notepad or other text editor) the Request URL along with each of the defined expressions.

    STEP 2: Create a Rule on MSR
    (c) Jump into Rule Sets and click "Create Rule". Click its title to rename the rule 'OpenWeather (API)" and click 'Rename'.
    (d) Decide on appropriate Triggers (in my case, it's an OR group that includes an [INTERVAL] set to "Every 3 hours" plus a few [ENTITY ATTRIBUTE] entries reacting to things like entering/leaving home, waking up, etc.).
    (e) In Set Reacion, create an [HTTP REQUEST] > [GET] action.
    (f) Paste your old "Request URL" into the "Request URL" box.

    FYI GET calls to OpenWeather API* take the form:

    http://api.openweathermap.org/data/2.5/weather?zip=<your_ZIP_code>&id=<your_Wx_ID>&appid=<app-id>&units=imperial
    

    (g) Create four new blank Expressions (name them openWx, Tx, Hx and Rx).
    (h) Click SAVE & EXIT

    STEP 3: Process the Response
    (i) Re-open rule "OpenWeather (API)" by clicking the 'Edit' icon.
    (j) Within the [HTTP REQUEST] action, assign "Capture response to:" ► openWx
    (k) Down in Expressions, click "[+]Add Expresssion" then enter the following:
    Tx := round(openWx.main.temp,1)
    // yields current outdoor temperature
    Hx := round(openWx.main.humidity)
    // yields current humidity conditions
    Rx := openWx.rain ? ( openWx.rain['3h'] ? openWx.rain['3h'] : 0) : 0
    // yields predicted rainfall, if present; otherwise 0
    (l) Click SAVE & EXIT. Enjoy!

    Naturally, your specific needs and workflow will differ from the one I've outlined here. For instance, you may wish to explore the contents of the JSON object in openWx for additional data of interest to you, and define variables to match.

    My goal here has been to illustrate some key concepts needed for moving from SiteSensor over to MSR:

    • Some syntax is the same, such as dot notation for object.item.access;
    • Other syntax has changed, such as the use of ternary A ? B : C in place of IF (A, B, C);
    • Manually setting an [INTERVAL] in lieu of SiteSensor's timed schedule;

    Pro tip: If your workflow demands that other Rules react to the output of the "OpenWeather (API)" rule, then be sure to create all of the aforementioned Expressions under "Global Expressions" instead, so they become accessible across all Rule Sets.

    Once the transition is complete, you can either DISARM SiteSensor on Vera or remove it entirely with "Remove Device" (which will automatically remove all of its child devices).

    *Additional reading:
    OpenWeather API : https://openweathermap.org/api
    FREE SUBSCRIPTION REQUIRED TO USE THIS SERVICE

    PRO TIP: See below for optimal way to incorporate OpenWeatherMap into your MSR workflow(s), by enabling the service directly in the reactor.yaml config file.

    cw-kidC 1 Reply Last reply
    3
    • G Offline
      G Offline
      gwp1
      wrote on last edited by
      #2

      I just this morning discovered this in MSR. I'm currently using two SiteSensors to read my Ambient weather station API and OpenWxMap's API. I use the data to drive HVAC reactors in Vera. Given the nature of APIs, I created the OpenWxMap one to be a backup. As such, there's a Master API Failover reactor in Vera that monitors the Ambient SiteSensor and, if the query fails, shuts it off and switches to the OpenWxMap SiteSensor. There are duplicate HVAC reactors, one for each API provider. When the next successful query from the Ambient SiteSensor is successful, the Master API Failover fails everything back again.

      Given in MSR there are no reactor devices I'm stumped on how to turn on and off rulesets to duplicate the above.

      Thoughts?

      I've only had my MSR online for a week now so I'm still uncovering things within it.

      *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
      1
      • toggledbitsT Offline
        toggledbitsT Offline
        toggledbits
        wrote on last edited by
        #3

        There's a OWMWeatherController built-in to MSR. If you're going to use OpenWeatherMap, that's a more efficient way to go about it. For other API integrations, the method described above is useful.

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

        G LibraSunL 2 Replies Last reply
        0
        • toggledbitsT toggledbits

          There's a OWMWeatherController built-in to MSR. If you're going to use OpenWeatherMap, that's a more efficient way to go about it. For other API integrations, the method described above is useful.

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

          @toggledbits I dug about a bit and found this in the manual. How would I invoke this, I don't see anything in Entities (post-config)?

          *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
          1
          • toggledbitsT Offline
            toggledbitsT Offline
            toggledbits
            wrote on last edited by
            #5

            In your reactor.yaml, did you switch the "enabled" setting for the weather to enabled? Maybe show/post your config section for that controller?

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

              sigh

              Wow. More coffee required. Yeah, it was set to false. Correction made. I now have entity OWM Weather > weather.system > sys_system.state (primary)

              *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
              1
              • toggledbitsT Offline
                toggledbitsT Offline
                toggledbits
                wrote on last edited by
                #7

                Great. If you filter the "Entities" list (left nav) for the "wx" capability, you should find the entity that contains your local weather data.

                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

                  There's a OWMWeatherController built-in to MSR. If you're going to use OpenWeatherMap, that's a more efficient way to go about it. For other API integrations, the method described above is useful.

                  LibraSunL Offline
                  LibraSunL Offline
                  LibraSun
                  wrote on last edited by LibraSun
                  #8

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

                  There's a OWMWeatherController built-in to MSR.

                  Could you possibly shoe-horn lat, lon, location (city) name, time zone, etc. with that object? Or do those values already surface elsewhere in MSR?

                  I'd be interested in using them as part of my "Weekly Report" quasi-mailmerge notifications.

                  1 Reply Last reply
                  0
                  • LibraSunL Offline
                    LibraSunL Offline
                    LibraSun
                    wrote on last edited by LibraSun
                    #9

                    OPENWEATHER PRO TIP

                    Users of MSR's built-in weather object ('weather>default') may wish to know how to convert the value in wx.icon to an actual thumbnail image.

                    Here's how:
                    Suppose the value stored in that variable is '01d'
                    Simply prepend 'http://openweathermap.org/img/wn/' to the beginning, and append '.png' to the end. (You can enlarge the image by including '@2x', '@4x', etc. before the '.png'!)

                    Better still, gather all of the icons files from https://openweathermap.org/weather-conditions and host them on your own local server/repo, to spare OWx from excess bandwidth. You can also grab their table of "Weather Condition Codes" containing a description of each possible value in wx.condition_code.

                    These tirbits would be helpful in designing a dynamic "Weather" tile for the MSR Dashboard feature!!

                    EXAMPLES:
                    clear sky Condition: 01d = "Clear Sky (day)"
                    clouds Condition: 04n = "Clouds (night)"

                    1 Reply Last reply
                    0
                    • LibraSunL Offline
                      LibraSunL Offline
                      LibraSun
                      wrote on last edited by LibraSun
                      #10

                      FEATURE REQUEST

                      Add "Solar Noon" to Sunrise/Sunset trigger in MSR, even if it's just derived as "halfway point between Sunrise and Sunset"
                      (No need for "Civil Noon" since that's automatically 12:00pm)

                      Could be useful for farms, solar installations, etc.

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

                        That's easy, it has it, so all I need to do is add the menu item to the UI.

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

                          Great. If you filter the "Entities" list (left nav) for the "wx" capability, you should find the entity that contains your local weather data.

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

                          @toggledbits I found this:
                          a66f3768-e8e4-4280-b215-ebc45ae3d696-image.png

                          Oddly, the historical is returning Melgrove lol I left the config so that it would pull from the default location which is using lat/long.

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

                            I'm not sure where you're going with this post? Are you reporting a problem?

                            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

                              I'm not sure where you're going with this post? Are you reporting a problem?

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

                              @toggledbits I guess I am - unless I'm misreading the docs. I believe to have OWM set to use the default location of MSR which is Hanahan SC, not Melgrove Someplace.

                              I don't want to file a bug until I'm sure it's MSR and not me.

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

                                OK. In order to sort that out, I need to see your configuration for both the default system location and OWM. Post here or PM is fine.

                                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

                                  OK. In order to sort that out, I need to see your configuration for both the default system location and OWM. Post here or PM is fine.

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

                                  @toggledbits Posted via PM.

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

                                    OK. Looks like all is good, OWM is just returning an odd place name (who knows what data they sourced that from), and since you are using "default" configuration (home location from Reactor main config), it's using OWM's returned name for the entity name. If you do a custom location in the OWM config, you can set the name by adding the "name" to the custom config. I'm going to extend that behavior to the default location config as well, and that will be in today's build. If you want to get it fixed before that, just add a location to your OWMController config section:

                                      - id: weather
                                        enabled: true
                                        implementation: OWMWeatherController
                                        name: OWM Weather
                                        config:
                                          appid: "yourappidhere"
                                          locations:
                                            - id: home
                                              name: "My Custom Place Name"
                                              latitude: nn.nnnnnn
                                              longitude: nn.nnnnnn
                                    

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

                                      OK. Looks like all is good, OWM is just returning an odd place name (who knows what data they sourced that from), and since you are using "default" configuration (home location from Reactor main config), it's using OWM's returned name for the entity name. If you do a custom location in the OWM config, you can set the name by adding the "name" to the custom config. I'm going to extend that behavior to the default location config as well, and that will be in today's build. If you want to get it fixed before that, just add a location to your OWMController config section:

                                        - id: weather
                                          enabled: true
                                          implementation: OWMWeatherController
                                          name: OWM Weather
                                          config:
                                            appid: "yourappidhere"
                                            locations:
                                              - id: home
                                                name: "My Custom Place Name"
                                                latitude: nn.nnnnnn
                                                longitude: nn.nnnnnn
                                      
                                      G Offline
                                      G Offline
                                      gwp1
                                      wrote on last edited by
                                      #18

                                      @toggledbits I'm a few nightly builds behind so I'll wait until you have tonight's out. Thanks!

                                      *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
                                      • LibraSunL LibraSun

                                        For MSR users with SiteSensor still installed back on Vera, you might want to consider letting MSR take over those duties. Here's a quick run-down of how I imported one of my SiteSensor recipes into a Rule on MSR, using OpenWeather API* as an example.

                                        STEP 1: Copy the Basics from Vera
                                        (a) Go to your Vera > Devices, locate SiteSensor (the main instance, not one of its children devices) and click ► for details then click SETTINGS.
                                        (b) Copy and paste (into Notepad or other text editor) the Request URL along with each of the defined expressions.

                                        STEP 2: Create a Rule on MSR
                                        (c) Jump into Rule Sets and click "Create Rule". Click its title to rename the rule 'OpenWeather (API)" and click 'Rename'.
                                        (d) Decide on appropriate Triggers (in my case, it's an OR group that includes an [INTERVAL] set to "Every 3 hours" plus a few [ENTITY ATTRIBUTE] entries reacting to things like entering/leaving home, waking up, etc.).
                                        (e) In Set Reacion, create an [HTTP REQUEST] > [GET] action.
                                        (f) Paste your old "Request URL" into the "Request URL" box.

                                        FYI GET calls to OpenWeather API* take the form:

                                        http://api.openweathermap.org/data/2.5/weather?zip=<your_ZIP_code>&id=<your_Wx_ID>&appid=<app-id>&units=imperial
                                        

                                        (g) Create four new blank Expressions (name them openWx, Tx, Hx and Rx).
                                        (h) Click SAVE & EXIT

                                        STEP 3: Process the Response
                                        (i) Re-open rule "OpenWeather (API)" by clicking the 'Edit' icon.
                                        (j) Within the [HTTP REQUEST] action, assign "Capture response to:" ► openWx
                                        (k) Down in Expressions, click "[+]Add Expresssion" then enter the following:
                                        Tx := round(openWx.main.temp,1)
                                        // yields current outdoor temperature
                                        Hx := round(openWx.main.humidity)
                                        // yields current humidity conditions
                                        Rx := openWx.rain ? ( openWx.rain['3h'] ? openWx.rain['3h'] : 0) : 0
                                        // yields predicted rainfall, if present; otherwise 0
                                        (l) Click SAVE & EXIT. Enjoy!

                                        Naturally, your specific needs and workflow will differ from the one I've outlined here. For instance, you may wish to explore the contents of the JSON object in openWx for additional data of interest to you, and define variables to match.

                                        My goal here has been to illustrate some key concepts needed for moving from SiteSensor over to MSR:

                                        • Some syntax is the same, such as dot notation for object.item.access;
                                        • Other syntax has changed, such as the use of ternary A ? B : C in place of IF (A, B, C);
                                        • Manually setting an [INTERVAL] in lieu of SiteSensor's timed schedule;

                                        Pro tip: If your workflow demands that other Rules react to the output of the "OpenWeather (API)" rule, then be sure to create all of the aforementioned Expressions under "Global Expressions" instead, so they become accessible across all Rule Sets.

                                        Once the transition is complete, you can either DISARM SiteSensor on Vera or remove it entirely with "Remove Device" (which will automatically remove all of its child devices).

                                        *Additional reading:
                                        OpenWeather API : https://openweathermap.org/api
                                        FREE SUBSCRIPTION REQUIRED TO USE THIS SERVICE

                                        PRO TIP: See below for optimal way to incorporate OpenWeatherMap into your MSR workflow(s), by enabling the service directly in the reactor.yaml config file.

                                        cw-kidC Offline
                                        cw-kidC Offline
                                        cw-kid
                                        wrote on last edited by
                                        #19

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

                                        My goal here has been to illustrate some key concepts needed for moving from SiteSensor over to MSR

                                        I never used SiteSensor plugin for Vera before.

                                        Thanks for the MSR example you wrote.

                                        I wanted to try this out and found this Covid-19 API here.

                                        However the http command they give doesn't seem to return any results data, either just in the web browser or in my MSR rule.

                                        https://covid19-api.com/country?name=UK&format=json
                                        

                                        52885b5e-6ae2-4454-8650-a2fb4b55eb4c-image.png

                                        The curl command does work OK however

                                        curl -X GET "https://covid19-api.com/country?name=UK&format=json" -H "accept: application/json"
                                        

                                        How do I specify the application/json in the MSR rule? Assuming the problem is related to that.

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

                                          Same way. One header per line in that field.

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

                                          cw-kidC 1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Recent Topics

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

                                          • Gradually turn on lights.
                                            Tom_DT
                                            Tom_D
                                            0
                                            3
                                            54

                                          • Error After Upgrade
                                            G
                                            gwp1
                                            0
                                            4
                                            64

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

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

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

                                          • Links to MSR from HA
                                            Tom_DT
                                            Tom_D
                                            0
                                            1
                                            65

                                          • Set Reaction > Script Action
                                            wmarcolinW
                                            wmarcolin
                                            0
                                            11
                                            396

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

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

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

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