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. Expressions page showing old data
Set reaction triggering wrong z-wave device
T
Topic thumbnail image
Multi-System Reactor
Can you run MSR on Home Assistant OS ?
cw-kidC
Looking at using Home Assistant for the first time, either on a Home Assistant Green, their own hardware or buying a cheap second hand mini PC. Sounds like Home Assistant OS is linux based using Docker for HA etc. Would I also be able to install things like MSR as well on their OS ? On the same box? Thanks.
Multi-System Reactor
How to upgrade from an old version of MSR?
cw-kidC
Hello I haven't updated my installation of MSR in a very long time. Its a bare metal Linux install currently on version 24366-3de60836 I see the latest version is now latest-26011-c621bbc7 I assume I cannot just jump from a very old version to the latest version? Or can I? Thanks
Multi-System Reactor
This trigger no longer working - complaining about the operator needing changing
cw-kidC
Topic thumbnail image
Multi-System Reactor
Self test
CatmanV2C
Having been messing around with some stuff I worked a way to self trigger some tests that I wanted to do on the HA <> MSR integration This got me wondering if there's an entity that changes state / is exposed when a configured controller goes off line? I can't see one but thought it might be hidden or something? Cheers C
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
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

Expressions page showing old data

Scheduled Pinned Locked Moved Multi-System Reactor
10 Posts 3 Posters 1.6k 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.
  • R Offline
    R Offline
    RHCPNG
    wrote on last edited by RHCPNG
    #1

    Hi @toggledbits,

    I seem to be having the same issue. Is it possible that the expressions are only saved to the json when a restart of Reactor is done?

    Today I looked in Reactor and saw an old version of all my expressions. My latest changes were gone (done a few days ago). Reactor didn't have a restart in the meantime.

    When I recreated all new expressions and looked in expression.json, the new expressions weren't there (yet). After I did a restart of Reactor, the changes were visible.

    Which moments are the expressions saved to the file?

    I'm not running the add-on, but the docker. I do not have the latest update yet (latest-23114-e4060aae)

    This doesn't explain why my changes were gone, but I'm still tinkering about that. Maybe my backup messes something up.

    toggledbitsT 1 Reply Last reply
    0
    • R RHCPNG

      Hi @toggledbits,

      I seem to be having the same issue. Is it possible that the expressions are only saved to the json when a restart of Reactor is done?

      Today I looked in Reactor and saw an old version of all my expressions. My latest changes were gone (done a few days ago). Reactor didn't have a restart in the meantime.

      When I recreated all new expressions and looked in expression.json, the new expressions weren't there (yet). After I did a restart of Reactor, the changes were visible.

      Which moments are the expressions saved to the file?

      I'm not running the add-on, but the docker. I do not have the latest update yet (latest-23114-e4060aae)

      This doesn't explain why my changes were gone, but I'm still tinkering about that. Maybe my backup messes something up.

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

      @RHCPNG said in Home Assistant add-on:

      I'm not running the add-on, but the docker.

      Well, then you're posting in the wrong thread. This thread is for the add-on (only). I'll move the post, but in future, please consider the relevance of your question to the subject (i.e. title) of the thread, not something any part of contents may mention in its progress. Check the posting guidelines as well.

      Always refresh your browser when things look "old" as a first step, rather than restarting Reactor. In particular, if the changes were made in a different browser, it's quite possible the "other" browser would continue to show out of date expressions.

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

        Sorry for posting in the other thread, but the problem didn't seem to only be applicable to the add-on.

        You don't understand the problem fully. The browser was not the problem. The changes were gone in the expressions.json.

        After doing the changes again in the browser, the changes were still not visible in the json. Only after a restart, they were visible in the json.

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

          That's correct. The caching doesn't save the changes to the JSON until Reactor shuts down. The changes are present in the engine's structure data, nonetheless.

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

            Is it possible to save it more often? I have to figure out what's causing the loss of the expressions, but for now my backup is "worthless". Now, the only way to get the expressions back would be a restore of a full backup of the docker files, but then I will potentially lose other changes.

            Any idea why I only lose the expressions and not other changes that are done later?

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

              Let's make sure you are getting an orderly shutdown of your container. Try stopping your container (not restarting, just stopping), and then examine the reactor.log file. You should see a series of messages that begins as follows (the signal named may vary somewhat)...

              [###BUILDVERSION###]2023-06-21T15:32:35.467Z <app:NOTICE> Shutdown signal (SIGTERM) received. Stopping Reaction Engine...
[###BUILDVERSION###]2023-06-21T15:32:35.467Z <app:NOTICE> Closing APIs...
[###BUILDVERSION###]2023-06-21T15:32:35.467Z <wsapi:NOTICE> wsapi: closing...
[###BUILDVERSION###]2023-06-21T15:32:35.467Z <httpapi:NOTICE> HTTP API closing...
[###BUILDVERSION###]2023-06-21T15:32:35.468Z <app:NOTICE> Stopping Engine...

              The messages that follow should be free of errors and point to an orderly shutdown ending with:

              [###BUILDVERSION###]2023-06-20T14:57:44.866Z <Structure:NOTICE> Structure Structure#1 stopped
[###BUILDVERSION###]2023-06-20T14:57:44.866Z <app:NOTICE> Stopping timers...
[###BUILDVERSION###]2023-06-20T14:57:44.866Z <app:NOTICE> Shutdown complete, process ID 1870702

              If you see any errors or things that look odd, post them in reply here (please format properly -- see the posting guidelines if you need advice/help).

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

              R 1 Reply Last reply
              0
              • toggledbitsT toggledbits

                Let's make sure you are getting an orderly shutdown of your container. Try stopping your container (not restarting, just stopping), and then examine the reactor.log file. You should see a series of messages that begins as follows (the signal named may vary somewhat)...

                [###BUILDVERSION###]2023-06-21T15:32:35.467Z <app:NOTICE> Shutdown signal (SIGTERM) received. Stopping Reaction Engine...
[###BUILDVERSION###]2023-06-21T15:32:35.467Z <app:NOTICE> Closing APIs...
[###BUILDVERSION###]2023-06-21T15:32:35.467Z <wsapi:NOTICE> wsapi: closing...
[###BUILDVERSION###]2023-06-21T15:32:35.467Z <httpapi:NOTICE> HTTP API closing...
[###BUILDVERSION###]2023-06-21T15:32:35.468Z <app:NOTICE> Stopping Engine...

                The messages that follow should be free of errors and point to an orderly shutdown ending with:

                [###BUILDVERSION###]2023-06-20T14:57:44.866Z <Structure:NOTICE> Structure Structure#1 stopped
[###BUILDVERSION###]2023-06-20T14:57:44.866Z <app:NOTICE> Stopping timers...
[###BUILDVERSION###]2023-06-20T14:57:44.866Z <app:NOTICE> Shutdown complete, process ID 1870702

                If you see any errors or things that look odd, post them in reply here (please format properly -- see the posting guidelines if you need advice/help).

                R Offline
                R Offline
                RHCPNG
                wrote on last edited by
                #7

                @toggledbits

                The exit procedure seems fine.

                [latest-23114]2023-06-21T17:47:59.159Z <Rule:INFO> Windows open (rule-grp1myo029o in Weer) starting evaluation; because expression-state-changed GlobalExpression#gTempOutside
[latest-23114]2023-06-21T17:47:59.159Z <Rule:INFO> Windows closed (rule-grp1mznck5b in Weer) starting evaluation; because expression-state-changed GlobalExpression#gTempOutside
[latest-23114]2023-06-21T17:47:59.160Z <Rule:INFO> Windows open (rule-grp1myo029o in Weer) trigger evaluation result is true (previously true)
[latest-23114]2023-06-21T17:47:59.160Z <Rule:INFO> Windows open (rule-grp1myo029o in Weer) evaluated; trigger state unchanged (true); rule state remains SET
[latest-23114]2023-06-21T17:47:59.161Z <Rule:INFO> Windows closed (rule-grp1mznck5b in Weer) trigger evaluation result is false (previously false)
[latest-23114]2023-06-21T17:47:59.162Z <Rule:INFO> Windows closed (rule-grp1mznck5b in Weer) evaluated; trigger state unchanged (false); rule state remains RESET
[latest-23114]2023-06-21T17:47:59.162Z <Rule:INFO> Windows open (rule-grp1myo029o in Weer) evaluation complete
[latest-23114]2023-06-21T17:47:59.162Z <Rule:INFO> Windows closed (rule-grp1mznck5b in Weer) evaluation complete
[latest-23114]2023-06-21T17:48:07.032Z <app:NOTICE> Shutdown signal (SIGTERM) received. Stopping Reaction Engine...
[latest-23114]2023-06-21T17:48:07.034Z <app:NOTICE> Closing APIs...
[latest-23114]2023-06-21T17:48:07.035Z <wsapi:NOTICE> wsapi: closing...
[latest-23114]2023-06-21T17:48:07.036Z <httpapi:NOTICE> HTTP API closing...
[latest-23114]2023-06-21T17:48:07.036Z <app:NOTICE> Stopping Engine...
[latest-23114]2023-06-21T17:48:07.039Z <Rule:NOTICE> Motor op lader (rule-liot7yyg in Garage) stopping
[latest-23114]2023-06-21T17:48:07.039Z <Rule:NOTICE> Zonnescherm auto IN (rule-lipp4379 in Tuin) stopping
[latest-23114]2023-06-21T17:48:07.039Z <Rule:NOTICE> Zonnescherm auto UIT (rule-lhdixs68 in Tuin) stopping
[latest-23114]2023-06-21T17:48:07.039Z <Rule:NOTICE> Disk space low (rule-lgyxocj5 in System) stopping
[latest-23114]2023-06-21T17:48:07.039Z <Rule:NOTICE> Niels at home (rule-lg7vjm7n in Proximity) stopping
[latest-23114]2023-06-21T17:48:07.042Z <Rule:NOTICE> Tessa at home (rule-lg7v960f in Proximity) stopping
[latest-23114]2023-06-21T17:48:07.043Z <Rule:NOTICE> Tessa driving (rule-lg7v6f3w in Proximity) stopping
[latest-23114]2023-06-21T17:48:07.043Z <Rule:NOTICE> Tessa at work (rule-lg7v3cm6 in Proximity) stopping
[latest-23114]2023-06-21T17:48:07.043Z <Rule:NOTICE> Tessa at S&K (rule-lg7uxvzo in Proximity) stopping
[latest-23114]2023-06-21T17:48:07.088Z <Rule:NOTICE> Windows open (rule-grp1myo029o in Weer) stopping
[latest-23114]2023-06-21T17:48:07.088Z <Rule:NOTICE> Windows closed (rule-grp1mznck5b in Weer) stopping
[latest-23114]2023-06-21T17:48:07.088Z <wsapi:NOTICE> wsapi: server closed
[latest-23114]2023-06-21T17:48:07.089Z <httpapi:INFO> HTTP server closed.
[latest-23114]2023-06-21T17:48:07.090Z <Rule:NOTICE> Motor op lader (rule-liot7yyg in Garage) stopped
[latest-23114]2023-06-21T17:48:07.091Z <Rule:NOTICE> Zonnescherm auto IN (rule-lipp4379 in Tuin) stopped
[latest-23114]2023-06-21T17:48:07.094Z <Rule:NOTICE> Zonnescherm auto UIT (rule-lhdixs68 in Tuin) stopped
[latest-23114]2023-06-21T17:48:07.095Z <Rule:NOTICE> Disk space low (rule-lgyxocj5 in System) stopped
[latest-23114]2023-06-21T17:48:07.096Z <Rule:NOTICE> Niels at home (rule-lg7vjm7n in Proximity) stopped
[latest-23114]2023-06-21T17:48:07.097Z <Rule:NOTICE> Tessa at home (rule-lg7v960f in Proximity) stopped
[latest-23114]2023-06-21T17:48:07.098Z <Rule:NOTICE> Tessa driving (rule-lg7v6f3w in Proximity) stopped
[latest-23114]2023-06-21T17:48:07.099Z <Rule:NOTICE> Tessa at work (rule-lg7v3cm6 in Proximity) stopped
[latest-23114]2023-06-21T17:48:07.100Z <Rule:NOTICE> Tessa at S&K (rule-lg7uxvzo in Proximity) stopped
[latest-23114]2023-06-21T17:48:07.101Z <Rule:NOTICE> Windows open (rule-grp1myo029o in Weer) stopped
[latest-23114]2023-06-21T17:48:07.102Z <Rule:NOTICE> Windows closed (rule-grp1mznck5b in Weer) stopped
[latest-23114]2023-06-21T17:48:07.111Z <Engine:NOTICE> [Engine]Engine#1 has shut down.
[latest-23114]2023-06-21T17:48:07.112Z <app:NOTICE> Closing Structure...
[latest-23114]2023-06-21T17:48:07.112Z <Structure:NOTICE> Structure#1 Stopping controllers...
[latest-23114]2023-06-21T17:48:07.112Z <Structure:INFO> Structure#1 stopping VeraController#openluup
[latest-23114]2023-06-21T17:48:07.113Z <Controller:NOTICE> VeraController#openluup stopping
[latest-23114]2023-06-21T17:48:07.117Z <Controller:ERR> Controller VeraController#openluup is off-line!
[latest-23114]2023-06-21T17:48:07.952Z <Structure:INFO> Structure#1 stopping HassController#hass
[latest-23114]2023-06-21T17:48:07.952Z <HassController:NOTICE> HassController#hass stopping
[latest-23114]2023-06-21T17:48:07.965Z <wsapi:WARN> client close from unknown connection? "192.168.1.174#25"
[latest-23114]2023-06-21T17:48:07.966Z <wsapi:WARN> client close from unknown connection? "192.168.1.174#24"
[latest-23114]2023-06-21T17:48:07.983Z <HassController:NOTICE> HassController#hass websocket closing, 1000
[latest-23114]2023-06-21T17:48:07.985Z <Controller:NOTICE> HassController#hass stopping
[latest-23114]2023-06-21T17:48:07.988Z <Controller:ERR> Controller HassController#hass is off-line!
[latest-23114]2023-06-21T17:48:09.266Z <Structure:INFO> Structure#1 stopping DynamicGroupController#groups
[latest-23114]2023-06-21T17:48:09.266Z <DynamicGroupController:null> DynamicGroupController#groups stopping
[latest-23114]2023-06-21T17:48:09.267Z <Controller:NOTICE> DynamicGroupController#groups stopping
[latest-23114]2023-06-21T17:48:09.268Z <Controller:ERR> Controller DynamicGroupController#groups is off-line!
[latest-23114]2023-06-21T17:48:09.279Z <Structure:INFO> Structure#1 stopping SystemController#reactor_system
[latest-23114]2023-06-21T17:48:09.279Z <Controller:NOTICE> SystemController#reactor_system stopping
[latest-23114]2023-06-21T17:48:09.281Z <Controller:ERR> Controller SystemController#reactor_system is off-line!
[latest-23114]2023-06-21T17:48:09.288Z <Structure:INFO> Structure#1 Final data sync...
[latest-23114]2023-06-21T17:48:09.288Z <default:INFO> Closing container Container#rulesets
[latest-23114]2023-06-21T17:48:09.289Z <default:INFO> Closing container Container#rules
[latest-23114]2023-06-21T17:48:09.289Z <default:INFO> Closing container Container#reactions
[latest-23114]2023-06-21T17:48:09.289Z <default:INFO> Closing container Container#states
[latest-23114]2023-06-21T17:48:09.316Z <default:INFO> Closing container Container#default
[latest-23114]2023-06-21T17:48:09.316Z <default:INFO> Closing container Container#expressions
[latest-23114]2023-06-21T17:48:09.318Z <Structure:NOTICE> Structure Structure#1 stopped
[latest-23114]2023-06-21T17:48:09.319Z <app:NOTICE> Stopping timers...
[latest-23114]2023-06-21T17:48:09.319Z <app:NOTICE> Shutdown complete, process ID 1

                I did get a disk space notification, so my first thought was that that was the problem. But I believe there always was enough space, more than 1 gb at least.

                Does Reactor do something more then only give a signal that disk space is low? Maybe save the cache or something in that line.

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

                  Reactor warns only when disk space starts to get low. There are attributes saved where you can write rules to respond, but Reactor doesn't take any action of its own.

                  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
                  • R Offline
                    R Offline
                    RHCPNG
                    wrote on last edited by
                    #9

                    The only lead I have is the disk space, I don't know what else it could be, although I cleared some space as soon as I got the notification.

                    I don't know what to do to further analyze this. I will monitor this and see if it happens again.

                    It would be helpful if Reactor could save the expressions to the json more often.

                    1 Reply Last reply
                    0
                    • K Offline
                      K Offline
                      kellyjelly32
                      wrote on last edited by
                      #10

                      Restarting reactor from reactor itself after changing any global expressions or making new global expressions is doing the trick for me currently.
                      But I am using MSR via the unofficial addon by @mrw298 .

                      1 Reply Last reply
                      0
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes

                      Recent Topics

                      • Set reaction triggering wrong z-wave device
                        T
                        tamorgen
                        0
                        13
                        60
                      • Can you run MSR on Home Assistant OS ?
                        CatmanV2C
                        CatmanV2
                        0
                        12
                        129
                      • RPi Alternative: Orange Pi 4 LTS (3GB RAM/16GB eMMC)
                        toggledbitsT
                        toggledbits
                        0
                        2
                        1.7k
                      • RPi Alternative: Orange Pi Zero 2 (1GB)
                        toggledbitsT
                        toggledbits
                        2
                        3
                        3.5k
                      • RPi Alternative: Libre Computer AML-S905X-CC "Le Potato" (2GB RAM)
                        toggledbitsT
                        toggledbits
                        5
                        6
                        3.1k
                      • HA and AI
                        therealdbT
                        therealdb
                        0
                        4
                        142
                      • How to upgrade from an old version of MSR?
                        CatmanV2C
                        CatmanV2
                        0
                        26
                        406
                      • This trigger no longer working - complaining about the operator needing changing
                        toggledbitsT
                        toggledbits
                        0
                        18
                        161
                      • Self test
                        CatmanV2C
                        CatmanV2
                        0
                        3
                        113
                      • Access control - allowing anonymous user to dashboard
                        toggledbitsT
                        toggledbits
                        0
                        2
                        125
                      • VEC Virtual Switch Auto Off
                        S
                        SweetGenius
                        1
                        1
                        91
                      • Upcoming Storage Change -- Got Back-ups?
                        toggledbitsT
                        toggledbits
                        3
                        1
                        83
                      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