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
Limit HA Entity in MSR
wmarcolinW
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
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
Custom capabilities in MQTT templates
M
Hi, I'm trying to integrate the sonos-mqtt (https://sonos2mqtt.svrooij.io/) with the MSR and it's coming along nicely so far. But cannot wrap my head around how to define custom capabilities in MQTT templates. I need this for the TTS announcements and similarly for the notification sounds where I would pass the sound file as parameter. So this is what I have in the local_mqtt_devices.yaml capabilities: x_sonos_announcement: attributes: actions: speak: arguments: text: type: string volume: type: int delay: type: int And this is the template: templates: sonos-announcement: capabilities: - x_sonos_announcement actions: x_sonos_announcement: speak: topic: "sonos/cmd/speak" payload: expr: > { "text": parameters.text, "volume": parameters.volume, "delayMs": parameters.delay, "onlyWhenPlaying": false, "engine": "neural" } type: json So the speak action should send something like this to topic sonos/cmd/speak { "text": "message goes here", "volume": 50, "delayMs": 100, "onlyWhenPlaying": false, "engine": "neural" } At startup the MSR seems to be quite unhappy with my configuration: reactor | [latest-25016]2025-02-09T08:19:59.029Z <MQTTController:WARN> MQTTController#mqtt entity Entity#mqtt>sonos-announcement unable to configure capabilities [Array][ "x_sonos_announcement" ] reactor | i18n: missing fi-FI language string: Configuration for {0:q} is incomplete because the following requested capabilities are undefined: {1} reactor | i18n: missing fi-FI language string: Configuration for {0:q} has unrecognized capability {1:q} in actions reactor | Trace: Configuration for {0:q} is incomplete because the following requested capabilities are undefined: {1} reactor | at _T (/opt/reactor/server/lib/i18n.js:611:28) reactor | at AlertManager.addAlert (/opt/reactor/server/lib/AlertManager.js:125:25) reactor | at MQTTController.sendWarning (/opt/reactor/server/lib/Controller.js:627:30) reactor | at MQTTController.start (/var/reactor/ext/MQTTController/MQTTController.js:268:26) reactor | at async Promise.allSettled (index 0) Configuration for "sonos-announcement" has unrecognized capability "x_sonos_announcement" in actions Controller: MQTTController#mqtt Last 10:21:37 AM Configuration for "sonos-announcement" is incomplete because the following requested capabilities are undefined: x_sonos_announcement Controller: MQTTController#mqtt Last 10:21:37 AM This is probably a pretty stupid question and the approach may not even work at all, but maybe someone or @toggledbits for sure, could point me to the right direction. Basically the idea is to be able to send TTS messages from reactions using entity actions. I've previously used HTTP requests to Sonos HTTP API (https://hub.docker.com/r/chrisns/docker-node-sonos-http-api/) for the same functionality, but since moving to sonos-mqtt, I need a way to send the TTS notifications using MQTTController. Along with the actual message, volume and delay must also be parameterizable. br, mgvra MSR latest-25016-d47fea38 / MQTTController [0.2.24293]
Multi-System Reactor
[SOLVED]Hass websocket falsely reporting ready on boot??
V
Hi, @toggledbits I just noticed that following a reboot of my raspberry pi, some of the rules, that I was expecting to recover, are not catching up following a reboot. I have made a simple test rule (rule-m6rz6ol1) with only "after Date/time" as trigger and "turn on a lamp" as a set reaction. All my infrastructure is on the same board so Reactor, Hass, Zwavejs, ... are all rebooting. Here is the sequence of the test case (All time converted to Zulu to match logs): Rule "after Date/Time" set to 14:05:00z Shutdown on Raspberry Pi at 14:04:00z Power back up at 14:08:00z Rule overview shows true as of 14:08:14z waiting for 00:00:00 in GUI From the log I can see that MSR is picking up the rule and knows that the state of the rule has changed from false to true and tries to send the update to HASS but failed with websocket error. Here is what I see from the log: 14:04:04z shutdown complete 14:08:08z Power up 14:08:13.111z websocket connection 14:08:15:323z Reaction to the light failed, Websocket not opened After there is a series of websocket connection attempt until 14:08:51z where it seemed to be really ready. Back in 2021 we had a discussion (https://smarthome.community/topic/700/solved-start-up?_=1738766986566) and you proposed to add a startup_delay:xxxx and startup_wait:xxxx parameter in the engine section of "reactor.yaml". When I try the startup_delay (this used to be a hard delay), the engine failed to start (I think). I then try the startup_wait:xxxx without any success. Since it wait for the connection status to be up to cancel the delay, it does not do anyting since Hass is reporting the socket up without really being up ( I think...). Questions: Did I figured it all wrong? should the startup_delay:xxxxx have worked? Any ideas? Here is the log: OK now I am stuck. I did add the log but when I submit the editor complained saying that I am limited to 32767 characters. The log from the shutdown to the time the websocket is stable is about 300000 character long. What are my options?
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.
  • 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

                                          • Limit HA Entity in MSR
                                            toggledbitsT
                                            toggledbits
                                            0
                                            5
                                            47

                                          • Reactor (Multi-System/Multi-Hub) Announcements
                                            toggledbitsT
                                            toggledbits
                                            5
                                            121
                                            35.2k

                                          • Disaster recovery and virtualisation
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            5
                                            584

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

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

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

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

                                          • Need help reducing false positive notifications
                                            T
                                            tamorgen
                                            0
                                            7
                                            461

                                          • Deleting widgets
                                            toggledbitsT
                                            toggledbits
                                            0
                                            4
                                            440

                                          • MQTT configuration question
                                            tunnusT
                                            tunnus
                                            0
                                            11
                                            592
                                          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