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. Expression to randomly run Global Reactions ?
Date/time condition
tunnusT
Topic thumbnail image
Multi-System Reactor
Device log?
G
@toggledbits is there a log that will show me what rule is turning on a specific device? I've got a switch that has been kicking on at 2200 ET for several nights now and the reactor.log doesn't have a thing in it that I can see on a device level (it being more rules-based).
Multi-System Reactor
Midnight crossing not working in date/time condition (build 25325)
tunnusT
Topic thumbnail image
Multi-System Reactor
Error: Command timeout
G
at _ClientAPI._commandTimeout (http://192.168.1.100:8111/client/ClientAPI.js:807:179 Seeing this randomly when returning to open browser tab after being away awhile. Once, maybe twice a day. "What did you do to trigger it?" Literally nothing, just walked away and returned and there it was. Actions taken in reasonably close proximity to this particular instance of it popping up: I'd restarted the MSR container in Portainer. I'll try to grab some logs here shortly.
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
[Solved] Local expression in Rule does not evaluate as they used to do
CrilleC
Topic thumbnail image
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

Expression to randomly run Global Reactions ?

Scheduled Pinned Locked Moved Multi-System Reactor
39 Posts 4 Posters 5.8k 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.
  • cw-kidC cw-kid

    @elcid said in Expression to randomly run Global Reactions ?:

    I use this to generate a random number that has not been used last time

    That's what I needed!

    ElcidE Offline
    ElcidE Offline
    Elcid
    wrote on last edited by Elcid
    #24

    @cw-kid This is probably more efficient

    ${{int(substr(replace("1234567", randomVal || 0,""),floor(random()*6),1))}}
    

    Then I looked at moving this to MSR as I have it in Reactor, . I found the remove function and this is now easily expanded to larger number and you can easily set a range

    ${{remove( 1..7, randomVal - 1)[floor(random()*6)]}}
    

    @toggledbits , possible bug
    list(1..7]) gives [[1,2,3,4,5,6,7]] a nested array.
    Is that expected.

    toggledbitsT LibraSunL cw-kidC 3 Replies Last reply
    2
    • ElcidE Elcid

      @cw-kid This is probably more efficient

      ${{int(substr(replace("1234567", randomVal || 0,""),floor(random()*6),1))}}
      

      Then I looked at moving this to MSR as I have it in Reactor, . I found the remove function and this is now easily expanded to larger number and you can easily set a range

      ${{remove( 1..7, randomVal - 1)[floor(random()*6)]}}
      

      @toggledbits , possible bug
      list(1..7]) gives [[1,2,3,4,5,6,7]] a nested array.
      Is that expected.

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

      @elcid said in Expression to randomly run Global Reactions ?:

      @toggledbits , possible bug
      list(1..7]) gives [[1,2,3,4,5,6,7]] a nested array.
      Is that expected.

      Yes, because 1..7 on its own produces an array. So wrapping it in list() gives you an array containing an array.

      FWIW, list() is basically deprecated, because lexpjs lets you use common array notation (e.g. [1,2,3,4,5,6,7]) to define an array.

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

      ElcidE 1 Reply Last reply
      0
      • ElcidE Elcid

        @cw-kid This is probably more efficient

        ${{int(substr(replace("1234567", randomVal || 0,""),floor(random()*6),1))}}
        

        Then I looked at moving this to MSR as I have it in Reactor, . I found the remove function and this is now easily expanded to larger number and you can easily set a range

        ${{remove( 1..7, randomVal - 1)[floor(random()*6)]}}
        

        @toggledbits , possible bug
        list(1..7]) gives [[1,2,3,4,5,6,7]] a nested array.
        Is that expected.

        LibraSunL Offline
        LibraSunL Offline
        LibraSun
        wrote on last edited by LibraSun
        #26

        @elcid said in Expression to randomly run Global Reactions ?:

        @cw-kid This is probably more efficient

        ${{int(substr(replace("1234567", randomVal || 0,""),floor(random()*6),1))}}
        

        Then I looked at moving this to MSR as I have it in Reactor, . I found the remove function and this is now easily expanded to larger number and you can easily set a range

        ${{remove( list(1..7)[0], randomVal - 1)[floor(random()*6)]}}
        

        GENIUS! Gonna borrow this.

        @toggledbits , possible bug
        list(1..7]) gives [[1,2,3,4,5,6,7]] a nested array.
        Is that expected.

        Yes, that's expected, since 1..7 itself creates an array – namely, [1,2,3,4,5,6,7] – while list() (now deprecated = avoid in MSR) also turns its argument into an array. I suggest omit list and see if things improve.

        1 Reply Last reply
        0
        • toggledbitsT toggledbits

          @elcid said in Expression to randomly run Global Reactions ?:

          @toggledbits , possible bug
          list(1..7]) gives [[1,2,3,4,5,6,7]] a nested array.
          Is that expected.

          Yes, because 1..7 on its own produces an array. So wrapping it in list() gives you an array containing an array.

          FWIW, list() is basically deprecated, because lexpjs lets you use common array notation (e.g. [1,2,3,4,5,6,7]) to define an array.

          ElcidE Offline
          ElcidE Offline
          Elcid
          wrote on last edited by
          #27

          @toggledbits just discovered that as you posted, is it mentioned in the docs, as I had not come acreoss it?

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

            Yup. That's in the docs.

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

            ElcidE 1 Reply Last reply
            0
            • toggledbitsT toggledbits

              Yup. That's in the docs.

              ElcidE Offline
              ElcidE Offline
              Elcid
              wrote on last edited by Elcid
              #29

              @toggledbits
              Its a bit confusing, i read this
              "[5,7,9], so this function is now obsolete and may be removed later)"
              and tried [1..7], when that failed, I assumed the only way to spread was list(1..7)
              May be add a note about 1..7 being the same as list(1..7). As I found it some what unclear.

              toggledbitsT 1 Reply Last reply
              1
              • ElcidE Elcid

                @toggledbits
                Its a bit confusing, i read this
                "[5,7,9], so this function is now obsolete and may be removed later)"
                and tried [1..7], when that failed, I assumed the only way to spread was list(1..7)
                May be add a note about 1..7 being the same as list(1..7). As I found it some what unclear.

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

                @elcid , it says:

                c4320d3a-82e9-463d-80f3-cf95bd0f4c34-image.png

                I think this is pretty clear. The range operator is documented separately.

                May be add a note about 1..7 being the same as list(1..7).

                But it's not. That's how we got started. 🙂

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

                ElcidE 1 Reply Last reply
                1
                • toggledbitsT toggledbits

                  @elcid , it says:

                  c4320d3a-82e9-463d-80f3-cf95bd0f4c34-image.png

                  I think this is pretty clear. The range operator is documented separately.

                  May be add a note about 1..7 being the same as list(1..7).

                  But it's not. That's how we got started. 🙂

                  ElcidE Offline
                  ElcidE Offline
                  Elcid
                  wrote on last edited by Elcid
                  #31

                  @toggledbits said in Expression to randomly run Global Reactions ?:

                  May be add a note about 1..7 being the same as list(1..7).

                  But it's not. That's how we got started.

                  I mean 1..7 being what I assume list(1..7) would produce a single array. That's why I found it confusing, I think that I expected a array to have [ ] around them.
                  Maybe add "also see range operator".

                  LibraSunL 1 Reply Last reply
                  0
                  • ElcidE Elcid

                    @toggledbits said in Expression to randomly run Global Reactions ?:

                    May be add a note about 1..7 being the same as list(1..7).

                    But it's not. That's how we got started.

                    I mean 1..7 being what I assume list(1..7) would produce a single array. That's why I found it confusing, I think that I expected a array to have [ ] around them.
                    Maybe add "also see range operator".

                    LibraSunL Offline
                    LibraSunL Offline
                    LibraSun
                    wrote on last edited by LibraSun
                    #32

                    @elcid said in Expression to randomly run Global Reactions ?:

                    I mean 1..7 being what I assume list(1..7) would produce

                    Funny you should mention this, since all yesterday, I grappled with the question, "How can I find the minimum of an array in MSR?" (Answer: Not easily at all!) Turns out the min() function only works on a list with 2 elements, not arrays of arbitrary length. In other words, min(1,2,3) yields 1 without a hitch, whereas min([1,2,3]) returns null (for good reason: There's no guarantee the argument will always be a 1-dimensional numeric array!). Same for max().

                    Which led me to the realization that there's no direct way in MSR to "convert" an array into a list. Seems your brain encountered the same type of mental collision while trying to work out your imported expression. 🙂

                    toggledbitsT 1 Reply Last reply
                    0
                    • LibraSunL LibraSun

                      @elcid said in Expression to randomly run Global Reactions ?:

                      I mean 1..7 being what I assume list(1..7) would produce

                      Funny you should mention this, since all yesterday, I grappled with the question, "How can I find the minimum of an array in MSR?" (Answer: Not easily at all!) Turns out the min() function only works on a list with 2 elements, not arrays of arbitrary length. In other words, min(1,2,3) yields 1 without a hitch, whereas min([1,2,3]) returns null (for good reason: There's no guarantee the argument will always be a 1-dimensional numeric array!). Same for max().

                      Which led me to the realization that there's no direct way in MSR to "convert" an array into a list. Seems your brain encountered the same type of mental collision while trying to work out your imported expression. 🙂

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

                      @librasun My notes in the code:

                      911a7b09-dc4b-4bd3-8cdf-ac8e14be82bf-image.png

                      Guess it's time to get to work.

                      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
                      1
                      • cw-kidC cw-kid

                        @librasun

                        What makes the expression run and generate a new number after a period of time?

                        This is what I have so far.

                        Trigger is the virtual switch in Vera.
                        Pulse every 1 seconds and repeat every 60 seconds.

                        40a55606-5dd6-4434-8131-03320411fb36-image.png

                        Set Reaction - Groups that look at the expression named "ChooseColour" and its current number value and then runs a Global Reaction now directly sets that colour on the LED strip.

                        c928ebf7-c1cf-4400-9230-0c3d15953375-image.png

                        The random number generator expression named "ChooseColour" this is a rule expression not a Global Expression.

                        b1a6ba74-2a13-40bc-b9f3-5cdebc0be840-image.png

                        I added an 1 minute interval to the triggers and the virtual switch is true trigger is also pulsing every minute.

                        The expression is now changing numbers every minute, but the reactions don't seem to be running as the colour is stuck and not changing.

                        Also I think this expression generates the number zero which I don't have assigned to any reaction.

                        LibraSunL Offline
                        LibraSunL Offline
                        LibraSun
                        wrote on last edited by
                        #34

                        @cw-kid Just so you know, I have a "Color Cycler" rule that uses the [Entity Action] [Set Color RGB] action with this expression inside each field ("R", "G" and "B"):

                        ${{ floor(random()*255) }}
                        

                        which makes the associated light (a Hue bulb) adopt a perfectly random color. Just something you might consider trying.

                        1 Reply Last reply
                        0
                        • cw-kidC Offline
                          cw-kidC Offline
                          cw-kid
                          wrote on last edited by
                          #35

                          Thanks I will try the "Color Cycler" in a brand new rule to test it out.

                          I haven't as yet looked at updating my current rule with the new expression to always guarantee a new random number that hasn't been repeated etc.

                          I will have a look over the weekend. Sure I will have questions.

                          Cheers

                          1 Reply Last reply
                          0
                          • ElcidE Elcid

                            @cw-kid This is probably more efficient

                            ${{int(substr(replace("1234567", randomVal || 0,""),floor(random()*6),1))}}
                            

                            Then I looked at moving this to MSR as I have it in Reactor, . I found the remove function and this is now easily expanded to larger number and you can easily set a range

                            ${{remove( 1..7, randomVal - 1)[floor(random()*6)]}}
                            

                            @toggledbits , possible bug
                            list(1..7]) gives [[1,2,3,4,5,6,7]] a nested array.
                            Is that expected.

                            cw-kidC Offline
                            cw-kidC Offline
                            cw-kid
                            wrote on last edited by cw-kid
                            #36

                            @elcid said in Expression to randomly run Global Reactions ?:

                            remove( 1..7, randomVal - 1)[floor(random()*6)]

                            I've just tried using this in my rule set, I added it as the expression for the rule. When I press the play button next to it, it seems to work and changes to different numbers between 1 to 7 etc.

                            00c35ba9-2e00-4e8a-9466-a9bdcab01860-image.png

                            However when I restart Reactor it says it cannot find the Global Expression named "randomVal".

                            So I then created it as a Global Expression, the error has now gone away, but I don't understand what this Global Expression is for?

                            be503a5a-92f9-4a03-bc35-2a9061f6fc94-image.png

                            Thanks

                            1 Reply Last reply
                            0
                            • ElcidE Offline
                              ElcidE Offline
                              Elcid
                              wrote on last edited by Elcid
                              #37

                              That should be used in the reaction as image below
                              Screenshot_20210619-173952.png

                              The expression global or normal is left blank. so every time your rule reaction runs it sets a new unique random number, ready for next time

                              cw-kidC 1 Reply Last reply
                              1
                              • ElcidE Elcid

                                That should be used in the reaction as image below
                                Screenshot_20210619-173952.png

                                The expression global or normal is left blank. so every time your rule reaction runs it sets a new unique random number, ready for next time

                                cw-kidC Offline
                                cw-kidC Offline
                                cw-kid
                                wrote on last edited by cw-kid
                                #38

                                @elcid

                                This look better now?

                                I have added the Set Variable in the Set Reaction and made the expression empty:

                                fec35140-bd79-4484-85e6-15ea34d22fe6-image.png

                                1 Reply Last reply
                                1
                                • cw-kidC Offline
                                  cw-kidC Offline
                                  cw-kid
                                  wrote on last edited by
                                  #39

                                  It looks to be working OK. Its changing the colours on the LED strip every 5 minutes currently. I'll leave it running for a while tonight.

                                  Thanks.

                                  1 Reply Last reply
                                  0
                                  • toggledbitsT toggledbits locked this topic on
                                  Reply
                                  • Reply as topic
                                  Log in to reply
                                  • Oldest to Newest
                                  • Newest to Oldest
                                  • Most Votes


                                  Recent Topics

                                  • Home Assistant Connect ZWA-2 & ZBT-2
                                    therealdbT
                                    therealdb
                                    1
                                    3
                                    46

                                  • Date/time condition
                                    tunnusT
                                    tunnus
                                    0
                                    3
                                    59

                                  • Is there a way to turn this section (image in post) off?
                                    toggledbitsT
                                    toggledbits
                                    0
                                    1
                                    54

                                  • Device log?
                                    toggledbitsT
                                    toggledbits
                                    0
                                    2
                                    88

                                  • Midnight crossing not working in date/time condition (build 25325)
                                    tunnusT
                                    tunnus
                                    0
                                    3
                                    95

                                  • Error: Command timeout
                                    G
                                    gwp1
                                    0
                                    6
                                    211

                                  • Reactor (Multi-System/Multi-Hub) Announcements
                                    toggledbitsT
                                    toggledbits
                                    5
                                    131
                                    75.5k

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

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

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

                                  • Requesting a proper ARM64/aarch64 Docker image (Pi 5 support)
                                    M
                                    mgvra
                                    1
                                    3
                                    219
                                  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