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. Dark Mode not Working - 24293
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
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
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

Dark Mode not Working - 24293

Scheduled Pinned Locked Moved Solved Multi-System Reactor
13 Posts 3 Posters 1.8k Views 3 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.
  • PablaP Offline
    PablaP Offline
    Pabla
    wrote on last edited by Pabla
    #1

    Seems like switching the UI to the newly added dark mode (thank you for this) does nothing. The UI stays in light mode and only a few buttons turn into dark mode (see screenshot)

    Things I have tried:

    Hard refresh
    Different browser
    Different computer
    Restarting Reactor

    Failed troubleshooting attempts:

    No errors in Chrome console
    No relevant errors in Reactor log (can still PM the full log file)

    Reactor version: latest-24293-ea42a81d
    Hardware: Odroid N2+
    Linux version: Ubuntu 24.04.1 LTS

    3df2806f-9146-485b-9ec1-d056e91cefe5-image.png Dark mode enabled

    ff823023-c079-4684-b01f-d6ac6527d31a-image.png Light mode enabled

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

      OK. Check to make sure you've done all the npm updates/installed (see the warning in the release notes).

      Second issue is that dark mode on Ubuntu 24.04 is known to have issues (it's a platform issue, not a Reactor issue). Check from a browser running on another platform. This works for me on every browser I'm able to test, but Ubuntu Desktop isn't part of that. I can also see that at least one other user is successfully using dark mode.

      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 Offline
        toggledbitsT Offline
        toggledbits
        wrote on last edited by
        #2

        Bare metal or Docker?

        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
        • PablaP Offline
          PablaP Offline
          Pabla
          wrote on last edited by
          #3

          Bare metal.. forgot to add that

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

            OK. Check to make sure you've done all the npm updates/installed (see the warning in the release notes).

            Second issue is that dark mode on Ubuntu 24.04 is known to have issues (it's a platform issue, not a Reactor issue). Check from a browser running on another platform. This works for me on every browser I'm able to test, but Ubuntu Desktop isn't part of that. I can also see that at least one other user is successfully using dark mode.

            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
            • PablaP Offline
              PablaP Offline
              Pabla
              wrote on last edited by Pabla
              #5

              Ha I obviously missed the first line in the release notes in my excitement for the dark mode.. also my update script also bit me in the ass here since it didn't run sudo npm i --no-save --no-package-lock --omit dev.

              All seems to be working well now, no more needing to use sunglasses when switching over to my Reactor tab 😉 .

              PS by stating my Linux version I was trying to show what version of Linux Reactor was running on and not the devices I was accessing the UI from.. so can't confirm that the UI shows correctly in Ubuntu

              toggledbitsT 1 Reply Last reply
              0
              • PablaP Pabla marked this topic as a question on
              • PablaP Pabla has marked this topic as solved on
              • PablaP Pabla

                Ha I obviously missed the first line in the release notes in my excitement for the dark mode.. also my update script also bit me in the ass here since it didn't run sudo npm i --no-save --no-package-lock --omit dev.

                All seems to be working well now, no more needing to use sunglasses when switching over to my Reactor tab 😉 .

                PS by stating my Linux version I was trying to show what version of Linux Reactor was running on and not the devices I was accessing the UI from.. so can't confirm that the UI shows correctly in Ubuntu

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

                @Pabla said in Dark Mode not Working - 24293:

                All seems to be working well now

                Outstanding. Love the easy ones!

                @Pabla said in Dark Mode not Working - 24293:

                PS by stating my Linux version I was trying to show what version of Linux Reactor was running on and not the devices I was accessing the UI from..

                Got it. Couldn't really tell, so it was worth lobbing it over the fence to see if it got thrown back. In any case, thanks for clarifying, because I use that as a data point either way.

                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 Online
                  CrilleC Online
                  Crille
                  wrote on last edited by Crille
                  #7

                  I'm getting the same issue even after running npm i --no-save --no-package-lock --omit dev, also tried npm run deps
                  Bare metal 24293 running on Ubuntu Server 22.04.5 LTS
                  Hard refreshed browser Chrome/Edge on Windows

                  What am I missing here?

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

                    Make sure you've hard-refreshed your browser after updating the packages. If you're still not getting dark mode, open your browser's console window (F12) and run the following commands exactly as shown:

                    1. $.fn.jquery — the browser should answer 3.7..1
                    2. $.ui.version — the browser should answer 1.14.0 (1.13.anything would be OK)
                    3. bootstrap.Tooltip.VERSION — the browser should answer 5.3.3

                    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 Online
                      CrilleC Online
                      Crille
                      wrote on last edited by
                      #9

                      @toggledbits said in Dark Mode not Working - 24293:

                      bootstrap.Tooltip.VERSION — the browser should answer 5.3.3

                      Hm I'm getting 5.2.0 in both newly updated browsers.

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

                        OK. If you have a file called package-lock.json in the Reactor directory, remove it and run npm i --no-save --no-package-lock --omit dev again. Then do npm ls and see what version of Bootstrap is showing.

                        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 Online
                          CrilleC Online
                          Crille
                          wrote on last edited by
                          #11

                          I can't find any package-lock.json and this is the output of npm ls

                          reactor-multi-system@1.3.0-24293 /home/homebridge/reactor
├── @influxdata/influxdb-client@1.22.0
├── @mdi/font@7.4.47
├── @popperjs/core@2.11.6
├── body-parser@1.20.1
├── bootstrap-icons@1.11.3
├── bootstrap@5.2.0
├── digest-fetch@2.0.3
├── diskusage-ng@1.0.2
├── express@4.17.2
├── feather-icons@4.28.0
├── font-awesome@4.7.0
├── gridstack@10.3.1
├── jquery-ui@1.14.0
├── jquery@3.7.1
├── js-yaml@4.1.0
├── node-fetch@2.6.7
├── node-stream-zip@1.15.0
├── nodemailer@6.8.0
├── serve-static@1.15.0
├── uuid@10.0.0
└── ws@7.5.9
                          1 Reply Last reply
                          0
                          • toggledbitsT Offline
                            toggledbitsT Offline
                            toggledbits
                            wrote on last edited by
                            #12

                            OK. Edit your package.json file so that the dependencies line for bootstrap says ^5.3, and then run the npm i command (with all command line arguments previously given) again.

                            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
                            • CrilleC Online
                              CrilleC Online
                              Crille
                              wrote on last edited by
                              #13

                              Yes, that did it! Thanks

                              1 Reply Last reply
                              0
                              • toggledbitsT toggledbits unlocked this topic on
                              • toggledbitsT toggledbits locked this topic on
                              Reply
                              • Reply as topic
                              Log in to reply
                              • Oldest to Newest
                              • Newest to Oldest
                              • Most Votes

                              Recent Topics

                              • VEC Virtual Switch Auto Off
                                S
                                SweetGenius
                                0
                                1
                                11
                              • Access control - allowing anonymous user to dashboard
                                tunnusT
                                tunnus
                                0
                                1
                                13
                              • Upcoming Storage Change -- Got Back-ups?
                                toggledbitsT
                                toggledbits
                                0
                                1
                                15
                              • Oddness in Copy/Move of Reactions
                                G
                                gwp1
                                0
                                1
                                50
                              • [Solved] function isRuleEnabled() issue
                                CrilleC
                                Crille
                                0
                                4
                                62
                              • [Reactor] Problem with Global Reactions and groups
                                therealdbT
                                therealdb
                                0
                                3
                                84
                              • Possible feature request 2?
                                CatmanV2C
                                CatmanV2
                                0
                                3
                                65
                              • Reactor (Multi-System/Multi-Hub) Announcements
                                toggledbitsT
                                toggledbits
                                5
                                133
                                79.8k
                              • Genuinely impressed with Zigbee and HA / Reactor
                                CatmanV2C
                                CatmanV2
                                1
                                9
                                370
                              • Copying a global reaction
                                toggledbitsT
                                toggledbits
                                0
                                3
                                111
                              • [HowTo] Using HABridge with Reactor
                                CatmanV2C
                                CatmanV2
                                0
                                9
                                440
                              • [Reactor] Bug when sending MQTT boolean payloads
                                toggledbitsT
                                toggledbits
                                0
                                4
                                163
                              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