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
Reactor Version 25310 : Office Light control via rule in reactor no longer working since last update.
P
Hello, I currently have an office light (connected via a Leviton Zwave Dimmer switch) controlled from a Gen5 Aeotech Zwave switch installed on my Synology 720+ NAS. I run HA(2025.11.10) in a virtual machine from my NAS and Reactor on the container manager of the same NAS. Prior to updating to 25304 the rule I had set to turn the light on to a specific dimming value worked correctly. Now the rule appears to follow the decision tree, however the reaction does not trigger setting the dimming or turning on the office light? Strangely I can still turn the light on and off as well as dim it directly from HASS..? I have tried using the ''try this action'' button in the rules reaction setting and it will not control the light and does not throw an error flagÉ Please help, P.S Reactor has been rock steady for me over the last few years and I'm a big fan of this solution.
Multi-System Reactor
[Solved] alarm() in global expression throws error in log.
CrilleC
Topic thumbnail image
Multi-System Reactor
[Solved] Define function issue in latest-25304
CrilleC
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
No Upgrade Notification for Build 25308?
CatmanV2C
FWIW I'm no longer getting a notification from MSR that there's an update. Just thought I'd mention it C
Multi-System Reactor
Strange behavior in MSR latest-25304 with disabled groups in Reaction
therealdbT
Topic thumbnail image
Multi-System Reactor
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
The reaction stopped working (Google Nest max playing a video)
F
Topic thumbnail image
Multi-System Reactor
Handling Dead Entities and Renamed Entities
PablaP
Hello all.. been a minute! I recently rebuilt my Z wave network and migrated to a new z wave stick. In order to prevent any downtime I kept my original z wave network up and ran a docker version of Z Wave JS UI with my new controller. This way I could add device by device without having any devices down. I finally moved all the devices over to my new stick today. The final step was to migrate everything from my Docker instance of Z Wave JS UI to the HA add-on of Z Wave JS UI. However during this migration some of the names didn't populate correctly which I later managed to import back into Z Wave JS UI. The issue was in Reactor it is stuck on the default names and the entities are not updating. I removed the controller from Reactor, restarted, hard refreshed, and added the controller back however the new entity names have not updated. Also it seems like the old entities from my previous instance of Z Wave JS UI are lingering and not being marked as dead (I believe a certain amount of time needs to lapse before they're marked as dead in Reactor). My goal is to basically purge all the entities for the 'ZWaveJS' controller in Reactor so it can pull all the updated entity names and only the entities that exist in Z Wave JS UI. I cannot find a quick way to do this, I know entities can be deleted one by one, but with over 100 entities this would take long I am guessing that if I added the controller with a new name in in the Reactor config it would pull the updated entities and names but I think that would break my rules since the entity IDs would change (I made sure to name all the entities the exact same as they were previously to prevent this issue).
Multi-System Reactor
Strange behavior for MQTT templates using payload and attributes
therealdbT
Topic thumbnail image
Multi-System Reactor
[MSR] reactor-mqtt-contrib package for additional MQTT templates
therealdbT
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only). Anyway, here's my reactor-mqtt-contrib package: https://github.com/dbochicchio/reactor-mqtt-contrib Simply download yaml files (everything or just the ones you need) and you're good to go. I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them. The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression. Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests
Multi-System Reactor
HA 2025.9.4 Supported Yet?
CatmanV2C
Tangentially did I miss 2025.9.4 getting blessed in MSR? I've been holding off Cheers C
Multi-System Reactor
Rule Set UI bug - RESOLVED
3
Topic thumbnail image
Multi-System Reactor
[Reactor] Copy&Paste of Rules
therealdbT
I don't know if I'm the only one, but managing more than one Reactor installs, the need to have some sort of copy&paste for rules has grown on me. While I understand the technical challenges, I'm wondering if a "god mode" where I could copy the raw JSON rule and paste it into another rule could be an advanced, flag only feature that could benefit power users. I know I can copy the JSON file and proceed, but I must stop Reactor and when doing maintenance, it's more clicks to do. Just an idea
Multi-System Reactor
[Reactor] Help with scene controller cycling logic
therealdbT
I’ve added a couple of Shelly Wave i4 as scene controllers and I’m planning to add more, since I can just use standard buttons instead of battery-powered scene controllers, which also looks better aesthetically. That said, I’m struggling to figure out how to write a simple rule that cycles between states every time I press a button. Example: Light 1 ON → OFF, then Light 2 ON → OFF. The part I can’t get right is handling the case where Light 1 or Light 2 might already be ON independently of the rule. Maybe it’s just too much sun and relaxation clouding my brain, but any hint would be appreciated.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor
Expose MSR entities
CatmanV2C
Probably a really dumb question. Currently I am using the owntracks_sensor for tracking phones being in region in MSR and it works great. Digging around with Home Assistant and toying with some dashboards, is there any way of exposing that sensor to HA trivially? I could set MSR to trip a virtual switch in OpenLuup which can then be exposed to HA (with all my other Vera devices) but that feels a bit in-elegant if I can do it directly. Any thoughts? Apologies if the ask is not clear/ TIA C
Multi-System Reactor
Comment in Globa Expressions
Tom_DT
I have several Global Expressions that are set by a rule so the definition area is blank. I'd like to add a comment in this area that explains what is setting the value. Commenting in this area breaks the remote setting. Any way to document what is setting the GE?
Multi-System Reactor
Unofficial thread for compatibility
tunnusT
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well. As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API. Updates: (the latest versions first in the list) OK: build "latest-25264-2fbe9217" with Hubitat C-8 platform v. 2.4.3.123
Multi-System Reactor
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
Multi-System Reactor

Expressions page showing old data

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

                      • Reactor Version 25310 : Office Light control via rule in reactor no longer working since last update.
                        G
                        gwp1
                        0
                        15
                        53
                      • [Solved] alarm() in global expression throws error in log.
                        toggledbitsT
                        toggledbits
                        0
                        26
                        118
                      • [Solved] Define function issue in latest-25304
                        CrilleC
                        Crille
                        0
                        12
                        189
                      • Reactor (Multi-System/Multi-Hub) Announcements
                        toggledbitsT
                        toggledbits
                        5
                        126
                        71.4k
                      • Shelly Wall Display XL
                        therealdbT
                        therealdb
                        2
                        8
                        517
                      • No Upgrade Notification for Build 25308?
                        toggledbitsT
                        toggledbits
                        0
                        2
                        32
                      • Strange behavior in MSR latest-25304 with disabled groups in Reaction
                        toggledbitsT
                        toggledbits
                        0
                        2
                        55
                      • Do you Matter?
                        akbooerA
                        akbooer
                        0
                        5
                        332
                      • [Reactor] Variables not updating correctly in latest-25201-2aa18550
                        toggledbitsT
                        toggledbits
                        0
                        95
                        9.0k
                      • The reaction stopped working (Google Nest max playing a video)
                        toggledbitsT
                        toggledbits
                        0
                        9
                        694
                      • Caution: zwave-js-ui docker 11.4.0 is broken
                        toggledbitsT
                        toggledbits
                        0
                        2
                        168
                      • Handling Dead Entities and Renamed Entities
                        PablaP
                        Pabla
                        0
                        5
                        297
                      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