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
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

Version 1.0 Pre-release Discussion

Scheduled Pinned Locked Moved Multi-System Reactor
46 Posts 14 Posters 6.4k 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.
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #1

    We're 60 days out from the 1.0 release date I gave earlier in this category. For about the next 30 days, I'll entertain new feature requests for anything you all feel is absolutely needed and not yet present for a 1.0 release, and you're going to have to make a strong case. Short of that, it will have to live on the wish list for a possible future release.

    Identify and discuss in this topic, please... go!

    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
    3
    • LibraSunL Offline
      LibraSunL Offline
      LibraSun
      wrote on last edited by
      #2

      The only thing that comes to mind is fleshing out the Docs (gonna be a fun chore!) and introducing more little (i) icons throughout the UI so that users can quickly jump to the related section of Docs for that panel/pane/action.

      Right now, 21140 is like butter and I have no pressing outstanding Feature Requests to suggest.
      Thanks for all the hard work you've put into making MSR as awesome as it is, even in beta!

      1 Reply Last reply
      2
      • MatohlM Offline
        MatohlM Offline
        Matohl
        wrote on last edited by
        #3

        Virtual Devices as discussed here:
        https://smarthome.community/topic/546/let-s-talk-about-msr-provided-virtual-devices-not

        1 Reply Last reply
        2
        • ElcidE Offline
          ElcidE Offline
          Elcid
          wrote on last edited by
          #4

          possibly add future wind readings to weather entity like rain(1h and 24hr)

          1 Reply Last reply
          1
          • MikeReadingtonM Offline
            MikeReadingtonM Offline
            MikeReadington
            wrote on last edited by
            #5

            +1 on the docs. As a non-programmer, I struggled with what could probably best be described as the lack of prerequisite programming knowledge. I certainly would never expect a programming course in the docs, but examples in the "how-to" section will really help point people like me in the right direction. The installation (docker), logic, and concept sections were excellent for me, but I already had the basic gist of things from Vera Reactor.

            +1 on the virtual devices.

            Dashboard: I don't know if you view this as a separate but related project, but since MSR concentrates entities in one system, it would be a wonderful addition.

            The only other thing I had thought of was a global "pause" button. I had to make lots of controller/device changes at one point, and I found myself looking for a way to put everything on hold while I reconfigured.

            I just wanted to say thank you again for everything you have created. MSR has brought a level of maturity to my automation that was not previously possible for me to accomplish at my skill level.

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

              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?

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

              cw-kidC wmarcolinW 2 Replies Last reply
              1
              • MikeReadingtonM Offline
                MikeReadingtonM Offline
                MikeReadington
                wrote on last edited by MikeReadington
                #7

                On the constraints, once groups were introduced, I stopped using the constraint subsection unless it was a straightforward rule that did not require groups. I think opinions on this would vary based on the way people have settled in on rule construction and layout. Groups allowed me to consolidate my rule sets, so I have less use for them.

                I thought of one other thing that would be helpful to me personally...

                Would you or anyone else see any value in an "entity in use by" inspector/report generator? As things got more complex, I found myself doing a little digging when I needed to address a logic issue with an entity used in multiple sections of logic.

                1 Reply Last reply
                4
                • LibraSunL Offline
                  LibraSunL Offline
                  LibraSun
                  wrote on last edited by LibraSun
                  #8

                  +1 on "Entity in use by" (or "watched by" or "referenced in") and see that as a possible extension of the objects we already see under ENTITIES. If, for instance, "Sofa Lamp" was referenced twice in the "Dim Lights" rule, it could list both occurrences as:
                  .references: Dim_Lights._Set_Reaction, Dim_Lights.Expr_DimLevel, where both are clickable links directly to those subsections of the referencing rule.

                  MikeReadingtonM 1 Reply Last reply
                  2
                  • LibraSunL LibraSun

                    +1 on "Entity in use by" (or "watched by" or "referenced in") and see that as a possible extension of the objects we already see under ENTITIES. If, for instance, "Sofa Lamp" was referenced twice in the "Dim Lights" rule, it could list both occurrences as:
                    .references: Dim_Lights._Set_Reaction, Dim_Lights.Expr_DimLevel, where both are clickable links directly to those subsections of the referencing rule.

                    MikeReadingtonM Offline
                    MikeReadingtonM Offline
                    MikeReadington
                    wrote on last edited by
                    #9
                    This post is deleted!
                    1 Reply Last reply
                    0
                    • MikeReadingtonM Offline
                      MikeReadingtonM Offline
                      MikeReadington
                      wrote on last edited by
                      #10

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

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

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

                                          • Error After Upgrade
                                            G
                                            gwp1
                                            0
                                            4
                                            64

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

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

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

                                          • Links to MSR from HA
                                            Tom_DT
                                            Tom_D
                                            0
                                            1
                                            65

                                          • Set Reaction > Script Action
                                            wmarcolinW
                                            wmarcolin
                                            0
                                            11
                                            396

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

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

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

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