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. [Resolved] Day mode implementation question
Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
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
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor
System Configuration Check - time is offset
F
Hi! I get this message when I'm on the status tab: System Configuration Check The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds. I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6. HA versions are: Core 2025.3.4 Supervisor 2025.03.4 Operating System 15.1 I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version. Do anyone know what I can try? Thanks in advance! Let's Be Careful Out There (Hill Street reference...) /Fanan
Multi-System Reactor
Programmatically capture HTTP Request action status code or error
therealdbT
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB. While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed. So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response. While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits Thanks!
Multi-System Reactor
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N
Hi , I'm on -Reactor (Multi-hub) latest-25067-62e21a2d -Docker on Synology NAS -ZWaveJSUI 9.31.0.6c80945 Problem with ZwaveJSUI: When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white. I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui. I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb". After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color. This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite. x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33} The "cold white" and "warm white" settings interfer with the rgb color settings. Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white. So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set. x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33 Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this? x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33} Thanks in advance.
Multi-System Reactor
Problem with simultaneous notifications.
T
Topic thumbnail image
Multi-System Reactor
Problem after upgrading to 25067
R
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem? I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Multi-System Reactor
Global expressions not always evaluated
tunnusT
Topic thumbnail image
Multi-System Reactor
[Solved] Local expression evaluation
V
Topic thumbnail image
Multi-System Reactor
[Solved] Runtime error when exiting global reaction that contains a group
S
I am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved. The Runtime Error is different in the two browsers Safari v18.3 @http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:44 You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Google Chrome 133.0.6943.142 TypeError: self.editor.isModified is not a function at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34) You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Steps to reproduce: Click the pencil to edit a global reaction with a group. Click the Exit button. Runtime error appears. or Click Create Reaction Click Add Action Select Group Add Condition such as Entity Attribute. Add an Action. Click Save Click Exit Runtime error appears. I don’t know how long the error has been there as I haven’t edited the global reaction in a long time. Reactor (Multi-hub) latest-25060-f32eaa46 Docker Mac OS: 15.3.1 Thanks
Multi-System Reactor
Cannot delete Global Expressions
SnowmanS
I am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons. I have not created a global expression for some times and just noticed this while doing some clean-up. I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success. Here's what the log shows. [latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay [latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } Reactor latest-25067-62e21a2d Docker on Synology NAS
Multi-System Reactor
Local notification methods?
CatmanV2C
Morning, experts. Hard on learning about the internet check script in MSR tools, I was wondering what suggestions anyone has about a local (i.e. non-internet dependent) notification method. This was prompted by yesterday's fun and games with my ISP. I've got the script Cronned and working properly but short of flashing a light on and off, I'm struggling to think of a way of alerting me (ideally to my phone) I guess I could set up a Discord server at home, but that feels like overkill for a rare occasion. Any other suggestions? TIA C
Multi-System Reactor
Custom capabilities in MQTT templates
M
Hi, I'm trying to integrate the sonos-mqtt (https://sonos2mqtt.svrooij.io/) with the MSR and it's coming along nicely so far. But cannot wrap my head around how to define custom capabilities in MQTT templates. I need this for the TTS announcements and similarly for the notification sounds where I would pass the sound file as parameter. So this is what I have in the local_mqtt_devices.yaml capabilities: x_sonos_announcement: attributes: actions: speak: arguments: text: type: string volume: type: int delay: type: int And this is the template: templates: sonos-announcement: capabilities: - x_sonos_announcement actions: x_sonos_announcement: speak: topic: "sonos/cmd/speak" payload: expr: > { "text": parameters.text, "volume": parameters.volume, "delayMs": parameters.delay, "onlyWhenPlaying": false, "engine": "neural" } type: json So the speak action should send something like this to topic sonos/cmd/speak { "text": "message goes here", "volume": 50, "delayMs": 100, "onlyWhenPlaying": false, "engine": "neural" } At startup the MSR seems to be quite unhappy with my configuration: reactor | [latest-25016]2025-02-09T08:19:59.029Z <MQTTController:WARN> MQTTController#mqtt entity Entity#mqtt>sonos-announcement unable to configure capabilities [Array][ "x_sonos_announcement" ] reactor | i18n: missing fi-FI language string: Configuration for {0:q} is incomplete because the following requested capabilities are undefined: {1} reactor | i18n: missing fi-FI language string: Configuration for {0:q} has unrecognized capability {1:q} in actions reactor | Trace: Configuration for {0:q} is incomplete because the following requested capabilities are undefined: {1} reactor | at _T (/opt/reactor/server/lib/i18n.js:611:28) reactor | at AlertManager.addAlert (/opt/reactor/server/lib/AlertManager.js:125:25) reactor | at MQTTController.sendWarning (/opt/reactor/server/lib/Controller.js:627:30) reactor | at MQTTController.start (/var/reactor/ext/MQTTController/MQTTController.js:268:26) reactor | at async Promise.allSettled (index 0) Configuration for "sonos-announcement" has unrecognized capability "x_sonos_announcement" in actions Controller: MQTTController#mqtt Last 10:21:37 AM Configuration for "sonos-announcement" is incomplete because the following requested capabilities are undefined: x_sonos_announcement Controller: MQTTController#mqtt Last 10:21:37 AM This is probably a pretty stupid question and the approach may not even work at all, but maybe someone or @toggledbits for sure, could point me to the right direction. Basically the idea is to be able to send TTS messages from reactions using entity actions. I've previously used HTTP requests to Sonos HTTP API (https://hub.docker.com/r/chrisns/docker-node-sonos-http-api/) for the same functionality, but since moving to sonos-mqtt, I need a way to send the TTS notifications using MQTTController. Along with the actual message, volume and delay must also be parameterizable. br, mgvra MSR latest-25016-d47fea38 / MQTTController [0.2.24293]
Multi-System Reactor
[SOLVED]Hass websocket falsely reporting ready on boot??
V
Hi, @toggledbits I just noticed that following a reboot of my raspberry pi, some of the rules, that I was expecting to recover, are not catching up following a reboot. I have made a simple test rule (rule-m6rz6ol1) with only "after Date/time" as trigger and "turn on a lamp" as a set reaction. All my infrastructure is on the same board so Reactor, Hass, Zwavejs, ... are all rebooting. Here is the sequence of the test case (All time converted to Zulu to match logs): Rule "after Date/Time" set to 14:05:00z Shutdown on Raspberry Pi at 14:04:00z Power back up at 14:08:00z Rule overview shows true as of 14:08:14z waiting for 00:00:00 in GUI From the log I can see that MSR is picking up the rule and knows that the state of the rule has changed from false to true and tries to send the update to HASS but failed with websocket error. Here is what I see from the log: 14:04:04z shutdown complete 14:08:08z Power up 14:08:13.111z websocket connection 14:08:15:323z Reaction to the light failed, Websocket not opened After there is a series of websocket connection attempt until 14:08:51z where it seemed to be really ready. Back in 2021 we had a discussion (https://smarthome.community/topic/700/solved-start-up?_=1738766986566) and you proposed to add a startup_delay:xxxx and startup_wait:xxxx parameter in the engine section of "reactor.yaml". When I try the startup_delay (this used to be a hard delay), the engine failed to start (I think). I then try the startup_wait:xxxx without any success. Since it wait for the connection status to be up to cancel the delay, it does not do anyting since Hass is reporting the socket up without really being up ( I think...). Questions: Did I figured it all wrong? should the startup_delay:xxxxx have worked? Any ideas? Here is the log: OK now I am stuck. I did add the log but when I submit the editor complained saying that I am limited to 32767 characters. The log from the shutdown to the time the websocket is stable is about 300000 character long. What are my options?
Multi-System Reactor

[Resolved] Day mode implementation question

Scheduled Pinned Locked Moved Multi-System Reactor
31 Posts 5 Posters 1.3k Views 5 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.
  • G Offline
    G Offline
    gwp1
    wrote on last edited by gwp1
    #1

    Day mode. We're all pretty much in agreement of the standard being "sunrise to sunset" = Day mode.

    I trigger HVAC, lighting, blinds, etc off of modes as do we all.

    My problem here is that, especially this time of year, wake-up time comes BEFORE sunrise by almost an hour. Given no one likes to get up in a cold house first thing I have Day mode HVAC settings start at wake-up time.

    I'm tracking another issue but also wanting to clean up rulesets.

    I'm opening this up to the group, showing my work, and asking for your thoughts/guidance on how to configure this Day mode.

    b68bf23b-1ea3-429f-86b7-8aa3e5ef3996-image.png 02359bc1-aa26-414c-8d1c-0794c995f769-image.png 15bdbebd-0c34-4968-8edd-396e620b0267-image.png

    Full transparency, the Defeat Midnight is new - it used to be set to just before sunrise and that means it's "eligible" at midnight.

    1 Reply Last reply
    0
    • PablaP Offline
      PablaP Offline
      Pabla
      wrote on last edited by
      #2

      Hmm I am not sure if I am following here, but why are you trying to mitigate the rule from going true at midnight? That shouldn't be an issue since the sunrise condition won't go true until the sun has risen which won't be at midnight ever?

      Also the rule state "Wake Up Times" that is referenced twice where is that?

      G 1 Reply Last reply
      0
      • PablaP Pabla

        Hmm I am not sure if I am following here, but why are you trying to mitigate the rule from going true at midnight? That shouldn't be an issue since the sunrise condition won't go true until the sun has risen which won't be at midnight ever?

        Also the rule state "Wake Up Times" that is referenced twice where is that?

        G Offline
        G Offline
        gwp1
        wrote on last edited by gwp1
        #3

        @pabla
        b629848e-ac27-4752-a4a6-ac04cc3c4d87-image.png

        Wake-Up times is literally just that: "after 0630 ET on weekdays/workdays" and "after 0730 ET on weekends", completely unrelated to sunrise/sunset.

        Regarding midnight: my preliminary findings around a different issue point to ruleset Day transitioning from RESET to SET! at midnight. I don't have all the required data pulled together yet to post about the issue I'm troubleshooting - this Day mode thing has been a burr under my proverbial saddle for some time.

        1 Reply Last reply
        0
        • PablaP Offline
          PablaP Offline
          Pabla
          wrote on last edited by Pabla
          #4

          Hm okay lets see if I can help, I think I am understanding what you want. You could move the whole "Wake Up Times" rulset to the constraints section in your "Day" rule set and remove the "Wake Up Times is TRUE" condition from your triggers. This would only allow the day mode to be triggered if the constraints are also met.

          Then you can completely delete the "One of these" groups" and replace it with the condition of between sunrise and sunset. You won't have to worry about the rule going true during midnight since you added the time/day constraint which will only allow the rule to go true if it past 6:35am on a weekday or 7:30am on a weekend. I attached a screenshot of what the rule should look like to better help.

          This layout will work like this:

          Triggers:

          • Your house should NOT be in Vacation, Guest or Night mode
          • AND the time should be within Sunrise and Sunset
          • AND one of the phones should be present (I know you only showed one device but I am assuming you will add others, hence the 'or' subgroup)

          Constraints:

          • All this can only go true if it is it past 6:35am on a weekday or 7:30am on a weekend

          efeeae5c-f420-4862-b07f-aea7a2b29564-image.png

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

            @gwp1 I don't understand all the complexity around the Day rule looking at sunrise and wake up times. I think what you are describing is that you want Day to start at the earlier of sunrise or your wake-up time, and that's a simple OR condition: Wake Up Times is true OR time is after sunrise. And the period before from midnight to either has nothing to do with that and isn't a consideration.

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

            G 3 Replies Last reply
            1
            • toggledbitsT toggledbits

              @gwp1 I don't understand all the complexity around the Day rule looking at sunrise and wake up times. I think what you are describing is that you want Day to start at the earlier of sunrise or your wake-up time, and that's a simple OR condition: Wake Up Times is true OR time is after sunrise. And the period before from midnight to either has nothing to do with that and isn't a consideration.

              G Offline
              G Offline
              gwp1
              wrote on last edited by gwp1
              #6

              @toggledbits Oy. I don't know how I missed that. I am embarassed.

              In my defense, I do have a history of designing rules much harder than they need to be. I tell myself "think edge" but still try to circle everything instead.

              Guessing for Evening the recommendation would be after sunset vs between sunset/sunrise?

              @Pabla the OR is there for future state... waiting on an update to iCloud3 in HASS that will allow triggering from the presence of my Apple Watch as well as iPhone for those times when it's a quick trip out and I let the Ultra do the work vs carrying the phone, too (think workout, bike ride, etc.)

              1 Reply Last reply
              0
              • toggledbitsT toggledbits

                @gwp1 I don't understand all the complexity around the Day rule looking at sunrise and wake up times. I think what you are describing is that you want Day to start at the earlier of sunrise or your wake-up time, and that's a simple OR condition: Wake Up Times is true OR time is after sunrise. And the period before from midnight to either has nothing to do with that and isn't a consideration.

                G Offline
                G Offline
                gwp1
                wrote on last edited by
                #7
                This post is deleted!
                1 Reply Last reply
                0
                • toggledbitsT toggledbits

                  @gwp1 I don't understand all the complexity around the Day rule looking at sunrise and wake up times. I think what you are describing is that you want Day to start at the earlier of sunrise or your wake-up time, and that's a simple OR condition: Wake Up Times is true OR time is after sunrise. And the period before from midnight to either has nothing to do with that and isn't a consideration.

                  G Offline
                  G Offline
                  gwp1
                  wrote on last edited by gwp1
                  #8

                  @toggledbits had to mess about with some mode additions/removals and changed sunrise/sunset to between to make this work as at sunset both Day and Evening modes were valid at sunset.

                  753fa5d3-b693-4a2f-adb6-889fd8d3114b-image.png

                  Would this be better served as is or by adding this under Constraints?

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

                    Depends entirely on what the actions are, and when you want them to run. I'm assuming it just sets mode to Day. If the mode changed during the day, would you want it changed back to Day? Trigger.

                    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
                    0
                    • toggledbitsT toggledbits

                      Depends entirely on what the actions are, and when you want them to run. I'm assuming it just sets mode to Day. If the mode changed during the day, would you want it changed back to Day? Trigger.

                      G Offline
                      G Offline
                      gwp1
                      wrote on last edited by
                      #10

                      @toggledbits Yep, absolutely - if I leave during the day mode shifts to Away - returning home the expectation would be a return to Day if still before sunset. Same with Evening if after sunset.

                      1 Reply Last reply
                      1
                      • toggledbitsT toggledbits

                        Depends entirely on what the actions are, and when you want them to run. I'm assuming it just sets mode to Day. If the mode changed during the day, would you want it changed back to Day? Trigger.

                        G Offline
                        G Offline
                        gwp1
                        wrote on last edited by gwp1
                        #11

                        I continue to wrestle with modes. Changing Wake-up and Sunrise to after in Day resulted in a battle between Day and Evening in the later hours as both were "valid" after sunset given the OR in Day

                        I've modified Wake-up to start at the two wake times, 0630 ET and 0730 ET, and end before 12noon ET. This closes it off from arguing at sunset.

                        2cfdf9c6-2018-49ba-971a-3b32f3884ac9-image.png

                        Day currently reads as such now:

                        • I must be home (can this be addressed better by "mode != Away"?)
                        • It must be after wake-up times OR after sunset sunrise, whichever comes first
                        • must be ignored if in Vacation (I'm away for extended period) or Guest (someone specific is checking on the house whilst I'm on vaca)

                        7b094e16-e40f-4266-90d4-ab578486832f-image.png

                        Evening

                        • should kick in after Sunset
                        • I must be home (again, can this be driven by mode != Away better?)
                          must be ignored if in Vacation (I'm away for extended period) or Guest (someone specific is checking on the house whilst I'm on vaca)

                        bed37190-98d0-4fc1-9824-4941e50bbaef-image.png

                        Night is set manually, ie not on a schedule. Two ways it can be set, the more basic is via voice command to Amazon Echo device that flips a virtual switch which triggers mode.

                        The second is more complex but still manual:

                        • phone must be in master bedroom
                        • phone must be charging for > 00:00:10 (so lockdown can be aborted if needed)
                        • can only be triggered if the above triggers happen whilst in Evening or Work (awakened in the middle of the night for a work thing and returning to sleep). If I happen to charge the phone during the day the house shouldn't lock down in Night mode.

                        0c0a6f03-f12e-4a21-8d73-3cdb56b28f08-image.png

                        I put this out there because I have a tendency (ok, more than a tendency) to overthink and over-complicate my rules as @toggledbits will confirm. This results in unnecessary demand on MSR as well as rules fighting with rules or duplicating outcomes.

                        CatmanV2C 1 Reply Last reply
                        0
                        • G gwp1

                          I continue to wrestle with modes. Changing Wake-up and Sunrise to after in Day resulted in a battle between Day and Evening in the later hours as both were "valid" after sunset given the OR in Day

                          I've modified Wake-up to start at the two wake times, 0630 ET and 0730 ET, and end before 12noon ET. This closes it off from arguing at sunset.

                          2cfdf9c6-2018-49ba-971a-3b32f3884ac9-image.png

                          Day currently reads as such now:

                          • I must be home (can this be addressed better by "mode != Away"?)
                          • It must be after wake-up times OR after sunset sunrise, whichever comes first
                          • must be ignored if in Vacation (I'm away for extended period) or Guest (someone specific is checking on the house whilst I'm on vaca)

                          7b094e16-e40f-4266-90d4-ab578486832f-image.png

                          Evening

                          • should kick in after Sunset
                          • I must be home (again, can this be driven by mode != Away better?)
                            must be ignored if in Vacation (I'm away for extended period) or Guest (someone specific is checking on the house whilst I'm on vaca)

                          bed37190-98d0-4fc1-9824-4941e50bbaef-image.png

                          Night is set manually, ie not on a schedule. Two ways it can be set, the more basic is via voice command to Amazon Echo device that flips a virtual switch which triggers mode.

                          The second is more complex but still manual:

                          • phone must be in master bedroom
                          • phone must be charging for > 00:00:10 (so lockdown can be aborted if needed)
                          • can only be triggered if the above triggers happen whilst in Evening or Work (awakened in the middle of the night for a work thing and returning to sleep). If I happen to charge the phone during the day the house shouldn't lock down in Night mode.

                          0c0a6f03-f12e-4a21-8d73-3cdb56b28f08-image.png

                          I put this out there because I have a tendency (ok, more than a tendency) to overthink and over-complicate my rules as @toggledbits will confirm. This results in unnecessary demand on MSR as well as rules fighting with rules or duplicating outcomes.

                          CatmanV2C Offline
                          CatmanV2C Offline
                          CatmanV2
                          wrote on last edited by
                          #12

                          @gwp1 said in Day mode implementation question:

                          It must be after wake-up times OR after sunset, whichever comes first

                          I suspect you mean 'Sunrise'?

                          C

                          The Ex-Vera abuser know as CatmanV2.....

                          G 1 Reply Last reply
                          0
                          • CatmanV2C CatmanV2

                            @gwp1 said in Day mode implementation question:

                            It must be after wake-up times OR after sunset, whichever comes first

                            I suspect you mean 'Sunrise'?

                            C

                            G Offline
                            G Offline
                            gwp1
                            wrote on last edited by
                            #13

                            @catmanv2 Egad, yes. Edited. Thank you!

                            1 Reply Last reply
                            1
                            • PablaP Offline
                              PablaP Offline
                              Pabla
                              wrote on last edited by
                              #14

                              In your "Day" ruleset for sunrise/sunset condition set the sunset condition to be a few minutes before sunset. This way both sunset conditions in "Day" and "Evening" won't go true at the same time. Alternatively you could also add a condition in the "Day" rule that the "Evening" rule must be false . This will make sure "Day" can't be true at the same time as "Evening".

                              G 1 Reply Last reply
                              0
                              • PablaP Pabla

                                In your "Day" ruleset for sunrise/sunset condition set the sunset condition to be a few minutes before sunset. This way both sunset conditions in "Day" and "Evening" won't go true at the same time. Alternatively you could also add a condition in the "Day" rule that the "Evening" rule must be false . This will make sure "Day" can't be true at the same time as "Evening".

                                G Offline
                                G Offline
                                gwp1
                                wrote on last edited by
                                #15

                                @pabla Add a specific condition for Evening = false or add it to this existing condition in Day:

                                051ce098-67ba-4607-af44-0dfe9a3620c5-image.png

                                PablaP 1 Reply Last reply
                                0
                                • G gwp1

                                  @pabla Add a specific condition for Evening = false or add it to this existing condition in Day:

                                  051ce098-67ba-4607-af44-0dfe9a3620c5-image.png

                                  PablaP Offline
                                  PablaP Offline
                                  Pabla
                                  wrote on last edited by
                                  #16

                                  @gwp1 On second thought I would just add the offset to the sunset time in the "Day" rule. Its less of a band-aid solution.

                                  G 1 Reply Last reply
                                  1
                                  • PablaP Pabla

                                    @gwp1 On second thought I would just add the offset to the sunset time in the "Day" rule. Its less of a band-aid solution.

                                    G Offline
                                    G Offline
                                    gwp1
                                    wrote on last edited by
                                    #17

                                    @pabla Updated to:

                                    653806ff-6383-4f86-8eea-fd3405ba38a5-image.png

                                    1 Reply Last reply
                                    0
                                    • PablaP Offline
                                      PablaP Offline
                                      Pabla
                                      wrote on last edited by Pabla
                                      #18

                                      Yeaup that should do the trick, what basically was happening as you said was the sunset conditions in both Day and Evening were true at the same time therefore causing the both rules to be true as well.

                                      Now that you added the 1 mins before sunset, they won't overlap.

                                      G 1 Reply Last reply
                                      0
                                      • PablaP Pabla

                                        Yeaup that should do the trick, what basically was happening as you said was the sunset conditions in both Day and Evening were true at the same time therefore causing the both rules to be true as well.

                                        Now that you added the 1 mins before sunset, they won't overlap.

                                        G Offline
                                        G Offline
                                        gwp1
                                        wrote on last edited by
                                        #19

                                        @pabla It should eliminate any race state. The original config was to have "Wake-up" and "sun" both use after but that created a mess alongside Evening as everything ran to midnight together.

                                        1 Reply Last reply
                                        0
                                        • therealdbT Offline
                                          therealdbT Offline
                                          therealdb
                                          wrote on last edited by
                                          #20

                                          I don't known why you're all setting a mode like this, but I'm still using home/away/night to drive my rules, plus a lot of flags (dark, sleeping, holiday, party, mute, green mode, solar, rainy, windy, bad weather) to combine all them together and drive my reactions. I'm curious to understand why you prefer this approach.

                                          --
                                          On a mission to automate everything.

                                          My MS Reactor contrib
                                          My Luup Plug-ins

                                          PablaP G 2 Replies Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Recent Topics

                                          • Limit HA Entity in MSR
                                            toggledbitsT
                                            toggledbits
                                            0
                                            5
                                            47

                                          • Reactor (Multi-System/Multi-Hub) Announcements
                                            toggledbitsT
                                            toggledbits
                                            5
                                            121
                                            35.2k

                                          • Disaster recovery and virtualisation
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            5
                                            584

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

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

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

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

                                          • Need help reducing false positive notifications
                                            T
                                            tamorgen
                                            0
                                            7
                                            461

                                          • Deleting widgets
                                            toggledbitsT
                                            toggledbits
                                            0
                                            4
                                            440

                                          • MQTT configuration question
                                            tunnusT
                                            tunnus
                                            0
                                            11
                                            592
                                          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