Navigation

    Discussion Forum to share and further the development of home control and automation, independent of platforms.

    SmartHome Community

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Unsolved
    (Last Updated: November 29, 2021)
    • Reactor (Multi-System/Multi-Hub) Announcements

      toggledbits

      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
    • MSR No longer Setting Reactions

      T

      Hello Everyone -

      I have a peculiar situation that I'm hoping to get some help with.

      Running Vera which is still handling my Zwave, MySensors, Zigbee, and still a balance of my Reactors.

      However, I've also been running MSR for several months in preparation for an eventual move off of Vera.

      Vera had one of its meltdowns this morning related to my Opensprinkler plug in.

      After getting that straightened out, I added the OpenSprinkler plugin to HAAS and that's when I started having issues.

      My existing MSR reactors (even simple ones) don't seem to fire their reactions. I can see the conditions go "true". If I manually fire the Reaction, it works fine.

      I do see this a lot in the logs:

      [1.0.2-21350]2022-05-16T19:02:44.518Z <Rule:INFO> Rule#rule-460 evaluation in progress; waiting for completion

      (Various rules - 460 is just an example)

      Is there anything I can do to further troubleshoot?

      Multi-System Reactor
    • MSR Telegram Messages Stopped Working

      T

      My MSR has been working flawlessly until a couple of days ago when it stopped sending Telegram Messages (or should I say they stopped getting through!). I have updated to MSR version 22004. The reactor.log is updating and is showing no errors:

      [latest-22004]2022-05-15T17:52:31.417Z Engine:NOTICE Starting reaction Message Test (re-l37h2fkj)
      [latest-22004]2022-05-15T17:52:31.417Z Engine:INFO Message Test all actions completed.
      [latest-22004]2022-05-15T17:52:31.704Z Engine:INFO Enqueueing "Message Test" (re-l37h2fkj)
      [latest-22004]2022-05-15T17:52:31.735Z Engine:NOTICE Starting reaction Message Test (re-l37h2fkj)
      [latest-22004]2022-05-15T17:52:31.736Z Engine:INFO Message Test all actions completed.
      [latest-22004]2022-05-15T17:52:32.007Z Engine:INFO Enqueueing "Message Test" (re-l37h2fkj)
      [latest-22004]2022-05-15T17:52:32.035Z Engine:NOTICE Starting reaction Message Test (re-l37h2fkj)
      [latest-22004]2022-05-15T17:52:32.036Z Engine:INFO Message Test all actions completed.
      [latest-22004]2022-05-15T17:52:41.324Z Engine:INFO Enqueueing "Variable Telegram Test" (re-kvnm57c3)

      If I use the following in my web browser the telegram message gets through:

      https://api.telegram.org/botxxxxx......./sendMessage?chat_id=xxxxx......&text=Test Message HTTPS

      I am running MSR on my QNAP network attached storage. Any assistance would be appreciated.

      Just another question...... I would like to post in the HOME HARDWARE VERA section of Smarthome, but I do not have the option to set up a new post. Do I need to request access for this?

      Multi-System Reactor
    • SSL Certificate for Multi System Reactor via LetsEncrypt

      W

      Details of runtime environment:

      Reactor (Multi-hub) stable-22055-9b40e12 Running as a service on Windows Server 2022 Std 21H2 Connecting to HASS (HASSOS) Is a migration WIP from OpenLuup/Reactor

      A complete description of your objective:

      Using LetsEncrypt, application "certifyTheWeb", retrieve and apply SSL certificate to Multi System Reactor

      A description of your approach/solution/implementation so far:

      Reviewed Config files, can't seen mention of certificate files in there

      Actual Question:

      How do I apply a certificate to whatever web server Reactor uses? I'm familiar with managing certificates on IIS and Apache but Reactor doesn't use either of these and I have not been able to locat ethe config file that Reactor uses for this. Which config file needs editing to apply a certificate? Does it use the computer certificate store or it's own store (e.g. pem files)

      The reason I want to achieve this, other than the general goodness of having everything I can in TLS is that I have Reactor as an IFRAME in my HASS console and as HASS is HTTPS and Reactor is HTTP then the iframe refuses to open.

      Search for "certificate" or "ssl" did not reveal anything relevant in this forum.

      Multi-System Reactor
    • MSR ZEN32 weird behavior

      R

      @toggledbits
      Hi Patrick,
      Running HASS 2022.5.3
      MSR zwavejs-22126-834c3e9

      Seeing weird behavior in MSR with regards to my Zen32's. Not sure how to capture info that might be relevent but will describe what I am seeing.
      In the example below I pressed scene 001 4 times. It flashed and changed the primary value to "4". The remaining buttons were previously showing the PV as "double" I pushed each button one time and they flashed and displayed the PV as 4.
      zen32.JPG

      In the zwavejs2mqtt debug screen that sequence looks like this.

      2022-05-10 09:38:44.078 INFO ZWAVE: Node 45: value notification: 91-0-scene-001 5 2022-05-10T16:38:44.081Z CNTRLR « [Node 045] received CentralScene notification { "nodeId": 45, "ccId": "Central Scene", "ccCommand": "0x03", "payload": "0x898501" } 2022-05-10 09:38:45.982 INFO ZWAVE: Node 45: value notification: 91-0-scene-002 0 2022-05-10T16:38:45.984Z CNTRLR « [Node 045] received CentralScene notification { "nodeId": 45, "ccId": "Central Scene", "ccCommand": "0x03", "payload": "0x8a8002" } 2022-05-10 09:38:47.807 INFO ZWAVE: Node 45: value notification: 91-0-scene-003 0 2022-05-10T16:38:47.810Z CNTRLR « [Node 045] received CentralScene notification { "nodeId": 45, "ccId": "Central Scene", "ccCommand": "0x03", "payload": "0x8b8003" } 2022-05-10 09:38:48.858 INFO ZWAVE: Node 45: value notification: 91-0-scene-004 0 2022-05-10T16:38:48.861Z CNTRLR « [Node 045] received CentralScene notification { "nodeId": 45, "ccId": "Central Scene", "ccCommand": "0x03", "payload": "0x8c8004" }

      Let me know what other info you would like me to supply.
      I have played around with a bunch of other key stroke combo's and it looks like buttons 2-5 display what ever button 1 is set to.
      Have tested this on 4 different ZEN32's and it is same on all.

      Multi-System Reactor
    • HASS 2022.5 issue with ZwaveJS in MSR

      R

      Running zwavejs-22118-baab576 in MSR, HASSOS 2022.5.1

      Due to an unreported issue in HASS, when I upgraded the 2022.5 yesterday, it dropped ZwaveJS2MQTT from my HASSOS build. Finally got it reinstalled and it appears to be working the way it was previously.
      MSR is now showing zwavejs down and in entities, nothing is updating.

      Seeing this in the logs:
      ZWaveJSController#zwavejs ws_open caught [Error]Error: connect ECONNREFUSED 192.168.0.16:3000

      Are there additional steps needed that are not mentioned in the manual?
      At a loss to figure out what is causing issue.

      Multi-System Reactor
    • Global Expression – Reference Error

      wmarcolin

      Hi!

      After several tests, restarting the computer where the MSR is, and the MSR itself by Tools > Restart, I have a persistent error in the logs.

      32d45bc3-51f8-4718-a113-3381e9d7edf2-image.png

      Looking at the global expression (screen below), I see that it is highlighted as an error, however, if I look at two other expressions above that have the same structure, they do not present an error, so I do not think the problem is with the expression's code.

      ca8a7867-4ac7-4f9a-9913-15a80da18f05-image.png

      This expression uses a group, which validates 4 devices of type door sensor, whether the status is true or false, door open or closed.

      "dgc_entrance_open": name: DGC Entrance Open select: - include_entity: - "hubitat>37" - "hubitat>38" - "hubitat>99" - "hubitat>130" filter_expression: > entity.attributes?.door_sensor?.state == true

      I also compared it with other groups, the structure is identical.

      Looking at the 4 devices in this group, I see that all are active in the MSR, have similar variables, are used in other groups and rules that do not present a problem.

      52b099f4-b9c4-46cb-ad3d-c873b09b7e13-image.png

      Looking at the log, I understand that it refers to some object that would be null, at which point I am lost on what to actually look at.

      [latest-22118]2022-05-02T22:33:11.711Z <Engine:INFO> Reaction Engine starting [latest-22118]2022-05-02T22:33:11.719Z <Engine:INFO> Checking rule sets... [latest-22118]2022-05-02T22:33:11.746Z <Engine:INFO> Checking rules... [latest-22118]2022-05-02T22:33:11.748Z <Engine:INFO> Data check complete; no corrections. [latest-22118]2022-05-02T22:33:11.892Z <Engine:ERR> [Engine]Engine#1: error evaluating expression EntranceOPEN: [ReferenceError]ReferenceError: Invalid scope in reference to member attributes of (object)null [latest-22118]2022-05-02T22:33:11.893Z <Engine:ERR> [Engine]Engine#1: expression: sort(each id in ( getEntity('groups>dgc_entrance_open').attributes.sys_group.members ): getEntity(id).name) [latest-22118]2022-05-02T22:33:11.894Z <Engine:CRIT> ReferenceError: Invalid scope in reference to member attributes of (object)null ReferenceError: Invalid scope in reference to member attributes of (object)null at _run (C:\MSR\reactor\common\lexp.js:1449:31) at _run (C:\MSR\reactor\common\lexp.js:1443:33) at _run (C:\MSR\reactor\common\lexp.js:1443:33) at _run (C:\MSR\reactor\common\lexp.js:1536:38) at _run (C:\MSR\reactor\common\lexp.js:1480:33) at C:\MSR\reactor\common\lexp.js:1283:29 at Array.forEach (<anonymous>) at _run (C:\MSR\reactor\common\lexp.js:1282:28) at run (C:\MSR\reactor\common\lexp.js:1663:22) at Object.evaluate (C:\MSR\reactor\common\lexp.js:1699:20) [latest-22118]2022-05-02T22:33:12.232Z <Engine:NOTICE> Reaction Engine running! [latest-22118]2022-05-02T22:33:12.233Z <Rule:INFO> Rule#rule-kxjp2el2 (Mode DAY) started [latest-22118]2022-05-02T22:33:12.234Z <Rule:INFO> Rule#rule-kxjp7kc8 (Mode EVENING) started [latest-22118]2022-05-02T22:33:12.234Z <Rule:INFO> Rule#rule-kxjparz7 (Mode NIGHT) started [latest-22118]2022-05-02T22:33:12.234Z <Rule:INFO> Rule#rule-kxjpd0d6 (Mode AWAY ∆) started [latest-22118]2022-05-02T22:33:12.235Z <Rule:INFO> Rule#rule-kxjqrcr9 (Mode PARTY) started [latest-22118]2022-05-02T22:33:12.235Z <Rule:INFO> Rule#rule-kxjqyhnu (Mode VACATION ∆) started

      Finally, if I return the expression and press the Try This Expression button, it is executed and the error disappears.

      102e5013-b9aa-4c26-98f5-1ae545f8897f-image.png

      This situation started to occur on the latest version of Reactor 22118, on a Windows 10 Bare Metal installation. Does anyone have a similar scenario?

      Sorry for the long post, I tried to document as best as possible to try to identify the problem.

      Thanks.

      Multi-System Reactor
    • Cheapest platform on which to run MSR

      T

      Please can anyone give me advice on a cheap way to run MSR (both initial cost and ongoing electricity cost). I currently run it on my QNAP network drive (which works very well incidentally). However, this draws a constant 35Watts (£90/yr @ 30p/kWh) and given the recent rise in fuel costs I am evaluating the best way forwards. Note, I only really need to turn my QNAP on for an hour a week to back-up my computer data. I understand that MSR can run on a Raspberry PI, but I am not competent with Linux! Thanks.

      Multi-System Reactor
    • Build 22118 - entity updates

      G

      I just noticed that the new hotness picked up the entities from when I added an integration temporarily to my Home Assistant and popped a lovely info notice into the Alerts pane.

      I know the info is new - but when did MSR suddenly become more real-time with devices being added to hubs? This is great!

      Multi-System Reactor
    • [Solved] Is there a cap or max number of devices a Global Reaction should not exceed?

      G

      Noticed in the last few nights that my Global Reaction to turn on a mere six lights in the evenings the same two devices no longer turn on. One is a dimming smart bulb, the other is a wall outlet.

      This has been running flawlessly for months - just in the last few nights I've noticed these two devices being left behind and yes, it's always these two devices only.

      "What changed?"

      No Hubitat firmware updates No new devices added to Hubitat list itemTwo MSR updates (the last two, I keep up with the latest) list itemHome Assistant releases (should have zero bearing, HA is nothing more than pretty dashboards) list itemAdded MQTT to MSR

      I did do a z-wave "repair" last night and am waiting to see if this helps.

      Is there any maximum or cap on number of devices that should be included in a Global Reaction?

      *Marked as solved as the question asked was answered. The issue persists but the question was answered.

      Multi-System Reactor
    • [Solved] Which version of npm should we be running for reactor-latest-22118-0f0772c.tar.gz

      G

      I've borked my install of reactor-latest-22118-0f0772c.tar.gz for some reason and am retracing steps. Running npm i --no-save --omit dev prompted to update npm and I did (current version now 8.6.0). Currently, attempts to load via browser/s (Brave and Safari) result in "This site can’t be reached192.168.1.xxx refused to connect." I am still able to SSH into the RPi.

      I haven't panicked yet but did just pull my config and storage directories - I believe I read where that's enough for a back-up if a clean install ends up being needed.

      So the question of the day: which version of nmp should we be running on for the latest Reactor?

      Multi-System Reactor
    • Is a global timestamp expression possible ?

      B

      I’ve looked and can’t find the answer which concerns me that the answer is obvious and thats why I can't find the answer to this.

      I’m new to MSR and this is my first post, so please bare with me 🙂

      What I’m trying to do is have a global expression that contains the current time so I can use it in Global reactions as well as Rulesets as part of my syslog messages.

      Example of what I’m experiencing:
      In Expressions, create a global expression: gMyTOD = strftime("%T %D”)
      In Rulesets, in a rule, create a local expression: MyTOD = strftime("%T %D”)

      In that same rule create a Notify type of Syslog.
      Set syslog message to: gMyTOD time is ${{gMyTOD}} and MyTOD time is ${{MyTOD}}
      Trigger the rule.

      The result is that the local expression (MyTOD) contains the correct time but the global expression (gMyTOD) does not update and reflects the wrong time in the final syslog message.

      Is there a different approach I should be using?

      Thank you in advance for any insight.

      -bh

      Multi-System Reactor
    • Restart router when it's gone offline?

      F

      Hi!
      Once a month or so, my internet access is lost, and I have to cut the power to the router, to restart it. When I'm away this become a problem, so I thought that if I got a zigbee switch (in Home Assistant), problem is solved. But how do I (MSR) know if it's offline?

      What's the easiest and most effective way to make this work? Do I ping a few websites every ten minutes or so, or is there a better approch? If I'm going to ping, what URL is recommended?

      For information, I have a set up with Asus routers, Home Assistent with zigbee-, z-wave and wifi devices (a total of appr. 150) and every of my 60-70 automation is done by MSR.
      I run MSR ver. 22080-ae7212f (docker on my Home Assistant blue). HA ver 2022.4.6.
      Thanks in advance.
      Take care, you all!
      /Fanan

      Multi-System Reactor
    • MSR for Scene Controllers

      therealdb

      I still have some code running on my Vera that I want to port and it's related to scene controllers.

      I'm mostly using Fibaro's switch/roller shutter and on the Vera side I'm getting sl_CentralScene/sl_CentralSceneAttr, but it seems too fast to be intercepted by MSR.

      What's anyone using? Thanks.

      Multi-System Reactor
    • Best strategy to get the difference between pulses in MSR

      therealdb

      So, I have a rule set that it's triggered when a local variable changes. Since it's tied to my solar production, it could change very frequently, so I've just added a reset delay to calm it down, but it's not working as intended.

      What I really need is a way to, let's say, define a percentage and define a variable to understand if the new value has changed +/- 10% before going true.

      I've tried a couple of ways, but I'm posting here anyway, in case anyone has found a better way to tackle this. Thanks!

      Multi-System Reactor
    • Status of MSR in Home Assistant

      Matohl

      Perhaps a dumb question. Can I check from Home Assistant that MSR is up and running? I would like to see that in a status page in HA. I can of course ping the other Pi but it doesn't say anything about the MSR status.

      Skärmavbild 2022-04-23 kl. 18.23.03.png

      Multi-System Reactor
    • Notifications from Alerts

      Crille

      @toggledbits Is there a way to get Current Alerts as an entity so I could monitor those and send notifications if needed.
      My usecase is sometimes openLuup crashes and MSR picks that up pretty quick, sending a pushover notification to me would get my attention to restart it.
      Of course there are many ways to monitor connectivity but since MSR already is doing that it would be neat to take advantage of it.

      Multi-System Reactor
    • Invocable rules via MQTT

      therealdb

      Hey @toggledbits.
      From the docs:

      You cannot control the state of rules via MQTT. Rule state is driven exclusively by the result of its conditions.

      And I'm OK when rules are triggered by something else, but I've built a couple of rules to be used by other rules, to streamline the logic, and it'll be useful to invoke a rule via MQTT. It's probably close to what rule/:id/restart is doing in the HTTP api.

      Thanks!

      Multi-System Reactor
    • Home Assistant Script, Reaction requires seclection that isnt there

      S

      I'm trying to create some automation so I can control my pool variable speed pump from reactor rather than iAqualink (which sucks). My controller is MQTT enabled so I created several scripts for my desired speeds. (I know reactor has MQTT ability but honestly I read the docs and could not make much sense of it and since I already have it set up in Home Assistant, I figured I would just leverage that instead)

      So I created all of my scripts and tested them, they worked perfectly. The I created a rule in reactor and set running the script as the action. The problem is that reactor is telling me that I have to make a selection. I try to click the dropdown and there is nothing to select. I cant save the rule, the only option is to exit.

      9e0a3147-5058-4893-9860-2f0d759dfe3c-image.png

      Here is my script in Home Assistant. Any advice on how to get this to work? If I am looking at this the wrong way I am open to suggestions (I would rather be able to call a specific action and specify a speed value but I cannot figure out how to do that). Thanks in advance.

      bfc7ba89-70a5-47d3-a111-0c2927ac3c73-image.png

      Multi-System Reactor
    • Installed latest MSR container and host time is wrong

      M

      Hi, I've been using msr for a while now and haven't had timezone issues until today when I updated to latest docker image (latest-22080-ae7212f)

      both docker date command and my local date command show the same time, same timezone, but for some reason MSR shows the host time as 2 hours in the past as a result all my timed rules run 2 hours late.

      my locale is set correctly in the host machine and is bound into the container as well.

      One possible hint I get is maybe this from the container startup log, but other than timezone stuff everything else seems to be working fine and all my settings loaded up just fine.

      [latest-22080]2022-04-07T07:52:52.423Z <SystemController:null> Module SystemController v22080 root {} CommonJS loading [latest-22080]2022-04-07T07:52:57.236Z <Engine:CRIT> SyntaxError: Unexpected end of JSON input SyntaxError: Unexpected end of JSON input at JSON.parse (<anonymous>) at IndividualFileStrategy.getDataObject (/opt/reactor/server/lib/IndividualFileStrategy.js:121:46) at Container.getDataObject (/opt/reactor/server/lib/Container.js:102:53) at new GlobalExpression (/opt/reactor/server/lib/GlobalExpression.js:105:179) at Function.getInstance (/opt/reactor/server/lib/GlobalExpression.js:123:89) at /opt/reactor/server/lib/Engine.js:1349:67 at Array.forEach (<anonymous>) at Engine.initializeGlobalExpressions (/opt/reactor/server/lib/Engine.js:1345:145) at Engine.start (/opt/reactor/server/lib/Engine.js:590:285) at /opt/reactor/app.js:362:103

      Let me know if I can provide further info to help debug this.

      Thanks

      Multi-System Reactor
    For those who registered but didn't received the confirmation email, please send an email to support@smarthome.community with the email you used

    [SOLVED] How do I: delay a notification to fire only if the ruleset actually fires

    Multi-System Reactor
    reactions delays
    4
    17
    177
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • G
      gwp1 last edited by gwp1

      Use case: Honeywell API gets easily flustered resulting in either one or both of my t-stats not receiving the change command/s. As such, I've written some "course correction" rulesets that basically look at the present situation and, if not matching what should be there, resends the command.

      Now... logic says if the first send didn't get thru then APIs generally aren't going to like another one right on it's heels. To combat this, I've added a Restriction to the correction ruleset that says the status must exist for 420 seconds before it will fire. This (hopefully) also prevents a race state when the real rule set AND the correction spring into action at the same time.

      I set a notification reaction to let me know a course correction had to be implemented but I've noticed that it fires even if the Restriction on the actual reaction never completes (is found unnecessary) and, as such, the correction ruleset never actually needs to fire.

      The ask: can a notification be tied to fire ONLY if/when the action actually fires?

      Hopefully that is clearer than mud.

      Solved here https://smarthome.community/post/10319.

      Hubitat C-7 2.3.0.124, Home Assistant 2022.2.9, MSR on RPi4 bare metal Model B 2GBs latest-22123-7faf18d

      1 Reply Last reply Reply Quote 0
      • LibraSun
        LibraSun last edited by

        I guess the simplest reply would be, "Why not just place your Notification step inside the Set Reaction portion of your 'Correction' rule?" I can't think of a more succinct way to ensure that it runs if (and only when) the 'Correction' rule fires Or am I missing something?

        I do realize my simplistic response side-steps your underlying question of "Why isn't Restriction X stopping Rule Y from proceeding?"

        G 1 Reply Last reply Reply Quote 0
        • G
          gwp1 @LibraSun last edited by

          @librasun That's where it lives. It's also the second action under the action to reset the stats. Yet what happens is, whilst the seven minutes is in progress and the action to reset the stats is waiting for a go command, the notification fires.

          Hubitat C-7 2.3.0.124, Home Assistant 2022.2.9, MSR on RPi4 bare metal Model B 2GBs latest-22123-7faf18d

          1 Reply Last reply Reply Quote 0
          • toggledbits
            toggledbits last edited by

            @gwp1 I feel like a grade school teacher having to write this, but... show your work.

            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 Reply Quote 0
            • G
              gwp1 @toggledbits last edited by gwp1

              @toggledbits "But Mr. Kedron, I did it in my head!"

              Screen Shot 2021-11-05 at 8.49.52 AM.png

              Screen Shot 2021-11-05 at 8.50.08 AM.png

              Screen Shot 2021-11-05 at 8.50.24 AM.png

              Screen Shot 2021-11-05 at 8.50.45 AM.png

              Screen Shot 2021-11-05 at 8.51.45 AM.png

              Concept is: other heating ruleset issues commands to Honeywell API to set heat at 68 upstairs, 65 downstairs. Sometimes this is ignored. As such, 'cause things happen, this ruleset essentially looks for the correct criteria to be UNMATCHED and, after waiting seven minutes, fires off the same command to Honeywell as well as notifying me.

              The seven minutes is to:

              • prevent a double hit on an API that already fumbled the first one

              • if, for some reason, the status change is just late and the original command was accepted then the Triggers here will go unmatched and this ruleset ultimately expires without needing to fire

              And yes, I do lie awake at night thinking up these convoluted scenarios because "food is a crutch, sleep is for wimps."

              Hubitat C-7 2.3.0.124, Home Assistant 2022.2.9, MSR on RPi4 bare metal Model B 2GBs latest-22123-7faf18d

              1 Reply Last reply Reply Quote 0
              • toggledbits
                toggledbits last edited by

                I'm not seeing a delay in your reaction. If there's no delay in your reaction, there won't be a delay between the actions. What am I missing?

                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 Reply Quote 0
                • G
                  gwp1 @toggledbits last edited by

                  @toggledbits I had a delay in it originally and all that did was delay the notification even if the ruleset ended up not ultimately firing because conditions changed and the Set Reaction didn't need to be fired - ie, I still got the notification (albeit delayed) even if the ruleset was aborted because the Triggers no longer applied.

                  Hubitat C-7 2.3.0.124, Home Assistant 2022.2.9, MSR on RPi4 bare metal Model B 2GBs latest-22123-7faf18d

                  toggledbits 1 Reply Last reply Reply Quote 0
                  • toggledbits
                    toggledbits @gwp1 last edited by

                    @gwp1 said in How do I: delay a notification to fire only if the ruleset actually fires:

                    even if the ruleset was aborted because the Triggers no longer applied.

                    That is correct behavior. You can get the reaction to stop if the rule resets by supplying a Reset Reaction. If the Reset Reaction is not empty, Reactor will abort the running Set Reaction. It can even contain just a comment (so not actually do anything); as long as it's not empty, Reactor will abort the delay and everything that follows it.

                    Documentation: Reaction Delays

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

                    G 2 Replies Last reply Reply Quote 0
                    • G
                      gwp1 @toggledbits last edited by

                      @toggledbits said in How do I: delay a notification to fire only if the ruleset actually fires:

                      You can get the reaction to stop if the rule resets by supplying a Reset Reaction. If the Reset Reaction is not empty, Reactor will abort the running Set Reaction. It can even contain just a comment (so not actually do anything); as long as it's not empty, Reactor will abort the delay and everything that follows it.

                      Wow, I never would have considered that, not in a million years. Thanks, Teach!

                      Hubitat C-7 2.3.0.124, Home Assistant 2022.2.9, MSR on RPi4 bare metal Model B 2GBs latest-22123-7faf18d

                      toggledbits 1 Reply Last reply Reply Quote 0
                      • toggledbits
                        toggledbits @gwp1 last edited by

                        @gwp1 said in How do I: delay a notification to fire only if the ruleset actually fires:

                        Wow, I never would have considered that, not in a million years.

                        Well, there's a place you can go (and it's not here) that will tell you this and many similar secrets... 😉

                        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 Reply Quote 0
                        • G
                          gwp1 @toggledbits last edited by

                          @toggledbits I certainly hope you aren't pointing to the MANUAL! Next thing, you'll want me asking directions before embarking on an excursion from the house!

                          Hubitat C-7 2.3.0.124, Home Assistant 2022.2.9, MSR on RPi4 bare metal Model B 2GBs latest-22123-7faf18d

                          1 Reply Last reply Reply Quote 1
                          • G
                            gwp1 @toggledbits last edited by

                            @toggledbits said in [SOLVED] How do I: delay a notification to fire only if the ruleset actually fires:

                            You can get the reaction to stop if the rule resets by supplying a Reset Reaction. If the Reset Reaction is not empty, Reactor will abort the running Set Reaction. It can even contain just a comment (so not actually do anything); as long as it's not empty, Reactor will abort the delay and everything that follows it.

                            Documentation: Reaction Delays

                            This functionality has stopped working as of build 21331 (and the subsequent 21332) from my observations.

                            Screen Shot 2021-11-28 at 9.17.29 PM.png

                            Screen Shot 2021-11-28 at 9.17.50 PM.png

                            (Yes, I literally c/p'd your explanation into the Comment field so I'd know why I created that particular Reset Reaction.) The current behaviour is how one would expect it to respond if the Reset Reaction were empty. I don't have logs pulled yet, sleep for work tomorrow beckons but I wanted to put it on the proverbial radar. If this should be reported in Mantis I'm happy to do so, just may be a couple days what with Giving Tuesday this week.

                            Hubitat C-7 2.3.0.124, Home Assistant 2022.2.9, MSR on RPi4 bare metal Model B 2GBs latest-22123-7faf18d

                            1 Reply Last reply Reply Quote 1
                            • toggledbits
                              toggledbits last edited by

                              I have a pretty short and definitive test for this, and it's working as expected. There have been no code changes in this area, so I'd be surprised to see a change in behavior.

                              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 Reply Quote 0
                              • A
                                Alan_F last edited by

                                I've re-read this thread a few times and still am confused by the whole thing. If I understand the images of the rule set, the notification should not be sent because this entire rule set doesn't become true unless one of the conditions is sustained for 420 seconds. That notification should never fire earlier than 420 seconds after one of the Thermostat.Setpoint <> XX is first detected. There is no issue of stopping a running rule set. This rule set isn't supposed to run unless the error state is sustained for 420 seconds. I have several rule sets that work just like this, and they work as expected. Nothing happens if the mis-matched conditions are corrected before the 'sustained for' time expires.

                                Light bulb moment: I think I just figured why this may be firing the notification when you don't want it to.

                                Existing conditions:
                                Downstairs set point is 62. it has been set to 62 for more than 420 seconds.
                                Downstairs mode is set to heat.
                                Armed for heating master rule set is true
                                House mode switches from 'away' to 'home'.

                                This rule set will fire immediately.

                                This would also occur if the Armed for heating master rule set changed to true, or if the downstairs thermostat mode changed to heat. As long as the thermostat has been set to something other than 65 or 68 for 420 seconds prior to those other conditions coming true, the 'delay' (really 'sustained for') is already met.

                                This either needs to be wrapped in an outer group with a 'sustained for 420 seconds' on the whole thing, or the house mode, armed for heating master, and thermostat mode conditions also need to be set to only go true when they are sustained for 420 seconds.

                                I'm not sure I understand your use case, but if it's possible for the set point to be other than 65/68 and one of those other conditions to then change, this could definitely be double-running your HVAC - Heating Day reaction. If, for example, you have a reduced set point when you're in away mode (or at night), and the HVAC - Heating Day reaction is supposed to fire when you come home (or switch to day mode), then this rule will fire at the same time, assuming you've been away more than 420 seconds (or in night mode more than 420 seconds) with the set points turned down.

                                If this really does involve an already-running reaction that needs to be stopped by a reset reaction, then I'm completely misunderstanding how the rules in the images you posted work.

                                G 1 Reply Last reply Reply Quote 0
                                • G
                                  gwp1 @Alan_F last edited by

                                  @alan_f The goal here is, for those times when Honeywell flakes on accepting the API post to change temps, this will monitor that and, if the expected setpoints aren't met for the specified conditions (ie, Heating at Home, Heating Away, etc.) then it will resend the commands to Honeywell. The reason for the 420 second delay is to allow the Honeywell API to "compose itself" since it's easily overrun and sending the course correction immediately will presumably result in no correction happening.

                                  @toggledbits I'm at a bit of a loss, then. Nothing was touched with this ruleset since I added the Reset Reaction and it resolved this issue originally. What is the test you have for this and can I use it to spin up a temp rule and validate locally?

                                  Hubitat C-7 2.3.0.124, Home Assistant 2022.2.9, MSR on RPi4 bare metal Model B 2GBs latest-22123-7faf18d

                                  1 Reply Last reply Reply Quote 0
                                  • toggledbits
                                    toggledbits last edited by toggledbits

                                    I think there's a misunderstanding here, and you need to review your logic and the state of devices in the detail panel for the rule, which shows the status of the condition targets and each condition as well as the running timers (when running).

                                    A Reset reaction can only stop a running Set reaction. There is no delay in your Set reaction, so your Set reaction will run instantly and completely when the trigger conditions are met. There is no opportunity here, based on what I see from what is posted earlier, for the Reset reaction to intervene. That whole issue is moot as it applies to the rule and reaction shown.

                                    The sustained for delay is self-cancelling. When the related condition is no longer met (i.e. result is false), the timer is cancelled. If this rule is setting, it is doing so because one of the two conditions is being met. A review of the detail panel and status will show this.

                                    I"m getting the idea that you are not looking at the detail panel. Go look at it. Post it if the results aren't what you expect.

                                    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 Reply Quote 0
                                    • A
                                      Alan_F last edited by Alan_F

                                      @gwp1 I think I correctly understood the use case then. The issue is that your rule set doesn't start counting the 420 seconds when the initial command is sent to the Honeywell API. The 420 seconds starts counting as soon as the setpoint is <> 65 (or 68). If you ever have the thermostats set to another value (when away, or night, or when not in heat mode) then the 'sustained for' will start counting and as soon as 420 seconds have passed, that element of the rule will go to true. You'll see it is green in the detail panel if you expand the rule set.

                                      The thing I'm not clear on, but am making some assumptions about, is what triggers the initial call to the Honeywell API that this rule is designed to monitor/verify. Making the assumption that you turn down the thermostat at night with something like "HVAC - Heating NIGHT", and that heating is still armed and the thermostat mode is still set to heat at night, then 420 seconds after you go into night mode, every element of this rule set will be true except the Hubitat house mode rule. The rule set is primed to activate if that goes true.

                                      So at night:

                                      • Armed for heating is true
                                      • (7 minutes after you enter night mode) Set point has been at some other value for more than 420 seconds
                                      • Thermostat mode is set to heat
                                      • But the rule set is NOT activated because the "AND house mode not in (night, vacation, away)" is not true

                                      In the morning when the Hubitat mode switches from "night" to "day", this rule will go true immediately as all elements are now true.

                                      • Armed for heating is true
                                      • Set point has been at some other value for more than 420 seconds. It is still at the night value until the API reports the new daytime value
                                      • Thermostat mode is set to heat
                                      • House mode not in (night, vacation, away)" is true

                                      If you add the 420 second 'sustained' to the other elements, then in the morning when the Hubitat mode switches to "day", this rule will NOT go true immediately

                                      • Armed for heating has been true for at least 420 seconds
                                      • Set point has been at some other value for at least 420 seconds
                                      • Thermostat mode is set to heat for at least 420 seconds
                                      • House mode not in (night, vacation, away)" has NOT been true for 420 seconds until 7 minutes after you switch to day mode.

                                      As long as one of the other elements goes false within 7 minutes, the rule set will never activate. The expected behavior is that the "set point has been at some other value" will go false within 7 minutes. If that doesn't happen, the whole rule set will go true and the set actions will fire including re-running the other rule set and notifying you.

                                      I still think this could be improved as I'm pretty sure this will only fire once. If the second attempt at setting the thermostat fails, this rule will remain set and there is nothing to cause it to un-set and then re-activate. That could be your desired behavior if you want to manually fix it when it fails the first time and avoid calling the rule every 7 minutes on repeated failures.

                                      I dealt with a lot of the same issues setting up rules for my flaky Lennox thermostat. It's still in Node-Red and looks like this:

                                      55821e35-adfb-495c-b2b3-2a6ad7ea47bd-image.png <img src="blob:chrome-untrusted://media-app/55d4404c-a480-4453-ae24-0e6410279a3b" alt="Screenshot 2021-11-29 11.34.25.png"/>

                                      I'm not smart/experienced/brave enough to try to replicate that in MSR yet.

                                      1 Reply Last reply Reply Quote 0
                                      • Locked by  toggledbits toggledbits 
                                      • First post
                                        Last post

                                      Welcome. If you’d like to participate in the discussion, rather than just read, then you can join the forum. As a member, you can interact with others here to share your experience and ask the questions you need answered.

                                      Powered by NodeBB | Contributors
                                      Hosted freely by PointPub Media Communications Inc. | Contact us