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. Error on start for MSR after update to 24293
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

Error on start for MSR after update to 24293

Scheduled Pinned Locked Moved Multi-System Reactor
14 Posts 3 Posters 930 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.
  • T Offline
    T Offline
    tamorgen
    wrote on last edited by
    #1

    @toggledbits
    I just upgraded to version MSR 24293, bare metal running on Fedora. Upon restart, I am getting a error banner:

    TypeError: Cannot read properties of undefined (reading 'value')
        at Rulesets.getRulesets (https://*************************/client/Rulesets.js:111:38)
        at async StatusTab.updateSetRules (https://*************************/reactor/en-US/lib/js/reactor-ui-status.js:276:28)
        at async StatusTab.drawSetRules (https://*************************/reactor/en-US/lib/js/reactor-ui-status.js:270:13)
    You may report this error, but do not screen shot it. Copy-paste the 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.
    

    I followed the new directions about npm

    npm i --no-save --no-package-lock --omit dev

    Any idea what the issue is?

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

      Hard refresh the browser, and if the error persists, press F12 (or whatever works for your browser) to open the browser console and see if there are any other error messages logged. That error suggests it can't read the Ruleset index, but that's a pretty basic function. If you can see your Rulesets listed in the left navigation, the index is fine.

      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
      0
      • T Offline
        T Offline
        tamorgen
        wrote on last edited by tamorgen
        #3

        Hard refresh on Chrome did not solve the issue, however, the rulesets are listed on the left side navigation, as you stated.

        Dev console shows one error in Rulesets.js

        image.png

        image.png

        image.png

        Running:

        MSR latest-24293-ea42a81d
        ZWaveJSController 0.1.24293
        Fedora Linux 40 (Server Edition)

        Home Assistant
        Core 2024.10.3
        Supervisor 2024.10.2
        Operating System 13.2
        Frontend 20240906.0

        Chrome: Windows, Version 129.0.6668.59 (Official Build) (32-bit)

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

          OK. Looks like a nuisance race condition. After acknowledging the error, if you're not getting any other errors, don't worry about it. I'll have a fix along in a bit.

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

          T G 2 Replies Last reply
          0
          • toggledbitsT toggledbits

            OK. Looks like a nuisance race condition. After acknowledging the error, if you're not getting any other errors, don't worry about it. I'll have a fix along in a bit.

            T Offline
            T Offline
            tamorgen
            wrote on last edited by
            #5

            @toggledbits,
            Okay, thanks. I don't receive any other errors, and it only appears when I initially load the page or do a refresh.

            1 Reply Last reply
            0
            • toggledbitsT toggledbits

              OK. Looks like a nuisance race condition. After acknowledging the error, if you're not getting any other errors, don't worry about it. I'll have a fix along in a bit.

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

              @toggledbits hate to pile on... I got this:

                  at _ClientAPI.sendrpc (https://192.168.1.241:8554/client/ClientAPI.js:309:45)
                  at _ClientAPI.echo (https://192.168.1.241:8554/client/ClientAPI.js:649:31)
                  at HTMLAnchorElement.handleTabClick (https://192.168.1.241:8554/reactor/en-US/lib/js/reactor-ui-core.js:132:13)
                  at HTMLAnchorElement.dispatch (https://192.168.1.241:8554/node_modules/jquery/dist/jquery.min.js:2:40035)
                  at v.handle (https://192.168.1.241:8554/node_modules/jquery/dist/jquery.min.js:2:38006)
              

              This was after using Tools > Restart Reactor because I wanted to ensure everything was good back and forth between Hubitat and MSR. I'm missing capabilities from my Roborock that were there prior to the release upgrade, specifically appScene and appRoomClean and appRoomResume. No updates have been made to the app in Hubitat, those capabilities are still there.

              db2011b5-35b0-4efb-a1f6-0fefad526d93-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

              toggledbitsT 1 Reply Last reply
              0
              • G gwp1

                @toggledbits hate to pile on... I got this:

                    at _ClientAPI.sendrpc (https://192.168.1.241:8554/client/ClientAPI.js:309:45)
                    at _ClientAPI.echo (https://192.168.1.241:8554/client/ClientAPI.js:649:31)
                    at HTMLAnchorElement.handleTabClick (https://192.168.1.241:8554/reactor/en-US/lib/js/reactor-ui-core.js:132:13)
                    at HTMLAnchorElement.dispatch (https://192.168.1.241:8554/node_modules/jquery/dist/jquery.min.js:2:40035)
                    at v.handle (https://192.168.1.241:8554/node_modules/jquery/dist/jquery.min.js:2:38006)
                

                This was after using Tools > Restart Reactor because I wanted to ensure everything was good back and forth between Hubitat and MSR. I'm missing capabilities from my Roborock that were there prior to the release upgrade, specifically appScene and appRoomClean and appRoomResume. No updates have been made to the app in Hubitat, those capabilities are still there.

                db2011b5-35b0-4efb-a1f6-0fefad526d93-image.png

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

                @gwp1 said in Error on start for MSR after update to 24293:

                @toggledbits hate to pile on... I got this:

                Rules of engagement haven't changed. That's clearly redacted content you posted, with no source... pop-up modal dialog? In the browser log stream? Where's the first line of the error saying what the error actually is?

                @gwp1 said in Error on start for MSR after update to 24293:

                I'm missing capabilities from my Roborock that were there prior to the release upgrade, specifically appScene and appRoomClean and appRoomResume.

                Open a separate thread for a separate problem. That said, those aren't Reactor capabilities, so be really detailed (per the posting guidelines) with what you give me there. Thank you.

                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

                  @gwp1 said in Error on start for MSR after update to 24293:

                  @toggledbits hate to pile on... I got this:

                  Rules of engagement haven't changed. That's clearly redacted content you posted, with no source... pop-up modal dialog? In the browser log stream? Where's the first line of the error saying what the error actually is?

                  @gwp1 said in Error on start for MSR after update to 24293:

                  I'm missing capabilities from my Roborock that were there prior to the release upgrade, specifically appScene and appRoomClean and appRoomResume.

                  Open a separate thread for a separate problem. That said, those aren't Reactor capabilities, so be really detailed (per the posting guidelines) with what you give me there. Thank you.

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

                  @toggledbits yes, I'd planned to split out the Roborock issue but included it above in case it provided value to troubleshooting.

                  To the original issue, the content is from a pop-up, yes.

                  Steps to reproduce: Tools > Restart Reactor

                  Result:
                  7c5e2881-7e8c-404c-bbea-ec4a8af9dd0a-image.png

                  Following the guidance, I did not screenshot it initially. Clicking on the text auto-highlights it; I present it here:

                  ReferenceError: payload is not defined
                      at _ClientAPI.sendrpc (https://192.168.1.241:8554/client/ClientAPI.js:309:45)
                      at _ClientAPI.echo (https://192.168.1.241:8554/client/ClientAPI.js:649:31)
                      at HTMLAnchorElement.handleTabClick (https://192.168.1.241:8554/reactor/en-US/lib/js/reactor-ui-core.js:132:13)
                      at HTMLAnchorElement.dispatch (https://192.168.1.241:8554/node_modules/jquery/dist/jquery.min.js:2:40035)
                      at v.handle (https://192.168.1.241:8554/node_modules/jquery/dist/jquery.min.js:2:38006)
                  

                  As to the separate issue... doing another Testing > Restart Reactor to obtain the above screenshot appears to have fixed the issue - the missing capabilities/commands are back and the rules are no longer erroring. 🤷♂

                  *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
                  • toggledbitsT Offline
                    toggledbitsT Offline
                    toggledbits
                    wrote on last edited by
                    #9

                    OK. That's benign, I think. I'm guessing you are switching to another tab pretty quickly, while the restart and browser-side reconnect are still happening. When you switch tabs, there's a query made to the Reactor service (which isn't running at that moment), and that's what's failing. If you wait on the Tools tab until Reactor reports it's connected again, then switch tabs, I'll bet you don't get the error.

                    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
                    1
                    • toggledbitsT toggledbits

                      OK. That's benign, I think. I'm guessing you are switching to another tab pretty quickly, while the restart and browser-side reconnect are still happening. When you switch tabs, there's a query made to the Reactor service (which isn't running at that moment), and that's what's failing. If you wait on the Tools tab until Reactor reports it's connected again, then switch tabs, I'll bet you don't get the error.

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

                      @toggledbits Yes, if I am patient and don't touch anything until MSR is showing green/CONNECTED it does not occur.

                      Patience is a tall order before 0900 EDT sans coffee on a Monday...

                      😬

                      *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

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

                        As I said, it's a benign message. I'll make sure it's not so picky on the next build.

                        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
                        0
                        • G gwp1

                          @toggledbits Yes, if I am patient and don't touch anything until MSR is showing green/CONNECTED it does not occur.

                          Patience is a tall order before 0900 EDT sans coffee on a Monday...

                          😬

                          T Offline
                          T Offline
                          tamorgen
                          wrote on last edited by
                          #12

                          modules:composer.user-said-in, @gwp1, Error on start for MSR after update to 24293

                          Patience is a tall order before 0900 EDT sans coffee on a Monday

                          Get some coffee 😄

                          Glad I'm not the only one that had the error. I thought I broke something.

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

                            By the way, just so you all know, all of these errors were happening before this build, you just didn't see them. The code structure that allowed the race condition that opened this thread has been there since 2021; few would get it, and maybe not even consistently (the nature of race conditions), and when it happened, it would just be logged in the browser console (which most people don't have up) but otherwise not much effect. Same with the post-restart tab switch message -- logged quietly in a place nobody ever looked. When I added the global error handling, a bunch of things crawled out of the woodwork... as they say, sunlight is a good disinfectant. A ton of things were found and fixed by that before releasing this build, but there will always be differences in the way I approach the app vs how everyone else does, so now your eyes are on things I wouldn't easily see. Alarming, maybe, but not harmful so far, and finding these things and fixing them really improves code quality. I suspect we'll have a few more of these in the coming weeks, but just report and keep on doing what you're doing (in the app and generally).

                            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

                              By the way, just so you all know, all of these errors were happening before this build, you just didn't see them. The code structure that allowed the race condition that opened this thread has been there since 2021; few would get it, and maybe not even consistently (the nature of race conditions), and when it happened, it would just be logged in the browser console (which most people don't have up) but otherwise not much effect. Same with the post-restart tab switch message -- logged quietly in a place nobody ever looked. When I added the global error handling, a bunch of things crawled out of the woodwork... as they say, sunlight is a good disinfectant. A ton of things were found and fixed by that before releasing this build, but there will always be differences in the way I approach the app vs how everyone else does, so now your eyes are on things I wouldn't easily see. Alarming, maybe, but not harmful so far, and finding these things and fixing them really improves code quality. I suspect we'll have a few more of these in the coming weeks, but just report and keep on doing what you're doing (in the app and generally).

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

                              @toggledbits ignorance is bliss 🙂

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

                              *HASS 2025.6.0
                              w/ ZST10-700 fw 7.18.3

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

                              1 Reply Last reply
                              1
                              • toggledbitsT toggledbits unlocked this topic on
                              • 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
                                94

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

                              • Error After Upgrade
                                G
                                gwp1
                                0
                                4
                                87

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

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

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

                              • Links to MSR from HA
                                Tom_DT
                                Tom_D
                                0
                                1
                                78

                              • Set Reaction > Script Action
                                wmarcolinW
                                wmarcolin
                                0
                                11
                                419

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

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

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

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