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. [SOLVED] Lights on all month UNTIL fourth Thursday of the month
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

[SOLVED] Lights on all month UNTIL fourth Thursday of the month

Scheduled Pinned Locked Moved Multi-System Reactor
8 Posts 3 Posters 334 Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G Offline
    G Offline
    gwp1
    wrote on last edited by gwp1
    #1

    I've a scene for Arming for Xmas Season that works great, starting on Black Friday (Friday after fourth Thursday/Thanksgiving) and it uses latch to achieve the goal.

    Now I want to have DIFFERENT lighting for November 1 - Thanksgiving night, fourth Thu of November. So far I have:

    Screen Shot 2021-11-01 at 9.11.30 PM.png

    I know that this will only end up with lights coming on ON the fourth Thu, not prior to it. Am I looking at Output Control or Constraints to make my end date/time Thanksgiving night?

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

    *Hubitat C-7 2.4.1.151
    *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

    *HASS 2025.3.4
    w/ ZST10-700 fw 7.18.3

    *Prod MSR in docker/portainer
    MSR: latest-25082-3c348de6
    MQTTController: 24257
    ZWave Controller: 25082

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

      Heck, does this mean MSR needs a "Movable Feasts Calendar" or "National Holidays" component in addition to Date/Time, so you can simply pick [BEFORE] [THANKSGIVING] [OFFSET: 0 DAYS]? I recall Calendar Creator 2.0 on my Apple //c had something similar. It figured out things like Easter, Lent (and by extension, Mardi Gras) and so forth. Even Google Calendar can't do all that, nearly 35 years later!

      1 Reply Last reply
      1
      • LibraSunL Offline
        LibraSunL Offline
        LibraSun
        wrote on last edited by
        #3

        And geez, thanks for sending me down a huge rabbit hole. I'm back! I contemplated the reasonableness (you be the judge) of using an API of some kind to simply fetch the always-changing annual date of Thanksgiving. Turns out there are many such APIs, but they cost money, so I focused on the tried-and-true Google Calendars API since Google hosts a robust calendar of U.S. holidays which MSR can query.

        Let's take a little stroll down the path I traveled lo these past couple of hours (again, thanks!):

        STEP 1. Create an API app in Google developer account https://console.developers.google.com

        STEP 2. From the "Credentials" tab, create an API key. You get something like this "AIzaSyBcOT_DpEQysiwFmmmZXupKpnrOdJYAhhM"

        STEP 3. Then you can pull events from Google's holiday calendar using this URL -
        https://www.googleapis.com/calendar/v3/calendars/en.usa%23holiday%40group.v.calendar.google.com/events?key=yourAPIKey

        STEP 4. To retrieve only events called "Thanksgiving" -- there are 3 of them... last year, current year and next year -- one must insert a 'q=' modifier, so the URL we will use in MSR looks like -
        https://www.googleapis.com/calendar/v3/calendars/en.usa%23holiday%40group.v.calendar.google.com/events?q=Thanksgiving&key=yourAPIKey

        STEP 5. Create a new Rule in MSR which (I guess every January 1st) retrieves the next occurrence of Thanksgiving Day and stores that value into a blank expression. The Rule would have (at minimum) the following parts:
        CONDITION = Date/Time set to execute on January 1st of each year
        SET REACTION = An [HTTP] request that performs a [GET] on the URL from Step 4 and captures the response to expression [Events].
        EXPRESSIONS =
        'Events' := (blank)
        'Items' := Events.items
        'TGend' := T = first Occur in Items with (substr(Occur.end.date,0,4) == dateparts(time()).year), T.end.date

        The magic is happening in the 'TGend' expression, which returns a date as string, such as "2021-11-26". You could then, in theory, have your Thanksgiving Lights rule active between November 1 and {{ TGend }}, with some judicious use of an added expression and/or conversion of that end date into epoch time (e.g. (number) 1637884800000) for mathematical purposes. Your call.

        BED TIME NOW!

        G 1 Reply Last reply
        0
        • LibraSunL LibraSun

          And geez, thanks for sending me down a huge rabbit hole. I'm back! I contemplated the reasonableness (you be the judge) of using an API of some kind to simply fetch the always-changing annual date of Thanksgiving. Turns out there are many such APIs, but they cost money, so I focused on the tried-and-true Google Calendars API since Google hosts a robust calendar of U.S. holidays which MSR can query.

          Let's take a little stroll down the path I traveled lo these past couple of hours (again, thanks!):

          STEP 1. Create an API app in Google developer account https://console.developers.google.com

          STEP 2. From the "Credentials" tab, create an API key. You get something like this "AIzaSyBcOT_DpEQysiwFmmmZXupKpnrOdJYAhhM"

          STEP 3. Then you can pull events from Google's holiday calendar using this URL -
          https://www.googleapis.com/calendar/v3/calendars/en.usa%23holiday%40group.v.calendar.google.com/events?key=yourAPIKey

          STEP 4. To retrieve only events called "Thanksgiving" -- there are 3 of them... last year, current year and next year -- one must insert a 'q=' modifier, so the URL we will use in MSR looks like -
          https://www.googleapis.com/calendar/v3/calendars/en.usa%23holiday%40group.v.calendar.google.com/events?q=Thanksgiving&key=yourAPIKey

          STEP 5. Create a new Rule in MSR which (I guess every January 1st) retrieves the next occurrence of Thanksgiving Day and stores that value into a blank expression. The Rule would have (at minimum) the following parts:
          CONDITION = Date/Time set to execute on January 1st of each year
          SET REACTION = An [HTTP] request that performs a [GET] on the URL from Step 4 and captures the response to expression [Events].
          EXPRESSIONS =
          'Events' := (blank)
          'Items' := Events.items
          'TGend' := T = first Occur in Items with (substr(Occur.end.date,0,4) == dateparts(time()).year), T.end.date

          The magic is happening in the 'TGend' expression, which returns a date as string, such as "2021-11-26". You could then, in theory, have your Thanksgiving Lights rule active between November 1 and {{ TGend }}, with some judicious use of an added expression and/or conversion of that end date into epoch time (e.g. (number) 1637884800000) for mathematical purposes. Your call.

          BED TIME NOW!

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

          @librasun Part of me tried, TRIED, to sympathize - but I just couldn't do it. I was poking at various iterations of this rule based off of reading and re-reading the manual and staring endlessly at the xmas rule (which is the opposite, it STARTS on the fourth Friday in November) during an incident bridge at work that did not require me or my team's attention any longer.

          *Hubitat C-7 2.4.1.151
          *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

          *HASS 2025.3.4
          w/ ZST10-700 fw 7.18.3

          *Prod MSR in docker/portainer
          MSR: latest-25082-3c348de6
          MQTTController: 24257
          ZWave Controller: 25082

          1 Reply Last reply
          1
          • G gwp1

            I've a scene for Arming for Xmas Season that works great, starting on Black Friday (Friday after fourth Thursday/Thanksgiving) and it uses latch to achieve the goal.

            Now I want to have DIFFERENT lighting for November 1 - Thanksgiving night, fourth Thu of November. So far I have:

            Screen Shot 2021-11-01 at 9.11.30 PM.png

            I know that this will only end up with lights coming on ON the fourth Thu, not prior to it. Am I looking at Output Control or Constraints to make my end date/time Thanksgiving night?

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

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

            @gwp1 If you want it to end Thanksgiving night, that means you don't want the lights on starting with the 4th Friday (so on from the Nov-1 to the end of the day on the 4th Thursday).

            55e85987-a1d8-4b85-8265-3ea323b01ebb-image.png

            Theory of operation:

            The first date/time condition bounds the operating time of the entire thing. It can only be active in the month of November.

            For the remainder, I'll work from the inside of the groups out...

            The weekday condition obviously selects the 4th Friday of the month. It is set for latching (options), so when that weekday is encountered, it sticks. Because it's latching, it needs another condition partnered with it to tell it when to reset, and that is the purpose of the accompanying date/time condition in the group: it will be true throughout the end of the month, starting with the earliest possible day that a fourth Thursday could be. So when the end of the month rolls off and the date goes to the first of the month, that condition goes false and causes the interior group to go false, and the group going false causes the latch to be released on its child condition. In all, that means this interior group is true from the fourth Friday through the end of the month, and false otherwise.

            Now, since we want the rule reset between that fourth Friday and the end of the month, we add a wrapper group with a NOT to invert the state of the interior group. Very important point here: you cannot take a shortcut and make the interior group NOT AND, because of the latched condition. You change the behavior of the group/latch relationship if you do that -- the latch relies on its parent group to go false to reset it, so you need to leave the logic state of that group unaltered to get correct latch and reset behavior for this solution. The wrapper group allows you to change (NOT) the inner group's state as needed for the rule without changing the interrmost group's native logic state.

            Key takeaway: the parent group of a latched condition must be a pure AND group (cannot be NOT AND, OR, XOR, NUL).

            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
            1
            • LibraSunL Offline
              LibraSunL Offline
              LibraSun
              wrote on last edited by
              #6

              Just to reinforce the patently obvious truism: If you ever see me and Patrick posting in the same thread, go with his sage advice!

              1 Reply Last reply
              1
              • toggledbitsT toggledbits

                @gwp1 If you want it to end Thanksgiving night, that means you don't want the lights on starting with the 4th Friday (so on from the Nov-1 to the end of the day on the 4th Thursday).

                55e85987-a1d8-4b85-8265-3ea323b01ebb-image.png

                Theory of operation:

                The first date/time condition bounds the operating time of the entire thing. It can only be active in the month of November.

                For the remainder, I'll work from the inside of the groups out...

                The weekday condition obviously selects the 4th Friday of the month. It is set for latching (options), so when that weekday is encountered, it sticks. Because it's latching, it needs another condition partnered with it to tell it when to reset, and that is the purpose of the accompanying date/time condition in the group: it will be true throughout the end of the month, starting with the earliest possible day that a fourth Thursday could be. So when the end of the month rolls off and the date goes to the first of the month, that condition goes false and causes the interior group to go false, and the group going false causes the latch to be released on its child condition. In all, that means this interior group is true from the fourth Friday through the end of the month, and false otherwise.

                Now, since we want the rule reset between that fourth Friday and the end of the month, we add a wrapper group with a NOT to invert the state of the interior group. Very important point here: you cannot take a shortcut and make the interior group NOT AND, because of the latched condition. You change the behavior of the group/latch relationship if you do that -- the latch relies on its parent group to go false to reset it, so you need to leave the logic state of that group unaltered to get correct latch and reset behavior for this solution. The wrapper group allows you to change (NOT) the inner group's state as needed for the rule without changing the interrmost group's native logic state.

                Key takeaway: the parent group of a latched condition must be a pure AND group (cannot be NOT AND, OR, XOR, NUL).

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

                @toggledbits Ok, unpacking this in my head:

                Topmost trigger, no brainer: eligible during November. My CDO wants to use the 29th as the end but I get it.

                The inverting wrapper - I'm kicking myself because I completely forgot about NOT even though I've used it several times in various rulesets. Ten demerits for me.

                Here's where I'm slightly behind the curve - detect and latch. Talking aloud, weekday is Friday. Ok, good. The trigger grouped with it essentially says "eligible during this sub-range of that big ol' trigger range way up top".

                Got it.

                Am I implementing the latch because there is a availability of multiple Friday's in that 22-EOM after range and latching the extra layer of weekday fourth vs any Friday is what caps the grouped sub-range from going beyond that fourth Friday?

                Sidenote: when have you ever known me to take a shortcut - if anything, I go the waaaaay long way around lol

                @LibraSun - no worries, I did give your method a shot and was successfully up to the point where my mental KB fails me: adding the {{ TGend }} expression into the ruleset.

                The last thing I want to review in my rulesets is to ensure everything tied to Thanksgiving is done/gone at midnight Friday so at sunset Friday the Xmas ruleset kicks in without any race states. I've been a master at creating those these past couple weeks....

                Post-script: I did add one additional trigger at the top: sunset +10 to sunrise -15.

                *Hubitat C-7 2.4.1.151
                *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                *HASS 2025.3.4
                w/ ZST10-700 fw 7.18.3

                *Prod MSR in docker/portainer
                MSR: latest-25082-3c348de6
                MQTTController: 24257
                ZWave Controller: 25082

                toggledbitsT 1 Reply Last reply
                1
                • G gwp1

                  @toggledbits Ok, unpacking this in my head:

                  Topmost trigger, no brainer: eligible during November. My CDO wants to use the 29th as the end but I get it.

                  The inverting wrapper - I'm kicking myself because I completely forgot about NOT even though I've used it several times in various rulesets. Ten demerits for me.

                  Here's where I'm slightly behind the curve - detect and latch. Talking aloud, weekday is Friday. Ok, good. The trigger grouped with it essentially says "eligible during this sub-range of that big ol' trigger range way up top".

                  Got it.

                  Am I implementing the latch because there is a availability of multiple Friday's in that 22-EOM after range and latching the extra layer of weekday fourth vs any Friday is what caps the grouped sub-range from going beyond that fourth Friday?

                  Sidenote: when have you ever known me to take a shortcut - if anything, I go the waaaaay long way around lol

                  @LibraSun - no worries, I did give your method a shot and was successfully up to the point where my mental KB fails me: adding the {{ TGend }} expression into the ruleset.

                  The last thing I want to review in my rulesets is to ensure everything tied to Thanksgiving is done/gone at midnight Friday so at sunset Friday the Xmas ruleset kicks in without any race states. I've been a master at creating those these past couple weeks....

                  Post-script: I did add one additional trigger at the top: sunset +10 to sunrise -15.

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

                  @gwp1 said in Lights on UNTIL fourth Thursday of the month:

                  Am I implementing the latch because there is a availability of multiple Friday's in that 22-EOM after range and latching the extra layer of weekday fourth vs any Friday is what caps the grouped sub-range from going beyond that fourth Friday?

                  No, you're using latch because 6 of 7 days of the week aren't Fridays, and as many as 8 days, including another Friday, or as few as 2 with no Friday, may follow the fourth Friday in November of any given year. So once we encounter the fourth Friday, we want to continue to hold that condition state on Saturday, Sunday, Monday, and every other day that may follow through the end of the month. The latch takes care of that easily.

                  I know @LibraSun is into expressions, so another possible solution is to use expressions to gin up the timestamp for midnight on the 22nd day of November (the earliest day of the month a fourth Friday could be) of the current year, and then get its day of the week. Knowing that Friday is weekday index 5, you can increment the date to figure out when the fourth Friday occurs. For example, if 11/22 is already weekday 5, you're on target and no offset is needed (that date is the fourth Friday). But if 11/22 is weekday 1 (Monday), you need to add 4 (days, 5-1) to the timestamp to get it to a Friday. I'll leave what to do if 11/22 is a Saturday (weekday index 6) as an exercise for the reader. 🙂 Once you've incremented the date, just compare it to the current time to see if you're on or before it.

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

                  1 Reply Last reply
                  2
                  • toggledbitsT toggledbits locked this topic on
                  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