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. Version 1.0 Pre-release Discussion
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
System Configuration Check - time is offset
F
Hi! I get this message when I'm on the status tab: System Configuration Check The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds. I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6. HA versions are: Core 2025.3.4 Supervisor 2025.03.4 Operating System 15.1 I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version. Do anyone know what I can try? Thanks in advance! Let's Be Careful Out There (Hill Street reference...) /Fanan
Multi-System Reactor
Programmatically capture HTTP Request action status code or error
therealdbT
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB. While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed. So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response. While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits Thanks!
Multi-System Reactor
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N
Hi , I'm on -Reactor (Multi-hub) latest-25067-62e21a2d -Docker on Synology NAS -ZWaveJSUI 9.31.0.6c80945 Problem with ZwaveJSUI: When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white. I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui. I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb". After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color. This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite. x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33} The "cold white" and "warm white" settings interfer with the rgb color settings. Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white. So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set. x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33 Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this? x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33} Thanks in advance.
Multi-System Reactor
Problem with simultaneous notifications.
T
Topic thumbnail image
Multi-System Reactor
Problem after upgrading to 25067
R
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem? I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Multi-System Reactor
Global expressions not always evaluated
tunnusT
Topic thumbnail image
Multi-System Reactor
[Solved] Local expression evaluation
V
Topic thumbnail image
Multi-System Reactor
[Solved] Runtime error when exiting global reaction that contains a group
S
I am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved. The Runtime Error is different in the two browsers Safari v18.3 @http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:44 You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Google Chrome 133.0.6943.142 TypeError: self.editor.isModified is not a function at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34) You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Steps to reproduce: Click the pencil to edit a global reaction with a group. Click the Exit button. Runtime error appears. or Click Create Reaction Click Add Action Select Group Add Condition such as Entity Attribute. Add an Action. Click Save Click Exit Runtime error appears. I don’t know how long the error has been there as I haven’t edited the global reaction in a long time. Reactor (Multi-hub) latest-25060-f32eaa46 Docker Mac OS: 15.3.1 Thanks
Multi-System Reactor
Cannot delete Global Expressions
SnowmanS
I am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons. I have not created a global expression for some times and just noticed this while doing some clean-up. I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success. Here's what the log shows. [latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay [latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } Reactor latest-25067-62e21a2d Docker on Synology NAS
Multi-System Reactor
Local notification methods?
CatmanV2C
Morning, experts. Hard on learning about the internet check script in MSR tools, I was wondering what suggestions anyone has about a local (i.e. non-internet dependent) notification method. This was prompted by yesterday's fun and games with my ISP. I've got the script Cronned and working properly but short of flashing a light on and off, I'm struggling to think of a way of alerting me (ideally to my phone) I guess I could set up a Discord server at home, but that feels like overkill for a rare occasion. Any other suggestions? TIA C
Multi-System Reactor

Version 1.0 Pre-release Discussion

Scheduled Pinned Locked Moved Multi-System Reactor
46 Posts 14 Posters 3.1k Views 13 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.
  • MikeReadingtonM MikeReadington

    +1 Libra. A clickable link to take you to the location of use would be really nice.

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

    @mikereadington said in Version 1.0 Pre-release Discussion:

    +1 Libra. A clickable link to take you to the location of use would be really nice.

    Although we have to acknowledge that expressions are able to reference entities without overtly looking like that's what they do - such as using loops and arrays - so it might be a technical challenge for MSR to pick up every single reference.

    1 Reply Last reply
    1
    • toggledbitsT toggledbits

      Potential change: now that constraints apply to groups in a Rule's reactions, I see no value in keeping the Constraints as a separate subsection at the top level of a rule (that is, the section between Triggers and the Set Reaction when you edit a Rule). So, I'm thinking about removing them from here (any rules you have with constraints in this area would just get them restructured into a group constraint).

      Thoughts?

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

      @toggledbits said in Version 1.0 Pre-release Discussion:

      now that constraints apply to groups in a Rule's reactions, I see no value in keeping the Constraints as a separate subsection at the top level of a rule (that is, the section between Triggers and the Set Reaction when you edit a Rule). So, I'm thinking about removing them from here

      Really?

      Are these not two separate things with different uses.

      I use the Contraints section of a rule as the main set of constraints / conditions for that rules Reaction / actions being run or not.

      And then in some of my rules in its Set Reaction I also have further additional and different "Group Constraints" that are only evaluated and carried out if the Set Reaction actions were even run in the first place by the main constraints being met.

      Personally I do not like at all this idea to remove the rules Contraints.

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

        I have to strongly object to removing the rules Contraints section, which would be a major change to the concept of a rule and its work flow.

        A logic engine has triggers then conditions then actions.

        This is the same concept PLEG had and I used it for a decade.

        We then asked you to give us the ability to have further additional conditions within the actions chain and you gave us that with Group Constraints.

        The system is perfect as is.

        What you are suggesting is to have triggers then actions with conditions mixed in with the actions.

        Keep the main conditions in the separate Constraints section as they are now.

        It's your project and creation and you can do with it what you like, but I won't be happy with this proposed major change if it happens.

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

          @toggledbits , As you stated in another thread "Capabilities on Hubitat are free-form, and there's no indication which capability might be the most useful or primary". Could you add the ability for a user to manually select the primary capability for each Hubitat device? This would allow the Entities screen to display info in the primary value. If the Dashboard feature is added in the future then the Hubitat device should display correctly there also.( I also would like to request the dashboard)

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

          1 Reply Last reply
          1
          • F Offline
            F Offline
            Fanan
            wrote on last edited by
            #15

            This might be off topic and it also reveals my lack of programming skills. But I wounder how is MSR going to be installed, once it leaves beta? I use it on a stationary Windows 10, and the problem is if the power goes out. Then my PC reboots and I have to start the app and change catalog and finally execute "node app.js". I could install it on a RPi, don't know if it can work alongside and on the same RPi as I got Home assistant installed? Then it would start straight away, when the power gets back. To summarize, it's basicly two questions;

            1. In which ways are we going to be able to install and start up MSR?
            2. Is it possible to install MSR on a RPi that already is running HA? Or on a Home assistant blue (Odroid N2+)?

            Another feature that would be nice is to have a optional setting of automatic updates.
            Regardsless - MSR is a great (one of the best) contribution to the smart home community - at least for me. Great job!!

            M therealdbT toggledbitsT 4 Replies Last reply
            1
            • F Fanan

              This might be off topic and it also reveals my lack of programming skills. But I wounder how is MSR going to be installed, once it leaves beta? I use it on a stationary Windows 10, and the problem is if the power goes out. Then my PC reboots and I have to start the app and change catalog and finally execute "node app.js". I could install it on a RPi, don't know if it can work alongside and on the same RPi as I got Home assistant installed? Then it would start straight away, when the power gets back. To summarize, it's basicly two questions;

              1. In which ways are we going to be able to install and start up MSR?
              2. Is it possible to install MSR on a RPi that already is running HA? Or on a Home assistant blue (Odroid N2+)?

              Another feature that would be nice is to have a optional setting of automatic updates.
              Regardsless - MSR is a great (one of the best) contribution to the smart home community - at least for me. Great job!!

              M Offline
              M Offline
              Matteburk
              wrote on last edited by
              #16

              @fanan The same thing happens with my RPI4 ... I have to start it manually...

              cw-kidC 1 Reply Last reply
              0
              • M Matteburk

                @fanan The same thing happens with my RPI4 ... I have to start it manually...

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

                @matteburk

                There was a thread about having MSR auto start on a Pi. I set it up on my Pi and it did work MSR was started automatically after a reboot / power on.

                https://smarthome.community/topic/439/how-to-auto-start-on-rpi-reboot?_=1621588014603

                1 Reply Last reply
                0
                • F Fanan

                  This might be off topic and it also reveals my lack of programming skills. But I wounder how is MSR going to be installed, once it leaves beta? I use it on a stationary Windows 10, and the problem is if the power goes out. Then my PC reboots and I have to start the app and change catalog and finally execute "node app.js". I could install it on a RPi, don't know if it can work alongside and on the same RPi as I got Home assistant installed? Then it would start straight away, when the power gets back. To summarize, it's basicly two questions;

                  1. In which ways are we going to be able to install and start up MSR?
                  2. Is it possible to install MSR on a RPi that already is running HA? Or on a Home assistant blue (Odroid N2+)?

                  Another feature that would be nice is to have a optional setting of automatic updates.
                  Regardsless - MSR is a great (one of the best) contribution to the smart home community - at least for me. Great job!!

                  therealdbT Offline
                  therealdbT Offline
                  therealdb
                  wrote on last edited by
                  #18

                  @fanan installing on a poi side by side with anything else will not hurt. On windows, just schedule it to run at startup via task scheduler.

                  --
                  On a mission to automate everything.

                  My MS Reactor contrib
                  My Luup Plug-ins

                  1 Reply Last reply
                  0
                  • F Fanan

                    This might be off topic and it also reveals my lack of programming skills. But I wounder how is MSR going to be installed, once it leaves beta? I use it on a stationary Windows 10, and the problem is if the power goes out. Then my PC reboots and I have to start the app and change catalog and finally execute "node app.js". I could install it on a RPi, don't know if it can work alongside and on the same RPi as I got Home assistant installed? Then it would start straight away, when the power gets back. To summarize, it's basicly two questions;

                    1. In which ways are we going to be able to install and start up MSR?
                    2. Is it possible to install MSR on a RPi that already is running HA? Or on a Home assistant blue (Odroid N2+)?

                    Another feature that would be nice is to have a optional setting of automatic updates.
                    Regardsless - MSR is a great (one of the best) contribution to the smart home community - at least for me. Great job!!

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

                    @fanan At least initially, like many other projects, I expect MSR to be delivered in the following forms:

                    1. Primary: Docker container. This facilitates not only a simpler integrated package to install that contains its dependencies, but also easily takes care of starting at boot on most systems. There are currently Docker containers available for Linux amd64 and armv7l (i.e. RPi4) architectures.
                    2. Generic tarball. This will be a manual install for platform power users (Linux, Windows, and anywhere else nodejs and the companion dependencies can be installed by the user). There are available examples for automatic startup for systemd.

                    There's no reason you cannot install MSR next to Hass or anything else on a platform that allows you to install such things (clearly you're not going to install it on your Hubitat). I don't know anything about Hass Blue, but if it lets you install docker containers or the generic package, I see no reason you can't run them side-by-side.

                    @cw-kid said in Version 1.0 Pre-release Discussion:

                    @matteburk
                    There was a thread about having MSR auto start on a Pi.

                    Slightly modernized version of the same here, should work on any platform that supports systemd: https://smarthome.community/post/8011

                    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
                    2
                    • F Fanan

                      This might be off topic and it also reveals my lack of programming skills. But I wounder how is MSR going to be installed, once it leaves beta? I use it on a stationary Windows 10, and the problem is if the power goes out. Then my PC reboots and I have to start the app and change catalog and finally execute "node app.js". I could install it on a RPi, don't know if it can work alongside and on the same RPi as I got Home assistant installed? Then it would start straight away, when the power gets back. To summarize, it's basicly two questions;

                      1. In which ways are we going to be able to install and start up MSR?
                      2. Is it possible to install MSR on a RPi that already is running HA? Or on a Home assistant blue (Odroid N2+)?

                      Another feature that would be nice is to have a optional setting of automatic updates.
                      Regardsless - MSR is a great (one of the best) contribution to the smart home community - at least for me. Great job!!

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

                      @fanan said in Version 1.0 Pre-release Discussion:

                      Another feature that would be nice is to have a optional setting of automatic updates.

                      I'll address this issue separately.

                      I think there are two interpretations here, so I'll start with the interpretation that I would more specifically call "unattended upgrades". Philosophically I'm opposed to unattended upgrades in all things, particularly on things that become "mission critical" in my environment. There is no "good time" for such updates except when I'm there to initiate them and recover if they come a gutser. History has shown that they otherwise will happen when I am far from home, usually for a sustained period and while Internet access is unavailable or inconvenient. When fully unattended upgrades to MSR happen, that will be your sign that I am no longer associated with this project. 🙂

                      The other interpretation is "push-to-start" upgrades from the UI. This is, frankly, a very low priority for me, and will not be something I entertain for 1.0, or likely 1.x. Docker containers are easily upgraded with a four-line script on command line-driven platforms, and still pretty painless in, for example, the Synology GUI (and still doable on the command line there as well). For users of the generic tarball, the detar and restart is even simpler. I understand that one click from the GUI would be easier, I don't disagree there, but keep in mind you've all been working in a mode where, for much of the history of its availability, MSR updates have come almost daily. That is not the norm, and I would not want it to be in production. In fact, production will go more to the model I use for R4V, where there is basically a very slow-moving release channel, a faster "stable" channel, and a bleeding-edge "latest" (what you have today).

                      The feature also introduces something that Reactor currently doesn't (on its own) require: access to a cloud infrastructure. Upgrades from within MSR require it to access cloud services, some existing, some not. This implies a lot of things, not the least of which include its security, its construction, and its cost to maintain and serve. If it gets done at some point, it will not come lightly, or easily, and it will likely be accompanied by license fees.

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

                      F 1 Reply Last reply
                      3
                      • toggledbitsT toggledbits

                        @fanan said in Version 1.0 Pre-release Discussion:

                        Another feature that would be nice is to have a optional setting of automatic updates.

                        I'll address this issue separately.

                        I think there are two interpretations here, so I'll start with the interpretation that I would more specifically call "unattended upgrades". Philosophically I'm opposed to unattended upgrades in all things, particularly on things that become "mission critical" in my environment. There is no "good time" for such updates except when I'm there to initiate them and recover if they come a gutser. History has shown that they otherwise will happen when I am far from home, usually for a sustained period and while Internet access is unavailable or inconvenient. When fully unattended upgrades to MSR happen, that will be your sign that I am no longer associated with this project. 🙂

                        The other interpretation is "push-to-start" upgrades from the UI. This is, frankly, a very low priority for me, and will not be something I entertain for 1.0, or likely 1.x. Docker containers are easily upgraded with a four-line script on command line-driven platforms, and still pretty painless in, for example, the Synology GUI (and still doable on the command line there as well). For users of the generic tarball, the detar and restart is even simpler. I understand that one click from the GUI would be easier, I don't disagree there, but keep in mind you've all been working in a mode where, for much of the history of its availability, MSR updates have come almost daily. That is not the norm, and I would not want it to be in production. In fact, production will go more to the model I use for R4V, where there is basically a very slow-moving release channel, a faster "stable" channel, and a bleeding-edge "latest" (what you have today).

                        The feature also introduces something that Reactor currently doesn't (on its own) require: access to a cloud infrastructure. Upgrades from within MSR require it to access cloud services, some existing, some not. This implies a lot of things, not the least of which include its security, its construction, and its cost to maintain and serve. If it gets done at some point, it will not come lightly, or easily, and it will likely be accompanied by license fees.

                        F Offline
                        F Offline
                        Fanan
                        wrote on last edited by
                        #21

                        @toggledbits I fully understand and respect that! Thanks for taking the time!
                        Hope you have a great weekend!

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

                          Would a Menu item for accessing the reactor log file or portion of the log be possible.Or ideally a way to monitor the log in real time from the GUI for troubleshooting?

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

                          J 1 Reply Last reply
                          1
                          • M Offline
                            M Offline
                            Matteburk
                            wrote on last edited by
                            #23

                            Feature requests .. Now when we have groups in set reactions and reset reactions it would be nice if they showed up in the the visual tree under trigger and conditions.
                            Then you have a more visual overview of the hole logic. /Mattias

                            1 Reply Last reply
                            1
                            • S SweetGenius

                              Would a Menu item for accessing the reactor log file or portion of the log be possible.Or ideally a way to monitor the log in real time from the GUI for troubleshooting?

                              J Offline
                              J Offline
                              jsimmo
                              wrote on last edited by
                              #24

                              @sweetgenius said in Version 1.0 Pre-release Discussion:

                              Would a Menu item for accessing the reactor log file or portion of the log be possible.Or ideally a way to monitor the log in real time from the GUI for troubleshooting?

                              +1 for this.

                              1 Reply Last reply
                              2
                              • LibraSunL Offline
                                LibraSunL Offline
                                LibraSun
                                wrote on last edited by
                                #25

                                How about exposing the Status and Alerts levels under Reactor_System, so that Rules could be written to react to, say, a Rule getting stuck SET for too long, or the count of a particular (esp. unexpected) Alert going too high, etc.? I love my warning messages!

                                1 Reply Last reply
                                0
                                • toggledbitsT toggledbits

                                  Potential change: now that constraints apply to groups in a Rule's reactions, I see no value in keeping the Constraints as a separate subsection at the top level of a rule (that is, the section between Triggers and the Set Reaction when you edit a Rule). So, I'm thinking about removing them from here (any rules you have with constraints in this area would just get them restructured into a group constraint).

                                  Thoughts?

                                  wmarcolinW Offline
                                  wmarcolinW Offline
                                  wmarcolin
                                  wrote on last edited by
                                  #26
                                  This post is deleted!
                                  1 Reply Last reply
                                  1
                                  • wmarcolinW Offline
                                    wmarcolinW Offline
                                    wmarcolin
                                    wrote on last edited by
                                    #27

                                    Hi!

                                    I've only been using MSR for 3 days, so I'm too much of a beginner to have opinions, but I want to try to collaborate:

                                    1. First thanks to @cw-kid , with the simple tip of the installation page in the manual, I finally managed to take the step and install it on Windows 10. I see some comments on automatic startup, it was simple to put in the task scheduler a bat to run the "node app.js", and works very well on computer restarts. Now I did not understand why the instruction "Running Reactor Continuously" with the command "nohup ./app.sh &", what is the difference?

                                    2. Regarding the Constraints question, I don't see much value, or don't know how to use them. I thought that if we first have the obligation to meet the Constraints (e.g. be in home mode and time between 8am and 5pm), only then do we start evaluating the Triggers (e.g. movement in room, open door...) it would make more sense to me. That is Constraints as a basic obligation, and Triggers in the next group of the variables of the action. Right now I'm thinking of putting everything in the Triggers block.

                                    As I commented I only have 3 days, but I already see that Patrick @toggledbits again doing an exceptional job, if the Reactor was already great, I do not know how to classify what will be the MSR by the little I've seen. What I see for the future:

                                    1. A translation will be needed in the selectors of so many technical terms, for a more fluent, layman-friendly message. An example FROM x_vera_svc_micasaverde_com_SecuritySensor1.Tripped TO only Tripped;

                                    2. A dashboard unique to the Rule Sets. What you have today allows us to turn on/off, edit, reset... I think of something simple and straightforward like the Action Icon (I love the Reactor icon), green color on, yellow already have conditions met and could go into execution, and red in execution. It would be a dashboard for easier visualization on the phone. If you can then configure that shows or not would be great, who knows version 3, 4....;

                                    And sorry this may not be the forum, but reading the posts I see a strong tendency to recommend the use of the Docker container. Is there a real difference in usage with respect to having the Windows 10 installation? Are there performance issues? Any functions that will not operate well? Is the communication between HA and the computer running Windows 10 worse? I see on the Vera panel that a device changes condition to unTrigger, and it takes quite a while to see the reaction on the MSR, is there a difference between container and windows?

                                    Once again my many thanks to everyone for the work being done, I finally see a light in not depending on hardware to be able to have good automation at home, in a simpler way. As many have commented, soon Vera will be just a radio antenna 🙂

                                    1 Reply Last reply
                                    2
                                    • wmarcolinW Offline
                                      wmarcolinW Offline
                                      wmarcolin
                                      wrote on last edited by
                                      #28

                                      I had forgotten one very important thing, if possible now, that "Reset Reaction" can copy the "Set Reaction" actions from the same rule sets. It will help a lot to configure to turn off several lights that were on before.

                                      1 Reply Last reply
                                      2
                                      • F Offline
                                        F Offline
                                        Fanan
                                        wrote on last edited by
                                        #29

                                        I would love if there was an option, at least for us old Vera users, to be able to use the house modes natively, which is possible in the Vera reactor app.

                                        LibraSunL 1 Reply Last reply
                                        0
                                        • F Fanan

                                          I would love if there was an option, at least for us old Vera users, to be able to use the house modes natively, which is possible in the Vera reactor app.

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

                                          @fanan House Mode is in MSR, just look under Entities.

                                          F 1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Recent Topics

                                          • Advice reqeusted to migrate MSR from Bare Metal to Container
                                            T
                                            tamorgen
                                            0
                                            5
                                            33

                                          • Reactor (Multi-System/Multi-Hub) Announcements
                                            toggledbitsT
                                            toggledbits
                                            5
                                            122
                                            35.4k

                                          • Z-Wave Future....
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            5
                                            126

                                          • Can´t restart or upgrade/deploy MSR
                                            toggledbitsT
                                            toggledbits
                                            0
                                            4
                                            83

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

                                          • Disaster recovery and virtualisation
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            5
                                            655

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

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

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

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

                                          • Need help reducing false positive notifications
                                            T
                                            tamorgen
                                            0
                                            7
                                            518
                                          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