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. Safari Mac Rule Sets Menu after upgrade build 21275
MFA
T
Topic thumbnail image
Multi-System Reactor
Reverse proxy & API ACL
tunnusT
I'm trying to allow anonymous access from a local network to /api/v1/log, but the problem now with the reverse proxy configuration is that this access is open via proxy to the internet. At least I wasn't able to configure ACL so that only an access from a local network would be permitted. reactor.yaml: baseurl: "http://192.168.1.12:8111" proxy_baseurl: "https://external.com:30000" trusted_proxy: "192.168.1.12" Local traffic would originate from 192.168.1.0/24 network. Synology is acting as a reverse proxy and hosting MSR as a docker container (which has its own network and IP 172.18.0.5). MSR build is latest-26298-fbb75fb8 users.yaml: - url: "/api/v1/log" method: "GET" source_ip: 172.18.0.0/24 allow: true Using the above ACL works, but it enables access via proxy also. If I use source_ip: 192.168.1.0/24, then it doesn't work either locally or remotely. So I'm kinda lost what should I use as source_ip in this case?
Multi-System Reactor
Grouped devices
G
I've seen many of you using Dynamic Group Controller. I'm using it myself for monitoring device battery levels. I've read and re-read the Dynamic Group Controller docs and still cannot come to an answer for my question so let me paint my scenario: I've migrated from EchoSpeaks in Hubitat ('cause borked and seemingly unmaintained) to Alexa Devices in Home Assistant ('cause not borked in 2026.11.0) to be able to send TTS to my Echo devices. In EchoSpeaks I could create groups. Sweet. In Alexa Devices I don't seem to be able to do so. As such, my thought was "wait - isn't there a way in MSR?" Is this an effective scenario that Dynamic Group Controller can be used for?
Multi-System Reactor
Login protections
tunnusT
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
Reactor Inspect - a small read-only helper panel for MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Reactor Build 26284 stuck at Loading Reactor UI
T
Topic thumbnail image
Multi-System Reactor
MSR with reverse proxy
tunnusT
I'm trying to use MSR via reserve proxy in Synology DSM, but MSR page does not load https://<public ip>:30000/reactor/en-US/ At the same time logging page loads normally https://<public ip>:30000/api/v1/log I thought maybe authentication was messing it up, but there was no deny entries in the log, and also disabling authentication did not make any difference. For this use case VPN is not an option (that works, but as said not an option for this particular use case). Any ideas what could cause this? MSR build latest-26242-28d69aa8, Chrome browser
Multi-System Reactor
Missing attribute after upgrade
3
Topic thumbnail image
Multi-System Reactor
[MSR] Native fan capabilty
therealdbT
Nothing more to add. I see we have hvac_blower, but, anyway, maybe a native fan on the same assumptions of the fan from HASS could be reasonable. I have a couple of them. ie, this is from ESPHome via HASS. x_hass.domain="fan" x_hass.entity_id="fan.kitchen_seashell_hood_ventilation_fan" x_hass.floor_id=null x_hass.services=["fan","esphome"] x_hass.source="esphome" x_hass.state="off" x_hass_attr.friendly_name="Seashell Hood Ventilation Fan" x_hass_attr.percentage=50 x_hass_attr.percentage_step=25 x_hass_attr.preset_mode="" x_hass_attr.preset_modes=[] x_hass_attr.supported_features=49 Thanks.
Multi-System Reactor
[MSR] Rule do not fire
therealdbT
Topic thumbnail image
Multi-System Reactor
Rule condition shows TRUE in UI but Rule never transitions to SET — survives full restart
N
Build: latest-26221-b25bb3e3, Docker on Synology. Hi, I have a Rule whose Trigger/Constraints reference other Rules via Rule State ... is TRUE. At some point it stops firing. Expanding the rule's condition tree in the UI shows every Trigger and Constraint condition green/TRUE — confirmed live by walking into the room and watching Motion go true in real time. Rule History shows no new SET, just old reset entries. Tried, on the same rule, same evening: recreating the trigger conditions with fresh IDs, recreating the constraint conditions with fresh IDs (flat and wrapped in a new Group — wrapping in a Group produced one SET, but it didn't reproduce on repeat attempts with the same structure), and finally a full container restart with a verified-correct saved rule. Still no SET, even with a fresh live motion event right after the restart. Separately, I found that this rule (and its 10 per-room clones) share identical internal condition/group IDs with each other — leftover from a batch clone done months ago, never regenerated. Not sure if that's related, since fixing the IDs didn't reliably fix the symptom either. Has anyone seen a Rule State condition show TRUE in the UI without the Rule ever producing a SET, surviving a clean restart? Thanks in advance
Multi-System Reactor
DynamicGroupController and attributes
therealdbT
Hey @toggledbits I'm back to trying to optimize a couple of things based on dynamic group. First of all, I think I found a typo in the doc: primary_attribute: "binary_sensor.state" primary_attribute_value: | d = false; each id in members: d = getEntity(id)?.attributes?.power_switch?.state or d, d I think the correct code snippet is d = false, All that said, my use case for dynamic groups is to group 3 different climate devices, so I could easily command them at the same time. Commands are good, but sometimes I want to check if any of the devices are on, and that's easily done with a similar snippet as the one you have in the docs. But this is limited to the primary attribute, while I want to have any of the attributes in the group to be driven by a similar logic (while all are null in the group). ie, access hvac_control.mode and see if any of the unit is set to cool, or heat. Is that possible, without re-defining an expression in each of my rules? Thanks!
Multi-System Reactor
Unofficial thread for compatibility
tunnusT
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well. As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API. Updates: (the latest versions first in the list) OK: build "latest-25264-2fbe9217" with Hubitat C-8 platform v. 2.4.3.123
Multi-System Reactor
Ooops - Deleted Reactor Ex Machina II
R
I accidentally deleted Reactor Ex Machina II (REM II) from my Reactor rules. I tried to recover it by deleting the .json and .dval in the Rules subdirectory and then recreating it from Togglebits original posting, but that did not work. Does anyone know how to recover REM ll ?
Multi-System Reactor
Bail out of failed reaction?
T
Topic thumbnail image
Multi-System Reactor
Arming Envisalink panel from MSR
T
Topic thumbnail image
Multi-System Reactor
[Solved] DynamicGroupController updating members issue
CrilleC
Edit: Solved in latest-26221. Bare-metal latest-26193 I have this group: "OKforLarm": name: OK för Larm select: - include_controller: vera - include_capability: door_sensor filter_expression: entity.attributes.door_sensor.state It contains the entities I expect but behaves a bit odd. When I open vera>device_10097 the entity attribute door_sensor.state changes to true but it won't show up as member in the group, when I also open vera>device_10095 they both shows as members and when I close vera>device_10095 it disappear from the group but when I close vera>device_10097 it lingers in the group until I restart Reactor.
Multi-System Reactor
Upgrade Issues
T
Topic thumbnail image
Multi-System Reactor
[SOLVED] Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
G
Topic thumbnail image
Multi-System Reactor

Safari Mac Rule Sets Menu after upgrade build 21275

Scheduled Pinned Locked Moved Multi-System Reactor
13 Posts 6 Posters 3.2k Views 6 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.
  • S Offline
    S Offline
    SweetGenius
    wrote on last edited by
    #1

    I can no longer access the Rule Sets menu after upgrading to build 21275. Nothing happens when I click on Rule Sets. Other menu options work fine. I have cleared history, hard refreshed the browser, Rebooted. Works fine in Firefox and google chrome. I have always used Safari.
    Suggestions?

    Safari for Mac version 15.0
    MSR Version 21275-df3d784
    Synology Docker

    Synology Docker MSR, Hubitat, Home Assistant, Homebridge, ZwaveJS, MQTT, NUT controller.

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

      I don't have a Mac or Safari, but let's try this. Enable the "Develop" menu in your browser if you haven't already (Safari > Preferences > Advanced and find the checkbox to enable the menu). Then Cmd + Option + C opens the console. Refresh the page and try to click into the Rule Sets menu. See if logs anything useful to the console (post here).

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

      S 1 Reply Last reply
      0
      • toggledbitsT toggledbits

        I don't have a Mac or Safari, but let's try this. Enable the "Develop" menu in your browser if you haven't already (Safari > Preferences > Advanced and find the checkbox to enable the menu). Then Cmd + Option + C opens the console. Refresh the page and try to click into the Rule Sets menu. See if logs anything useful to the console (post here).

        S Offline
        S Offline
        SweetGenius
        wrote on last edited by SweetGenius
        #3

        @toggledbits I did as you suggested. It is showing an error on refresh but nothing changes when clicking Rule sets. If I continually hit refresh, sometimes the error is gone and then the rule sets menu works. It appears if I open in a private window the error is not there either.

        Screen Shot 2021-10-03 at 3.22.51 PM.png

        Edit: The reactor.log shows this also. I do not know if it related but I have no idea what the 172. address is.

        2021-10-03T19:07:55.494Z Engine:5:1448:Engine.js Engine#1 reaction rule-kpw0p0rl:R step 0 perform { "entity": "hubitat>11", "action": "power_switch.off" }
        2021-10-03T19:07:55.494Z HubitatController:null HubitatController#hubitat final action path for power_switch.off on Entity#hubitat>11: http://192.168.1.70/apps/api/416/devices/11/off
        2021-10-03T19:07:55.495Z Engine:5:1351:Engine.js _process_reaction_queue() task returned, new status 3; task 66
        2021-10-03T19:07:55.496Z Engine:5:1386:Engine.js _process_reaction_queue ending with 1 in queue; none delayed/ready; waiting
        2021-10-03T19:07:55.538Z Engine:5:1386:Engine.js _process_reaction_queue() wake-up!
        2021-10-03T19:07:55.540Z Engine:5:1347:Engine.js _process_reaction_queue() running task 66 { "tid": 66, "id": "rule-kpw0p0rl:R", "rule": "rule-kpw0p0rl", "__reaction": [RuleReaction#rule-kpw0p0rl:R], "next_step": 1, "status": 1, "ts": 1633288075480, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise], "attempts": 1 }
        2021-10-03T19:07:55.540Z Engine:NOTICE Resuming reaction Pantry Light<RESET> (rule-kpw0p0rl:R) from step 1
        2021-10-03T19:07:55.540Z Engine:INFO Pantry Light<RESET> all actions completed.
        2021-10-03T19:07:55.540Z Engine:5:1351:Engine.js _process_reaction_queue() task returned, new status -1; task 66
        2021-10-03T19:07:55.541Z Engine:5:1386:Engine.js _process_reaction_queue ending with 0 in queue; none delayed/ready; waiting
        2021-10-03T19:08:22.586Z wsapi:INFO wsapi: connection from ::ffff:172.17.0.1
        2021-10-03T19:08:30.307Z wsapi:INFO client "172.17.0.1#51" closed, code=1006, reason=
        2021-10-03T19:08:30.416Z wsapi:INFO wsapi: connection from ::ffff:172.17.0.1
        2021-10-03T19:08:31.621Z wsapi:INFO client "172.17.0.1#52" closed, code=1006, reason=
        2021-10-03T19:08:31.705Z wsapi:INFO wsapi: connection from ::ffff:172.17.0.1

        Synology Docker MSR, Hubitat, Home Assistant, Homebridge, ZwaveJS, MQTT, NUT controller.

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

          Well, unfortunately, the message doesn't really help me. It points to a line with a class declaration, no variable reference on it at all. If it's actually complaining about something inside the class declaration, it isn't detailed enough to figure out what in over 1300 lines of code in that class it may be. My usual lint (code checking) tools don't complain, and other browsers don't, so while I'd like to fix it, I don't really have a path to fixing it, and you have other options, so I'm afraid it's going to stay broken for now.

          The 172 addresses are bridge addresses between your real network and the docker containers internal/virtual LAN.

          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
          • S SweetGenius

            @toggledbits I did as you suggested. It is showing an error on refresh but nothing changes when clicking Rule sets. If I continually hit refresh, sometimes the error is gone and then the rule sets menu works. It appears if I open in a private window the error is not there either.

            Screen Shot 2021-10-03 at 3.22.51 PM.png

            Edit: The reactor.log shows this also. I do not know if it related but I have no idea what the 172. address is.

            2021-10-03T19:07:55.494Z Engine:5:1448:Engine.js Engine#1 reaction rule-kpw0p0rl:R step 0 perform { "entity": "hubitat>11", "action": "power_switch.off" }
            2021-10-03T19:07:55.494Z HubitatController:null HubitatController#hubitat final action path for power_switch.off on Entity#hubitat>11: http://192.168.1.70/apps/api/416/devices/11/off
            2021-10-03T19:07:55.495Z Engine:5:1351:Engine.js _process_reaction_queue() task returned, new status 3; task 66
            2021-10-03T19:07:55.496Z Engine:5:1386:Engine.js _process_reaction_queue ending with 1 in queue; none delayed/ready; waiting
            2021-10-03T19:07:55.538Z Engine:5:1386:Engine.js _process_reaction_queue() wake-up!
            2021-10-03T19:07:55.540Z Engine:5:1347:Engine.js _process_reaction_queue() running task 66 { "tid": 66, "id": "rule-kpw0p0rl:R", "rule": "rule-kpw0p0rl", "__reaction": [RuleReaction#rule-kpw0p0rl:R], "next_step": 1, "status": 1, "ts": 1633288075480, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise], "attempts": 1 }
            2021-10-03T19:07:55.540Z Engine:NOTICE Resuming reaction Pantry Light<RESET> (rule-kpw0p0rl:R) from step 1
            2021-10-03T19:07:55.540Z Engine:INFO Pantry Light<RESET> all actions completed.
            2021-10-03T19:07:55.540Z Engine:5:1351:Engine.js _process_reaction_queue() task returned, new status -1; task 66
            2021-10-03T19:07:55.541Z Engine:5:1386:Engine.js _process_reaction_queue ending with 0 in queue; none delayed/ready; waiting
            2021-10-03T19:08:22.586Z wsapi:INFO wsapi: connection from ::ffff:172.17.0.1
            2021-10-03T19:08:30.307Z wsapi:INFO client "172.17.0.1#51" closed, code=1006, reason=
            2021-10-03T19:08:30.416Z wsapi:INFO wsapi: connection from ::ffff:172.17.0.1
            2021-10-03T19:08:31.621Z wsapi:INFO client "172.17.0.1#52" closed, code=1006, reason=
            2021-10-03T19:08:31.705Z wsapi:INFO wsapi: connection from ::ffff:172.17.0.1

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

            @sweetgenius said in Safari Mac Rule Sets Menu after upgrade build 21275:

            It appears if I open in a private window the error is not there either.

            Kind of suggests something in your browser cache is a problem. Maybe try a hard refresh (always a good idea after an upgrade), and the usual debugging steps for this kind of thing: flush your browser cache and restart the browser, turn off all extensions, etc.

            Safari 15.0 was officially released about two weeks ago, and there are lots of reports of problems with commonly-used web sites, so I have doubts. Do some Google searches. Other things perhaps to try here: https://apple.stackexchange.com/questions/427935/safari-15-0-error-message-a-problem-repeatedly-occurred-catalina-10-15-7

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

            S 1 Reply Last reply
            0
            • toggledbitsT toggledbits

              @sweetgenius said in Safari Mac Rule Sets Menu after upgrade build 21275:

              It appears if I open in a private window the error is not there either.

              Kind of suggests something in your browser cache is a problem. Maybe try a hard refresh (always a good idea after an upgrade), and the usual debugging steps for this kind of thing: flush your browser cache and restart the browser, turn off all extensions, etc.

              Safari 15.0 was officially released about two weeks ago, and there are lots of reports of problems with commonly-used web sites, so I have doubts. Do some Google searches. Other things perhaps to try here: https://apple.stackexchange.com/questions/427935/safari-15-0-error-message-a-problem-repeatedly-occurred-catalina-10-15-7

              S Offline
              S Offline
              SweetGenius
              wrote on last edited by
              #6

              @toggledbits I agree, I think it's a browser issue. I have tried all the recommended fixes to no avail. Clear Caches, History, Hard Refresh, Reinstall etc.. Will see if they fix it in a later version of Safari. I have found if I keeping hitting refresh it I can get it to work or use a private window or other browser. So I have plenty of options.
              Thanks for the suggestions.

              Synology Docker MSR, Hubitat, Home Assistant, Homebridge, ZwaveJS, MQTT, NUT controller.

              MatohlM 1 Reply Last reply
              0
              • V Offline
                V Offline
                vezinpi
                wrote on last edited by vezinpi
                #7

                @toggledbits Other information pertaining to this problem. Maybe you already know this, if so just disreguard.

                My wife has an Apple tablet and I have an android one along with a windows pc. I am using MSR on a pi with MSR version 21292. All is fine on the pc and android but on the ios tablet (ios 12.5.5), using safari or chrome, MSR start just fine but do not actually connect as indicated in the upper right corner with "connecting...". It never gets to connected status.

                If you need more info feel free to ask.

                Edit:
                The more I look at this the more this seemed to be a different issue since MSR is not connecting at all from the ios tablet. At the moment, I wonder if I should I open a different post?

                Using MSR 26177 on Docker, on a Raspberry Pi with Trixie. Home Assistant 2026.08, Z-Wave JS-UI 11.21.1

                1 Reply Last reply
                0
                • S SweetGenius

                  @toggledbits I agree, I think it's a browser issue. I have tried all the recommended fixes to no avail. Clear Caches, History, Hard Refresh, Reinstall etc.. Will see if they fix it in a later version of Safari. I have found if I keeping hitting refresh it I can get it to work or use a private window or other browser. So I have plenty of options.
                  Thanks for the suggestions.

                  MatohlM Offline
                  MatohlM Offline
                  Matohl
                  wrote on last edited by Matohl
                  #8

                  @sweetgenius I have the same issue but with Safari 14.2.1. I have to use Chrome on my Mac instead.

                  1 Reply Last reply
                  0
                  • SnowmanS Offline
                    SnowmanS Offline
                    Snowman
                    wrote on last edited by
                    #9

                    For me, running Safari Version 15.1 (15612.2.9.1.30, 15612) on macOS Catalina 10.15.7, it works sometimes and other times, it does not. At moment, I have to windows open. On one window, I can collapse the Rule Sets. On the other window, not happening. Weird.

                    Synology NAS, Docker, Zooz Z-Wave Stick 700, Z-Wave JS-UI, Reactor, Home Assistant, Grafana, and InfluxDB.

                    1 Reply Last reply
                    0
                    • S Offline
                      S Offline
                      SweetGenius
                      wrote on last edited by SweetGenius
                      #10

                      A workaround: When you open MSR and before you click on any menus, if you see the Plus sign by Rule Sets then it is not going to work. If you click refresh repeatedly until the plus sign goes away then everything functions properly. The uninitialized variable error in the code window goes away also.
                      Screen Shot 2021-11-06 at 12.49.17 PM.png Screen Shot 2021-11-06 at 12.50.13 PM.png

                      Synology Docker MSR, Hubitat, Home Assistant, Homebridge, ZwaveJS, MQTT, NUT controller.

                      G 1 Reply Last reply
                      0
                      • S SweetGenius

                        A workaround: When you open MSR and before you click on any menus, if you see the Plus sign by Rule Sets then it is not going to work. If you click refresh repeatedly until the plus sign goes away then everything functions properly. The uninitialized variable error in the code window goes away also.
                        Screen Shot 2021-11-06 at 12.49.17 PM.png Screen Shot 2021-11-06 at 12.50.13 PM.png

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

                        @sweetgenius said in Safari Mac Rule Sets Menu after upgrade build 21275:

                        A workaround: When you open MSR and before you click on any menus, if you see the Plus sign by Rule Sets then it is not going to work. If you click refresh repeatedly until the plus sign goes away then everything functions properly.

                        This works beautifully, thanks for this!

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

                        *HAOS
                        Core 2026.10.4
                        w/ HA Connect ZWA-2 & ZBT-2
                        FW: v1.1
                        SDK: v7.23.1

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

                        S 1 Reply Last reply
                        0
                        • G gwp1

                          @sweetgenius said in Safari Mac Rule Sets Menu after upgrade build 21275:

                          A workaround: When you open MSR and before you click on any menus, if you see the Plus sign by Rule Sets then it is not going to work. If you click refresh repeatedly until the plus sign goes away then everything functions properly.

                          This works beautifully, thanks for this!

                          S Offline
                          S Offline
                          SweetGenius
                          wrote on last edited by SweetGenius
                          #12

                          @gwp1 With build latest-21321-c2fda1c, this problem has gone away. It might be a coincidence but on two different Mac accounts this is now working for me. Are you still having the issue?

                          Synology Docker MSR, Hubitat, Home Assistant, Homebridge, ZwaveJS, MQTT, NUT controller.

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

                            Unfortunately, I can't correlate with any specific builds but, yes, I've noticed recently it's WAE.

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

                            *HAOS
                            Core 2026.10.4
                            w/ HA Connect ZWA-2 & ZBT-2
                            FW: v1.1
                            SDK: v7.23.1

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

                            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

                            • MFA
                              T
                              tamorgen
                              0
                              28
                              598

                            • Reverse proxy & API ACL
                              toggledbitsT
                              toggledbits
                              0
                              8
                              125

                            • Grouped devices
                              G
                              gwp1
                              0
                              3
                              93

                            • Login protections
                              toggledbitsT
                              toggledbits
                              0
                              2
                              139

                            • Reactor (Multi-System/Multi-Hub) Announcements
                              toggledbitsT
                              toggledbits
                              5
                              152
                              152.4k

                            • Reactor Inspect - a small read-only helper panel for MSR
                              G
                              gwp1
                              2
                              6
                              403

                            • Reactor Build 26284 stuck at Loading Reactor UI
                              T
                              tamorgen
                              0
                              16
                              1.5k

                            • MSR with reverse proxy
                              tunnusT
                              tunnus
                              0
                              12
                              744

                            • Missing attribute after upgrade
                              3
                              3rdStng
                              0
                              3
                              440

                            • Use of Google Gemini as an MSR and Hubitat configuration aid
                              therealdbT
                              therealdb
                              0
                              2
                              262

                            • [MSR] Native fan capabilty
                              therealdbT
                              therealdb
                              1
                              3
                              250

                            • [MSR] Rule do not fire
                              therealdbT
                              therealdb
                              0
                              4
                              368
                            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