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
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor

"changes from" operator stops to detect change

Scheduled Pinned Locked Moved Multi-System Reactor
19 Posts 3 Posters 1.5k 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.
  • 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 Offline
      tunnusT Offline
      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 Offline
                tunnusT Offline
                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 Offline
                      tunnusT Offline
                      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

                                      • Gradually turn on lights.
                                        G
                                        gwp1
                                        0
                                        4
                                        87

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

                                      • Error After Upgrade
                                        G
                                        gwp1
                                        0
                                        4
                                        82

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

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

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

                                      • Links to MSR from HA
                                        Tom_DT
                                        Tom_D
                                        0
                                        1
                                        75

                                      • Set Reaction > Script Action
                                        wmarcolinW
                                        wmarcolin
                                        0
                                        11
                                        412

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

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

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

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