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
Access control - allowing anonymous user to dashboard
tunnusT
Using build 25328 and having the following users.yaml configuration: users: # This section defines your valid users. admin: ******* groups: # This section defines your user groups. Optionally, it defines application # and API access restrictions (ACLs) for the group. Users may belong to # more than one group. Again, no required or special groups here. admin_group: users: - admin applications: true # special form allows access to ALL applications guests: users: "*" applications: - dashboard api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin_group allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: true session: timeout: 7200 # (seconds) rolling: true # activity extends timeout when true # If log_acls is true, the selected ACL for every API access is logged. log_acls: true # If debug_acls is true, even more information about ACL selection is logged. debug_acls: true My goal is to allow anonymous user to dashboard, but MSR is still asking for a password when trying to access that. Nothing in the logs related to dashboard access. Probably an error in the configuration, but help needed to find that. Tried to put url: "/dashboard" under api_acls, but that was a long shot and didn't work.
Multi-System Reactor
VEC Virtual Switch Auto Off
S
I use Virtual Entity Controller virtual switches which I turn on via webhooks from other applications. Once a switch triggers and turns on, I can then activate associated rules. I would like each virtual switch to automatically turn off after a configurable time (e.g., 5 seconds, 10 seconds). Is there a better way to achieve this auto-off behavior instead of creating a separate rule for each switch that uses the 'Condition must be sustained for' option to turn it off? With a large number of these switches (and the associated turn-off rules), I'm checking to see if there is a simpler approach.If not, could this be a feature request to add an auto-off timer directly to the virtual switches. Thanks Reactor (Multi-hub) latest-26011-c621bbc7 VirtualEntityController v25356 Synology Docker
Multi-System Reactor
Upcoming Storage Change -- Got Back-ups?
toggledbitsT
TL;DR: Format of data in storage directory will soon change. Make sure you are backing up the contents of that directory in its entirety, and you preserve your backups for an extended period, particularly the backup you take right before upgrading to the build containing this change (date of that is still to be determined, but soon). The old data format will remain readable (so you'll be able to read your pre-change backups) for the foreseeable future. In support of a number of other changes in the works, I have found it necessary to change the storage format for Reactor objects in storage at the physical level. Until now, plain, standard JSON has been used to store the data (everything under the storage directory). This has served well, but has a few limitations, including no real support for native JavaScript objects like Date, Map, Set, and others. It also is unable to store data that contains "loops" — objects that reference themselves in some way. I'm not sure exactly when, but in the not-too-distant future I will publish a build using the new data format. It will automatically convert existing JSON data to the new format. For the moment, it will save data in both the new format and the old JSON format, preferring the former when loading data from storage. I have been running my own home with this new format for several months, and have no issues with data loss or corruption. A few other things to know: If you are not already backing up your storage directory, you should be. At a minimum, back this directory up every time you make big changes to your Rules, Reactions, etc. Your existing JSON-format backups will continue to be readable for the long-term (years). The code that loads data from these files looks for the new file format first (which will have a .dval suffix), and if not found, will happily read (and convert) a same-basenamed .json file (i.e. it looks for ruleid.dval first, and if it doesn't find it, it tries to load ruleid.json). I'll publish detailed instructions for restoring from old backups when the build is posted (it's easy). The new .dval files are not directly human-readable or editable as easily as the old .json files. A new utility will be provided in the tools directory to convert .dval data to .json format, which you can then read or edit if you find that necessary. However, that may not work for all future data, as my intent is to make more native JavaScript objects directly storable, and many of those objects cannot be stored in JSON. You may need to modify your backup tools/scripts to pick up the new files: if you explicitly name .json files (rather than just specifying the entire storage directory) in your backup configuration, you will need to add .dval files to get a complete, accurate backup. I don't think this will be an issue for any of you; I imagine that you're all just backing up the entire contents of storage regardless of format/name, that is the safest (and IMO most correct) way to go (if that's not what you're doing, consider changing your approach). The current code stores the data in both the .dval form and the .json form to hedge against any real-world problems I don't encounter in my own use. Some future build will drop this redundancy (i.e. save only to .dval form). However, the read code for the .json form will remain in any case. This applies only to persistent storage that Reactor creates and controls under the storage tree. All other JSON data files (e.g. device data for Controllers) are unaffected by this change and will remain in that form. YAML files are also unaffected by this change. This thread is open for any questions or concerns.
Multi-System Reactor
Oddness in Copy/Move of Reactions
G
Topic thumbnail image
Multi-System Reactor
[Solved] function isRuleEnabled() issue
CrilleC
Topic thumbnail image
Multi-System Reactor
[Reactor] Problem with Global Reactions and groups
therealdbT
Topic thumbnail image
Multi-System Reactor
Possible feature request 2?
CatmanV2C
Just another thought. Adding devices from my Home Assistant / Zigbee2MQTT integration. Works perfectly but they always add as their IEEE address. Some of these devices have up to 10 entities associated, and the moment they are renamed to something sensible, each of those entities 'ceases to exist' in MSR. I like things tidy, and deleting each defunct entity needs 3 clicks. Any chance of a 'bulk delete' option? No biggy as I've pretty much finished my Z-wave migration and I don't expect to be adding more than 2 new Zigbee devices Cheers C
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
Copying a global reaction
tunnusT
With build 25328, if you copy a global reaction, a new reaction does not appear in the UI unless you do a refresh. I recall this used to work without needing this page refresh? Anyway, only a minor nuisance.
Multi-System Reactor
[Reactor] Bug when sending MQTT boolean payloads
therealdbT
Topic thumbnail image
Multi-System Reactor
Difficulty defining repeating annual period
R
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Multi-System Reactor
Need help with sequence
T
Good evening all, For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time. Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed. Thanks.
Multi-System Reactor
Possible feature request?
CatmanV2C
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations. Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction? Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for. I guess it's something of an edge case so no huge issue. TIA! C
Multi-System Reactor
Logic Assistance: Exterior Lights on when Illuminance Below Threshold
PablaP
Topic thumbnail image
Multi-System Reactor
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
MQTT templates for ZIgbee scene controller, or a better way?
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reset a delay
CatmanV2C
I'm sure this has been asked, and answered, but damned if I can figure it out Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage. Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts. After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!) What I would like is for the 3 minute delay until the lights go off to start from the latest door open event. That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity. I've tried 'hacking' with a virtual switch, but can't seem to stop the delay. Any pointers? TIA C
Multi-System Reactor
Reactor Loading Screen Safari
S
Topic thumbnail image
Multi-System Reactor
Constraints states visually do not match actual
S
Topic thumbnail image
Multi-System Reactor
[MSR] Feature request: For Each action on arrays/groups
therealdbT
Topic thumbnail image
Multi-System Reactor

localization settings

Scheduled Pinned Locked Moved Multi-System Reactor
17 Posts 4 Posters 2.3k 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 & ZWA-2

    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 & ZWA-2

        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 & ZWA-2

            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 & ZWA-2

              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 & ZWA-2

                  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 & ZWA-2

                              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 & ZWA-2

                                  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

                                    • Access control - allowing anonymous user to dashboard
                                      toggledbitsT
                                      toggledbits
                                      0
                                      2
                                      54

                                    • VEC Virtual Switch Auto Off
                                      S
                                      SweetGenius
                                      1
                                      1
                                      46

                                    • Upcoming Storage Change -- Got Back-ups?
                                      toggledbitsT
                                      toggledbits
                                      2
                                      1
                                      38

                                    • Oddness in Copy/Move of Reactions
                                      G
                                      gwp1
                                      0
                                      1
                                      67

                                    • [Solved] function isRuleEnabled() issue
                                      CrilleC
                                      Crille
                                      0
                                      4
                                      103

                                    • [Reactor] Problem with Global Reactions and groups
                                      therealdbT
                                      therealdb
                                      0
                                      3
                                      118

                                    • Possible feature request 2?
                                      CatmanV2C
                                      CatmanV2
                                      0
                                      3
                                      88

                                    • Reactor (Multi-System/Multi-Hub) Announcements
                                      toggledbitsT
                                      toggledbits
                                      5
                                      133
                                      80.2k

                                    • Genuinely impressed with Zigbee and HA / Reactor
                                      CatmanV2C
                                      CatmanV2
                                      1
                                      9
                                      397

                                    • Copying a global reaction
                                      toggledbitsT
                                      toggledbits
                                      0
                                      3
                                      122

                                    • [HowTo] Using HABridge with Reactor
                                      CatmanV2C
                                      CatmanV2
                                      0
                                      9
                                      458

                                    • [Reactor] Bug when sending MQTT boolean payloads
                                      toggledbitsT
                                      toggledbits
                                      0
                                      4
                                      181
                                    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