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. Idiot questions. Feel free to ignore.
[Solved] Local expression in Rule does not evaluate as they used to do
CrilleC
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
Home Assistant 2025.11.2 and latest-25315
CrilleC
Topic thumbnail image
Multi-System Reactor
Notice to Docker + ARM Users (RPi 3/4/5 and others)
toggledbitsT
This post does not apply to users of Intel/AMD-based systems. If you are using a Reactor image tagged latest-amd64 or stable-amd64, then this post does not apply to you. It also does not apply to bare-metal installs; it's for users of docker images on ARM-based systems only (principally Raspberry Pi hosts, but could be others). After January 15, 2026, I will no longer produce the aarch64-tagged docker image for Reactor. The ARM images will be arm64 for 64-bit operating systems, and armv7l for 32-bit operating systems. For those of you running a container from the aarch64 image today, this will be a relatively simple change: you just need to switch the image used for your docker container to a differently-tagged image. If you are using docker-compose, then this is a relatively simple matter of changing the image line in your docker-compose.yaml file and then stopping (docker-compose down) and restarting (docker-compose up -d) your Reactor daemon. But there's a catch... not all of you can safely just switch from the aarch64 image to the arm64 image. And, you can't just trust the output of uname -m, for example, because this exposes the CPU architecture, but not the word size of the OS running on that CPU. For Raspberry Pi systems, the transition to 64-bit operating systems was long (starting in 2016) and not always obvious — although there was a first "official" 64-bit OS for RPis in 2020, it did not become a default recommendation in the Raspberry Pi Imager until 2021, and then that was only the default for Pi 3/4 systems with >4GB RAM; it was 2022 before it was universally recommended for all 64-bit CPUs regardless of RAM size. Depending on when you first imaged your RPi system and what default you may have been offered/chosen, you could today easily have a 64-bit CPU Raspberry Pi running a 32-bit version of the operating system. Upgrades along the way would not change this; changing it to fully 64-bit requires a full reimage of the system. To establish if your OS is 64- or 32-bit, log in to your Pi and run: sudo dpkg-architecture -q DEB_HOST_ARCH. If the response is arm64 or aarch64, then you are running a 64-bit OS and you should use the arm64-tagged image. If it's anything else, you are running a 32-bit OS, and you should use the armv7l-tagged image. pi@rpi4-1:~ $ sudo dpkg-architecture -q DEB_HOST_ARCH armhf pi@rpi4-1:~ $ uname -m aarch64 pi@rpi4-1:~ $ In the example above, the uname command reports that the CPU is 64-bit architecture (aarch64), which is true for the host on which I ran these commands, but the DEB_HOST_ARCH value is armhf, indicating a 32-bit operating system. This system has to use the armv7l-tagged image. Other systems will have their own ways of determining the word size of the running OS. Since the majority of Reactor users running ARM systems are on Raspberry Pis, I am able to supply the above instructions, but if you happen to have a different ARM system, you'll need to do some web searching to figure out how to expose that information. Or, you can just try the arm64 image, and if it doesn't start up, try the armv7l image. Remember to always back up your system before making any changes. For everyone, please make this change as soon as possible, and if you have any trouble finding a working image, please (1) go back to the current aarch64 image; and (2) let me know in this thread along with as much detail about your host system as you can offer (including the output of the dpkg-architecture command mentioned above).
Multi-System Reactor
Requesting a proper ARM64/aarch64 Docker image (Pi 5 support)
M
Hi, I'm in the process of migrating from a Raspberry Pi 4 (ARMv7) to a Raspberry Pi 5 (ARMv8/aarch64), but I’ve run into an issue: there is no proper ARMv8/aarch64 image available. None of the existing images run on the Pi 5 - they all exit immediately with code 139 (segmentation fault), which typically indicates that the binaries inside the image are not compatible with the ARM64/aarch64 architecture used by the Pi 5. Would it be possible to publish a correct ARMv8/aarch64 (linux/arm64) image? Building one should be relatively straightforward using docker buildx with multi-arch support. For example, my own Node.js images are built this way: docker buildx build --push \ -t <localrepo>/<project>:<tag> \ --platform=linux/arm64,linux/amd64 \ --file ./apps/<project>/Dockerfile . This produces both the AMD64 and ARM64/v8 variants automatically. Also, as a side note, it may be best to avoid using Alpine as the base image for the ARM64 build, since musl-based builds often cause compatibility issues and unnecessary headaches. A glibc-based base image (e.g., Debian or Ubuntu) tends to work far more reliably on ARM64, especially for Node.js applications. @toggledbits - tagging you in case you missed this. Thanks, mgvra
Multi-System Reactor
Script action and custom timers
therealdbT
Sorry to write here without trying, but I’m flying today. Am I correct if i say that script action with alarm() makes it possible to execute a reaction in a given interval, lets say 15 seconds or 3.5 minutes? That sounds amazing, since I’ve used weird tricks, including a custom controller, just to do this.
Multi-System Reactor
Help resolve change in behaviour post update
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reactor w/HA 2025.11 error on set_datetime service call setting only time
CrilleC
@toggledbits Do you know if this is related to that PR or is it a change they made in 2025.11.1? [latest-25310]2025-11-11T13:16:24.319Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag with { "time": "10:45" } [latest-25310]2025-11-11T13:16:24.320Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag action: { "type": "call_service", "service_data": { "date": (null), "time": "10:45", "datetime": (null), "timestamp": (null) }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_dag" } } [latest-25310]2025-11-11T13:16:24.321Z <HassController:ERR> HassController#hass request 1762866984320<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.321Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "10:45" }) on Entity#hass>input_datetime_vvb_dag failed! [latest-25310]2025-11-11T13:16:24.321Z <HassController:INFO> Service call payload: {"type":"call_service","service_data":{"date":null,"time":"10:45","datetime":null,"timestamp":null},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_dag"},"id":1762866984320} [latest-25310]2025-11-11T13:16:24.322Z <HassController:INFO> Service data: {"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}} [latest-25310]2025-11-11T13:16:24.322Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 0 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Engine#1 action args: { "time": "10:45" } [latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 1 [latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt with { "time": "03:00", "timestamp": 0 } [latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt action: { "type": "call_service", "service_data": { "date": (null), "time": "03:00", "datetime": (null), "timestamp": 0 }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_natt" } } [latest-25310]2025-11-11T13:16:24.324Z <HassController:ERR> HassController#hass request 1762866984323<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.324Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "03:00", "timestamp": 0 }) on Entity#hass>input_datetime_vvb_natt failed! [latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service call payload: {"type":"call_service","service_data":{"date":null,"time":"03:00","datetime":null,"timestamp":0},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_natt"},"id":1762866984323} [latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service data: {"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}} [latest-25310]2025-11-11T13:16:24.324Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 1 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.324Z <Engine:INFO> Engine#1 action args: { "time": "03:00", "timestamp": 0 } [latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 2 [latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Sätt Schema VVB i Home Assistant<AKTIV> all actions completed.
Multi-System Reactor
Reactor Version 25310 : Office Light control via rule in reactor no longer working since last update.
P
Hello, I currently have an office light (connected via a Leviton Zwave Dimmer switch) controlled from a Gen5 Aeotech Zwave switch installed on my Synology 720+ NAS. I run HA(2025.11.10) in a virtual machine from my NAS and Reactor on the container manager of the same NAS. Prior to updating to 25304 the rule I had set to turn the light on to a specific dimming value worked correctly. Now the rule appears to follow the decision tree, however the reaction does not trigger setting the dimming or turning on the office light? Strangely I can still turn the light on and off as well as dim it directly from HASS..? I have tried using the ''try this action'' button in the rules reaction setting and it will not control the light and does not throw an error flagÉ Please help, P.S Reactor has been rock steady for me over the last few years and I'm a big fan of this solution.
Multi-System Reactor
[Solved] alarm() in global expression throws error in log.
CrilleC
Topic thumbnail image
Multi-System Reactor
[Solved] Define function issue in latest-25304
CrilleC
Topic thumbnail image
Multi-System Reactor
No Upgrade Notification for Build 25308?
CatmanV2C
FWIW I'm no longer getting a notification from MSR that there's an update. Just thought I'd mention it C
Multi-System Reactor
Strange behavior in MSR latest-25304 with disabled groups in Reaction
therealdbT
Topic thumbnail image
Multi-System Reactor
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
The reaction stopped working (Google Nest max playing a video)
F
Topic thumbnail image
Multi-System Reactor
Handling Dead Entities and Renamed Entities
PablaP
Hello all.. been a minute! I recently rebuilt my Z wave network and migrated to a new z wave stick. In order to prevent any downtime I kept my original z wave network up and ran a docker version of Z Wave JS UI with my new controller. This way I could add device by device without having any devices down. I finally moved all the devices over to my new stick today. The final step was to migrate everything from my Docker instance of Z Wave JS UI to the HA add-on of Z Wave JS UI. However during this migration some of the names didn't populate correctly which I later managed to import back into Z Wave JS UI. The issue was in Reactor it is stuck on the default names and the entities are not updating. I removed the controller from Reactor, restarted, hard refreshed, and added the controller back however the new entity names have not updated. Also it seems like the old entities from my previous instance of Z Wave JS UI are lingering and not being marked as dead (I believe a certain amount of time needs to lapse before they're marked as dead in Reactor). My goal is to basically purge all the entities for the 'ZWaveJS' controller in Reactor so it can pull all the updated entity names and only the entities that exist in Z Wave JS UI. I cannot find a quick way to do this, I know entities can be deleted one by one, but with over 100 entities this would take long I am guessing that if I added the controller with a new name in in the Reactor config it would pull the updated entities and names but I think that would break my rules since the entity IDs would change (I made sure to name all the entities the exact same as they were previously to prevent this issue).
Multi-System Reactor
Strange behavior for MQTT templates using payload and attributes
therealdbT
Topic thumbnail image
Multi-System Reactor
[MSR] reactor-mqtt-contrib package for additional MQTT templates
therealdbT
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only). Anyway, here's my reactor-mqtt-contrib package: https://github.com/dbochicchio/reactor-mqtt-contrib Simply download yaml files (everything or just the ones you need) and you're good to go. I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them. The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression. Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests
Multi-System Reactor
HA 2025.9.4 Supported Yet?
CatmanV2C
Tangentially did I miss 2025.9.4 getting blessed in MSR? I've been holding off Cheers C
Multi-System Reactor
Rule Set UI bug - RESOLVED
3
Topic thumbnail image
Multi-System Reactor

Idiot questions. Feel free to ignore.

Scheduled Pinned Locked Moved Multi-System Reactor
19 Posts 5 Posters 1.8k 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.
  • CatmanV2C Offline
    CatmanV2C Offline
    CatmanV2
    wrote on last edited by
    #1

    Starting to (very slowly) migrate and improve some of my automation from Reactor to the fabulous MSR. Couple of questions which are probably really obvious but, well, you know me 😞

    Is it possible to repeat an action from a set rule? i.e. if the rule remains triggered for an hour, re-run the set reaction. And to continue re-running that every hour until the rule is reset?

    Sorry if it's really stupid.

    C

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

    wmarcolinW 1 Reply Last reply
    0
    • CatmanV2C CatmanV2

      Starting to (very slowly) migrate and improve some of my automation from Reactor to the fabulous MSR. Couple of questions which are probably really obvious but, well, you know me 😞

      Is it possible to repeat an action from a set rule? i.e. if the rule remains triggered for an hour, re-run the set reaction. And to continue re-running that every hour until the rule is reset?

      Sorry if it's really stupid.

      C

      wmarcolinW Offline
      wmarcolinW Offline
      wmarcolin
      wrote on last edited by
      #2

      @catmanv2

      Hi, if I understand correctly, you can do this using Pulse, determine how long the rule can stay active, and then it resets, and repeats again.

      In the example below, it is active for 15 seconds, then it is false and deactivated for 30 seconds, then it is valid again, and so on repeatably.

      10b6af86-8964-46a8-b6d6-49a8f664d029-image.png

      1 Reply Last reply
      1
      • CatmanV2C Offline
        CatmanV2C Offline
        CatmanV2
        wrote on last edited by
        #3

        That would be perfect, except I have no pulse. Only follow and latch....

        Am I out of date already?

        c

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

        wmarcolinW 1 Reply Last reply
        0
        • CatmanV2C CatmanV2

          That would be perfect, except I have no pulse. Only follow and latch....

          Am I out of date already?

          c

          wmarcolinW Offline
          wmarcolinW Offline
          wmarcolin
          wrote on last edited by
          #4

          @catmanv2

          Ok, depending on the rule/action on a device (ie change validation), this option does or does not appear. When this happens, I create a group and put the device instruction into the group. Surely the group will then have the pulse option.

          1 Reply Last reply
          1
          • CatmanV2C Offline
            CatmanV2C Offline
            CatmanV2
            wrote on last edited by CatmanV2
            #5

            Thanks. That almost works but it fires the 'Reset' action when the pulse ends.

            I mean I can work around that by making two rules that set as opposed to one that sets and resets with an action.

            I was just trying to minimise the number of objects

            C

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

            1 Reply Last reply
            0
            • G Offline
              G Offline
              gwp1
              wrote on last edited by
              #6

              @CatmanV2 Check this thread. It goes thru my trials with PULSE to much success.

              https://smarthome.community/topic/816/solved-will-pulse-work-for-retrying-a-ruleset-if-the-device-hasn-t-responded-as-expected/26

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

              *HASS 2025.11.1
              w/ ZST10-700 fw 7.18.3

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

              CatmanV2C 1 Reply Last reply
              2
              • G gwp1

                @CatmanV2 Check this thread. It goes thru my trials with PULSE to much success.

                https://smarthome.community/topic/816/solved-will-pulse-work-for-retrying-a-ruleset-if-the-device-hasn-t-responded-as-expected/26

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

                @gwp1 thanks, not sure it's directly applicable but I think it's prompted me to a possible restructure of the logic which may do it in fewer components.

                Nope still can't make it work.

                Cheers

                C

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

                G 1 Reply Last reply
                0
                • CatmanV2C CatmanV2

                  @gwp1 thanks, not sure it's directly applicable but I think it's prompted me to a possible restructure of the logic which may do it in fewer components.

                  Nope still can't make it work.

                  Cheers

                  C

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

                  @catmanv2 Read thru the post - my goal was to have pulse implemented to retry setting my t-stats if they did not accept the first attempt and to continue for a set amount of time until they did.

                  I also use it for my washing machine "done" alert - if I don't open the lid, signaling I'm emptying the washer upon completion, it continues up to ten more times announcing for the world to hear (the whole house via Alexa Echo devices) that it needs emptied.

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

                  *HASS 2025.11.1
                  w/ ZST10-700 fw 7.18.3

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

                  CatmanV2C 1 Reply Last reply
                  1
                  • G gwp1

                    @catmanv2 Read thru the post - my goal was to have pulse implemented to retry setting my t-stats if they did not accept the first attempt and to continue for a set amount of time until they did.

                    I also use it for my washing machine "done" alert - if I don't open the lid, signaling I'm emptying the washer upon completion, it continues up to ten more times announcing for the world to hear (the whole house via Alexa Echo devices) that it needs emptied.

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

                    @gwp1 Oh yes, I understand that. The challenge I have is that when the pulse ends the reset reaction is triggered, which is specifically what I was looking to avoid.

                    I currently have a use case where the Server room temperature goes too high (set) and fires a warning reaction. I want it to repeat that warning (pulse does that just fine) but when the temperature drops (reset) it runs another notification. (To say everything is fine)

                    If I pulse the output of the set to get the warning to repeat (which it does) then when the pulse ends, the rule is reset and the 'Everything is fine' notification is sent. Which I want to avoid as everything is not fine.

                    I can absolutely have two rules both of which 'set' and get around it that way, but I was trying to do it with one.

                    C

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

                    CrilleC 1 Reply Last reply
                    0
                    • CatmanV2C CatmanV2

                      @gwp1 Oh yes, I understand that. The challenge I have is that when the pulse ends the reset reaction is triggered, which is specifically what I was looking to avoid.

                      I currently have a use case where the Server room temperature goes too high (set) and fires a warning reaction. I want it to repeat that warning (pulse does that just fine) but when the temperature drops (reset) it runs another notification. (To say everything is fine)

                      If I pulse the output of the set to get the warning to repeat (which it does) then when the pulse ends, the rule is reset and the 'Everything is fine' notification is sent. Which I want to avoid as everything is not fine.

                      I can absolutely have two rules both of which 'set' and get around it that way, but I was trying to do it with one.

                      C

                      CrilleC Offline
                      CrilleC Offline
                      Crille
                      wrote on last edited by
                      #10

                      @catmanv2 If you use pulse you could create a local expression that is true when temperature is below threshold, otherwise false and in the reset reaction you only send the notification if the expression is true.

                      send.PNG

                      reset.PNG

                      CatmanV2C 1 Reply Last reply
                      1
                      • CrilleC Crille

                        @catmanv2 If you use pulse you could create a local expression that is true when temperature is below threshold, otherwise false and in the reset reaction you only send the notification if the expression is true.

                        send.PNG

                        reset.PNG

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

                        @crille ahhh, now that sounds like a good learning exercise! Thanks 🙂

                        C

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

                        1 Reply Last reply
                        0
                        • CatmanV2C Offline
                          CatmanV2C Offline
                          CatmanV2
                          wrote on last edited by CatmanV2
                          #12

                          And it was. Didn't want to start coding but hey 🙂

                          <exit>

                          And I assume I can use this for the other idiot question I was going to ask: Can I change the reactions as an ELSE type thing.

                          So I'm assuming I can have two groups in the set and reset reactions with mutually exclusive conditions

                          Thanks!

                          C

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

                          1 Reply Last reply
                          0
                          • CrilleC Offline
                            CrilleC Offline
                            Crille
                            wrote on last edited by
                            #13

                            Yes, you can have multiple groups in both set reaction and reset reaction, if conditions is not met in a group but in another group those actions will fire instead.

                            CatmanV2C 1 Reply Last reply
                            1
                            • CrilleC Crille

                              Yes, you can have multiple groups in both set reaction and reset reaction, if conditions is not met in a group but in another group those actions will fire instead.

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

                              @crille as I have just found out! Thanks 🙂

                              C

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

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

                                Also don't forget that there's a "repeat...while" group available in reactions, which seems on reading the original problem statement to be a likely candidate for repeating a command or set commands until they are honored.

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

                                CatmanV2C CrilleC 2 Replies Last reply
                                1
                                • toggledbitsT toggledbits

                                  Also don't forget that there's a "repeat...while" group available in reactions, which seems on reading the original problem statement to be a likely candidate for repeating a command or set commands until they are honored.

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

                                  @toggledbits thanks, I tried that but couldn't work out how to define the repeat cadence. 😞

                                  C

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

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

                                    Use a delay action in the repeat group.

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

                                    CatmanV2C 1 Reply Last reply
                                    1
                                    • toggledbitsT toggledbits

                                      Use a delay action in the repeat group.

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

                                      @toggledbits said in Idiot questions. Feel free to ignore.:

                                      Use a delay action in the repeat group.

                                      DOH

                                      Thanks 🙂

                                      C

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

                                      1 Reply Last reply
                                      1
                                      • toggledbitsT toggledbits

                                        Also don't forget that there's a "repeat...while" group available in reactions, which seems on reading the original problem statement to be a likely candidate for repeating a command or set commands until they are honored.

                                        CrilleC Offline
                                        CrilleC Offline
                                        Crille
                                        wrote on last edited by
                                        #19

                                        @toggledbits said in Idiot questions. Feel free to ignore.:

                                        there's a "repeat...while" group

                                        I didn't mention that because I had some issues/questions about it that I have not found time to test futher, so this is a heads up. I will try to find time to test more and create a new topic soon. 🙂

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


                                        Recent Topics

                                        • [Solved] Local expression in Rule does not evaluate as they used to do
                                          CrilleC
                                          Crille
                                          0
                                          5
                                          61

                                        • Reactor (Multi-System/Multi-Hub) Announcements
                                          toggledbitsT
                                          toggledbits
                                          5
                                          130
                                          73.8k

                                        • Home Assistant 2025.11.2 and latest-25315
                                          G
                                          gwp1
                                          0
                                          6
                                          89

                                        • Notice to Docker + ARM Users (RPi 3/4/5 and others)
                                          toggledbitsT
                                          toggledbits
                                          1
                                          1
                                          49

                                        • Requesting a proper ARM64/aarch64 Docker image (Pi 5 support)
                                          M
                                          mgvra
                                          1
                                          3
                                          129

                                        • Script action and custom timers
                                          toggledbitsT
                                          toggledbits
                                          0
                                          4
                                          148

                                        • Help resolve change in behaviour post update
                                          CatmanV2C
                                          CatmanV2
                                          0
                                          12
                                          400

                                        • There is an alternative to homebridge-mqttthing
                                          akbooerA
                                          akbooer
                                          1
                                          2
                                          115

                                        • Reactor w/HA 2025.11 error on set_datetime service call setting only time
                                          CrilleC
                                          Crille
                                          0
                                          6
                                          166

                                        • Reactor Version 25310 : Office Light control via rule in reactor no longer working since last update.
                                          toggledbitsT
                                          toggledbits
                                          0
                                          17
                                          479

                                        • Shelly Wall Display XL
                                          akbooerA
                                          akbooer
                                          2
                                          9
                                          802

                                        • [Solved] alarm() in global expression throws error in log.
                                          toggledbitsT
                                          toggledbits
                                          0
                                          26
                                          890
                                        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