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
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
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
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
Multi-System Reactor
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor

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

Scheduled Pinned Locked Moved Multi-System Reactor
22 Posts 2 Posters 1.3k 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.1.177
    *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

    *HASS 2025.6.0
    w/ ZST10-700 fw 7.18.3

    *Prod MSR in docker/portainer
    MSR: latest-25139-fbd67abc
    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.1.177
      *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

      *HASS 2025.6.0
      w/ ZST10-700 fw 7.18.3

      *Prod MSR in docker/portainer
      MSR: latest-25139-fbd67abc
      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.1.177
          *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

          *HASS 2025.6.0
          w/ ZST10-700 fw 7.18.3

          *Prod MSR in docker/portainer
          MSR: latest-25139-fbd67abc
          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.1.177
              *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

              *HASS 2025.6.0
              w/ ZST10-700 fw 7.18.3

              *Prod MSR in docker/portainer
              MSR: latest-25139-fbd67abc
              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.1.177
                  *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                  *HASS 2025.6.0
                  w/ ZST10-700 fw 7.18.3

                  *Prod MSR in docker/portainer
                  MSR: latest-25139-fbd67abc
                  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.1.177
                    *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                    *HASS 2025.6.0
                    w/ ZST10-700 fw 7.18.3

                    *Prod MSR in docker/portainer
                    MSR: latest-25139-fbd67abc
                    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.1.177
                          *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                          *HASS 2025.6.0
                          w/ ZST10-700 fw 7.18.3

                          *Prod MSR in docker/portainer
                          MSR: latest-25139-fbd67abc
                          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.1.177
                              *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                              *HASS 2025.6.0
                              w/ ZST10-700 fw 7.18.3

                              *Prod MSR in docker/portainer
                              MSR: latest-25139-fbd67abc
                              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.1.177
                                *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                                *HASS 2025.6.0
                                w/ ZST10-700 fw 7.18.3

                                *Prod MSR in docker/portainer
                                MSR: latest-25139-fbd67abc
                                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.1.177
                                    *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                                    *HASS 2025.6.0
                                    w/ ZST10-700 fw 7.18.3

                                    *Prod MSR in docker/portainer
                                    MSR: latest-25139-fbd67abc
                                    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.1.177
                                      *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                                      *HASS 2025.6.0
                                      w/ ZST10-700 fw 7.18.3

                                      *Prod MSR in docker/portainer
                                      MSR: latest-25139-fbd67abc
                                      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

                                          • Gradually turn on lights.
                                            G
                                            gwp1
                                            0
                                            4
                                            135

                                          • Stop the MSR by an external switch on Hubitat.
                                            wmarcolinW
                                            wmarcolin
                                            0
                                            1
                                            34

                                          • Error After Upgrade
                                            G
                                            gwp1
                                            0
                                            4
                                            105

                                          • Reset attribute value of entity in event handler
                                            R
                                            RHCPNG
                                            0
                                            5
                                            205

                                          • Need help figuring out how to delay a reset on reaction
                                            G
                                            gwp1
                                            0
                                            22
                                            927

                                          • Way to search for rules (rule state) in other rules
                                            T
                                            tamorgen
                                            0
                                            3
                                            101

                                          • Links to MSR from HA
                                            Tom_DT
                                            Tom_D
                                            0
                                            1
                                            91

                                          • Set Reaction > Script Action
                                            wmarcolinW
                                            wmarcolin
                                            0
                                            11
                                            437

                                          • Wiring Samotech SM308-S into light fitting
                                            akbooerA
                                            akbooer
                                            0
                                            2
                                            150

                                          • Errors after updating to MQTTController build 25139
                                            toggledbitsT
                                            toggledbits
                                            0
                                            6
                                            238

                                          • 🎉 My very first MSR controller: OpenSprinkler
                                            therealdbT
                                            therealdb
                                            5
                                            13
                                            919

                                          • Advice reqeusted to migrate MSR from Bare Metal to Container
                                            T
                                            tamorgen
                                            0
                                            5
                                            262
                                          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