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

Localization

Scheduled Pinned Locked Moved Multi-System Reactor
11 Posts 4 Posters 756 Views 4 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.
  • CrilleC Offline
    CrilleC Offline
    Crille
    wrote on last edited by
    #1

    @toggledbits I've done a (test) Swedish translation for MSR, I don't want/need a translated version, but I had the time and perhaps some future users would find it useful 🙂
    I noticed it's a bit early in the process to go live with systemwide localizations so no github in place yet, do you want input on this now or should we wait a few releases? considering it may be low priority issues.
    If so, do you want feedback here or in mantis?

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

      Go ahead and put it in Mantis. That's exciting!

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

      1 Reply Last reply
      0
      • CrilleC Crille

        @toggledbits I've done a (test) Swedish translation for MSR, I don't want/need a translated version, but I had the time and perhaps some future users would find it useful 🙂
        I noticed it's a bit early in the process to go live with systemwide localizations so no github in place yet, do you want input on this now or should we wait a few releases? considering it may be low priority issues.
        If so, do you want feedback here or in mantis?

        CrilleC Offline
        CrilleC Offline
        Crille
        wrote on last edited by
        #3

        A little preview of the Swedish version of MSR 🙂
        preview.PNG

        F 1 Reply Last reply
        2
        • CrilleC Crille

          A little preview of the Swedish version of MSR 🙂
          preview.PNG

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

          @crille great job!! I was hoping for someone to do the translation into swedish. English works just fine, but I wouldn't mind having it in swedish. 🙂 (Gärna på bred småländska )

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

            This is so cool. I don't even have the words, honestly. There are very personal feelings at work here. I'll just say I come from a world family, so seeing Reactor in a language other than English adds a connection for me that I have long wanted to see. Thank you for taking the time to do this.

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

            CrilleC 2 Replies Last reply
            1
            • toggledbitsT toggledbits

              This is so cool. I don't even have the words, honestly. There are very personal feelings at work here. I'll just say I come from a world family, so seeing Reactor in a language other than English adds a connection for me that I have long wanted to see. Thank you for taking the time to do this.

              CrilleC Offline
              CrilleC Offline
              Crille
              wrote on last edited by
              #6

              @toggledbits Well you made it fairly easy, all it needs is a little bit of time and correct wordings for the appropriate places, so thank you.

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

                Good job. I will test it when it is available, and I am at home 🙂

                1 Reply Last reply
                0
                • toggledbitsT toggledbits

                  This is so cool. I don't even have the words, honestly. There are very personal feelings at work here. I'll just say I come from a world family, so seeing Reactor in a language other than English adds a connection for me that I have long wanted to see. Thank you for taking the time to do this.

                  CrilleC Offline
                  CrilleC Offline
                  Crille
                  wrote on last edited by
                  #8

                  @toggledbits According to the documentation for localization:

                  "You may, at your option, contribute your language file to be included with future builds of Reactor as an add-on ... We will simply pull your latest language file from your Github repository directly when and as needed during builds..."

                  Will this hold back the release of a new build, waiting for translators to update their repos with new versions matching the new build?

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

                    This is all so new, I hadn't really thought about it, but here's my first reaction to it:

                    • I would not delay a latest build, as these are not scheduled, and sometimes have urgency.
                    • I would delay a numbered release (e.g. 1.0.1, etc.). But, my plan and practice so far has been to derive these from prior latest builds that have proven stable, so I can factor in the necessary changes at that point and wait for them. This may require a bit of additional configuration management on my part, but I can plan the timing of the release, and give everyone predictable schedules.

                    Going forward, I think there are two practices that we will need to follow to give the best/longest compatibility:

                    • Strings are not removed from the translation files when later versions disuse them, at least, not for a very long time. Rather, they can perhaps be moved to the bottom of the file under a comment # Strings not used as of 21267 (for example) to keep them organized but still present. In this way, a 22044 translation file would still work well for 21267 or versions prior, because it still contains the old strings. At some major revision (2.0) we can clean house and remove the old strings. We've removed a few already; I won't ask you to remove any more, I'll just call them out as "disused."
                    • Strings will not change their keys, use, or meaning. If a changes in these ways, a new string (or tag) will be created for the purpose, and the old version can go on the list of old/disused strings. This should help ensure that 21267 and 22044 use a string in the same way, and the translations are valid in both. So, for example, the 1:T change I just asked you to make will never be repeated; it was the first and last such request, and we'll do it by replacement going forward.

                    Any thoughts or recommendations you have about all this are more than welcome. I've done many product localizations from the original engineering side. What I haven't done is worked with language teams on localized builds thereafter -- that has always ended up going to other departments and other companies in other countries, and handled weeks or months after my work has been packaged and released in the US. So, I don't have any experience at policies and procedures that work in helping you maintain the work. I have a good imagination, but it's a bit of "the tail wagging the dog" as we say here, so I'm eager to have you tell me what you think should be done. What we're doing now is only my first guess to see what happens to get it rolling.

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

                    CrilleC 1 Reply Last reply
                    0
                    • toggledbitsT toggledbits

                      This is all so new, I hadn't really thought about it, but here's my first reaction to it:

                      • I would not delay a latest build, as these are not scheduled, and sometimes have urgency.
                      • I would delay a numbered release (e.g. 1.0.1, etc.). But, my plan and practice so far has been to derive these from prior latest builds that have proven stable, so I can factor in the necessary changes at that point and wait for them. This may require a bit of additional configuration management on my part, but I can plan the timing of the release, and give everyone predictable schedules.

                      Going forward, I think there are two practices that we will need to follow to give the best/longest compatibility:

                      • Strings are not removed from the translation files when later versions disuse them, at least, not for a very long time. Rather, they can perhaps be moved to the bottom of the file under a comment # Strings not used as of 21267 (for example) to keep them organized but still present. In this way, a 22044 translation file would still work well for 21267 or versions prior, because it still contains the old strings. At some major revision (2.0) we can clean house and remove the old strings. We've removed a few already; I won't ask you to remove any more, I'll just call them out as "disused."
                      • Strings will not change their keys, use, or meaning. If a changes in these ways, a new string (or tag) will be created for the purpose, and the old version can go on the list of old/disused strings. This should help ensure that 21267 and 22044 use a string in the same way, and the translations are valid in both. So, for example, the 1:T change I just asked you to make will never be repeated; it was the first and last such request, and we'll do it by replacement going forward.

                      Any thoughts or recommendations you have about all this are more than welcome. I've done many product localizations from the original engineering side. What I haven't done is worked with language teams on localized builds thereafter -- that has always ended up going to other departments and other companies in other countries, and handled weeks or months after my work has been packaged and released in the US. So, I don't have any experience at policies and procedures that work in helping you maintain the work. I have a good imagination, but it's a bit of "the tail wagging the dog" as we say here, so I'm eager to have you tell me what you think should be done. What we're doing now is only my first guess to see what happens to get it rolling.

                      CrilleC Offline
                      CrilleC Offline
                      Crille
                      wrote on last edited by
                      #10

                      @toggledbits I believe your suggestions for long term compatibility is spot on.
                      Considering this is new and we are running "latest" there will be frequent acceptable changes that demand translators/user actions for keeping things up to date.
                      As you say numbered releases should probably already have an updated file for localization and I really like the implementation of disused strings for backward compatibility.

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

                        OK. I'm updating the docs with all of this. Keep the discoveries and suggestions coming!

                        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
                        1
                        • toggledbitsT toggledbits locked this topic on
                        Reply
                        • Reply as topic
                        Log in to reply
                        • Oldest to Newest
                        • Newest to Oldest
                        • Most Votes


                        Recent Topics

                        • Gradually turn on lights.
                          G
                          gwp1
                          0
                          4
                          95

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

                        • Error After Upgrade
                          G
                          gwp1
                          0
                          4
                          87

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

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

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

                        • Links to MSR from HA
                          Tom_DT
                          Tom_D
                          0
                          1
                          79

                        • Set Reaction > Script Action
                          wmarcolinW
                          wmarcolin
                          0
                          11
                          420

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

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

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

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