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
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
[Solved] Runtime error when exiting global reaction that contains a group
S
I am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved. The Runtime Error is different in the two browsers Safari v18.3 @http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:44 You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Google Chrome 133.0.6943.142 TypeError: self.editor.isModified is not a function at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34) You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Steps to reproduce: Click the pencil to edit a global reaction with a group. Click the Exit button. Runtime error appears. or Click Create Reaction Click Add Action Select Group Add Condition such as Entity Attribute. Add an Action. Click Save Click Exit Runtime error appears. I don’t know how long the error has been there as I haven’t edited the global reaction in a long time. Reactor (Multi-hub) latest-25060-f32eaa46 Docker Mac OS: 15.3.1 Thanks
Multi-System Reactor
Cannot delete Global Expressions
SnowmanS
I am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons. I have not created a global expression for some times and just noticed this while doing some clean-up. I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success. Here's what the log shows. [latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay [latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } Reactor latest-25067-62e21a2d Docker on Synology NAS
Multi-System Reactor
Local notification methods?
CatmanV2C
Morning, experts. Hard on learning about the internet check script in MSR tools, I was wondering what suggestions anyone has about a local (i.e. non-internet dependent) notification method. This was prompted by yesterday's fun and games with my ISP. I've got the script Cronned and working properly but short of flashing a light on and off, I'm struggling to think of a way of alerting me (ideally to my phone) I guess I could set up a Discord server at home, but that feels like overkill for a rare occasion. Any other suggestions? TIA C
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.
  • 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.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
      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.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
          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.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
              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.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
                            #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.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
                                #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.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
                                    #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.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
                                      • 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

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

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

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

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

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

                                          • Disaster recovery and virtualisation
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            5
                                            682

                                          • Remote access of Zwave stick from Z-wave server
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            3
                                            396

                                          • Organizing/ structuring rule sets and rules
                                            G
                                            gwp1
                                            0
                                            5
                                            395

                                          • Moving MSR from a QNAP container to RP 5 - some issues
                                            G
                                            gwp1
                                            0
                                            5
                                            367

                                          • Widget deletion does not work and landing page (status) is empy
                                            G
                                            gwp1
                                            0
                                            4
                                            356

                                          • Need help reducing false positive notifications
                                            T
                                            tamorgen
                                            0
                                            7
                                            548
                                          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