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. Possible Bug With Reaction Groups
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

Possible Bug With Reaction Groups

Scheduled Pinned Locked Moved Multi-System Reactor
4 Posts 3 Posters 205 Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • PablaP Offline
    PablaP Offline
    Pabla
    wrote on last edited by
    #1

    Not 100% sure this is a bug because I may have an error in my logic but here is the issue I am running into.

    I have created 3 dynamic groups, the first group called "battery_35" filters all battery_powered devices that have a battery_level between 11% and 35%. My second dynamic group is called "battery_10" and it filters the same type of devices but only the ones with a battery_level between 1% and 10%. The third group is "battery_dead" and filters the same type of devices as the previous groups, but only the ones that have 0% battery. Refer to my earlier thread about the specifics of the dynamic group if necessary.

    My triggers are as follow in the screenshot. Basically if the local expression that spits out the devices that match the criteria for one of three dynamic groups changes and the respective dynamic group is false, the rule goes true.

    Screenshot 2022-10-31 at 8.34.16 PM.png

    I have 3 reaction groups, all set up basically the same. I have a condition for each group to only trigger the notify action if the variable that contains the low battery device (either 35%, 10% or dead) changes. I have it set this way to prevent multiple notifications of device low battery and to mitigate the need to create 3 different rulesets for each battery level.

    Screenshot 2022-10-31 at 8.36.40 PM.png Screenshot 2022-10-31 at 8.37.05 PM.png Screenshot 2022-10-31 at 8.38.44 PM.png

    The issue occurs here, if say the "name_battery_10" and/or "name_battery_dead" are empty, and the "name_battery_35" changes (ie a device battery is now between 11-35%) the "35% Battery" successfully (and expectedly) triggers and the notification is sent. However at the same time one of the triggers "name_battery_10" or "name_battery_dead" trigger and those notifications are sent, albeit with empty device names since no devices actually met their filters (haven't found a pattern of which trigger group goes triggers). This only happens if the variable values are empty. If all the variables are not empty I do not experience this issue.

    I think I could mitigate this by adding the same dynamic group condition that's in the triggers section into the reaction groups but before I do this I want to see if this is a bug or incorrect logic. I have included some logs when this issue occurred I do not see any error besides the dynamic group for "offline devices" which I am still figuring out so please ignore that :).

    [latest-22302]2022-11-01T02:48:18.571Z <Rule:INFO> Low Battery (rule-l9vvokiq in Notifications) starting evaluation; because entity-changed Entity#hass>sensor_backyard_gate_battery_level
    [latest-22302]2022-11-01T02:48:18.705Z <Rule:INFO> Low Battery (rule-l9vvokiq in Notifications) evaluated; trigger state unchanged (false); rule state remains RESET
    [latest-22302]2022-11-01T02:48:18.709Z <Rule:INFO> Low Battery (rule-l9vvokiq in Notifications) evaluation complete
    [latest-22302]2022-11-01T02:48:18.782Z <DynamicGroupController:ERR> DynamicGroupController#groups filter expression entity.attributes.x_hass.state == 'unknown' ||  entity.attributes.x_hass.state == 'unavailable' || entity.attributes.x_hass.state == 'none'
     error with Group#hass>controller_all: [ReferenceError]ReferenceError: Invalid scope in reference to member state of (object)null
    [latest-22302]2022-11-01T02:48:18.783Z <DynamicGroupController:ERR> DynamicGroupController#groups filter expression entity.attributes.x_hass.state == 'unknown' ||  entity.attributes.x_hass.state == 'unavailable' || entity.attributes.x_hass.state == 'none'
     error with System#hass>system: [ReferenceError]ReferenceError: Invalid scope in reference to member state of (object)null
    [latest-22302]2022-11-01T02:48:19.047Z <Rule:INFO> Low Battery (rule-l9vvokiq in Notifications) starting evaluation; because entity-changed Group#groups>low_battery_35
    [latest-22302]2022-11-01T02:48:19.148Z <Rule:INFO> Low Battery (rule-l9vvokiq in Notifications) evaluated; rule state transition from RESET to SET!
    [latest-22302]2022-11-01T02:48:19.198Z <Rule:INFO> Low Battery (rule-l9vvokiq in Notifications) evaluation complete
    [latest-22302]2022-11-01T02:48:19.200Z <Engine:INFO> Enqueueing "Low Battery<SET>" (rule-l9vvokiq:S)
    [latest-22302]2022-11-01T02:48:19.230Z <Rule:INFO> Low Battery (rule-l9vvokiq in Notifications) starting evaluation; because timer-trigger Timer#rule-l9vvokiq
    [latest-22302]2022-11-01T02:48:19.331Z <Rule:INFO> Low Battery (rule-l9vvokiq in Notifications) evaluated; rule state transition from SET to RESET!
    [latest-22302]2022-11-01T02:48:19.380Z <Rule:INFO> Low Battery (rule-l9vvokiq in Notifications) evaluation complete
    [latest-22302]2022-11-01T02:48:19.384Z <Engine:NOTICE> Starting reaction Low Battery<SET> (rule-l9vvokiq:S)
    [latest-22302]2022-11-01T02:48:19.385Z <Engine:INFO> Low Battery<SET> all actions completed. ```![Screenshot 2022-10-31 at 8.38.44 PM.png](/assets/uploads/files/1667273939467-screenshot-2022-10-31-at-8.38.44-pm-resized.png)
    1 Reply Last reply
    0
    • toggledbitsT Offline
      toggledbitsT Offline
      toggledbits
      wrote on last edited by toggledbits
      #2

      There's a bug here, but probably not what you think: the changes operator should not be allowed in constraints. It's special, in that it's a reactive operator that can only respond once and immediately when a value changes. After it has declared that a value has changed, that test will not succeed again unless and until the value changes again, so its behavior in a constraint is effectively undefined and nondeterministic. Fixed: next build the changes operator will not be listed as an option in constraint context.

      Instead of using changes again on your group, why not just test to see if your name list is empty/blank or not?

      The group expression errors showing in the log suggest you have a battery-operated device (or whatever matches your selectors) that isn't from Hass (i.e. the x_hass capability isn't present on it). You may need to handle this condition in your expression, which may be as simple as using the coalesce operators in your expression so that a missing attribute doesn't generate an error:

      entity.attributes.x_hass?.state == 'unknown' ||  entity.attributes.x_hass?.state == 'unavailable' || entity.attributes.x_hass?.state == 'none'
      

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

      PablaP 1 Reply Last reply
      0
      • toggledbitsT toggledbits

        There's a bug here, but probably not what you think: the changes operator should not be allowed in constraints. It's special, in that it's a reactive operator that can only respond once and immediately when a value changes. After it has declared that a value has changed, that test will not succeed again unless and until the value changes again, so its behavior in a constraint is effectively undefined and nondeterministic. Fixed: next build the changes operator will not be listed as an option in constraint context.

        Instead of using changes again on your group, why not just test to see if your name list is empty/blank or not?

        The group expression errors showing in the log suggest you have a battery-operated device (or whatever matches your selectors) that isn't from Hass (i.e. the x_hass capability isn't present on it). You may need to handle this condition in your expression, which may be as simple as using the coalesce operators in your expression so that a missing attribute doesn't generate an error:

        entity.attributes.x_hass?.state == 'unknown' ||  entity.attributes.x_hass?.state == 'unavailable' || entity.attributes.x_hass?.state == 'none'
        
        PablaP Offline
        PablaP Offline
        Pabla
        wrote on last edited by
        #3

        @toggledbits said in Possible Bug With Reaction Groups:

        There's a bug here, but probably not what you think: the changes operator should not be allowed in constraints. It's special, in that it's a reactive operator that can only respond once and immediately when a value changes. After it has declared that a value has changed, that test will not succeed again unless and until the value changes again, so its behavior in a constraint is effectively undefined and nondeterministic. Fixed: next build the changes operator will not be listed as an option in constraint context.
        Instead of using changes again on your group, why not just test to see if your name list is empty/blank or not?

        Sounds good, I was pulling my hair out trying to figure out what was wrong. I swapped it for "is not empty" now it triggers as expected.

        @toggledbits said in Possible Bug With Reaction Groups:

        The group expression errors showing in the log suggest you have a battery-operated device (or whatever matches your selectors) that isn't from Hass (i.e. the x_hass capability isn't present on it). You may need to handle this condition in your expression, which may be as simple as using the coalesce operators in your expression so that a missing attribute doesn't generate an error:

        This seems to have done the trick as well.

        I have a question about the time shown stamps shown in the logs, it never matches up with my local time. Its usually a few hours ahead, is there anyway to have that changed to match the time zone MSR is in? It makes debugging a bit easier.

        G 1 Reply Last reply
        0
        • PablaP Pabla

          @toggledbits said in Possible Bug With Reaction Groups:

          There's a bug here, but probably not what you think: the changes operator should not be allowed in constraints. It's special, in that it's a reactive operator that can only respond once and immediately when a value changes. After it has declared that a value has changed, that test will not succeed again unless and until the value changes again, so its behavior in a constraint is effectively undefined and nondeterministic. Fixed: next build the changes operator will not be listed as an option in constraint context.
          Instead of using changes again on your group, why not just test to see if your name list is empty/blank or not?

          Sounds good, I was pulling my hair out trying to figure out what was wrong. I swapped it for "is not empty" now it triggers as expected.

          @toggledbits said in Possible Bug With Reaction Groups:

          The group expression errors showing in the log suggest you have a battery-operated device (or whatever matches your selectors) that isn't from Hass (i.e. the x_hass capability isn't present on it). You may need to handle this condition in your expression, which may be as simple as using the coalesce operators in your expression so that a missing attribute doesn't generate an error:

          This seems to have done the trick as well.

          I have a question about the time shown stamps shown in the logs, it never matches up with my local time. Its usually a few hours ahead, is there anyway to have that changed to match the time zone MSR is in? It makes debugging a bit easier.

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

          @pabla Logs are in UTC.

          *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 toggledbits locked this topic on
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          Recent Topics

          • Limit HA Entity in MSR
            toggledbitsT
            toggledbits
            0
            5
            46

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

          • Disaster recovery and virtualisation
            CatmanV2C
            CatmanV2
            0
            5
            583

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

          • 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
            296

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

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

          • Deleting widgets
            toggledbitsT
            toggledbits
            0
            4
            440

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