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

Scheduled Pinned Locked Moved Multi-System Reactor
17 Posts 4 Posters 1.0k 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.
  • tunnusT Offline
    tunnusT Offline
    tunnus
    wrote on last edited by
    #1

    Using the following localization settings in reactor.yaml:

      units: metric
      locale: fi-FI
      time_format: "%H:%M:%S"
      date_format: "%d/%m/%Y"
    

    But still I'm getting US date & time formatting, so settings do not seem to override defaults? Using 23049 on Synology Docker

    Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT

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

      There's no custom language file for Finnish that I'm aware of (there is definitely not one in the standard distribution). The config override of locale is really intended only for developer testing of localizations while they are doing them. In the absence of such a config/language file, Reactor can't know what to do and relies on nodejs to provide the formatting, which requires that the locale be correctly configured on the host.

      Locale for the host side is usually derived from configuration of the host itself (OS-dependent), or the docker container (by adding a LC_ALL environment variable to the container configuration).

      Display on the browser side (i.e. in the UI) is controlled by the browser's locale setting. Always (regardless of the locale setting on the host or in config).

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

      tunnusT 1 Reply Last reply
      0
      • toggledbitsT toggledbits

        There's no custom language file for Finnish that I'm aware of (there is definitely not one in the standard distribution). The config override of locale is really intended only for developer testing of localizations while they are doing them. In the absence of such a config/language file, Reactor can't know what to do and relies on nodejs to provide the formatting, which requires that the locale be correctly configured on the host.

        Locale for the host side is usually derived from configuration of the host itself (OS-dependent), or the docker container (by adding a LC_ALL environment variable to the container configuration).

        Display on the browser side (i.e. in the UI) is controlled by the browser's locale setting. Always (regardless of the locale setting on the host or in config).

        tunnusT Offline
        tunnusT Offline
        tunnus
        wrote on last edited by
        #3

        @toggledbits wasn't expecting language localization, but date & time. From the manual:

        "You can override the locale Reactor uses for both browser and host display by setting the locale key in the reactor section of reactor.yaml"
        ...
        "By default, dates and times are displayed in the settings determined by the locale (including the order of month, day and year in date displays, and 12/24 time display)"

        So by setting locale in reactor.yaml I was expecting to see e.g. 24 h time format. That didn't happen and then I added time_format and date_format, but still no change?

        Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT

        toggledbitsT 1 Reply Last reply
        0
        • tunnusT tunnus

          @toggledbits wasn't expecting language localization, but date & time. From the manual:

          "You can override the locale Reactor uses for both browser and host display by setting the locale key in the reactor section of reactor.yaml"
          ...
          "By default, dates and times are displayed in the settings determined by the locale (including the order of month, day and year in date displays, and 12/24 time display)"

          So by setting locale in reactor.yaml I was expecting to see e.g. 24 h time format. That didn't happen and then I added time_format and date_format, but still no change?

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

          @tunnus The time_format and date_format are no longer used, since the locale configuration now determines the date and time format.

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

          tunnusT 1 Reply Last reply
          0
          • toggledbitsT toggledbits

            @tunnus The time_format and date_format are no longer used, since the locale configuration now determines the date and time format.

            tunnusT Offline
            tunnusT Offline
            tunnus
            wrote on last edited by
            #5

            @toggledbits okay, but any idea why using "locale: fi-FI" in reactor.yaml does not change date & time format in UI? Or should it?

            FWIW, using Chrome with Finnish as preferred language (but as said, not expecting to see language impact here, only date/time formatting)

            Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT

            1 Reply Last reply
            0
            • tunnusT Offline
              tunnusT Offline
              tunnus
              wrote on last edited by
              #6

              ...I even tried adding LC_ALL variable to Docker with "fi_FI.UTF-8" as a value, but again no impact (for time formatting).

              Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT

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

                At the moment it's an all or nothing deal... if there's a translation file, it will accept the locale; otherwise, it just sticks to default US English.

                Maybe you should write the fi-FI translation? 🙂

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

                tunnusT 1 Reply Last reply
                0
                • toggledbitsT toggledbits

                  At the moment it's an all or nothing deal... if there's a translation file, it will accept the locale; otherwise, it just sticks to default US English.

                  Maybe you should write the fi-FI translation? 🙂

                  tunnusT Offline
                  tunnusT Offline
                  tunnus
                  wrote on last edited by
                  #8

                  @toggledbits said in localization settings:

                  At the moment it's an all or nothing deal... if there's a translation file, it will accept the locale; otherwise, it just sticks to default US English.

                  Maybe you should write the fi-FI translation? 🙂

                  Might even do that 😁 But in the meanwhile wondering if nobody else is interested to get 24 hour time display. @therealdb & @Crille ?

                  Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT

                  therealdbT 1 Reply Last reply
                  0
                  • CrilleC Offline
                    CrilleC Offline
                    Crille
                    wrote on last edited by Crille
                    #9

                    The Swedish translation at http://[ip]:8111/reactor/sv-SE/ is in 24h format if the browsers locale setting is set to it.

                    1 Reply Last reply
                    1
                    • tunnusT tunnus

                      @toggledbits said in localization settings:

                      At the moment it's an all or nothing deal... if there's a translation file, it will accept the locale; otherwise, it just sticks to default US English.

                      Maybe you should write the fi-FI translation? 🙂

                      Might even do that 😁 But in the meanwhile wondering if nobody else is interested to get 24 hour time display. @therealdb & @Crille ?

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

                      @tunnus I have started Italian translation, but I'm busy with other things and I like American English anyway. But we could try to create an international English with 24h clock and right date formats, just in case 🤣

                      --
                      On a mission to automate everything.

                      My MS Reactor contrib
                      My Luup Plug-ins

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

                        I'm working on some changes, but it may be another week. I'm swamped right now.

                        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
                        • therealdbT Offline
                          therealdbT Offline
                          therealdb
                          wrote on last edited by
                          #12

                          For anyone here trying to get the 24H & right date format 🙂 just add this to your reactor config file (at least v 23063 required):

                          reactor:
                            ...
                            units: metric
                            date_format: "%d/%m/%Y"
                            time_format: "%H:%M:%S"
                          

                          Restart, hard refresh your browser and you're good to go. Thanks @toggledbits !

                          --
                          On a mission to automate everything.

                          My MS Reactor contrib
                          My Luup Plug-ins

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

                            Note: you only need to do this if your locale-defined time format isn't 24 hour.

                            Also, the format shown by @therealdb might be normal for his locale, but not yours specifically. This config will also override the locale-defined date format; if you don't want that, set time_format only.

                            Final note: Locale setting is determined by (both) the locale set for the host OS and the locale settings of your browser. This is the preferred way to set locale. Setting locale in Reactor's config is specifically not recommended.

                            Edit: to be clear, to get your language's preferred date and time formats, you should do the following, in the order listed:

                            1. Configure your host system (or the Reactor docker container) and your browser for the correct locale. This may be sufficient for most uses. Make sure to re-open browser windows from the "root" of the Reactor URL (e.g. click the Reactor logo in the upper-left corner of the page).
                            2. If the time or date format presented by correctly completing step 1 does not suit your preferences, then and only then set date_format and/or time_format in Reactor's config.
                            3. Never use the Reactor config locale setting; this is for developers only and is not a complete solution for getting the correct locale. Locale configuration is always inherited from (both) your host system and browser, and that is the only correct way to do it permanently.

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

                            tunnusT 1 Reply Last reply
                            0
                            • toggledbitsT toggledbits

                              Note: you only need to do this if your locale-defined time format isn't 24 hour.

                              Also, the format shown by @therealdb might be normal for his locale, but not yours specifically. This config will also override the locale-defined date format; if you don't want that, set time_format only.

                              Final note: Locale setting is determined by (both) the locale set for the host OS and the locale settings of your browser. This is the preferred way to set locale. Setting locale in Reactor's config is specifically not recommended.

                              Edit: to be clear, to get your language's preferred date and time formats, you should do the following, in the order listed:

                              1. Configure your host system (or the Reactor docker container) and your browser for the correct locale. This may be sufficient for most uses. Make sure to re-open browser windows from the "root" of the Reactor URL (e.g. click the Reactor logo in the upper-left corner of the page).
                              2. If the time or date format presented by correctly completing step 1 does not suit your preferences, then and only then set date_format and/or time_format in Reactor's config.
                              3. Never use the Reactor config locale setting; this is for developers only and is not a complete solution for getting the correct locale. Locale configuration is always inherited from (both) your host system and browser, and that is the only correct way to do it permanently.
                              tunnusT Offline
                              tunnusT Offline
                              tunnus
                              wrote on last edited by tunnus
                              #14

                              @toggledbits so with build 23063 Docker environment variable LC_ALL should work (tried with build 23049, but no success)?

                              Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT

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

                                That will change it on the host side. It has no effect on the browser settings (which are browser-dependent).

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

                                tunnusT 1 Reply Last reply
                                0
                                • toggledbitsT toggledbits

                                  That will change it on the host side. It has no effect on the browser settings (which are browser-dependent).

                                  tunnusT Offline
                                  tunnusT Offline
                                  tunnus
                                  wrote on last edited by
                                  #16

                                  @toggledbits yes, just wanted to confirm that with earlier builds LC_ALL was essentially ignored

                                  Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT

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

                                    Not ignored, just not used if there was no language file present for the selected language.

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

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

                                    • Error After Upgrade
                                      G
                                      gwp1
                                      0
                                      4
                                      103

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

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

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

                                    • Links to MSR from HA
                                      Tom_DT
                                      Tom_D
                                      0
                                      1
                                      90

                                    • Set Reaction > Script Action
                                      wmarcolinW
                                      wmarcolin
                                      0
                                      11
                                      433

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

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

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

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