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: June 14, 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] restricting lights from a certain hour

    Multi-System Reactor
    3
    42
    181
    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

      I have "rainstorm lights", those couple lights in the house that come on during the day when it's gotten so dark due to weather that it's almost like night inside. The trigger for this is mode + solar radiation level.

      However, this gets triggered in that last hour before I wake in the morning due to the fact that I switch the house from NIGHT mode to DAY mode at 05:30 so climate control has an hour to warm the house appropriately before I rise at 06:30 weekdays (07:30 weekends.) To circumvent that I've added two "excludes" for hours "not between".

      Everything is working great with the exception of blocking the pre-alarm hours. I'm posting what I've created for another set of eyes to review and point out my obvious-to-all-but-me error.

      969cb424-f1e6-41da-b785-f0b35e9cc644-image.png 50ee5a24-ac0a-4d2c-9e7b-36923b56c4d9-image.png

      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

        At first blush, everything you've got there looks correct to me, and I would not expect the lights to go on during your "exclude" hours.

        Some quick mental notes I made while reviewing:

        1. The XOR might be overkill in that last group; OR should suffice, since a day cannot be both a Weekday and Weekend;
        2. I prefer placing time constraints in Constraints, with the faster-moving conditions in Triggers;
        3. When you click on STATUS, does MSR throw you any warning message concerning host time vs. browser time?

        Other than that, I got nothin' for ya at this early hour of the morning. 🙂

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

          Is the day vs night coming from modes on Hubitat? It's quite likely that the time is not in perfect sync between the Hubitat hub and your MSR host. If the Hubitat goes to day even 1 second before the MSR host thinks it's 05:30:00.000, your restrictions won't work. You might try buffering your time a little bit (that is, opening the restriction window a few minutes earlier).

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

          LibraSun G 2 Replies Last reply Reply Quote 1
          • LibraSun
            LibraSun @toggledbits last edited by

            @toggledbits Makes me wanna write a "Time Sync Warning" rule that compares MSR's time with that of each controller, and sends out a message if they drift apart too far.

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

              @toggledbits Yes, coming from Hubitat. So you're saying back up to 05:25?

              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

                Try that. How are you setting mode? Where is that coming from?

                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 Had to go verify as I'd done that originally in Hubitat but then shifted to MSR because I didn't want "some stuff here, some stuff there" model.

                  28b42deb-4745-4110-87f2-0757a8f896df-image.png

                  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
                  • G
                    gwp1 @LibraSun last edited by

                    @librasun Combined your notes with those from @toggledbits
                    20dc466f-5220-4bae-93d8-517df833006e-image.png

                    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 toggledbits

                      OK. Keep in mind that there's no guarantee to the order of rule evaluation. If two rules A and B both have conditions for 05:30, there's no guarantee which will be evaluated first. If it happens that B also depends on A directly, or on something A does, it's possible that if B is evaluated first, it will be looking at the "old" state of A because it hasn't updated yet. This may cause B to do some unexpected reaction. And worse, a moment later, A will be evaluated to its new state, and then B will see A changed and re-evaluate to the correct, expected state. This will happen so fast that the only way you'll see it is by examining the logs (or, you can add Notify/Alert actions to your reactions as a poor-man's debug stream). Leaving a wider window on time conditions can help with this as well. Other mitigation strategies may include moving time conditions that are often repeated into a rule, and then using the rule instead of the date/time condition(s).

                      In this particular case, you also don't really care if it's 5:30 in the constraints. You're thinking that way because that's when your day mode changes, but in fact, your time tests should probably just be before 6:30 and before 7:30. This would not be true if your "night" mode starts after midnight, but if it starts before, you're being too specific here.

                      If you don't change it to before, then put your ending times back to 6:30 and 7:30. You don't need to change those.

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

                        @toggledbits Wouldn't be the first time I've over-complicated the thinking...

                        This is where I am now given 99% of the time NIGHT is invoked before midnight. My m-i-l always says "nothing good happens after 9pm" 😉

                        55421c76-06e3-4d99-aa2f-c38518024f57-image.png

                        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
                        • LibraSun
                          LibraSun last edited by

                          Let us know how things go tomorrow morning and thereafter.

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

                            @librasun There was no joy in Muddville... and then I got to staring at the rule and realized, in setting it to before 6:30 and before 7:30 we'd lost the not between aspect.

                            I've adjust the rule to this for testing tomorrow morning:
                            47651b83-1dfc-4df6-8a23-0ac9e82497cd-image.png

                            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

                              The future is looking bright!

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

                                @librasun It's already bright - we're trying to make it less so lol

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

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

                                  @gwp1 Welp, awoke this morning to... light. Really scratching my head here. Unless I'm misunderstanding how the not between works I'm stumped.

                                  I'll send @toggledbits a log snip for the ten minute window around this event.

                                  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
                                  • LibraSun
                                    LibraSun last edited by

                                    I think I'd "widen" those time slots by another 30 minutes (i.e. 5-7am / 5-8am), and give it another day of testing. Something tells me it's too precise for now, still. Nothing else jumps out at me, but as you've already pinpointed, Logs are your friend as is watching the Rule's live status in RuleSets.

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

                                      I disagree. Unless the controller is down at the moment, one minute would be sufficient widening to prevent a race condition. There's something more here than meets the eye.

                                      @gwp1 if you're going to send logs, don't snip, send me the whole thing, and also send all rules involved (if you click on the rule name in the Rule Sets list, it shows you the rule ID under the conditions -- there's a JSON file in your reactor/storage/rules with that ID as its base name).

                                      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 1
                                      • toggledbits
                                        toggledbits last edited by toggledbits

                                        Actually, before we go any further, look at this more carefully:

                                        Let's say for the sake of argument that it's 4am. Your "not between" conditions are going to be true (4am is not between 5:30 and 7:30), so the condition is true, and that means your "exclusion" isn't.

                                        For me, based on what I understand your intent to be, and working within the existing structure, you really want these to be after operators with the earliest time you're willing to accept the lights coming on.

                                        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 Hmmm... that's an interesting approach. Mode + After alarm time = lights allowed. Let me try that.

                                          Edited to add screenshot of updated ruleset:
                                          1eb6e773-8a25-41a7-8abe-03627dce1649-image.png

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

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

                                            @gwp1 Sadness abounds. Lights this morning. I've emailed @toggledbits the logs he requested in full.

                                            Of note: when I was originally creating this rule I noticed something with the Weekday and Weekend "button/links"... when saved, the days chosen by using those were blank again. Only way I could save them visibly was by manually checking them. I should have filed a bug - work intervened and then it slipped my mind. Perhaps unrelated - perhaps not, if the choices aren't really saved.

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