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. Help resolve change in behaviour post update
Help resolve change in behaviour post update
CatmanV2C
Topic thumbnail image
Multi-System Reactor
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

Help resolve change in behaviour post update

Scheduled Pinned Locked Moved Multi-System Reactor
7 Posts 2 Posters 31 Views 2 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.
  • CatmanV2C Offline
    CatmanV2C Offline
    CatmanV2
    wrote last edited by CatmanV2
    #1

    Current set up: Bare metal (virtualised) on Debian 10.2
    MSR 25310

    Updated over the weekend and two reactions that have worked for literally years have changed. I'm pretty sure it was due to the 'nuances' in previous versions of evaluating global variables, so just looking for some help to 'fix'?

    I have two reactions that are dependant in large part on the global variable GlobalAlarmTime This is set in the Alarm Clock plugin of Openluup.

    One reaction turns the heating on one hour before the alarm goes off. The other turns the outside lights on one hour before the alarm goes off.

    Typically I change GlobalAlarmTime depending on the day of the week and the plans of the day ahead.
    GlobalAlarmTime is a string, current value (string) "05:40:00"
    Local variable HeatTime is calculated:
    time(GlobalAlarmTime) - 3600000
    Currently that has a value of 1762749600000
    Which is (quite correctly) 04:40:00 GMT 10th November. It's this because I changed the value of GlobalAlarmTime checking stuff out this morning, and HeatTime was re-evaluated at 09:37:17

    Screenshot 2025-11-10 at 10.01.49.png

    The challenge that I'm facing is that prior to the upgrade, HeatTime would be re-evaluated every 15 minutes (triggered by the 'Interval' function and come midnight (or at worst 00:15:00) HeatTime would re-evaluate to time(GlobalAlarmTime) - 3600000 today (if you get my point)

    That update to 'today' no longer happens. So the heating never comes on.

    [latest-25310]2025-11-10T00:00:00.025Z <Rule:INFO> Holiday Shutdown (rule-l8ys5tzy in Heating Control) starting rule state evaluation; because timer-trigger Timer#rule-l8ys5tzy
[latest-25310]2025-11-10T00:00:00.031Z <Rule:INFO> Holiday Heating (rule-ltsdvzi8 in Heating Control) starting rule state evaluation; because timer-trigger Timer#rule-ltsdvzi8
[latest-25310]2025-11-10T00:00:00.051Z <Rule:INFO> Holiday Lights (rule-ltse0zb4 in Heating Control) starting rule state evaluation; because timer-trigger Timer#rule-ltse0zb4
[latest-25310]2025-11-10T00:00:00.058Z <Rule:INFO> Set Greeting to Evening (rule-lioalha1 in Test Bed) starting rule state evaluation; because timer-trigger Timer#rule-lioalha1
[latest-25310]2025-11-10T00:00:00.068Z <Rule:INFO> Set Greeting to Evening (rule-lioalha1 in Test Bed) evaluated; rule state transition from SET to 'RESET'
[latest-25310]2025-11-10T00:00:00.084Z <Rule:INFO> Garden lights on when the doors are open (rule-lb2h69nb in Outside Lights) starting rule state evaluation; because timer-trigger Timer#rule-lb2h69nb
[latest-25310]2025-11-10T00:00:00.086Z <Rule:INFO> Set Greeting to Afternoon (rule-lioanahk in Test Bed) starting rule state evaluation; because timer-trigger Timer#rule-lioanahk
[latest-25310]2025-11-10T00:00:00.095Z <Rule:INFO> Evening Lights are On (rule-l5senfyv in Outside Lights) starting rule state evaluation; because timer-trigger Timer#rule-l5senfyv
[latest-25310]2025-11-10T00:00:00.096Z <Rule:INFO> Morning Lights are on (rule-l6gxvycu in Outside Lights) starting rule state evaluation; because timer-trigger Timer#rule-l6gxvycu
[latest-25310]2025-11-10T00:00:00.102Z <Rule:INFO> Rule#rule-l6gxvycu local LightTime is a dependency of another variable
[latest-25310]2025-11-10T00:00:00.102Z <Rule:INFO> Rule#rule-l6gxvycu local LightTime has object dependency
[latest-25310]2025-11-10T00:00:00.102Z <Rule:INFO> Rule#rule-l6gxvycu local LightOn is a dependency of another variable
[latest-25310]2025-11-10T00:00:00.103Z <Rule:INFO> Morning Lights are on (rule-l6gxvycu in Outside Lights) evaluated; rule state transition from RESET to 'SET'
[latest-25310]2025-11-10T00:00:00.139Z <Engine:INFO> Enqueueing "Morning Lights are on<SET>" (rule-l6gxvycu:S)
[latest-25310]2025-11-10T00:00:00.140Z <Engine:NOTICE> Starting reaction Set Greeting to Morning<SET> (rule-lioajm6q:S)
[latest-25310]2025-11-10T00:00:00.147Z <Engine:INFO> Set Greeting to Morning<SET> all actions completed.
[latest-25310]2025-11-10T00:00:00.162Z <Engine:NOTICE> Starting reaction Morning Lights are on<SET> (rule-l6gxvycu:S)
[latest-25310]2025-11-10T00:00:00.163Z <VeraController:INFO> VeraController#vera perform action power_switch.on on Switch#vera>device_20170 with {  }
[latest-25310]2025-11-10T00:00:00.170Z <VeraController:INFO> VeraController#vera perform action power_switch.set on Switch#vera>device_20170 with { "state": true }
[latest-25310]2025-11-10T00:00:00.173Z <Rule:INFO> Morning Heating (rule-l60fkpo3 in Heating Control) starting rule state evaluation; because timer-trigger Timer#rule-l60fkpo3
[latest-25310]2025-11-10T00:00:00.178Z <Rule:INFO> Rule#rule-l60fkpo3 local AlarmTime has object dependency
[latest-25310]2025-11-10T00:00:00.179Z <Rule:INFO> Rule#rule-l60fkpo3 local HeatTime is a dependency of another variable
[latest-25310]2025-11-10T00:00:00.179Z <Rule:INFO> Rule#rule-l60fkpo3 local HeatTime has object dependency
[latest-25310]2025-11-10T00:00:00.179Z <Rule:INFO> Rule#rule-l60fkpo3 local HeatOn is a dependency of another variable
[latest-25310]2025-11-10T00:00:00.180Z <Rule:INFO> Rule#rule-l60fkpo3 local HeatOff is a dependency of another variable
[latest-25310]2025-11-10T00:00:00.185Z <Rule:INFO> Morning Lights are on (rule-l6gxvycu in Outside Lights) starting rule state evaluation; because timer-trigger Timer#rule-l6gxvycu
[latest-25310]2025-11-10T00:00:00.192Z <Rule:INFO> Rule#rule-l6gxvycu local LightTime is a dependency of another variable
[latest-25310]2025-11-10T00:00:00.193Z <Rule:INFO> Rule#rule-l6gxvycu local LightTime has object dependency
[latest-25310]2025-11-10T00:00:00.193Z <Rule:INFO> Rule#rule-l6gxvycu local LightOn is a dependency of another variable
[latest-25310]2025-11-10T00:00:00.195Z <Rule:INFO> Morning Heating (rule-l60fkpo3 in Heating Control) starting rule state evaluation; because timer-trigger Timer#rule-l60fkpo3
[latest-25310]2025-11-10T00:00:00.196Z <Rule:INFO> Rule#rule-l60fkpo3 local AlarmTime has object dependency
[latest-25310]2025-11-10T00:00:00.196Z <Rule:INFO> Rule#rule-l60fkpo3 local HeatTime is a dependency of another variable
[latest-25310]2025-11-10T00:00:00.196Z <Rule:INFO> Rule#rule-l60fkpo3 local HeatTime has object dependency
[latest-25310]2025-11-10T00:00:00.196Z <Rule:INFO> Rule#rule-l60fkpo3 local HeatOn is a dependency of another variable
[latest-25310]2025-11-10T00:00:00.196Z <Rule:INFO> Rule#rule-l60fkpo3 local HeatOff is a dependency of another variable
[latest-25310]2025-11-10T00:00:00.233Z <VeraController:NOTICE> VeraController#vera action power_switch.set({ "state": true }) on Switch#vera>device_20170 succeeded
[latest-25310]2025-11-10T00:00:00.234Z <Engine:INFO> Resuming reaction Morning Lights are on<SET> (rule-l6gxvycu:S) from step 1
[latest-25310]2025-11-10T00:00:00.234Z <VeraController:INFO> VeraController#vera perform action power_switch.on on Switch#vera>device_20090 with {  }
[latest-25310]2025-11-10T00:00:00.234Z <VeraController:INFO> VeraController#vera perform action power_switch.set on Switch#vera>device_20090 with { "state": true }
[latest-25310]2025-11-10T00:00:00.289Z <VeraController:NOTICE> VeraController#vera action power_switch.set({ "state": true }) on Switch#vera>device_20090 succeeded
[latest-25310]2025-11-10T00:00:00.289Z <Engine:INFO> Resuming reaction Morning Lights are on<SET> (rule-l6gxvycu:S) from step 2
[latest-25310]2025-11-10T00:00:00.290Z <Engine:INFO> Morning Lights are on<SET> all actions completed.
[latest-25310]2025-11-10T00:00:43.383Z <Engine:INFO> Engine#1 master timer tick, local time "10/11/2025 00:00:43" (TZ offset 0 mins from UTC)
[latest-25310]2025-11-10T00:00:43.452Z <Rule:INFO> Internet Check (rule-m6z41xhd in Office Environment) starting rule state evaluation; because entity-changed System#reactor_system>system
[latest-25310]2025-11-10T00:00:43.463Z <httpapi:INFO> HTTPAPI(#1) API request from ::ffff:192.168.70.249: GET /api/v1/netstatus
[latest-25310]2025-11-10T00:00:43.476Z <Rule:INFO> Internet Check (rule-m6z41xhd in Office Environment) starting rule state evaluation; because entity-changed System#reactor_system>system
[latest-25310]2025-11-10T00:00:43.488Z <Rule:INFO> Internet Check (rule-m6z41xhd in Office Environment) starting rule state evaluation; because entity-changed System#reactor_system>system
[latest-25310]2025-11-10T00:00:43.490Z <Rule:INFO> Internet Check (rule-m6z41xhd in Office Environment) starting rule state evaluation; because entity-changed System#reactor_system>system
[latest-25310]2025-11-10T00:00:43.510Z <Rule:INFO> Internet Check (rule-m6z41xhd in Office Environment) starting rule state evaluation; because entity-changed System#reactor_system>system
[latest-25310]2025-11-10T00:00:43.516Z <HassController:NOTICE> HassController#hass websocket closing, 1006

    I'm going to guess I need to use the new alarm function.

    I'm further guessing that I'd set up a new global variable to replace HeatTime and have something like
    GlobalHeatTime = alarm ( 900) , time(GlobalAlarmTime) - 3600000 ?

    Am I on the right lines?

    TIA

    C

    The Ex-Vera abuser know as CatmanV2.....

    toggledbitsT 1 Reply Last reply
    0
    • CatmanV2C CatmanV2

      Current set up: Bare metal (virtualised) on Debian 10.2
      MSR 25310

      Updated over the weekend and two reactions that have worked for literally years have changed. I'm pretty sure it was due to the 'nuances' in previous versions of evaluating global variables, so just looking for some help to 'fix'?

      I have two reactions that are dependant in large part on the global variable GlobalAlarmTime This is set in the Alarm Clock plugin of Openluup.

      One reaction turns the heating on one hour before the alarm goes off. The other turns the outside lights on one hour before the alarm goes off.

      Typically I change GlobalAlarmTime depending on the day of the week and the plans of the day ahead.
      GlobalAlarmTime is a string, current value (string) "05:40:00"
      Local variable HeatTime is calculated:
      time(GlobalAlarmTime) - 3600000
      Currently that has a value of 1762749600000
      Which is (quite correctly) 04:40:00 GMT 10th November. It's this because I changed the value of GlobalAlarmTime checking stuff out this morning, and HeatTime was re-evaluated at 09:37:17

      Screenshot 2025-11-10 at 10.01.49.png

      The challenge that I'm facing is that prior to the upgrade, HeatTime would be re-evaluated every 15 minutes (triggered by the 'Interval' function and come midnight (or at worst 00:15:00) HeatTime would re-evaluate to time(GlobalAlarmTime) - 3600000 today (if you get my point)

      That update to 'today' no longer happens. So the heating never comes on.

      [latest-25310]2025-11-10T00:00:00.025Z <Rule:INFO> Holiday Shutdown (rule-l8ys5tzy in Heating Control) starting rule state evaluation; because timer-trigger Timer#rule-l8ys5tzy
[latest-25310]2025-11-10T00:00:00.031Z <Rule:INFO> Holiday Heating (rule-ltsdvzi8 in Heating Control) starting rule state evaluation; because timer-trigger Timer#rule-ltsdvzi8
[latest-25310]2025-11-10T00:00:00.051Z <Rule:INFO> Holiday Lights (rule-ltse0zb4 in Heating Control) starting rule state evaluation; because timer-trigger Timer#rule-ltse0zb4
[latest-25310]2025-11-10T00:00:00.058Z <Rule:INFO> Set Greeting to Evening (rule-lioalha1 in Test Bed) starting rule state evaluation; because timer-trigger Timer#rule-lioalha1
[latest-25310]2025-11-10T00:00:00.068Z <Rule:INFO> Set Greeting to Evening (rule-lioalha1 in Test Bed) evaluated; rule state transition from SET to 'RESET'
[latest-25310]2025-11-10T00:00:00.084Z <Rule:INFO> Garden lights on when the doors are open (rule-lb2h69nb in Outside Lights) starting rule state evaluation; because timer-trigger Timer#rule-lb2h69nb
[latest-25310]2025-11-10T00:00:00.086Z <Rule:INFO> Set Greeting to Afternoon (rule-lioanahk in Test Bed) starting rule state evaluation; because timer-trigger Timer#rule-lioanahk
[latest-25310]2025-11-10T00:00:00.095Z <Rule:INFO> Evening Lights are On (rule-l5senfyv in Outside Lights) starting rule state evaluation; because timer-trigger Timer#rule-l5senfyv
[latest-25310]2025-11-10T00:00:00.096Z <Rule:INFO> Morning Lights are on (rule-l6gxvycu in Outside Lights) starting rule state evaluation; because timer-trigger Timer#rule-l6gxvycu
[latest-25310]2025-11-10T00:00:00.102Z <Rule:INFO> Rule#rule-l6gxvycu local LightTime is a dependency of another variable
[latest-25310]2025-11-10T00:00:00.102Z <Rule:INFO> Rule#rule-l6gxvycu local LightTime has object dependency
[latest-25310]2025-11-10T00:00:00.102Z <Rule:INFO> Rule#rule-l6gxvycu local LightOn is a dependency of another variable
[latest-25310]2025-11-10T00:00:00.103Z <Rule:INFO> Morning Lights are on (rule-l6gxvycu in Outside Lights) evaluated; rule state transition from RESET to 'SET'
[latest-25310]2025-11-10T00:00:00.139Z <Engine:INFO> Enqueueing "Morning Lights are on<SET>" (rule-l6gxvycu:S)
[latest-25310]2025-11-10T00:00:00.140Z <Engine:NOTICE> Starting reaction Set Greeting to Morning<SET> (rule-lioajm6q:S)
[latest-25310]2025-11-10T00:00:00.147Z <Engine:INFO> Set Greeting to Morning<SET> all actions completed.
[latest-25310]2025-11-10T00:00:00.162Z <Engine:NOTICE> Starting reaction Morning Lights are on<SET> (rule-l6gxvycu:S)
[latest-25310]2025-11-10T00:00:00.163Z <VeraController:INFO> VeraController#vera perform action power_switch.on on Switch#vera>device_20170 with {  }
[latest-25310]2025-11-10T00:00:00.170Z <VeraController:INFO> VeraController#vera perform action power_switch.set on Switch#vera>device_20170 with { "state": true }
[latest-25310]2025-11-10T00:00:00.173Z <Rule:INFO> Morning Heating (rule-l60fkpo3 in Heating Control) starting rule state evaluation; because timer-trigger Timer#rule-l60fkpo3
[latest-25310]2025-11-10T00:00:00.178Z <Rule:INFO> Rule#rule-l60fkpo3 local AlarmTime has object dependency
[latest-25310]2025-11-10T00:00:00.179Z <Rule:INFO> Rule#rule-l60fkpo3 local HeatTime is a dependency of another variable
[latest-25310]2025-11-10T00:00:00.179Z <Rule:INFO> Rule#rule-l60fkpo3 local HeatTime has object dependency
[latest-25310]2025-11-10T00:00:00.179Z <Rule:INFO> Rule#rule-l60fkpo3 local HeatOn is a dependency of another variable
[latest-25310]2025-11-10T00:00:00.180Z <Rule:INFO> Rule#rule-l60fkpo3 local HeatOff is a dependency of another variable
[latest-25310]2025-11-10T00:00:00.185Z <Rule:INFO> Morning Lights are on (rule-l6gxvycu in Outside Lights) starting rule state evaluation; because timer-trigger Timer#rule-l6gxvycu
[latest-25310]2025-11-10T00:00:00.192Z <Rule:INFO> Rule#rule-l6gxvycu local LightTime is a dependency of another variable
[latest-25310]2025-11-10T00:00:00.193Z <Rule:INFO> Rule#rule-l6gxvycu local LightTime has object dependency
[latest-25310]2025-11-10T00:00:00.193Z <Rule:INFO> Rule#rule-l6gxvycu local LightOn is a dependency of another variable
[latest-25310]2025-11-10T00:00:00.195Z <Rule:INFO> Morning Heating (rule-l60fkpo3 in Heating Control) starting rule state evaluation; because timer-trigger Timer#rule-l60fkpo3
[latest-25310]2025-11-10T00:00:00.196Z <Rule:INFO> Rule#rule-l60fkpo3 local AlarmTime has object dependency
[latest-25310]2025-11-10T00:00:00.196Z <Rule:INFO> Rule#rule-l60fkpo3 local HeatTime is a dependency of another variable
[latest-25310]2025-11-10T00:00:00.196Z <Rule:INFO> Rule#rule-l60fkpo3 local HeatTime has object dependency
[latest-25310]2025-11-10T00:00:00.196Z <Rule:INFO> Rule#rule-l60fkpo3 local HeatOn is a dependency of another variable
[latest-25310]2025-11-10T00:00:00.196Z <Rule:INFO> Rule#rule-l60fkpo3 local HeatOff is a dependency of another variable
[latest-25310]2025-11-10T00:00:00.233Z <VeraController:NOTICE> VeraController#vera action power_switch.set({ "state": true }) on Switch#vera>device_20170 succeeded
[latest-25310]2025-11-10T00:00:00.234Z <Engine:INFO> Resuming reaction Morning Lights are on<SET> (rule-l6gxvycu:S) from step 1
[latest-25310]2025-11-10T00:00:00.234Z <VeraController:INFO> VeraController#vera perform action power_switch.on on Switch#vera>device_20090 with {  }
[latest-25310]2025-11-10T00:00:00.234Z <VeraController:INFO> VeraController#vera perform action power_switch.set on Switch#vera>device_20090 with { "state": true }
[latest-25310]2025-11-10T00:00:00.289Z <VeraController:NOTICE> VeraController#vera action power_switch.set({ "state": true }) on Switch#vera>device_20090 succeeded
[latest-25310]2025-11-10T00:00:00.289Z <Engine:INFO> Resuming reaction Morning Lights are on<SET> (rule-l6gxvycu:S) from step 2
[latest-25310]2025-11-10T00:00:00.290Z <Engine:INFO> Morning Lights are on<SET> all actions completed.
[latest-25310]2025-11-10T00:00:43.383Z <Engine:INFO> Engine#1 master timer tick, local time "10/11/2025 00:00:43" (TZ offset 0 mins from UTC)
[latest-25310]2025-11-10T00:00:43.452Z <Rule:INFO> Internet Check (rule-m6z41xhd in Office Environment) starting rule state evaluation; because entity-changed System#reactor_system>system
[latest-25310]2025-11-10T00:00:43.463Z <httpapi:INFO> HTTPAPI(#1) API request from ::ffff:192.168.70.249: GET /api/v1/netstatus
[latest-25310]2025-11-10T00:00:43.476Z <Rule:INFO> Internet Check (rule-m6z41xhd in Office Environment) starting rule state evaluation; because entity-changed System#reactor_system>system
[latest-25310]2025-11-10T00:00:43.488Z <Rule:INFO> Internet Check (rule-m6z41xhd in Office Environment) starting rule state evaluation; because entity-changed System#reactor_system>system
[latest-25310]2025-11-10T00:00:43.490Z <Rule:INFO> Internet Check (rule-m6z41xhd in Office Environment) starting rule state evaluation; because entity-changed System#reactor_system>system
[latest-25310]2025-11-10T00:00:43.510Z <Rule:INFO> Internet Check (rule-m6z41xhd in Office Environment) starting rule state evaluation; because entity-changed System#reactor_system>system
[latest-25310]2025-11-10T00:00:43.516Z <HassController:NOTICE> HassController#hass websocket closing, 1006

      I'm going to guess I need to use the new alarm function.

      I'm further guessing that I'd set up a new global variable to replace HeatTime and have something like
      GlobalHeatTime = alarm ( 900) , time(GlobalAlarmTime) - 3600000 ?

      Am I on the right lines?

      TIA

      C

      toggledbitsT Offline
      toggledbitsT Offline
      toggledbits
      wrote last edited by
      #2

      @CatmanV2 said in Help resolve change in behaviour post update:

      I'm further guessing that I'd set up a new global variable to replace HeatTime and have something like
      GlobalHeatTime = alarm ( 900) , time(GlobalAlarmTime) - 3600000

      You're on the right track. If I understand your description, something like this should work (all globals):

      gAlarmTime = getEntity( ... )

gHeatTime = time(gAlarmTime) - 3600000

gHeatOn = alarm(900), time() >= gHeatTime

      gAlarmTime will be updated any time the dependent entity changes. gHeatTime will change any time gAlarmTime changes (reference to another variable creates a dependency on that variable). gHeatOn will be updated by the periodic alarm() tripping.

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

      1 Reply Last reply
      1
      • CatmanV2C Offline
        CatmanV2C Offline
        CatmanV2
        wrote last edited by
        #3

        Super. I think I can understand that. Will I see it updating in the logs?

        C

        The Ex-Vera abuser know as CatmanV2.....

        toggledbitsT 1 Reply Last reply
        0
        • CatmanV2C CatmanV2

          Super. I think I can understand that. Will I see it updating in the logs?

          C

          toggledbitsT Offline
          toggledbitsT Offline
          toggledbits
          wrote last edited by
          #4

          @CatmanV2 said in Help resolve change in behaviour post update:

          Will I see it updating in the logs?

          Yes, and on the Expressions page.

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

          CatmanV2C 1 Reply Last reply
          0
          • toggledbitsT toggledbits

            @CatmanV2 said in Help resolve change in behaviour post update:

            Will I see it updating in the logs?

            Yes, and on the Expressions page.

            CatmanV2C Offline
            CatmanV2C Offline
            CatmanV2
            wrote last edited by
            #5

            @toggledbits Thanks so much

            I've now got this

            Screenshot 2025-11-10 at 13.23.36.png

            With GlobalHeatOn as one of my conditions in the reaction.

            My assumption is it will go false at, or immediately after midnight?

            I'm guessing I can lose the Interval statement as well?

            Screenshot 2025-11-10 at 13.26.55.png

            Cheers

            C

            The Ex-Vera abuser know as CatmanV2.....

            toggledbitsT 1 Reply Last reply
            0
            • CatmanV2C CatmanV2

              @toggledbits Thanks so much

              I've now got this

              Screenshot 2025-11-10 at 13.23.36.png

              With GlobalHeatOn as one of my conditions in the reaction.

              My assumption is it will go false at, or immediately after midnight?

              I'm guessing I can lose the Interval statement as well?

              Screenshot 2025-11-10 at 13.26.55.png

              Cheers

              C

              toggledbitsT Offline
              toggledbitsT Offline
              toggledbits
              wrote last edited by
              #6

              @CatmanV2 said in Help resolve change in behaviour post update:

              My assumption is it will go false at, or immediately after midnight?

              No. If your GlobalAlarmTime will always show time only (no date components), then you can safely add an alarm() call to GlobalHeatTime as well.

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

              CatmanV2C 1 Reply Last reply
              0
              • toggledbitsT toggledbits

                @CatmanV2 said in Help resolve change in behaviour post update:

                My assumption is it will go false at, or immediately after midnight?

                No. If your GlobalAlarmTime will always show time only (no date components), then you can safely add an alarm() call to GlobalHeatTime as well.

                CatmanV2C Offline
                CatmanV2C Offline
                CatmanV2
                wrote last edited by CatmanV2
                #7

                @toggledbits Ahh super

                GlobalAlarmTime is never date (or I guess we'd not have this issue!)

                Screenshot 2025-11-10 at 17.35.30.png

                I do appreciate you thinking down to my level 🙂

                C

                The Ex-Vera abuser know as CatmanV2.....

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

                Recent Topics

                • Help resolve change in behaviour post update
                  CatmanV2C
                  CatmanV2
                  0
                  7
                  31
                • Reactor Version 25310 : Office Light control via rule in reactor no longer working since last update.
                  toggledbitsT
                  toggledbits
                  0
                  16
                  136
                • Shelly Wall Display XL
                  akbooerA
                  akbooer
                  2
                  9
                  576
                • [Solved] alarm() in global expression throws error in log.
                  toggledbitsT
                  toggledbits
                  0
                  26
                  222
                • [Solved] Define function issue in latest-25304
                  CrilleC
                  Crille
                  0
                  12
                  240
                • Reactor (Multi-System/Multi-Hub) Announcements
                  toggledbitsT
                  toggledbits
                  5
                  126
                  71.7k
                • No Upgrade Notification for Build 25308?
                  toggledbitsT
                  toggledbits
                  0
                  2
                  53
                • Strange behavior in MSR latest-25304 with disabled groups in Reaction
                  toggledbitsT
                  toggledbits
                  0
                  2
                  74
                • Do you Matter?
                  akbooerA
                  akbooer
                  0
                  5
                  355
                • [Reactor] Variables not updating correctly in latest-25201-2aa18550
                  toggledbitsT
                  toggledbits
                  0
                  95
                  9.2k
                • The reaction stopped working (Google Nest max playing a video)
                  toggledbitsT
                  toggledbits
                  0
                  9
                  723
                • Caution: zwave-js-ui docker 11.4.0 is broken
                  toggledbitsT
                  toggledbits
                  0
                  2
                  175
                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