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

Reactor Ex Machina

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

    @toggledbits was looking thru rule sets and updating which (new) lights I wanted REMII to impact and saw that this...

    4711b0df-5e98-4992-bb25-d0e53203f0e8-image.png

    ...is showing as (missing) in the rule Deactivatedand looking in the dropdown of Variables it appears I cannot select that local expression (only Global) as I did when originally building this out back in 2021.

    27f7025c-057e-441a-88ea-dc4bdf39614d-image.png

    In looking at the rule Active Period I'm seeing:
    487074ef-3bfa-4a84-b03d-ed6d920c118c-image.png which appears to be pointing to setting a variable in a rule?

    It's admittedly been a couple years since this was built and it's def not fresh in my memory.

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

    *HASS 2025.3.4
    w/ ZST10-700 fw 7.18.3

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

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

      You didn't show the local expressions?

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

      G 1 Reply Last reply
      0
      • toggledbitsT toggledbits

        You didn't show the local expressions?

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

        @toggledbits I guess that's the problem: there are only Global expressions selectable. Looking thru the rules:

        d4dd50f4-f37f-4a5a-b7c7-1f70b39cb1aa-image.png

        15189579-1ed6-4fff-9259-5750396878ef-image.png 7e4615fc-2621-40e8-a9c8-2abee0e1075b-image.png

        61dfcd60-2e89-41a5-895d-04f42f72d67e-image.png

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

        *HASS 2025.3.4
        w/ ZST10-700 fw 7.18.3

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

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

          Back in mid-2021 there were a bunch of changes to variable evaluation and the rules around that, and among them, a rule cannot set or examine a local variable in another rule. I suspect you're just noticing the effect of that here. The engine still runs those rules, but you cannot edit them and leave them in that condition. The shared variable needs to be moved to global scope.

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

          G 1 Reply Last reply
          0
          • toggledbitsT toggledbits

            Back in mid-2021 there were a bunch of changes to variable evaluation and the rules around that, and among them, a rule cannot set or examine a local variable in another rule. I suspect you're just noticing the effect of that here. The engine still runs those rules, but you cannot edit them and leave them in that condition. The shared variable needs to be moved to global scope.

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

            @toggledbits I suspected that might be the case (something changed). Of course, I've poked at the Deactivated rule this morning so I've probably broken things now.

            I'm guessing I need to convert any Local expression "sets" to Global to fix this?

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

            *HASS 2025.3.4
            w/ ZST10-700 fw 7.18.3

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

            toggledbitsT 1 Reply Last reply
            0
            • G gwp1

              @toggledbits I suspected that might be the case (something changed). Of course, I've poked at the Deactivated rule this morning so I've probably broken things now.

              I'm guessing I need to convert any Local expression "sets" to Global to fix this?

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

              @gwp1 said in Reactor Ex Machina:

              I'm guessing I need to convert any Local expression "sets" to Global to fix this?

              Not all, just the ones that referred to from other rules.

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

              R 1 Reply Last reply
              1
              • toggledbitsT toggledbits

                @gwp1 said in Reactor Ex Machina:

                I'm guessing I need to convert any Local expression "sets" to Global to fix this?

                Not all, just the ones that referred to from other rules.

                R Offline
                R Offline
                retireditguy
                wrote on last edited by
                #7

                @toggledbits
                Working on migrating off of Vera. I am also trying to use Reactor Ex Machina and wonder whether the changes you referenced above might also keep REM from shutting down properly. REM toggles the lights off and on up until the expiration of the active period. REM ends without turning all of the lights off. The construct I am wondering about is - {{ each light in REM_Lights: performAction( light, 'power_switch.off' , { } 😞 0 }}
                I assume this is supposed to turn all of the lights in the array. I modified the "code" to handle the local/global variable change by moving cycler_stim to Global , but otherwise my REM is as it was after you modified "Deactivate REM' back on May 28, 2021. Any ideas?

                https://smarthome.community/topic/557/solved-random-ghosting-of-lights-when-away/32?_=1677904265383

                G 1 Reply Last reply
                0
                • R Offline
                  R Offline
                  retireditguy
                  wrote on last edited by retireditguy
                  #8

                  The Board changed ) : to an emoticon.

                  1 Reply Last reply
                  0
                  • R Offline
                    R Offline
                    retireditguy
                    wrote on last edited by
                    #9
                    This post is deleted!
                    1 Reply Last reply
                    0
                    • R retireditguy

                      @toggledbits
                      Working on migrating off of Vera. I am also trying to use Reactor Ex Machina and wonder whether the changes you referenced above might also keep REM from shutting down properly. REM toggles the lights off and on up until the expiration of the active period. REM ends without turning all of the lights off. The construct I am wondering about is - {{ each light in REM_Lights: performAction( light, 'power_switch.off' , { } 😞 0 }}
                      I assume this is supposed to turn all of the lights in the array. I modified the "code" to handle the local/global variable change by moving cycler_stim to Global , but otherwise my REM is as it was after you modified "Deactivate REM' back on May 28, 2021. Any ideas?

                      https://smarthome.community/topic/557/solved-random-ghosting-of-lights-when-away/32?_=1677904265383

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

                      @retireditguy Here are my rulesets and it works just fine.

                      be598ee8-3e73-4620-be34-3190c63722cb-image.png

                      efde0d01-4b33-4f6b-985e-9acbeec9ccc2-image.png

                      e992eb3e-f092-4c9f-b9a3-ac5b43846008-image.png

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

                      *HASS 2025.3.4
                      w/ ZST10-700 fw 7.18.3

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

                      1 Reply Last reply
                      0
                      • R Offline
                        R Offline
                        retireditguy
                        wrote on last edited by
                        #11

                        Except for the values defining the active time in "Active Period", our scripts are identical. Additionally we are both controlling Hubitat systems. My testing seems to indicate that REM only shuts off one light at the end of the defined period. I believe it was the last one turned on. Are you sure that REM turns off all of your lights at the end of the defined period? I suspect there may be something wrong with the execution of the statement {{ each light in REM_Lights: performAction( light, 'power_switch.off' , { } ) : 0 }} as I noted above. Another "anomaly" occurs at start-up. The 3 scripts together are sensitive to the start sequence. If "Cycler" is started before both "Active Period" and "Deactivated", "Cycler" will trigger as soon as either starts since they both change cycler_stim.

                        toggledbitsT 1 Reply Last reply
                        0
                        • R retireditguy

                          Except for the values defining the active time in "Active Period", our scripts are identical. Additionally we are both controlling Hubitat systems. My testing seems to indicate that REM only shuts off one light at the end of the defined period. I believe it was the last one turned on. Are you sure that REM turns off all of your lights at the end of the defined period? I suspect there may be something wrong with the execution of the statement {{ each light in REM_Lights: performAction( light, 'power_switch.off' , { } ) : 0 }} as I noted above. Another "anomaly" occurs at start-up. The 3 scripts together are sensitive to the start sequence. If "Cycler" is started before both "Active Period" and "Deactivated", "Cycler" will trigger as soon as either starts since they both change cycler_stim.

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

                          @retireditguy said in Reactor Ex Machina:

                          I suspect there may be something wrong with the execution of the statement {{ each light in REM_Lights: performAction( light, 'power_switch.off' , { } ) : 0 }}

                          The expression you show is incorrect -- where you have a colon (:) at the end of the each subexpression (after the closing paren of performAction()) should be a semicolon (;), like this:

                          ${{ each light in REM_lights: performAction( light, 'power_switch.off', {} ); 0 }}
                          

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

                          G 1 Reply Last reply
                          0
                          • toggledbitsT toggledbits

                            @retireditguy said in Reactor Ex Machina:

                            I suspect there may be something wrong with the execution of the statement {{ each light in REM_Lights: performAction( light, 'power_switch.off' , { } ) : 0 }}

                            The expression you show is incorrect -- where you have a colon (:) at the end of the each subexpression (after the closing paren of performAction()) should be a semicolon (;), like this:

                            ${{ each light in REM_lights: performAction( light, 'power_switch.off', {} ); 0 }}
                            
                            G Offline
                            G Offline
                            gwp1
                            wrote on last edited by
                            #13

                            @toggledbits Not gonna lie, you made me go squint at mine just to be sure.

                            d666bb65-b54c-4cb9-b6e1-e06d65544a3e-image.png

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

                            *HASS 2025.3.4
                            w/ ZST10-700 fw 7.18.3

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

                            1 Reply Last reply
                            0
                            • K Offline
                              K Offline
                              kellyjelly32
                              wrote on last edited by kellyjelly32
                              #14

                              If anyone is interested, I will copy/paste my code here for my solution. It builds on the initial "Reactor Ex Machina" from 2021 but incorporates the changes made to MSR since then. I also modified it in such a way to have the OFF switching done individually for each light with definable delays. A bathroom light that way can go OFF after a random 1-5m while the kitchen stays on for longer for example. I made some other changes as well to suit my needs. It works for me, it might not for you.

                              You need four "Global Expressions":

                              • REM_lights
                              #list of all DeusExMachina (now ReactorExMachina REM) lights to control
                              #this is an array [ ]
                              #every entity in ' ' (apostrophes) separated by , (comma) in new line
                              #check entity list to get canonical ID to be used
                              #comments start with hash and are ignored
                              [
                              'hass>input_boolean_testlight', #Test 
                              'hass>input_boolean_testlight2', #test2
                              'hass>input_boolean_testlight3', #Stephan
                              'hass>input_boolean_testlight4', #Stephan
                              'hass>input_boolean_testlight5', #Stephan
                              'hass>input_boolean_testlight5', #Stephan
                              'hass>input_boolean_testlight5' #Stephan
                              ]
                              
                              • REM_dummy (leave empty)

                              • REM_cycler_stimulus (leave empty)

                              • REM_status (leave empty)

                              If you want a light to be more frequently "ghosted" add it multiple times into the list. In my case light5. If you are on HA, you can add via the helper section some virtual toggles as I did to test your setup. Probably also possible on other platforms.

                              My rules are like this:
                              e1826f8b-27c8-4248-89c3-2790d39dba45-image.png

                              Start & Stop rule (via set/reset reaction), the ghost switching on the lights and then for each light a ghost which switches off so I can manage the individual behavior per light.

                              The Start&Stop rule:
                              47c893f8-0bdd-4829-b906-64a227863fef-image.png ab665d14-6b87-4236-9dee-a6cce644e73d-image.png

                              The reset code bit, hard to read/copy from screenshot:

                              ${{ each light in REM_lights: performAction( light, 'power_switch.off', {} ); 0 }}
                              

                              The ghost for switching ON a random element/light from the list:
                              b0a190e8-62b0-4ed9-aa55-08485dee378a-image.png 340d6e2f-0eba-48f5-a19d-4bf6590ef812-image.png

                              Code:

                              ${{ performAction( REM_lights[ floor( random() * len( REM_lights ) ) ], 'toggle.toggle', {} ) }}
                              
                              ${{ random()*600 + 600 }}
                              
                              ${{ REM_cycler_stimulus + 1 }}
                              

                              The light-specific OFF ghost:
                              055a3fa0-7b73-4633-b631-76aa858f42db-image.png

                              ${{ random()*600 + 300 }}
                              

                              Some explanation for random function and the values used with it. It randomly generates number between 0 and 1 (example: 0.4739302) The delay time is in seconds. So the above example will create a delay of 300s minimum plus anything between 0 to 10m, effectively a random time of 5m-15m. See what works for you.

                              This REM is working well for me and I am now finally ready to migrate it all to HA after many years on my trusty Vera Lite which is about to die of flash memory degradation.

                              a1a102f8-ee20-47c6-b45d-663b42769885-image.png

                              3 1 Reply Last reply
                              2
                              • 3 Offline
                                3 Offline
                                3rdStng
                                wrote on last edited by 3rdStng
                                #15

                                Ahh... I miss that app. Probably one of my favorites from my Vera days. The "Lighting Director" app on Hubitat just isn't the same.

                                Thanks for posting your setup @kellyjelly32. I've mocked this into my MSR and if all works well, DeusExMachina returns. Well kinda

                                1 Reply Last reply
                                0
                                • K kellyjelly32

                                  If anyone is interested, I will copy/paste my code here for my solution. It builds on the initial "Reactor Ex Machina" from 2021 but incorporates the changes made to MSR since then. I also modified it in such a way to have the OFF switching done individually for each light with definable delays. A bathroom light that way can go OFF after a random 1-5m while the kitchen stays on for longer for example. I made some other changes as well to suit my needs. It works for me, it might not for you.

                                  You need four "Global Expressions":

                                  • REM_lights
                                  #list of all DeusExMachina (now ReactorExMachina REM) lights to control
                                  #this is an array [ ]
                                  #every entity in ' ' (apostrophes) separated by , (comma) in new line
                                  #check entity list to get canonical ID to be used
                                  #comments start with hash and are ignored
                                  [
                                  'hass>input_boolean_testlight', #Test 
                                  'hass>input_boolean_testlight2', #test2
                                  'hass>input_boolean_testlight3', #Stephan
                                  'hass>input_boolean_testlight4', #Stephan
                                  'hass>input_boolean_testlight5', #Stephan
                                  'hass>input_boolean_testlight5', #Stephan
                                  'hass>input_boolean_testlight5' #Stephan
                                  ]
                                  
                                  • REM_dummy (leave empty)

                                  • REM_cycler_stimulus (leave empty)

                                  • REM_status (leave empty)

                                  If you want a light to be more frequently "ghosted" add it multiple times into the list. In my case light5. If you are on HA, you can add via the helper section some virtual toggles as I did to test your setup. Probably also possible on other platforms.

                                  My rules are like this:
                                  e1826f8b-27c8-4248-89c3-2790d39dba45-image.png

                                  Start & Stop rule (via set/reset reaction), the ghost switching on the lights and then for each light a ghost which switches off so I can manage the individual behavior per light.

                                  The Start&Stop rule:
                                  47c893f8-0bdd-4829-b906-64a227863fef-image.png ab665d14-6b87-4236-9dee-a6cce644e73d-image.png

                                  The reset code bit, hard to read/copy from screenshot:

                                  ${{ each light in REM_lights: performAction( light, 'power_switch.off', {} ); 0 }}
                                  

                                  The ghost for switching ON a random element/light from the list:
                                  b0a190e8-62b0-4ed9-aa55-08485dee378a-image.png 340d6e2f-0eba-48f5-a19d-4bf6590ef812-image.png

                                  Code:

                                  ${{ performAction( REM_lights[ floor( random() * len( REM_lights ) ) ], 'toggle.toggle', {} ) }}
                                  
                                  ${{ random()*600 + 600 }}
                                  
                                  ${{ REM_cycler_stimulus + 1 }}
                                  

                                  The light-specific OFF ghost:
                                  055a3fa0-7b73-4633-b631-76aa858f42db-image.png

                                  ${{ random()*600 + 300 }}
                                  

                                  Some explanation for random function and the values used with it. It randomly generates number between 0 and 1 (example: 0.4739302) The delay time is in seconds. So the above example will create a delay of 300s minimum plus anything between 0 to 10m, effectively a random time of 5m-15m. See what works for you.

                                  This REM is working well for me and I am now finally ready to migrate it all to HA after many years on my trusty Vera Lite which is about to die of flash memory degradation.

                                  a1a102f8-ee20-47c6-b45d-663b42769885-image.png

                                  3 Offline
                                  3 Offline
                                  3rdStng
                                  wrote on last edited by
                                  #16

                                  @kellyjelly32 Is there a way to specify how many lights should be on at one time? I tested REM last night and the most on at the same time appeared to be two. I'm fine with this, but curious if there was an option or way to adjust it. Again, thanks for sharing your logic.

                                  1 Reply Last reply
                                  0
                                  • K Offline
                                    K Offline
                                    kellyjelly32
                                    wrote on last edited by
                                    #17

                                    My REM "Switch ON Ghost" is using the "toggle" action. This means it can also switch a light off if the one chosen randomly is (still) on. Change that to power_switch.on and it can only switch lights ON. This will at least prevent the "ON Ghost" from turning/toggling lights OFF. Then it all comes down the the times used to in the random() functions between the "ON Ghost" toggles/switches lights ON and the "OFF Ghosts" switching lights OFF.
                                    Probably the introduction of another variable like REM_active_lights which is increased every time the "ON Ghost" switches something ON and decreased when the "OFF Ghost xyz" turns it off, you can track how many lights are ON. Add a AND trigger in the "On Ghost" that states "REM_Active_lights" equal/smaller than "4" and you can make sure that no more than four lights will be on at any time.
                                    Probably you need to somehow force the MSR to re-evaluate the "Ghost ON" conditions to start another cycle, once enough lights are out again. Maybe another "Ghost" to keep track of the REM_Active_lights, when below 4 to count the REM_cycler_stimulus up to re-start the ON Ghost.

                                    I will see if I can get it to work...

                                    1 Reply Last reply
                                    0
                                    • 3 Offline
                                      3 Offline
                                      3rdStng
                                      wrote on last edited by
                                      #18

                                      I'm not in need of it. As I was moving off Lighting Director I just happened to notice they had a max number of lights. I think the OG DeusExMachina did too. I think how you have it would be more lifelike. Especially when you couple of a few specific OFF rules so the lights turn off faster than 10-20 minutes.

                                      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

                                      • [Solved] Limit HA Entity in MSR
                                        wmarcolinW
                                        wmarcolin
                                        0
                                        7
                                        63

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

                                      • Disaster recovery and virtualisation
                                        CatmanV2C
                                        CatmanV2
                                        0
                                        5
                                        584

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

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

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

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

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

                                      • Deleting widgets
                                        toggledbitsT
                                        toggledbits
                                        0
                                        4
                                        440

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