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
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
[Solved] Error: Command timeout
G
at _ClientAPI._commandTimeout (http://192.168.1.100:8111/client/ClientAPI.js:807:179 Seeing this randomly when returning to open browser tab after being away awhile. Once, maybe twice a day. "What did you do to trigger it?" Literally nothing, just walked away and returned and there it was. Actions taken in reasonably close proximity to this particular instance of it popping up: I'd restarted the MSR container in Portainer. I'll try to grab some logs here shortly.
Multi-System Reactor
Issue with MSR UI becoming unresponsive
S
I'm having an issue with MSR's UI being very unresponsive. It started happening a couple days ago and I didn't make any changes that would have caused this except adding some meross lan devices in HA. When I go into an entity action and use the search functionality, it usually will start filtering and then get to a place after a few letters are entered where it will take 30 seconds or more (sometimes minutes) for the UI to show what I am typing. During this time MSR ui is completely unresponsive. I've tried multiple browsers and multiple computers. HA and MSR are both deployed in docker. I have run HTOP on the host and when the problem happens there are no CPU/Memory spikes at all. From a functionality standpoint MSR is working perfectly. This seems to be an UI issue only. Do i need to ditch Docker and run MSR on a Proxmox VM? I have both stand alone Docker and Proxmox environments. I dont mind doing that I just want to be able to use the UI again... Installation method Home Assistant Container Core 2025.7.3 Frontend 20250702.3 nothing crazy in the logs except some openweather map stuff that doesn't make any sense as it is working fine in MSR Any help would be greatly appreciated Reactor latest-25328-b2ed1365 app 25328 configuration from /var/reactor/config NODE_PATH /opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.843Z <app:null> Reactor build latest-25328-b2ed1365 starting on v24.11.1 /usr/local/bin/node [latest-25328]2025-11-30T20:01:53.844Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #161-Ubuntu SMP Tue Jul 22 14:25:40 UTC 2025; locale (undefined) [latest-25328]2025-11-30T20:01:53.844Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-25328]2025-11-30T20:01:53.844Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.865Z <app:null> Resolved timezone=America/New_York, environment TZ=America/New_York; offset minutes from UTC=-300 [latest-25328]2025-11-30T20:01:53.867Z <default:null> Module i18n v25141 [latest-25328]2025-11-30T20:01:53.867Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8 [latest-25328]2025-11-30T20:01:53.879Z <app:null> Loaded locale en-US for en-US [latest-25328]2025-11-30T20:01:53.879Z <app:null> Local date/time using configured timezone and locale formatting is "11/30/2025, 3:01:53 PM" [latest-25328]2025-11-30T20:01:53.889Z <Structure:null> Module Structure v25326 [latest-25328]2025-11-30T20:01:53.890Z <Capabilities:null> Module Capabilities v24312 [latest-25328]2025-11-30T20:01:53.904Z <Plugin:null> Module Plugin v25141 [latest-25328]2025-11-30T20:01:53.923Z <Timer:null> Module Timer v25279 [latest-25328]2025-11-30T20:01:53.924Z <TimerBroker:null> Module TimerBroker v25314 [latest-25328]2025-11-30T20:01:53.927Z <Entity:null> Module Entity v25251 [latest-25328]2025-11-30T20:01:53.929Z <Controller:null> Module Controller v25253 [latest-25328]2025-11-30T20:01:53.930Z <AlertManager:null> Module AlertManager v25318 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Ruleset v25283 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Rulesets v25141 [latest-25328]2025-11-30T20:01:53.942Z <GlobalExpression:null> Module GlobalExpression v25258 [latest-25328]2025-11-30T20:01:53.953Z <Predicate:null> Module Predicate v25328 [latest-25328]2025-11-30T20:01:53.956Z <Rule:null> Module Rule v25323 [latest-25328]2025-11-30T20:01:53.958Z <GlobalReaction:null> Module GlobalReaction v25292 [latest-25328]2025-11-30T20:01:53.959Z <Engine:null> Module Engine v25325 [latest-25328]2025-11-30T20:01:53.964Z <httpapi:null> Module httpapi v25328 [latest-25328]2025-11-30T20:01:53.972Z <wsapi:null> Module wsapi v25328 [latest-25328]2025-11-30T20:01:53.994Z <TaskQueue:null> Module TaskQueue 24138 [latest-25328]2025-11-30T20:01:53.994Z <VeraController:null> Module VeraController v25141 [latest-25328]2025-11-30T20:01:54.179Z <HassController:null> Module HassController v25325 [latest-25328]2025-11-30T20:02:13.797Z <OWMWeatherController:null> Module OWMWeatherController v25268 [latest-25328]2025-11-30T20:02:13.800Z <SystemController:null> Module SystemController v25323 [latest-25328]2025-11-30T20:02:13.807Z <MQTTController:null> Module MQTTController v22092 [latest-25328]2025-11-30T20:02:20.630Z <OWMWeatherController:CRIT> FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxx&lon=-xxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxxxxxxxxx&units=standard&_r=1xxxxxxxxxxxxxxfailed, reason: [-] FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxxx&lon=-xxxxxxxxxxxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxx&units=standard&_r=xxxxxxxxxxxxxxxfailed, reason: at ClientRequest.<anonymous> (/opt/reactor/node_modules/node-fetch/lib/index.js:1501:11) at ClientRequest.emit (node:events:508:28) at ClientRequest.emit (node:domain:489:12) at emitErrorEvent (node:_http_client:108:11) at TLSSocket.socketErrorListener (node:_http_client:575:5) at TLSSocket.emit (node:events:508:28) at TLSSocket.emit (node:domain:489:12) at emitErrorNT (node:internal/streams/destroy:170:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at processTicksAndRejections (node:internal/process/task_queues:89:21
Multi-System Reactor
Date/time condition
tunnusT
Topic thumbnail image
Multi-System Reactor
Device log?
G
@toggledbits is there a log that will show me what rule is turning on a specific device? I've got a switch that has been kicking on at 2200 ET for several nights now and the reactor.log doesn't have a thing in it that I can see on a device level (it being more rules-based).
Multi-System Reactor
Midnight crossing not working in date/time condition (build 25325)
tunnusT
Topic thumbnail image
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
[Solved] Local expression in Rule does not evaluate as they used to do
CrilleC
Topic thumbnail image
Multi-System Reactor
Home Assistant 2025.11.2 and latest-25315
CrilleC
Topic thumbnail image
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

                      • Copying a global reaction
                        toggledbitsT
                        toggledbits
                        0
                        3
                        70
                      • [HowTo] Using HABridge with Reactor
                        CatmanV2C
                        CatmanV2
                        0
                        9
                        368
                      • [Reactor] Bug when sending MQTT boolean payloads
                        toggledbitsT
                        toggledbits
                        0
                        4
                        121
                      • Genuinely impressed with Zigbee and HA / Reactor
                        therealdbT
                        therealdb
                        1
                        8
                        277
                      • Difficulty defining repeating annual period
                        G
                        gwp1
                        0
                        5
                        76
                      • Need help with sequence
                        therealdbT
                        therealdb
                        0
                        3
                        47
                      • Possible feature request?
                        therealdbT
                        therealdb
                        0
                        5
                        159
                      • Logic Assistance: Exterior Lights on when Illuminance Below Threshold
                        CatmanV2C
                        CatmanV2
                        0
                        11
                        325
                      • Time series documentation
                        tunnusT
                        tunnus
                        0
                        11
                        384
                      • MQTT templates for ZIgbee scene controller, or a better way?
                        CatmanV2C
                        CatmanV2
                        0
                        3
                        154
                      • Reset a delay
                        CatmanV2C
                        CatmanV2
                        0
                        8
                        213
                      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