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. [SOLVED] All Modes not visible in MSR 21337 from Hubitat
Oddness in Copy/Move of Reactions
G
Topic thumbnail image
Multi-System Reactor
[Solved] function isRuleEnabled() issue
CrilleC
Topic thumbnail image
Multi-System Reactor
[Reactor] Problem with Global Reactions and groups
therealdbT
Topic thumbnail image
Multi-System Reactor
Possible feature request 2?
CatmanV2C
Just another thought. Adding devices from my Home Assistant / Zigbee2MQTT integration. Works perfectly but they always add as their IEEE address. Some of these devices have up to 10 entities associated, and the moment they are renamed to something sensible, each of those entities 'ceases to exist' in MSR. I like things tidy, and deleting each defunct entity needs 3 clicks. Any chance of a 'bulk delete' option? No biggy as I've pretty much finished my Z-wave migration and I don't expect to be adding more than 2 new Zigbee devices Cheers C
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Copying a global reaction
tunnusT
With build 25328, if you copy a global reaction, a new reaction does not appear in the UI unless you do a refresh. I recall this used to work without needing this page refresh? Anyway, only a minor nuisance.
Multi-System Reactor
[Reactor] Bug when sending MQTT boolean payloads
therealdbT
Topic thumbnail image
Multi-System Reactor
Difficulty defining repeating annual period
R
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Multi-System Reactor
Need help with sequence
T
Good evening all, For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time. Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed. Thanks.
Multi-System Reactor
Possible feature request?
CatmanV2C
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations. Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction? Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for. I guess it's something of an edge case so no huge issue. TIA! C
Multi-System Reactor
Logic Assistance: Exterior Lights on when Illuminance Below Threshold
PablaP
Topic thumbnail image
Multi-System Reactor
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
MQTT templates for ZIgbee scene controller, or a better way?
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reset a delay
CatmanV2C
I'm sure this has been asked, and answered, but damned if I can figure it out Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage. Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts. After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!) What I would like is for the 3 minute delay until the lights go off to start from the latest door open event. That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity. I've tried 'hacking' with a virtual switch, but can't seem to stop the delay. Any pointers? TIA C
Multi-System Reactor
Reactor Loading Screen Safari
S
Topic thumbnail image
Multi-System Reactor
Constraints states visually do not match actual
S
Topic thumbnail image
Multi-System Reactor
[MSR] Feature request: For Each action on arrays/groups
therealdbT
Topic thumbnail image
Multi-System Reactor
[Solved] Error: Command timeout
G
at _ClientAPI._commandTimeout (http://192.168.1.100:8111/client/ClientAPI.js:807:179 Seeing this randomly when returning to open browser tab after being away awhile. Once, maybe twice a day. "What did you do to trigger it?" Literally nothing, just walked away and returned and there it was. Actions taken in reasonably close proximity to this particular instance of it popping up: I'd restarted the MSR container in Portainer. I'll try to grab some logs here shortly.
Multi-System Reactor
Issue with MSR UI becoming unresponsive
S
I'm having an issue with MSR's UI being very unresponsive. It started happening a couple days ago and I didn't make any changes that would have caused this except adding some meross lan devices in HA. When I go into an entity action and use the search functionality, it usually will start filtering and then get to a place after a few letters are entered where it will take 30 seconds or more (sometimes minutes) for the UI to show what I am typing. During this time MSR ui is completely unresponsive. I've tried multiple browsers and multiple computers. HA and MSR are both deployed in docker. I have run HTOP on the host and when the problem happens there are no CPU/Memory spikes at all. From a functionality standpoint MSR is working perfectly. This seems to be an UI issue only. Do i need to ditch Docker and run MSR on a Proxmox VM? I have both stand alone Docker and Proxmox environments. I dont mind doing that I just want to be able to use the UI again... Installation method Home Assistant Container Core 2025.7.3 Frontend 20250702.3 nothing crazy in the logs except some openweather map stuff that doesn't make any sense as it is working fine in MSR Any help would be greatly appreciated Reactor latest-25328-b2ed1365 app 25328 configuration from /var/reactor/config NODE_PATH /opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.843Z <app:null> Reactor build latest-25328-b2ed1365 starting on v24.11.1 /usr/local/bin/node [latest-25328]2025-11-30T20:01:53.844Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #161-Ubuntu SMP Tue Jul 22 14:25:40 UTC 2025; locale (undefined) [latest-25328]2025-11-30T20:01:53.844Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-25328]2025-11-30T20:01:53.844Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.865Z <app:null> Resolved timezone=America/New_York, environment TZ=America/New_York; offset minutes from UTC=-300 [latest-25328]2025-11-30T20:01:53.867Z <default:null> Module i18n v25141 [latest-25328]2025-11-30T20:01:53.867Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8 [latest-25328]2025-11-30T20:01:53.879Z <app:null> Loaded locale en-US for en-US [latest-25328]2025-11-30T20:01:53.879Z <app:null> Local date/time using configured timezone and locale formatting is "11/30/2025, 3:01:53 PM" [latest-25328]2025-11-30T20:01:53.889Z <Structure:null> Module Structure v25326 [latest-25328]2025-11-30T20:01:53.890Z <Capabilities:null> Module Capabilities v24312 [latest-25328]2025-11-30T20:01:53.904Z <Plugin:null> Module Plugin v25141 [latest-25328]2025-11-30T20:01:53.923Z <Timer:null> Module Timer v25279 [latest-25328]2025-11-30T20:01:53.924Z <TimerBroker:null> Module TimerBroker v25314 [latest-25328]2025-11-30T20:01:53.927Z <Entity:null> Module Entity v25251 [latest-25328]2025-11-30T20:01:53.929Z <Controller:null> Module Controller v25253 [latest-25328]2025-11-30T20:01:53.930Z <AlertManager:null> Module AlertManager v25318 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Ruleset v25283 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Rulesets v25141 [latest-25328]2025-11-30T20:01:53.942Z <GlobalExpression:null> Module GlobalExpression v25258 [latest-25328]2025-11-30T20:01:53.953Z <Predicate:null> Module Predicate v25328 [latest-25328]2025-11-30T20:01:53.956Z <Rule:null> Module Rule v25323 [latest-25328]2025-11-30T20:01:53.958Z <GlobalReaction:null> Module GlobalReaction v25292 [latest-25328]2025-11-30T20:01:53.959Z <Engine:null> Module Engine v25325 [latest-25328]2025-11-30T20:01:53.964Z <httpapi:null> Module httpapi v25328 [latest-25328]2025-11-30T20:01:53.972Z <wsapi:null> Module wsapi v25328 [latest-25328]2025-11-30T20:01:53.994Z <TaskQueue:null> Module TaskQueue 24138 [latest-25328]2025-11-30T20:01:53.994Z <VeraController:null> Module VeraController v25141 [latest-25328]2025-11-30T20:01:54.179Z <HassController:null> Module HassController v25325 [latest-25328]2025-11-30T20:02:13.797Z <OWMWeatherController:null> Module OWMWeatherController v25268 [latest-25328]2025-11-30T20:02:13.800Z <SystemController:null> Module SystemController v25323 [latest-25328]2025-11-30T20:02:13.807Z <MQTTController:null> Module MQTTController v22092 [latest-25328]2025-11-30T20:02:20.630Z <OWMWeatherController:CRIT> FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxx&lon=-xxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxxxxxxxxx&units=standard&_r=1xxxxxxxxxxxxxxfailed, reason: [-] FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxxx&lon=-xxxxxxxxxxxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxx&units=standard&_r=xxxxxxxxxxxxxxxfailed, reason: at ClientRequest.<anonymous> (/opt/reactor/node_modules/node-fetch/lib/index.js:1501:11) at ClientRequest.emit (node:events:508:28) at ClientRequest.emit (node:domain:489:12) at emitErrorEvent (node:_http_client:108:11) at TLSSocket.socketErrorListener (node:_http_client:575:5) at TLSSocket.emit (node:events:508:28) at TLSSocket.emit (node:domain:489:12) at emitErrorNT (node:internal/streams/destroy:170:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at processTicksAndRejections (node:internal/process/task_queues:89:21
Multi-System Reactor
Date/time condition
tunnusT
Topic thumbnail image
Multi-System Reactor

[SOLVED] All Modes not visible in MSR 21337 from Hubitat

Scheduled Pinned Locked Moved Multi-System Reactor
22 Posts 2 Posters 2.6k 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.
  • G Offline
    G Offline
    gwp1
    wrote on last edited by gwp1
    #1

    I updated to latest-21337-b535732 last night before heading off to sleep. I have a ruleset that checks for phone charging, mode evening, and room-assistant home. The system then waits five minutes and flips to mode night and announces it has done so via Echo devices.

    At 05:30 ET each morning the system shifts to mode day.

    However...

    Last night MSR went thru the paces but mode evening never switched to mode night. Multiple attempts including reboots of MSR and Hubitat, no change.

    This morning, instead of mode day it went back to mode evening which isn't supposed to trigger until sunset. This is confirmed across MSR, H-A, and Hubitat.

    I'd missed the 21336 update and went from 21332 to 21337. I'll be log diving after coffee is ready.

    Updated title to reflect what the issue seems to actually be.

    *Hubitat C-7 2.4.3.177
    *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

    *HAOS
    Core 2026.1.1
    w/ HA Connect ZWA-2
    FW: v1.1
    SDK: v7.23.1

    *Prod MSR in docker/portainer
    MSR: latest-26011-c621bbc7
    MQTTController: 25139
    ZWave Controller: 25139

    G 1 Reply Last reply
    0
    • G gwp1

      I updated to latest-21337-b535732 last night before heading off to sleep. I have a ruleset that checks for phone charging, mode evening, and room-assistant home. The system then waits five minutes and flips to mode night and announces it has done so via Echo devices.

      At 05:30 ET each morning the system shifts to mode day.

      However...

      Last night MSR went thru the paces but mode evening never switched to mode night. Multiple attempts including reboots of MSR and Hubitat, no change.

      This morning, instead of mode day it went back to mode evening which isn't supposed to trigger until sunset. This is confirmed across MSR, H-A, and Hubitat.

      I'd missed the 21336 update and went from 21332 to 21337. I'll be log diving after coffee is ready.

      Updated title to reflect what the issue seems to actually be.

      G Offline
      G Offline
      gwp1
      wrote on last edited by gwp1
      #2

      @gwp1 This is interesting: can't have the house in mode evening so I hit the reset icon on the day mode ruleset Rule ID: rule-kmfo3pz8. It shows I took the action:

      6bcb2028-dc27-4c47-bb8f-b03eff942746-image.png

      ...but I don't see any reference to that action in the log nor did the mode change to day.

      This is the log since 0529 ET.

      [latest-21337]2021-12-04T15:05:29.018Z <Rule:NOTICE> Rule#rule-kmfo3pz8 resetting!
      [latest-21337]2021-12-04T15:05:29.020Z <Rule:NOTICE> Rule#rule-kmfo3pz8 stopping rule
      [latest-21337]2021-12-04T15:05:29.021Z <Rule:5:Rule.js:743> Rule#rule-kmfo3pz8 acquiring semaphore
      [latest-21337]2021-12-04T15:05:29.023Z <Rule:5:Rule.js:746> Rule#rule-kmfo3pz8 semaphore acquired; releasing timer
      [latest-21337]2021-12-04T15:05:29.024Z <Rule:5:Rule.js:746> Rule#rule-kmfo3pz8 semaphore acquired; unsubscribing from condition dependencies
      [latest-21337]2021-12-04T15:05:29.036Z <Rule:5:Rule.js:748> Rule#rule-kmfo3pz8 saving states
      [latest-21337]2021-12-04T15:05:29.041Z <Rule:5:Rule.js:752> Rule#rule-kmfo3pz8 stopped
      [latest-21337]2021-12-04T15:05:29.041Z <Rule:NOTICE> Rule Rule#rule-kmfo3pz8 stopped
      [latest-21337]2021-12-04T15:05:29.044Z <Rule:NOTICE> Rule#rule-kmfo3pz8 restarting after reset
      [latest-21337]2021-12-04T15:05:29.045Z <Rule:5:Rule.js:716> Rule#rule-kmfo3pz8 start(), awaiting semaphore
      [latest-21337]2021-12-04T15:05:29.051Z <Rule:5:Rule.js:724> Rule#rule-kmfo3pz8 restored states: trig=(null), rule=(null)
      [latest-21337]2021-12-04T15:05:29.052Z <Rule:5:Rule.js:724> Rule#rule-kmfo3pz8 subscribing to dependencies
      [latest-21337]2021-12-04T15:05:29.053Z <Rule:INFO> Rule#rule-kmfo3pz8 (Day mode:  05:30 ET) started
      [latest-21337]2021-12-04T15:05:29.054Z <Rule:5:Rule.js:728> Rule#rule-kmfo3pz8 start() dependencies resolved, performing initial evaluation
      [latest-21337]2021-12-04T15:05:29.055Z <Rule:5:Rule.js:1005> Rule#rule-kmfo3pz8 (Day mode:  05:30 ET) evaluate() acquiring mutex
      [latest-21337]2021-12-04T15:05:29.056Z <Rule:5:Rule.js:1009> Rule#rule-kmfo3pz8._evaluate() mutex acquired, evaluating
      [latest-21337]2021-12-04T15:05:29.057Z <Rule:5:Rule.js:1013> Rule#rule-kmfo3pz8 update rate is 0/min limit 60/min
      [latest-21337]2021-12-04T15:05:29.058Z <Rule:5:Rule.js:936> Rule#rule-kmfo3pz8 evaluateExpressions() with 0 expressions
      [latest-21337]2021-12-04T15:05:29.065Z <Rule:5:Rule.js:1689> cond cond6xza990 evaluation state (null)->false
      [latest-21337]2021-12-04T15:05:29.069Z <Rule:5:Rule.js:1689> cond condkmfo3pz8 evaluation state (null)->true
      [latest-21337]2021-12-04T15:05:29.074Z <Rule:5:Rule.js:1689> cond condeadfqgq evaluation state (null)->true
      [latest-21337]2021-12-04T15:05:29.075Z <Rule:5:Rule.js:1689> cond trig evaluation state (null)->false
      [latest-21337]2021-12-04T15:05:29.079Z <Rule:5:Rule.js:1033> Rule#rule-kmfo3pz8._evaluate() trigger state now false (was (null))
      [latest-21337]2021-12-04T15:05:29.080Z <Rule:5:Rule.js:1035> Rule#rule-kmfo3pz8._evaluate() constraints state true
      [latest-21337]2021-12-04T15:05:29.081Z <Rule:5:Rule.js:1041> Rule#rule-kmfo3pz8 trigger conditions not met
      [latest-21337]2021-12-04T15:05:29.081Z <Rule:5:Rule.js:1042> Rule#rule-kmfo3pz8 rule state changed, was (undefined) now false
      [latest-21337]2021-12-04T15:05:29.082Z <Rule:INFO> Day mode:  05:30 ET (Rule#rule-kmfo3pz8) RESET!
      [latest-21337]2021-12-04T15:05:29.083Z <Rule:5:Rule.js:1044> Rule#rule-kmfo3pz8 rule state now false, changed true
      [latest-21337]2021-12-04T15:05:38.996Z <Rule:5:Rule.js:793> Rule#rule-grpoix7c2a Office On/Off requesting eval; entity-changed from Entity#hubitat>51
      [latest-21337]2021-12-04T15:05:38.997Z <Rule:5:Rule.js:1005> Rule#rule-grpoix7c2a (Office On/Off) evaluate() acquiring mutex
      [latest-21337]2021-12-04T15:05:38.998Z <Rule:5:Rule.js:1009> Rule#rule-grpoix7c2a._evaluate() mutex acquired, evaluating
      [latest-21337]2021-12-04T15:05:38.999Z <Rule:5:Rule.js:1013> Rule#rule-grpoix7c2a update rate is 4/min limit 60/min
      [latest-21337]2021-12-04T15:05:39.000Z <Rule:5:Rule.js:936> Rule#rule-grpoix7c2a evaluateExpressions() with 0 expressions
      [latest-21337]2021-12-04T15:05:39.006Z <Rule:5:Rule.js:1033> Rule#rule-grpoix7c2a._evaluate() trigger state now false (was false)
      [latest-21337]2021-12-04T15:05:39.007Z <Rule:5:Rule.js:1035> Rule#rule-grpoix7c2a._evaluate() constraints state true
      [latest-21337]2021-12-04T15:05:39.008Z <Rule:5:Rule.js:1044> Rule#rule-grpoix7c2a rule state now false, changed no
      [latest-21337]2021-12-04T15:05:45.991Z <Rule:5:Rule.js:793> Rule#rule-grpoix7c2a Office On/Off requesting eval; entity-changed from Entity#hubitat>51
      [latest-21337]2021-12-04T15:05:45.995Z <Rule:5:Rule.js:1005> Rule#rule-grpoix7c2a (Office On/Off) evaluate() acquiring mutex
      [latest-21337]2021-12-04T15:05:45.998Z <Rule:5:Rule.js:1009> Rule#rule-grpoix7c2a._evaluate() mutex acquired, evaluating
      [latest-21337]2021-12-04T15:05:46.000Z <Rule:5:Rule.js:1013> Rule#rule-grpoix7c2a update rate is 4/min limit 60/min
      [latest-21337]2021-12-04T15:05:46.002Z <Rule:5:Rule.js:936> Rule#rule-grpoix7c2a evaluateExpressions() with 0 expressions
      [latest-21337]2021-12-04T15:05:46.005Z <Rule:5:Rule.js:1033> Rule#rule-grpoix7c2a._evaluate() trigger state now false (was false)
      [latest-21337]2021-12-04T15:05:46.007Z <Rule:5:Rule.js:1035> Rule#rule-grpoix7c2a._evaluate() constraints state true
      [latest-21337]2021-12-04T15:05:46.009Z <Rule:5:Rule.js:1044> Rule#rule-grpoix7c2a rule state now false, changed no
      [latest-21337]2021-12-04T15:06:02.533Z <Rule:5:Rule.js:793> Rule#rule-kphozuch Upstairs bulb requesting eval; entity-changed from Entity#hubitat>55
      [latest-21337]2021-12-04T15:06:02.534Z <Rule:5:Rule.js:793> Rule#rule-komaz8fr Upstairs motion requesting eval; entity-changed from Entity#hubitat>55
      [latest-21337]2021-12-04T15:06:02.535Z <Rule:5:Rule.js:1005> Rule#rule-kphozuch (Upstairs bulb) evaluate() acquiring mutex
      [latest-21337]2021-12-04T15:06:02.535Z <Rule:5:Rule.js:1005> Rule#rule-komaz8fr (Upstairs motion) evaluate() acquiring mutex
      [latest-21337]2021-12-04T15:06:02.536Z <Rule:5:Rule.js:1009> Rule#rule-kphozuch._evaluate() mutex acquired, evaluating
      [latest-21337]2021-12-04T15:06:02.537Z <Rule:5:Rule.js:1013> Rule#rule-kphozuch update rate is 0/min limit 60/min
      [latest-21337]2021-12-04T15:06:02.538Z <Rule:5:Rule.js:936> Rule#rule-kphozuch evaluateExpressions() with 0 expressions
      [latest-21337]2021-12-04T15:06:02.540Z <Rule:5:Rule.js:1033> Rule#rule-kphozuch._evaluate() trigger state now false (was false)
      [latest-21337]2021-12-04T15:06:02.541Z <Rule:5:Rule.js:1035> Rule#rule-kphozuch._evaluate() constraints state true
      [latest-21337]2021-12-04T15:06:02.541Z <Rule:5:Rule.js:1044> Rule#rule-kphozuch rule state now false, changed no
      [latest-21337]2021-12-04T15:06:02.545Z <Rule:5:Rule.js:1009> Rule#rule-komaz8fr._evaluate() mutex acquired, evaluating
      [latest-21337]2021-12-04T15:06:02.545Z <Rule:5:Rule.js:1013> Rule#rule-komaz8fr update rate is 0/min limit 60/min
      [latest-21337]2021-12-04T15:06:02.546Z <Rule:5:Rule.js:936> Rule#rule-komaz8fr evaluateExpressions() with 0 expressions
      [latest-21337]2021-12-04T15:06:02.548Z <Rule:5:Rule.js:1033> Rule#rule-komaz8fr._evaluate() trigger state now false (was false)
      [latest-21337]2021-12-04T15:06:02.549Z <Rule:5:Rule.js:1035> Rule#rule-komaz8fr._evaluate() constraints state true
      [latest-21337]2021-12-04T15:06:02.549Z <Rule:5:Rule.js:1044> Rule#rule-komaz8fr rule state now false, changed no
      [latest-21337]2021-12-04T15:06:03.376Z <Rule:5:Rule.js:793> Rule#rule-grpoix7c2a Office On/Off requesting eval; timer-trigger from Timer#rule-grpoix7c2a
      [latest-21337]2021-12-04T15:06:03.377Z <Rule:5:Rule.js:1005> Rule#rule-grpoix7c2a (Office On/Off) evaluate() acquiring mutex
      [latest-21337]2021-12-04T15:06:03.378Z <Rule:5:Rule.js:1009> Rule#rule-grpoix7c2a._evaluate() mutex acquired, evaluating
      [latest-21337]2021-12-04T15:06:03.379Z <Rule:5:Rule.js:1013> Rule#rule-grpoix7c2a update rate is 3/min limit 60/min
      [latest-21337]2021-12-04T15:06:03.380Z <Rule:5:Rule.js:936> Rule#rule-grpoix7c2a evaluateExpressions() with 0 expressions
      [latest-21337]2021-12-04T15:06:03.381Z <Rule:5:Rule.js:1033> Rule#rule-grpoix7c2a._evaluate() trigger state now false (was false)
      [latest-21337]2021-12-04T15:06:03.382Z <Rule:5:Rule.js:1035> Rule#rule-grpoix7c2a._evaluate() constraints state true
      [latest-21337]2021-12-04T15:06:03.383Z <Rule:5:Rule.js:1044> Rule#rule-grpoix7c2a rule state now false, changed no

      *Hubitat C-7 2.4.3.177
      *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

      *HAOS
      Core 2026.1.1
      w/ HA Connect ZWA-2
      FW: v1.1
      SDK: v7.23.1

      *Prod MSR in docker/portainer
      MSR: latest-26011-c621bbc7
      MQTTController: 25139
      ZWave Controller: 25139

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

        I just tested mode sensitivity, which I also had done before the build, and it's working as expected. So that part is fine. The log shows "Day mode" rule is going to Reset state, so unless your action is in the Reset reaction, I wouldn't expect it to log the change you seem to anticipate. You haven't shown the rules or reactions, so I have no way of judging what it will do or whether what I can see it doing is right. Show your work, please! Also check your host time zone settings. Logs are Zulu (UTC), not ET, and that would account for a five hour difference in host time vs log time, normally (standard time).

        http://your-reactor-ip:8111/diag/sun

        Also look at the rule detail panel any time you are troubleshooting logic. Your log snippets don't show any actions being run at all for rule-kmfo3pz8, just the rule eval/update to Reset state. Logging of actions in HubitatController is currently unconditional, so if any action was being sent, it would be in the logs (regardless of log level).

        G 1 Reply Last reply
        0
        • toggledbitsT toggledbits

          I just tested mode sensitivity, which I also had done before the build, and it's working as expected. So that part is fine. The log shows "Day mode" rule is going to Reset state, so unless your action is in the Reset reaction, I wouldn't expect it to log the change you seem to anticipate. You haven't shown the rules or reactions, so I have no way of judging what it will do or whether what I can see it doing is right. Show your work, please! Also check your host time zone settings. Logs are Zulu (UTC), not ET, and that would account for a five hour difference in host time vs log time, normally (standard time).

          http://your-reactor-ip:8111/diag/sun

          Also look at the rule detail panel any time you are troubleshooting logic. Your log snippets don't show any actions being run at all for rule-kmfo3pz8, just the rule eval/update to Reset state. Logging of actions in HubitatController is currently unconditional, so if any action was being sent, it would be in the logs (regardless of log level).

          G Offline
          G Offline
          gwp1
          wrote on last edited by
          #4

          @toggledbits The host time is currently 12/4/2021, 10:41:24 AM offset -300 minutes from UTC, which lines up to log timestamps of 15:xx:xx.

          c363e0d1-506e-4bb9-8aaa-4056295ce48a-image.png

          This ruleset hasn't changed since MSR came online months ago so I'm loathe to point to that, esp since it's across multiple modes.

          Searching the log for this ruleset shows it first appearing at that RESET! line.

          c1a8ea88-7dd4-4819-bff7-0b855654a81f-image.png

          I've rolled back to 21332 and retested. Mode day did not kick over as expected. Given this has worked flawlessly with this build I'm digging further. Right now it appears like the house never moved to mode night even though all the actions (lights off, announcement made, unlocked locks locked) happened.

          How far back does MSR retain logs time-wise?

          *Hubitat C-7 2.4.3.177
          *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

          *HAOS
          Core 2026.1.1
          w/ HA Connect ZWA-2
          FW: v1.1
          SDK: v7.23.1

          *Prod MSR in docker/portainer
          MSR: latest-26011-c621bbc7
          MQTTController: 25139
          ZWave Controller: 25139

          toggledbitsT 1 Reply Last reply
          0
          • G gwp1

            @toggledbits The host time is currently 12/4/2021, 10:41:24 AM offset -300 minutes from UTC, which lines up to log timestamps of 15:xx:xx.

            c363e0d1-506e-4bb9-8aaa-4056295ce48a-image.png

            This ruleset hasn't changed since MSR came online months ago so I'm loathe to point to that, esp since it's across multiple modes.

            Searching the log for this ruleset shows it first appearing at that RESET! line.

            c1a8ea88-7dd4-4819-bff7-0b855654a81f-image.png

            I've rolled back to 21332 and retested. Mode day did not kick over as expected. Given this has worked flawlessly with this build I'm digging further. Right now it appears like the house never moved to mode night even though all the actions (lights off, announcement made, unlocked locks locked) happened.

            How far back does MSR retain logs time-wise?

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

            @gwp1 said in Modes not changing correctly since 21337:

            How far back does MSR retain logs time-wise?

            As far as your log rotation allows.

            Can you go back to 21337 and show the result of the rule detail/status panel?

            Also, make sure to check the case of all mode setting actions. Mode names are case-sensitive in Hubitat ( day =/= Day ), so if they don't match, the action won't work. When testing in conditions, make sure the test is case-insensitive (it is in the rule you've shown, so that's good).

            G 1 Reply Last reply
            0
            • toggledbitsT toggledbits

              @gwp1 said in Modes not changing correctly since 21337:

              How far back does MSR retain logs time-wise?

              As far as your log rotation allows.

              Can you go back to 21337 and show the result of the rule detail/status panel?

              Also, make sure to check the case of all mode setting actions. Mode names are case-sensitive in Hubitat ( day =/= Day ), so if they don't match, the action won't work. When testing in conditions, make sure the test is case-insensitive (it is in the rule you've shown, so that's good).

              G Offline
              G Offline
              gwp1
              wrote on last edited by
              #6

              @toggledbits I just moved back to 21337 a moment ago. I cannot seem to get the house into mode night atm. Troubleshooting this as my thinking now is that the house, though doing all the actions (and I repeated that just now), doesn't actually going into mode night anymore.

              *Hubitat C-7 2.4.3.177
              *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

              *HAOS
              Core 2026.1.1
              w/ HA Connect ZWA-2
              FW: v1.1
              SDK: v7.23.1

              *Prod MSR in docker/portainer
              MSR: latest-26011-c621bbc7
              MQTTController: 25139
              ZWave Controller: 25139

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

                Try "Night" (capital N)... case matters to Hubitat

                G 1 Reply Last reply
                0
                • toggledbitsT toggledbits

                  Try "Night" (capital N)... case matters to Hubitat

                  G Offline
                  G Offline
                  gwp1
                  wrote on last edited by gwp1
                  #8

                  @toggledbits When it is time for the house to go into night there is an Alexa routine that flips a virtual switch. This is the sole trigger and the result is the running of a Reaction.

                  3f86e866-4a46-485e-9644-1aa84f67f559-image.png

                  This has been unchanged.

                  At the end of the reaction is a :10 delay and the virtual switch flips back off again (for next time.) That's it. Nothing fancy. All of these steps are working except for the mode actually changing to night.

                  This has worked for MONTHS untouched. I'm literally watching it step thru here:

                  1805cdf5-a08e-43f9-a649-db12a871ec25-image.png

                  80b5cebe-623f-4d36-9d62-c7284db77f5e-image.png

                  *Hubitat C-7 2.4.3.177
                  *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                  *HAOS
                  Core 2026.1.1
                  w/ HA Connect ZWA-2
                  FW: v1.1
                  SDK: v7.23.1

                  *Prod MSR in docker/portainer
                  MSR: latest-26011-c621bbc7
                  MQTTController: 25139
                  ZWave Controller: 25139

                  G 1 Reply Last reply
                  0
                  • G gwp1

                    @toggledbits When it is time for the house to go into night there is an Alexa routine that flips a virtual switch. This is the sole trigger and the result is the running of a Reaction.

                    3f86e866-4a46-485e-9644-1aa84f67f559-image.png

                    This has been unchanged.

                    At the end of the reaction is a :10 delay and the virtual switch flips back off again (for next time.) That's it. Nothing fancy. All of these steps are working except for the mode actually changing to night.

                    This has worked for MONTHS untouched. I'm literally watching it step thru here:

                    1805cdf5-a08e-43f9-a649-db12a871ec25-image.png

                    80b5cebe-623f-4d36-9d62-c7284db77f5e-image.png

                    G Offline
                    G Offline
                    gwp1
                    wrote on last edited by
                    #9

                    @gwp1 Ok, this is very odd. I can change the mode in this reaction to any other mode but night and it works. Put it back to night as the outcome and nada.

                    *Hubitat C-7 2.4.3.177
                    *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                    *HAOS
                    Core 2026.1.1
                    w/ HA Connect ZWA-2
                    FW: v1.1
                    SDK: v7.23.1

                    *Prod MSR in docker/portainer
                    MSR: latest-26011-c621bbc7
                    MQTTController: 25139
                    ZWave Controller: 25139

                    toggledbitsT 1 Reply Last reply
                    0
                    • toggledbitsT Offline
                      toggledbitsT Offline
                      toggledbits
                      wrote on last edited by toggledbits
                      #10
                      This post is deleted!
                      1 Reply Last reply
                      0
                      • G gwp1

                        @gwp1 Ok, this is very odd. I can change the mode in this reaction to any other mode but night and it works. Put it back to night as the outcome and nada.

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

                        @gwp1 Please show the entity detail for the "Mode" entity (Entities list).

                        Also, try setting "Night" from the Entities list actions. And grab logs for the action if it doesn't change.

                        G 1 Reply Last reply
                        0
                        • toggledbitsT toggledbits

                          @gwp1 Please show the entity detail for the "Mode" entity (Entities list).

                          Also, try setting "Night" from the Entities list actions. And grab logs for the action if it doesn't change.

                          G Offline
                          G Offline
                          gwp1
                          wrote on last edited by gwp1
                          #12

                          @toggledbits This is odd. Wouldn't I expect to see all the modes listed under x_hubitat_sys_mode.modes={"Day":1}?

                          6049c2a4-770a-4d1f-81d0-b2937d16bf2c-image.png

                          Tried setting Night from the Entities list actions. Nada.

                          [latest-21337]2021-12-04T16:45:03.111Z <Rule:5:Rule.js:793> Rule#rule-kphozuch Upstairs bulb requesting eval; entity-changed from Entity#hubitat>55
                          [latest-21337]2021-12-04T16:45:03.112Z <Rule:5:Rule.js:793> Rule#rule-komaz8fr Upstairs motion requesting eval; entity-changed from Entity#hubitat>55
                          [latest-21337]2021-12-04T16:45:03.113Z <Rule:5:Rule.js:1005> Rule#rule-kphozuch (Upstairs bulb) evaluate() acquiring mutex
                          [latest-21337]2021-12-04T16:45:03.114Z <Rule:5:Rule.js:1005> Rule#rule-komaz8fr (Upstairs motion) evaluate() acquiring mutex
                          [latest-21337]2021-12-04T16:45:03.120Z <Rule:5:Rule.js:1009> Rule#rule-kphozuch._evaluate() mutex acquired, evaluating
                          [latest-21337]2021-12-04T16:45:03.121Z <Rule:5:Rule.js:1013> Rule#rule-kphozuch update rate is 0/min limit 60/min
                          [latest-21337]2021-12-04T16:45:03.122Z <Rule:5:Rule.js:936> Rule#rule-kphozuch evaluateExpressions() with 0 expressions
                          [latest-21337]2021-12-04T16:45:03.124Z <Rule:5:Rule.js:1033> Rule#rule-kphozuch._evaluate() trigger state now false (was false)
                          [latest-21337]2021-12-04T16:45:03.125Z <Rule:5:Rule.js:1035> Rule#rule-kphozuch._evaluate() constraints state true
                          [latest-21337]2021-12-04T16:45:03.127Z <Rule:5:Rule.js:1044> Rule#rule-kphozuch rule state now false, changed no
                          [latest-21337]2021-12-04T16:45:03.131Z <Rule:5:Rule.js:1009> Rule#rule-komaz8fr._evaluate() mutex acquired, evaluating
                          [latest-21337]2021-12-04T16:45:03.133Z <Rule:5:Rule.js:1013> Rule#rule-komaz8fr update rate is 0/min limit 60/min
                          [latest-21337]2021-12-04T16:45:03.134Z <Rule:5:Rule.js:936> Rule#rule-komaz8fr evaluateExpressions() with 0 expressions
                          [latest-21337]2021-12-04T16:45:03.136Z <Rule:5:Rule.js:1033> Rule#rule-komaz8fr._evaluate() trigger state now false (was false)
                          [latest-21337]2021-12-04T16:45:03.137Z <Rule:5:Rule.js:1035> Rule#rule-komaz8fr._evaluate() constraints state true
                          [latest-21337]2021-12-04T16:45:03.139Z <Rule:5:Rule.js:1044> Rule#rule-komaz8fr rule state now false, changed no
                          [latest-21337]2021-12-04T16:45:46.427Z <Rule:5:Rule.js:793> Rule#rule-grpoix7c2a Office On/Off requesting eval; entity-changed from Entity#hubitat>51
                          [latest-21337]2021-12-04T16:45:46.429Z <Rule:5:Rule.js:1005> Rule#rule-grpoix7c2a (Office On/Off) evaluate() acquiring mutex
                          [latest-21337]2021-12-04T16:45:46.431Z <Rule:5:Rule.js:1009> Rule#rule-grpoix7c2a._evaluate() mutex acquired, evaluating
                          [latest-21337]2021-12-04T16:45:46.432Z <Rule:5:Rule.js:1013> Rule#rule-grpoix7c2a update rate is 2/min limit 60/min
                          [latest-21337]2021-12-04T16:45:46.433Z <Rule:5:Rule.js:936> Rule#rule-grpoix7c2a evaluateExpressions() with 0 expressions
                          [latest-21337]2021-12-04T16:45:46.436Z <Rule:5:Rule.js:1033> Rule#rule-grpoix7c2a._evaluate() trigger state now false (was false)
                          [latest-21337]2021-12-04T16:45:46.437Z <Rule:5:Rule.js:1035> Rule#rule-grpoix7c2a._evaluate() constraints state true
                          [latest-21337]2021-12-04T16:45:46.439Z <Rule:5:Rule.js:1044> Rule#rule-grpoix7c2a rule state now false, changed no
                          [latest-21337]2021-12-04T16:45:46.673Z <HubitatController:null> HubitatController#hubitat final action path for x_hubitat_sys_mode.set on Entity#hubitat>sys_mode: http://192.168.1.214/apps/api/14/modes/Night

                          *Hubitat C-7 2.4.3.177
                          *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                          *HAOS
                          Core 2026.1.1
                          w/ HA Connect ZWA-2
                          FW: v1.1
                          SDK: v7.23.1

                          *Prod MSR in docker/portainer
                          MSR: latest-26011-c621bbc7
                          MQTTController: 25139
                          ZWave Controller: 25139

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

                            According to the entity, the only mode that exists on the hub is Day. Log in to your hub and check the Modes screen. If that agrees, something happened to your hub (firmware upgrade to latest new version recently?).

                            G 1 Reply Last reply
                            0
                            • toggledbitsT toggledbits

                              According to the entity, the only mode that exists on the hub is Day. Log in to your hub and check the Modes screen. If that agrees, something happened to your hub (firmware upgrade to latest new version recently?).

                              G Offline
                              G Offline
                              gwp1
                              wrote on last edited by
                              #14

                              @toggledbits d5562d84-24e6-4aa8-bc58-65555ab8caff-image.png

                              Latest release to 2.3.0.115 on Hubitat. Rolling back to .113 to see what happens.

                              *Hubitat C-7 2.4.3.177
                              *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                              *HAOS
                              Core 2026.1.1
                              w/ HA Connect ZWA-2
                              FW: v1.1
                              SDK: v7.23.1

                              *Prod MSR in docker/portainer
                              MSR: latest-26011-c621bbc7
                              MQTTController: 25139
                              ZWave Controller: 25139

                              G 1 Reply Last reply
                              0
                              • G gwp1

                                @toggledbits d5562d84-24e6-4aa8-bc58-65555ab8caff-image.png

                                Latest release to 2.3.0.115 on Hubitat. Rolling back to .113 to see what happens.

                                G Offline
                                G Offline
                                gwp1
                                wrote on last edited by
                                #15

                                @gwp1 Rolled back to .113, saw this:

                                aeeca882-f92d-43d7-b045-ebf68bce460c-image.png

                                When the restore was done it was in Evening because that's where it was when the release was deployed and backup taken.

                                Did a Tools > Restart on MSR to ensure everything was synced and now I see this again:

                                c2fcaee3-4aec-4212-84f7-129ed07fc604-image.png

                                *Hubitat C-7 2.4.3.177
                                *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                                *HAOS
                                Core 2026.1.1
                                w/ HA Connect ZWA-2
                                FW: v1.1
                                SDK: v7.23.1

                                *Prod MSR in docker/portainer
                                MSR: latest-26011-c621bbc7
                                MQTTController: 25139
                                ZWave Controller: 25139

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

                                  Are you on their latest firmware?

                                  G 1 Reply Last reply
                                  0
                                  • toggledbitsT toggledbits

                                    Are you on their latest firmware?

                                    G Offline
                                    G Offline
                                    gwp1
                                    wrote on last edited by
                                    #17

                                    @toggledbits Well I was until apparently an hour ago lol Seems there's .116 out now. Also, rolling back apparently doesn't restore the old firmware to .113 like I thought it would. I'm still on .115. Guess I'll fail forward to .116.

                                    *Hubitat C-7 2.4.3.177
                                    *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                                    *HAOS
                                    Core 2026.1.1
                                    w/ HA Connect ZWA-2
                                    FW: v1.1
                                    SDK: v7.23.1

                                    *Prod MSR in docker/portainer
                                    MSR: latest-26011-c621bbc7
                                    MQTTController: 25139
                                    ZWave Controller: 25139

                                    G 1 Reply Last reply
                                    0
                                    • G gwp1

                                      @toggledbits Well I was until apparently an hour ago lol Seems there's .116 out now. Also, rolling back apparently doesn't restore the old firmware to .113 like I thought it would. I'm still on .115. Guess I'll fail forward to .116.

                                      G Offline
                                      G Offline
                                      gwp1
                                      wrote on last edited by gwp1
                                      #18

                                      @gwp1 On Hubitat's latest, .116. No change.

                                      5d7b9c70-4ecc-4c0d-8180-51c440079eca-image.png

                                      Following my Rule#1 of troubleshooting, "what changed?" I rolled back MSR to 21332 (because I'd just updated to 21337) just in case and now I see this:

                                      b7e462b6-7251-45a4-b06c-c0647c3ebac3-image.png

                                      Things are behaving as they should. Using the Entities menu I triggered mode night and it flipped over (only to flip back to day as it should because it's day time - but I watched it three times visibly flip to the correct mode.)

                                      *Hubitat C-7 2.4.3.177
                                      *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                                      *HAOS
                                      Core 2026.1.1
                                      w/ HA Connect ZWA-2
                                      FW: v1.1
                                      SDK: v7.23.1

                                      *Prod MSR in docker/portainer
                                      MSR: latest-26011-c621bbc7
                                      MQTTController: 25139
                                      ZWave Controller: 25139

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

                                        Yup, and I think I see the issue... stay tuned...

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

                                          OK. 21338

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


                                          Recent Topics

                                          • Oddness in Copy/Move of Reactions
                                            G
                                            gwp1
                                            0
                                            1
                                            36

                                          • [Solved] function isRuleEnabled() issue
                                            CrilleC
                                            Crille
                                            0
                                            4
                                            51

                                          • [Reactor] Problem with Global Reactions and groups
                                            therealdbT
                                            therealdb
                                            0
                                            3
                                            71

                                          • Possible feature request 2?
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            3
                                            51

                                          • Reactor (Multi-System/Multi-Hub) Announcements
                                            toggledbitsT
                                            toggledbits
                                            5
                                            133
                                            79.7k

                                          • Genuinely impressed with Zigbee and HA / Reactor
                                            CatmanV2C
                                            CatmanV2
                                            1
                                            9
                                            358

                                          • Copying a global reaction
                                            toggledbitsT
                                            toggledbits
                                            0
                                            3
                                            104

                                          • [HowTo] Using HABridge with Reactor
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            9
                                            421

                                          • [Reactor] Bug when sending MQTT boolean payloads
                                            toggledbitsT
                                            toggledbits
                                            0
                                            4
                                            157

                                          • Difficulty defining repeating annual period
                                            G
                                            gwp1
                                            0
                                            5
                                            128

                                          • Need help with sequence
                                            therealdbT
                                            therealdb
                                            0
                                            3
                                            80

                                          • Possible feature request?
                                            therealdbT
                                            therealdb
                                            0
                                            5
                                            187
                                          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