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
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor
System Configuration Check - time is offset
F
Hi! I get this message when I'm on the status tab: System Configuration Check The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds. I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6. HA versions are: Core 2025.3.4 Supervisor 2025.03.4 Operating System 15.1 I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version. Do anyone know what I can try? Thanks in advance! Let's Be Careful Out There (Hill Street reference...) /Fanan
Multi-System Reactor
Programmatically capture HTTP Request action status code or error
therealdbT
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB. While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed. So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response. While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits Thanks!
Multi-System Reactor
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N
Hi , I'm on -Reactor (Multi-hub) latest-25067-62e21a2d -Docker on Synology NAS -ZWaveJSUI 9.31.0.6c80945 Problem with ZwaveJSUI: When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white. I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui. I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb". After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color. This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite. x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33} The "cold white" and "warm white" settings interfer with the rgb color settings. Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white. So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set. x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33 Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this? x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33} Thanks in advance.
Multi-System Reactor
Problem with simultaneous notifications.
T
Topic thumbnail image
Multi-System Reactor
Problem after upgrading to 25067
R
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem? I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Multi-System Reactor
Global expressions not always evaluated
tunnusT
Topic thumbnail image
Multi-System Reactor
[Solved] Local expression evaluation
V
Topic thumbnail image
Multi-System Reactor

Expressions page showing old data

Scheduled Pinned Locked Moved Multi-System Reactor
10 Posts 3 Posters 570 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

                      • Wiring Samotech SM308-S into light fitting
                        akbooerA
                        akbooer
                        0
                        2
                        34
                      • Errors after updating to MQTTController build 25139
                        toggledbitsT
                        toggledbits
                        0
                        6
                        63
                      • 🎉 My very first MSR controller: OpenSprinkler
                        therealdbT
                        therealdb
                        5
                        13
                        629
                      • Set Reaction > Script Action
                        toggledbitsT
                        toggledbits
                        0
                        4
                        58
                      • Advice reqeusted to migrate MSR from Bare Metal to Container
                        T
                        tamorgen
                        0
                        5
                        91
                      • Reactor (Multi-System/Multi-Hub) Announcements
                        toggledbitsT
                        toggledbits
                        5
                        122
                        37.3k
                      • Z-Wave Future....
                        CatmanV2C
                        CatmanV2
                        0
                        5
                        173
                      • Can´t restart or upgrade/deploy MSR
                        toggledbitsT
                        toggledbits
                        0
                        4
                        130
                      • [Solved] Limit HA Entity in MSR
                        wmarcolinW
                        wmarcolin
                        0
                        7
                        257
                      • Disaster recovery and virtualisation
                        CatmanV2C
                        CatmanV2
                        0
                        5
                        693
                      • Remote access of Zwave stick from Z-wave server
                        CatmanV2C
                        CatmanV2
                        0
                        3
                        418
                      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