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
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor
System Configuration Check - time is offset
F
Hi! I get this message when I'm on the status tab: System Configuration Check The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds. I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6. HA versions are: Core 2025.3.4 Supervisor 2025.03.4 Operating System 15.1 I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version. Do anyone know what I can try? Thanks in advance! Let's Be Careful Out There (Hill Street reference...) /Fanan
Multi-System Reactor
Programmatically capture HTTP Request action status code or error
therealdbT
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB. While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed. So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response. While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits Thanks!
Multi-System Reactor
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N
Hi , I'm on -Reactor (Multi-hub) latest-25067-62e21a2d -Docker on Synology NAS -ZWaveJSUI 9.31.0.6c80945 Problem with ZwaveJSUI: When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white. I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui. I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb". After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color. This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite. x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33} The "cold white" and "warm white" settings interfer with the rgb color settings. Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white. So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set. x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33 Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this? x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33} Thanks in advance.
Multi-System Reactor
Problem with simultaneous notifications.
T
Topic thumbnail image
Multi-System Reactor
Problem after upgrading to 25067
R
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem? I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Multi-System Reactor
Global expressions not always evaluated
tunnusT
Topic thumbnail image
Multi-System Reactor
[Solved] Local expression evaluation
V
Topic thumbnail image
Multi-System Reactor
[Solved] Runtime error when exiting global reaction that contains a group
S
I am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved. The Runtime Error is different in the two browsers Safari v18.3 @http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:44 You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Google Chrome 133.0.6943.142 TypeError: self.editor.isModified is not a function at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34) You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community. Steps to reproduce: Click the pencil to edit a global reaction with a group. Click the Exit button. Runtime error appears. or Click Create Reaction Click Add Action Select Group Add Condition such as Entity Attribute. Add an Action. Click Save Click Exit Runtime error appears. I don’t know how long the error has been there as I haven’t edited the global reaction in a long time. Reactor (Multi-hub) latest-25060-f32eaa46 Docker Mac OS: 15.3.1 Thanks
Multi-System Reactor
Cannot delete Global Expressions
SnowmanS
I am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons. I have not created a global expression for some times and just noticed this while doing some clean-up. I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success. Here's what the log shows. [latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay [latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } Reactor latest-25067-62e21a2d Docker on Synology NAS
Multi-System Reactor
Local notification methods?
CatmanV2C
Morning, experts. Hard on learning about the internet check script in MSR tools, I was wondering what suggestions anyone has about a local (i.e. non-internet dependent) notification method. This was prompted by yesterday's fun and games with my ISP. I've got the script Cronned and working properly but short of flashing a light on and off, I'm struggling to think of a way of alerting me (ideally to my phone) I guess I could set up a Discord server at home, but that feels like overkill for a rare occasion. Any other suggestions? TIA C
Multi-System Reactor
Custom capabilities in MQTT templates
M
Hi, I'm trying to integrate the sonos-mqtt (https://sonos2mqtt.svrooij.io/) with the MSR and it's coming along nicely so far. But cannot wrap my head around how to define custom capabilities in MQTT templates. I need this for the TTS announcements and similarly for the notification sounds where I would pass the sound file as parameter. So this is what I have in the local_mqtt_devices.yaml capabilities: x_sonos_announcement: attributes: actions: speak: arguments: text: type: string volume: type: int delay: type: int And this is the template: templates: sonos-announcement: capabilities: - x_sonos_announcement actions: x_sonos_announcement: speak: topic: "sonos/cmd/speak" payload: expr: > { "text": parameters.text, "volume": parameters.volume, "delayMs": parameters.delay, "onlyWhenPlaying": false, "engine": "neural" } type: json So the speak action should send something like this to topic sonos/cmd/speak { "text": "message goes here", "volume": 50, "delayMs": 100, "onlyWhenPlaying": false, "engine": "neural" } At startup the MSR seems to be quite unhappy with my configuration: reactor | [latest-25016]2025-02-09T08:19:59.029Z <MQTTController:WARN> MQTTController#mqtt entity Entity#mqtt>sonos-announcement unable to configure capabilities [Array][ "x_sonos_announcement" ] reactor | i18n: missing fi-FI language string: Configuration for {0:q} is incomplete because the following requested capabilities are undefined: {1} reactor | i18n: missing fi-FI language string: Configuration for {0:q} has unrecognized capability {1:q} in actions reactor | Trace: Configuration for {0:q} is incomplete because the following requested capabilities are undefined: {1} reactor | at _T (/opt/reactor/server/lib/i18n.js:611:28) reactor | at AlertManager.addAlert (/opt/reactor/server/lib/AlertManager.js:125:25) reactor | at MQTTController.sendWarning (/opt/reactor/server/lib/Controller.js:627:30) reactor | at MQTTController.start (/var/reactor/ext/MQTTController/MQTTController.js:268:26) reactor | at async Promise.allSettled (index 0) Configuration for "sonos-announcement" has unrecognized capability "x_sonos_announcement" in actions Controller: MQTTController#mqtt Last 10:21:37 AM Configuration for "sonos-announcement" is incomplete because the following requested capabilities are undefined: x_sonos_announcement Controller: MQTTController#mqtt Last 10:21:37 AM This is probably a pretty stupid question and the approach may not even work at all, but maybe someone or @toggledbits for sure, could point me to the right direction. Basically the idea is to be able to send TTS messages from reactions using entity actions. I've previously used HTTP requests to Sonos HTTP API (https://hub.docker.com/r/chrisns/docker-node-sonos-http-api/) for the same functionality, but since moving to sonos-mqtt, I need a way to send the TTS notifications using MQTTController. Along with the actual message, volume and delay must also be parameterizable. br, mgvra MSR latest-25016-d47fea38 / MQTTController [0.2.24293]
Multi-System Reactor
[SOLVED]Hass websocket falsely reporting ready on boot??
V
Hi, @toggledbits I just noticed that following a reboot of my raspberry pi, some of the rules, that I was expecting to recover, are not catching up following a reboot. I have made a simple test rule (rule-m6rz6ol1) with only "after Date/time" as trigger and "turn on a lamp" as a set reaction. All my infrastructure is on the same board so Reactor, Hass, Zwavejs, ... are all rebooting. Here is the sequence of the test case (All time converted to Zulu to match logs): Rule "after Date/Time" set to 14:05:00z Shutdown on Raspberry Pi at 14:04:00z Power back up at 14:08:00z Rule overview shows true as of 14:08:14z waiting for 00:00:00 in GUI From the log I can see that MSR is picking up the rule and knows that the state of the rule has changed from false to true and tries to send the update to HASS but failed with websocket error. Here is what I see from the log: 14:04:04z shutdown complete 14:08:08z Power up 14:08:13.111z websocket connection 14:08:15:323z Reaction to the light failed, Websocket not opened After there is a series of websocket connection attempt until 14:08:51z where it seemed to be really ready. Back in 2021 we had a discussion (https://smarthome.community/topic/700/solved-start-up?_=1738766986566) and you proposed to add a startup_delay:xxxx and startup_wait:xxxx parameter in the engine section of "reactor.yaml". When I try the startup_delay (this used to be a hard delay), the engine failed to start (I think). I then try the startup_wait:xxxx without any success. Since it wait for the connection status to be up to cancel the delay, it does not do anyting since Hass is reporting the socket up without really being up ( I think...). Questions: Did I figured it all wrong? should the startup_delay:xxxxx have worked? Any ideas? Here is the log: OK now I am stuck. I did add the log but when I submit the editor complained saying that I am limited to 32767 characters. The log from the shutdown to the time the websocket is stable is about 300000 character long. What are my options?
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.1k 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.151
    *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

    *HASS 2025.3.4
    w/ ZST10-700 fw 7.18.3

    *Prod MSR in docker/portainer
    MSR: latest-25082-3c348de6
    MQTTController: 24257
    ZWave Controller: 25082

    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.151
      *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

      *HASS 2025.3.4
      w/ ZST10-700 fw 7.18.3

      *Prod MSR in docker/portainer
      MSR: latest-25082-3c348de6
      MQTTController: 24257
      ZWave Controller: 25082

      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.151
          *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

          *HASS 2025.3.4
          w/ ZST10-700 fw 7.18.3

          *Prod MSR in docker/portainer
          MSR: latest-25082-3c348de6
          MQTTController: 24257
          ZWave Controller: 25082

          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.151
              *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

              *HASS 2025.3.4
              w/ ZST10-700 fw 7.18.3

              *Prod MSR in docker/portainer
              MSR: latest-25082-3c348de6
              MQTTController: 24257
              ZWave Controller: 25082

              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.151
                  *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                  *HASS 2025.3.4
                  w/ ZST10-700 fw 7.18.3

                  *Prod MSR in docker/portainer
                  MSR: latest-25082-3c348de6
                  MQTTController: 24257
                  ZWave Controller: 25082

                  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.151
                    *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                    *HASS 2025.3.4
                    w/ ZST10-700 fw 7.18.3

                    *Prod MSR in docker/portainer
                    MSR: latest-25082-3c348de6
                    MQTTController: 24257
                    ZWave Controller: 25082

                    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.151
                          *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                          *HASS 2025.3.4
                          w/ ZST10-700 fw 7.18.3

                          *Prod MSR in docker/portainer
                          MSR: latest-25082-3c348de6
                          MQTTController: 24257
                          ZWave Controller: 25082

                          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.151
                              *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                              *HASS 2025.3.4
                              w/ ZST10-700 fw 7.18.3

                              *Prod MSR in docker/portainer
                              MSR: latest-25082-3c348de6
                              MQTTController: 24257
                              ZWave Controller: 25082

                              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.151
                                *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                                *HASS 2025.3.4
                                w/ ZST10-700 fw 7.18.3

                                *Prod MSR in docker/portainer
                                MSR: latest-25082-3c348de6
                                MQTTController: 24257
                                ZWave Controller: 25082

                                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.151
                                    *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                                    *HASS 2025.3.4
                                    w/ ZST10-700 fw 7.18.3

                                    *Prod MSR in docker/portainer
                                    MSR: latest-25082-3c348de6
                                    MQTTController: 24257
                                    ZWave Controller: 25082

                                    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.151
                                      *Proxmox VE v8, Beelink MiniPC 12GBs, SSD

                                      *HASS 2025.3.4
                                      w/ ZST10-700 fw 7.18.3

                                      *Prod MSR in docker/portainer
                                      MSR: latest-25082-3c348de6
                                      MQTTController: 24257
                                      ZWave Controller: 25082

                                      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

                                          • [Solved] Limit HA Entity in MSR
                                            wmarcolinW
                                            wmarcolin
                                            0
                                            7
                                            63

                                          • Reactor (Multi-System/Multi-Hub) Announcements
                                            toggledbitsT
                                            toggledbits
                                            5
                                            121
                                            35.2k

                                          • Disaster recovery and virtualisation
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            5
                                            584

                                          • Remote access of Zwave stick from Z-wave server
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            3
                                            308

                                          • Organizing/ structuring rule sets and rules
                                            G
                                            gwp1
                                            0
                                            5
                                            348

                                          • Moving MSR from a QNAP container to RP 5 - some issues
                                            G
                                            gwp1
                                            0
                                            5
                                            298

                                          • Widget deletion does not work and landing page (status) is empy
                                            G
                                            gwp1
                                            0
                                            4
                                            268

                                          • Need help reducing false positive notifications
                                            T
                                            tamorgen
                                            0
                                            7
                                            463

                                          • Deleting widgets
                                            toggledbitsT
                                            toggledbits
                                            0
                                            4
                                            440

                                          • MQTT configuration question
                                            tunnusT
                                            tunnus
                                            0
                                            11
                                            595
                                          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