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

[Resolved] Day mode implementation question

Scheduled Pinned Locked Moved Multi-System Reactor
31 Posts 5 Posters 1.4k 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.
  • 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.

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

      *HASS 2025.6.0
      w/ ZST10-700 fw 7.18.3

      *Prod MSR in docker/portainer
      MSR: latest-25139-fbd67abc
      MQTTController: 25139
      ZWave Controller: 25139

      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.

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

        *HASS 2025.6.0
        w/ ZST10-700 fw 7.18.3

        *Prod MSR in docker/portainer
        MSR: latest-25139-fbd67abc
        MQTTController: 25139
        ZWave Controller: 25139

        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!

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

            *HASS 2025.6.0
            w/ ZST10-700 fw 7.18.3

            *Prod MSR in docker/portainer
            MSR: latest-25139-fbd67abc
            MQTTController: 25139
            ZWave Controller: 25139

            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

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

                *HASS 2025.6.0
                w/ ZST10-700 fw 7.18.3

                *Prod MSR in docker/portainer
                MSR: latest-25139-fbd67abc
                MQTTController: 25139
                ZWave Controller: 25139

                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

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

                    *HASS 2025.6.0
                    w/ ZST10-700 fw 7.18.3

                    *Prod MSR in docker/portainer
                    MSR: latest-25139-fbd67abc
                    MQTTController: 25139
                    ZWave Controller: 25139

                    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.

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

                        *HASS 2025.6.0
                        w/ ZST10-700 fw 7.18.3

                        *Prod MSR in docker/portainer
                        MSR: latest-25139-fbd67abc
                        MQTTController: 25139
                        ZWave Controller: 25139

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

                            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.

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

                            @therealdb My house modes are simple: Night/Home/Away/Vacation. All them are configured very simply, based on if the alarm is turned on (either stay or away) and who's home. That way there is no accidental/unexpected mode changes

                            G 1 Reply Last reply
                            0
                            • therealdbT therealdb

                              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.

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

                              @therealdb said in Day mode implementation question:

                              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.

                              This is exactly what I'm driving at. I use Mode followed by a number of what I call "shared rules" (Wake-up times, cloudy day, temp < 40º, presence, etc.) that can be/are referenced in many other rulesets. Where I'm hitting my wall is the actual triggering of the modes (Day, Away, Evening, Night).

                              My curiosity is around how you're actually triggering the modes themselves. The rest... I've got that nailed down.

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

                              *HASS 2025.6.0
                              w/ ZST10-700 fw 7.18.3

                              *Prod MSR in docker/portainer
                              MSR: latest-25139-fbd67abc
                              MQTTController: 25139
                              ZWave Controller: 25139

                              therealdbT 1 Reply Last reply
                              0
                              • PablaP Pabla

                                @therealdb My house modes are simple: Night/Home/Away/Vacation. All them are configured very simply, based on if the alarm is turned on (either stay or away) and who's home. That way there is no accidental/unexpected mode changes

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

                                So I went back in time to when I first set modes up. Here's my current settings:

                                b383c52d-84a6-43bd-bb3b-f298f25642f8-image.png

                                3d099145-a298-4314-af18-d612321024c9-image.png

                                53c7b6b5-eedb-40b6-a955-140c9ae469eb-image.png 9c58c5b8-bf57-474a-9fe8-d8c71d9c1200-image.png

                                3827169b-c2e7-44f2-9d14-9b1d6f3764f7-image.png

                                I will use Wake Up Times internally with other rulesets rather than trying to use it to drive at the higher Mode level. Presence will be in those rulesets as well.

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

                                *HASS 2025.6.0
                                w/ ZST10-700 fw 7.18.3

                                *Prod MSR in docker/portainer
                                MSR: latest-25139-fbd67abc
                                MQTTController: 25139
                                ZWave Controller: 25139

                                1 Reply Last reply
                                0
                                • G gwp1

                                  @therealdb said in Day mode implementation question:

                                  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.

                                  This is exactly what I'm driving at. I use Mode followed by a number of what I call "shared rules" (Wake-up times, cloudy day, temp < 40º, presence, etc.) that can be/are referenced in many other rulesets. Where I'm hitting my wall is the actual triggering of the modes (Day, Away, Evening, Night).

                                  My curiosity is around how you're actually triggering the modes themselves. The rest... I've got that nailed down.

                                  therealdbT Offline
                                  therealdbT Offline
                                  therealdb
                                  wrote on last edited by
                                  #24

                                  @gwp1 I'm using the alarm to drive modes, as @Pabla
                                  I'm also triggering wakeup mode from the alexa's alarm, so it's possible to move the time and automatically execute actions.

                                  --
                                  On a mission to automate everything.

                                  My MS Reactor contrib
                                  My Luup Plug-ins

                                  G 1 Reply Last reply
                                  0
                                  • therealdbT therealdb

                                    @gwp1 I'm using the alarm to drive modes, as @Pabla
                                    I'm also triggering wakeup mode from the alexa's alarm, so it's possible to move the time and automatically execute actions.

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

                                    @therealdb Interesting approach, using the Echo devices. I'd be concerned over any outage potential, has that been an issue?

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

                                    *HASS 2025.6.0
                                    w/ ZST10-700 fw 7.18.3

                                    *Prod MSR in docker/portainer
                                    MSR: latest-25139-fbd67abc
                                    MQTTController: 25139
                                    ZWave Controller: 25139

                                    therealdbT 1 Reply Last reply
                                    0
                                    • G gwp1

                                      @therealdb Interesting approach, using the Echo devices. I'd be concerned over any outage potential, has that been an issue?

                                      therealdbT Offline
                                      therealdbT Offline
                                      therealdb
                                      wrote on last edited by
                                      #26

                                      @gwp1 I'm in my 3rd year with this automation and it never failed, but I have fallbacks. the alarm is working even if offline, and the house alarm will override the wake-up mode anyway (if the holiday flag is not set). The only minor drawback is that the announcements will not be turned on coordinated with the alarm, but I can live with that.

                                      --
                                      On a mission to automate everything.

                                      My MS Reactor contrib
                                      My Luup Plug-ins

                                      G 1 Reply Last reply
                                      0
                                      • therealdbT therealdb

                                        @gwp1 I'm in my 3rd year with this automation and it never failed, but I have fallbacks. the alarm is working even if offline, and the house alarm will override the wake-up mode anyway (if the holiday flag is not set). The only minor drawback is that the announcements will not be turned on coordinated with the alarm, but I can live with that.

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

                                        @therealdb this idea intrigues me because I occasionally have to wake up on a weekend morning very, very early for a software deployment. As such, I set my usual physical alarm (an ancient Bose Wave radio) as well as adding in a failsafe alarm from my Echo devices.

                                        I don't see in my integration between Hubitat and Alexa anything to do with alarms, however. Are you using Alexa Routines for this? That would require manually editing the routine each time, no?

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

                                        *HASS 2025.6.0
                                        w/ ZST10-700 fw 7.18.3

                                        *Prod MSR in docker/portainer
                                        MSR: latest-25139-fbd67abc
                                        MQTTController: 25139
                                        ZWave Controller: 25139

                                        therealdbT 1 Reply Last reply
                                        0
                                        • G gwp1

                                          @therealdb this idea intrigues me because I occasionally have to wake up on a weekend morning very, very early for a software deployment. As such, I set my usual physical alarm (an ancient Bose Wave radio) as well as adding in a failsafe alarm from my Echo devices.

                                          I don't see in my integration between Hubitat and Alexa anything to do with alarms, however. Are you using Alexa Routines for this? That would require manually editing the routine each time, no?

                                          therealdbT Offline
                                          therealdbT Offline
                                          therealdb
                                          wrote on last edited by
                                          #28

                                          @gwp1 yes. I have a routing setting a virtual flag on when the alarm is triggered. My Alexa UI is localized in Italia, but this should be a trigger named "When alarm goes off" or similar. I'm also getting next alarm time during the night routine, and I'll probably use it to prototype some dynamic lights before the scheduled alarm. Plenty of ideas, so little time 🙂

                                          --
                                          On a mission to automate everything.

                                          My MS Reactor contrib
                                          My Luup Plug-ins

                                          G 1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Recent Topics

                                          • Gradually turn on lights.
                                            G
                                            gwp1
                                            0
                                            4
                                            132

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

                                          • Error After Upgrade
                                            G
                                            gwp1
                                            0
                                            4
                                            104

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

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

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

                                          • Links to MSR from HA
                                            Tom_DT
                                            Tom_D
                                            0
                                            1
                                            90

                                          • Set Reaction > Script Action
                                            wmarcolinW
                                            wmarcolin
                                            0
                                            11
                                            433

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

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

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

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