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. "changes from" operator stops to detect change
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

"changes from" operator stops to detect change

Scheduled Pinned Locked Moved Multi-System Reactor
19 Posts 3 Posters 1.3k Views 3 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.
  • tunnusT Online
    tunnusT Online
    tunnus
    wrote on last edited by
    #1

    I have the following rule:

    Screenshot 2022-08-09 at 17.33.39.png

    Use this to detect errors in Nibe uplink service, and every time updated data is fetched, a timestamp is stored. This triggered already yesterday, but re-triggered as I tried to manually recover this rule with a reset (hence there's no original "true as of xxx" time).

    So as a clarification, service works now and timestamps are updated, but this rule does not "recover" (stays triggered / SET). Did also restart MSR during this situation, though it was not related to this.

    The condition where there was no change (and rule was working correctly) lasted over 24 hours.

    Running MSR 22179 on Synology Docker. Can PM relevant logs if needed.

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

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

      You have "not" set on the outer group. The inside condition is false, so the group state will be true (not false).

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

      tunnusT 1 Reply Last reply
      0
      • toggledbitsT toggledbits

        You have "not" set on the outer group. The inside condition is false, so the group state will be true (not false).

        tunnusT Online
        tunnusT Online
        tunnus
        wrote on last edited by tunnus
        #3

        @toggledbits but that inside condition should have been true, it was "stuck" in a way, as I tried to explain. If you look carefully that previous screenshot, you'll see that the timestamp is newer than "false as of" time confirming this bug.

        I did another MSR restart, but it didn't help. Then I added one second to "delay reset" & did reset the rule, and situation is resolved (for now):

        Screenshot 2022-08-09 at 23.03.13.png

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

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

          The string displayed to the left of the "true/false as of" is irrelevant to me, because it is just a string. I have no idea what its source is or how it was generated. You haven't shown that work, so I have no basis on which to gauge it, and no basis on which to assume that the string displayed has any bearing on actual time and when, or useful in comparing to the other timestamps. I guess you have more you need to present to make your case here?

          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
          • T Offline
            T Offline
            tbully
            wrote on last edited by
            #5

            @tunnus - I think we're struggling with a similar issue. I came here to post a similar issue and saw your situation.

            I'm still moving things over from Vera to stand alone MSR (With Home Assistant being my eventual controller). This rule worked great in Vera but not so much here. I'm basically just looking for this string to change every xxx seconds. I don't care what the string is. As long as it changes, I know that in this case, my SiteSensor is getting new data. However, it appears to not reset even though I see the string (time stamp) changing:

            811ff419-c732-4440-aaa8-972830b836e4-image.png

            Here's another rule behaving the same way:

            c5bb9552-8a33-40b8-a9bc-050bbaf6e57a-image.png 50e6e39c-6b44-4225-884d-054396eb1fc9-image.png

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

              Both of you need to show all the work... where the strings are being generated and set, etc.

              Edit: I'm moving my son to college, so I will not be available for the next few days.

              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
              2
              • T Offline
                T Offline
                tbully
                wrote on last edited by
                #7

                😳 I kind of knew you'd respond with that but I'm not sure what else to show. I'm sorry.

                Congrats on the move. My twin daughters are just a few years away from that and I'm dreading it.

                This is a SiteSensor coming from Vera. It generates strings depending on what's returned from the API call. In this case, I'm just looking at a timestamp response. 2022-08-10T17:12:06Z Other strings are temperature, humidity, wind info, etc. But "Value 8" is the timestamp of the last packet of data from my weather station. If it doesn't change, it means my Weather Station (or Wunderground, etc) has given up.

                The other one is a LuupReload counter from Vera. Again, I don't care what the value is - just that it changed (in this case - incremented).

                toggledbitsT 1 Reply Last reply
                0
                • tunnusT Online
                  tunnusT Online
                  tunnus
                  wrote on last edited by
                  #8

                  I’ll try to reproduce this issue at some point, but my hypothesis is that if the value (string whatever) is static ”too long”, underlying code ”gives up” and stops to monitor it.

                  In my case there was a long maintenance break and didn’t receive new data for about 24 hours and hence timestamp remained the same.

                  Why this conclusion? Because so far this rule has worked fine (there hasn’t been long breaks getting data).

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

                  1 Reply Last reply
                  0
                  • T Offline
                    T Offline
                    tbully
                    wrote on last edited by tbully
                    #9

                    Thanks. I've just disabled those rules and gone back to Vera's Reactor for now. I'm not convinced is something I'm not translating from Vera to MSR....

                    I'm currently running: stable-22168-1f3a1cf1

                    1 Reply Last reply
                    0
                    • T tbully

                      😳 I kind of knew you'd respond with that but I'm not sure what else to show. I'm sorry.

                      Congrats on the move. My twin daughters are just a few years away from that and I'm dreading it.

                      This is a SiteSensor coming from Vera. It generates strings depending on what's returned from the API call. In this case, I'm just looking at a timestamp response. 2022-08-10T17:12:06Z Other strings are temperature, humidity, wind info, etc. But "Value 8" is the timestamp of the last packet of data from my weather station. If it doesn't change, it means my Weather Station (or Wunderground, etc) has given up.

                      The other one is a LuupReload counter from Vera. Again, I don't care what the value is - just that it changed (in this case - incremented).

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

                      @tbully said in "changes from" operator stops to detect change:

                      but I'm not sure what else to show. I'm sorry.

                      I'm back from my trip. I am asking you to show exactly what I asked for:

                      where the strings are being generated and set, etc

                      I think that's pretty clear, but I'll detail it out: that means, you show me the expression variable where the time is stored, and if the time is set by a reaction, you show me (all of) that reaction, and if it's in a rule, you show me (all of) the triggers and constraints in that rule as well.

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

                      tunnusT 1 Reply Last reply
                      0
                      • toggledbitsT toggledbits

                        @tbully said in "changes from" operator stops to detect change:

                        but I'm not sure what else to show. I'm sorry.

                        I'm back from my trip. I am asking you to show exactly what I asked for:

                        where the strings are being generated and set, etc

                        I think that's pretty clear, but I'll detail it out: that means, you show me the expression variable where the time is stored, and if the time is set by a reaction, you show me (all of) that reaction, and if it's in a rule, you show me (all of) the triggers and constraints in that rule as well.

                        tunnusT Online
                        tunnusT Online
                        tunnus
                        wrote on last edited by
                        #11

                        @toggledbits in my case timestamp is updated as follows (and I admit it seems bit of a hack overall, but it is what it is...)

                        bug.png

                        Updated data along with time are fetched to g_txtResponse variable and then time is parsed separately to another g_UplinkStatus variable which is used to monitor that data feed is working

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

                        T 1 Reply Last reply
                        0
                        • tunnusT tunnus

                          @toggledbits in my case timestamp is updated as follows (and I admit it seems bit of a hack overall, but it is what it is...)

                          bug.png

                          Updated data along with time are fetched to g_txtResponse variable and then time is parsed separately to another g_UplinkStatus variable which is used to monitor that data feed is working

                          T Offline
                          T Offline
                          tbully
                          wrote on last edited by
                          #12

                          @toggledbits

                          Apologies for the delay. I was out last week. I promise I'm not dense. I just wasn't clear how much detail you wanted so I'll try again. I thought my explanation and screen shots would be sufficient:

                          6f8a4f0b-8c6e-47ce-812e-14bf16d36ba5-image.png

                          ca24bc72-632a-4297-a0af-e1a3f865aa78-image.png

                          Here's the SiteSensor Config in Vera (recipe below).

                          a2b82a8a-4569-468c-8232-ae9f480cc4b1-image.png

                          {
                              "name": "",
                              "author": "",
                              "description": "",
                              "config": {
                                  "RequestURL": "https://api.weather.com/v2/pws/observations/current?stationId=KMICANTO5&format=json&units=e&apiKey=XXXXX",
                                  "Headers": "Accept-Encoding: gzip",
                                  "Interval": "120",
                                  "Timeout": "30",
                                  "QueryArmed": "0",
                                  "ResponseType": "json",
                                  "Trigger": "err",
                                  "NumExp": "8",
                                  "FailMasterOnExpressionError": "1",
                                  "FailChildOnExpressionError": "1",
                                  "BlankChildOnExpressionError": "0",
                                  "Expr1": "response.observations[1]",
                                  "Expr2": "response.observations[1].imperial.temp",
                                  "Child2": "urn:schemas-micasaverde-com:device:TemperatureSensor:1",
                                  "Expr3": "response.observations[1].imperial.windSpeed",
                                  "Child3": "urn:schemas-micasaverde-com:device:GenericSensor:1",
                                  "Expr4": "response.observations[1].imperial.windGust",
                                  "Child4": "urn:schemas-micasaverde-com:device:GenericSensor:1",
                                  "Expr5": "response.observations[1].imperial.precipRate",
                                  "Child5": "urn:schemas-micasaverde-com:device:GenericSensor:1",
                                  "Expr6": "response.observations[1].winddir",
                                  "Child6": "urn:schemas-micasaverde-com:device:GenericSensor:1",
                                  "Expr8": "response.observations[1].obsTimeUtc"
                              },
                              "source": "20095",
                              "version": "22234.1336"
                          }
                          
                          1 Reply Last reply
                          0
                          • T Offline
                            T Offline
                            tbully
                            wrote on last edited by
                            #13

                            Given this thread: https://smarthome.community/topic/455/replacing-sitesensor-plugin-vera-with-msr/34

                            Maybe I just turn this responsibility over to MSR and make life easier. It will have to be done at some point anyway (as Vera is going away)

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

                              I think you need to make sure the time is actually changing; I'm betting its not, because I think obsTimeUtc isn't what you think it is/doesn't work the way you think it does. Just because SiteSensor makes a request doesn't mean that time is going to change. The time you are putting into Expression 8 in SiteSensor is the observation time, that is, when the weather stats it is reporting were gathered by weather.com, not the current time of the SiteSensor request. It's very easy to imagine that it can be considerable time between observations (more than 600 seconds) even when SiteSensor requests are running every two minutes. If weather.com is only updating its own data every 30 minutes, then I would expect this logic to fail most of time, except once every 30 minutes (or whatever the actual time is between weather.com observations/refreshes of its own data), but certainly not give you what you want.

                              If you want the time to change every time SiteSensor makes a successful request, put time() into Expression 8 in SiteSensor.

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

                              T 1 Reply Last reply
                              1
                              • toggledbitsT toggledbits

                                I think you need to make sure the time is actually changing; I'm betting its not, because I think obsTimeUtc isn't what you think it is/doesn't work the way you think it does. Just because SiteSensor makes a request doesn't mean that time is going to change. The time you are putting into Expression 8 in SiteSensor is the observation time, that is, when the weather stats it is reporting were gathered by weather.com, not the current time of the SiteSensor request. It's very easy to imagine that it can be considerable time between observations (more than 600 seconds) even when SiteSensor requests are running every two minutes. If weather.com is only updating its own data every 30 minutes, then I would expect this logic to fail most of time, except once every 30 minutes (or whatever the actual time is between weather.com observations/refreshes of its own data), but certainly not give you what you want.

                                If you want the time to change every time SiteSensor makes a successful request, put time() into Expression 8 in SiteSensor.

                                T Offline
                                T Offline
                                tbully
                                wrote on last edited by
                                #15

                                @toggledbits
                                I have thought about that. But I just checked again. Value 8 updates (to the second) each time it successfully runs. This is the observation time from the weather station itself (the station at my home). This is important as it's that lack-of-update that I'm trying to detect. Otherwise, I would agree that time() would be sufficient.

                                Another interesting fact is that this rule/reaction works OK in the "Vera Instance" of Reactor.

                                de98c639-a38c-4908-967b-ea1f88337a06-image.png

                                4693c789-baf2-45bd-a887-bb31cdc7867d-image.png

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

                                  OK... one more thing I noticed, hating to state the obvious but I can only react to what you give me... as shown, the rule is disabled.

                                  Beyond that, I think you need to debug this using your Vera and the status view for the rule:

                                  1. Open the rule's status view, so you can see each condition and its state and dependent values.
                                  2. Open your Vera UI in a separate tab, and go to the SiteSensor's control panel, Advanced > Variables tab.
                                  3. Modify the Value8 variable to anything else, and observe what happens to the displayed value and status in the rule status view. It should follow (the current value in the condition state should change to what you set it to on the Vera, and that should trigger the condition, carry up through the group inverted as programmed, etc.).
                                  4. If the value changes and triggers the changes condition, make sure the rest of your logic is doing what you expect.

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

                                  T 1 Reply Last reply
                                  0
                                  • toggledbitsT toggledbits

                                    OK... one more thing I noticed, hating to state the obvious but I can only react to what you give me... as shown, the rule is disabled.

                                    Beyond that, I think you need to debug this using your Vera and the status view for the rule:

                                    1. Open the rule's status view, so you can see each condition and its state and dependent values.
                                    2. Open your Vera UI in a separate tab, and go to the SiteSensor's control panel, Advanced > Variables tab.
                                    3. Modify the Value8 variable to anything else, and observe what happens to the displayed value and status in the rule status view. It should follow (the current value in the condition state should change to what you set it to on the Vera, and that should trigger the condition, carry up through the group inverted as programmed, etc.).
                                    4. If the value changes and triggers the changes condition, make sure the rest of your logic is doing what you expect.
                                    T Offline
                                    T Offline
                                    tbully
                                    wrote on last edited by
                                    #17

                                    @toggledbits

                                    Apologies for the silence. The work week got away from me.

                                    While I wouldn't put it past me, the rule is indeed enabled.

                                    I'm doing something similar to your suggestion in order to test.

                                    1. MSR status up in one window (see screenshot)
                                    2. In Vera console in another window, I disarm/arm SiteSensor. As you're aware, this causes a re-fire of the recipe.
                                    3. I can then visual see the Value8 value change in the window.

                                    Is that a good enough test or should I go further somehow? (e.g. manually modifying Value8) Is there a way to increase debug level so we can see the payload coming back from Vera to MSR?

                                    734bab51-8c5d-4508-bbcc-cb29ab326096-image.png

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

                                      Maybe good enough, but I prefer assigning unambiguous, easy-to-read random strings (alpha, beta, gamma, ...). Either way, the point is to make sure you see the string change to match what you set it to here (highlighted location):

                                      02937c5b-6f51-4151-8e56-d14f720782d3-image.png

                                      What I'm going for here is a first level check: make sure the value is making it from the Vera to Reactor. I don't care about the logic state of the condition or any parent groups at this point, I just want you to confirm that the value shown changes immediately in Reactor when you change it on the Vera.

                                      Oh, and by the way, please upgrade to latest and try it as well.

                                      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
                                      • T Offline
                                        T Offline
                                        tbully
                                        wrote on last edited by
                                        #19

                                        Sigh. So this is weird. I updated to the latest and no change.

                                        I then took your advice and just was manually changing the Value8 variable in Vera from alpha to beta. It still didn't help. I finally took the 600 second delay out and noted that the set/reset started working. Put the delay back and all is good (I think).

                                        I'll keep an eye on it. Thanks for sticking with me on this one.

                                        1 Reply Last reply
                                        0
                                        • tunnusT tunnus referenced this topic on
                                        • toggledbitsT toggledbits locked this topic on
                                        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
                                          38

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

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

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

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

                                        • Disaster recovery and virtualisation
                                          CatmanV2C
                                          CatmanV2
                                          0
                                          5
                                          662

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

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

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

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

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