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

Reactor Ex Machina

Scheduled Pinned Locked Moved Multi-System Reactor
18 Posts 5 Posters 1.2k 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.
  • 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.177
        *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

        *HASS 2025.6.0
        w/ ZST10-700 fw 7.18.3

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

        1 Reply Last reply
        0
        • 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.177
              *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

              *HASS 2025.6.0
              w/ ZST10-700 fw 7.18.3

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

              1 Reply Last reply
              0
              • 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

                        • Gradually turn on lights.
                          G
                          gwp1
                          0
                          4
                          93

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

                        • Error After Upgrade
                          G
                          gwp1
                          0
                          4
                          84

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

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

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

                        • Links to MSR from HA
                          Tom_DT
                          Tom_D
                          0
                          1
                          77

                        • Set Reaction > Script Action
                          wmarcolinW
                          wmarcolin
                          0
                          11
                          416

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

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

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

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