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] build 26150 - engine not starting
[MSR] Native fan capabilty
therealdbT
Nothing more to add. I see we have hvac_blower, but, anyway, maybe a native fan on the same assumptions of the fan from HASS could be reasonable. I have a couple of them. ie, this is from ESPHome via HASS. x_hass.domain="fan" x_hass.entity_id="fan.kitchen_seashell_hood_ventilation_fan" x_hass.floor_id=null x_hass.services=["fan","esphome"] x_hass.source="esphome" x_hass.state="off" x_hass_attr.friendly_name="Seashell Hood Ventilation Fan" x_hass_attr.percentage=50 x_hass_attr.percentage_step=25 x_hass_attr.preset_mode="" x_hass_attr.preset_modes=[] x_hass_attr.supported_features=49 Thanks.
Multi-System Reactor
[MSR] Rule do not fire
therealdbT
Topic thumbnail image
Multi-System Reactor
Rule condition shows TRUE in UI but Rule never transitions to SET — survives full restart
N
Build: latest-26221-b25bb3e3, Docker on Synology. Hi, I have a Rule whose Trigger/Constraints reference other Rules via Rule State ... is TRUE. At some point it stops firing. Expanding the rule's condition tree in the UI shows every Trigger and Constraint condition green/TRUE — confirmed live by walking into the room and watching Motion go true in real time. Rule History shows no new SET, just old reset entries. Tried, on the same rule, same evening: recreating the trigger conditions with fresh IDs, recreating the constraint conditions with fresh IDs (flat and wrapped in a new Group — wrapping in a Group produced one SET, but it didn't reproduce on repeat attempts with the same structure), and finally a full container restart with a verified-correct saved rule. Still no SET, even with a fresh live motion event right after the restart. Separately, I found that this rule (and its 10 per-room clones) share identical internal condition/group IDs with each other — leftover from a batch clone done months ago, never regenerated. Not sure if that's related, since fixing the IDs didn't reliably fix the symptom either. Has anyone seen a Rule State condition show TRUE in the UI without the Rule ever producing a SET, surviving a clean restart? Thanks in advance
Multi-System Reactor
DynamicGroupController and attributes
therealdbT
Hey @toggledbits I'm back to trying to optimize a couple of things based on dynamic group. First of all, I think I found a typo in the doc: primary_attribute: "binary_sensor.state" primary_attribute_value: | d = false; each id in members: d = getEntity(id)?.attributes?.power_switch?.state or d, d I think the correct code snippet is d = false, All that said, my use case for dynamic groups is to group 3 different climate devices, so I could easily command them at the same time. Commands are good, but sometimes I want to check if any of the devices are on, and that's easily done with a similar snippet as the one you have in the docs. But this is limited to the primary attribute, while I want to have any of the attributes in the group to be driven by a similar logic (while all are null in the group). ie, access hvac_control.mode and see if any of the unit is set to cool, or heat. Is that possible, without re-defining an expression in each of my rules? Thanks!
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
Unofficial thread for compatibility
tunnusT
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well. As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API. Updates: (the latest versions first in the list) OK: build "latest-25264-2fbe9217" with Hubitat C-8 platform v. 2.4.3.123
Multi-System Reactor
Ooops - Deleted Reactor Ex Machina II
R
I accidentally deleted Reactor Ex Machina II (REM II) from my Reactor rules. I tried to recover it by deleting the .json and .dval in the Rules subdirectory and then recreating it from Togglebits original posting, but that did not work. Does anyone know how to recover REM ll ?
Multi-System Reactor
Bail out of failed reaction?
T
Topic thumbnail image
Multi-System Reactor
Arming Envisalink panel from MSR
T
Topic thumbnail image
Multi-System Reactor
[Solved] DynamicGroupController updating members issue
CrilleC
Edit: Solved in latest-26221. Bare-metal latest-26193 I have this group: "OKforLarm": name: OK för Larm select: - include_controller: vera - include_capability: door_sensor filter_expression: entity.attributes.door_sensor.state It contains the entities I expect but behaves a bit odd. When I open vera>device_10097 the entity attribute door_sensor.state changes to true but it won't show up as member in the group, when I also open vera>device_10095 they both shows as members and when I close vera>device_10095 it disappear from the group but when I close vera>device_10097 it lingers in the group until I restart Reactor.
Multi-System Reactor
Upgrade Issues
T
Topic thumbnail image
Multi-System Reactor
[SOLVED] Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
G
Topic thumbnail image
Multi-System Reactor
[SOLVED] Question regarding "in" vs "contains" vs contents of the string
G
Topic thumbnail image
Multi-System Reactor
Logon screen timeout
G
Noticing since 170 that the lock screen doesn't switch to the logon prompt but, rather, stays on the active UI until such time as you go to click something within it. Then it jumps to the login screen. Brave browser Brave 1.92.139 (Official Build) (arm64) Chromium: 150.0.7871.114
Multi-System Reactor
[MSR] Copy&past of actions and/or drag&drop between set/reset
therealdbT
Hey @toggledbits One thing that bothers me while doing work on new systems/new features, is that I cannot copy&paste actions, and I cannot drag&drop between set and resets. #1 is for when I want to copy an action between different rules opened in two separate browser windows, while #2 is when I just need to flip a bunch of actions in the reset, or move some logic back and forth. Both will be appreciated, but I understand the technical challenges. Thanks!
Multi-System Reactor
Upgrade advice - upgrade from aarch64 to ARM64 image
T
I'm currently on version 26011. I understand that the aarch64 image is no longer supported. So, I therefore need to update to the ARM64 image. Can anyone possibly suggest how I update my docker compose.yaml file (see below). Ideally I'd like to keep my existing reactions etc. rather than start from scratch. # Multi-System Reactor template docker-compose.yml (version 22160) # # Change the lines indicated by "DO"... # services: reactor: container_name: reactor environment: # DO change the TZ: line to set your local time zone. # See valid TZ list: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones TZ: GB # # DO NOT change this path. Your directory location is in "source" below. REACTOR_DATA_PREFIX: /var/reactor # DO change the image below to the one you are using (e.g. armv7l or aarch64 for RPi 4) image: toggledbits/reactor:latest-aarch64 restart: "always" expose: - 8111 ports: - 8111:8111 volumes: # DO change the /home/username/reactor below to the directory you created for # your local data; DO NOT change the /var/reactor part - /home/pi/docker/reactor:/var/reactor - /etc/localtime:/etc/localtime:ro tmpfs: /tmp
Multi-System Reactor
Alexa for MSR, any interest?
MikeReadingtonM
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Telegram notification broke with latest update
3
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Phantom device, “INFO” appears
wmarcolinW
Topic thumbnail image
Multi-System Reactor
[RESOLVED] Mode Status NULL
wmarcolinW
Topic thumbnail image
Multi-System Reactor

[Solved] build 26150 - engine not starting

Scheduled Pinned Locked Moved Multi-System Reactor
8 Posts 2 Posters 636 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

    @toggledbits I pulled the image (well, Watchtower did) and within minutes the whole system went offline.

    The log looks like it ends with 26143.

    [latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mkahsmgf/26qq82mw-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lqyfljfi/22f8on0t-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lsb61rw8/24oenqi2-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/rule-lrh58he0:S-1c00gfib-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1c00dylr-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lrh58he0/1nam9w5u-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miuh2qqi/22ls4lql-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1vj8sdfc-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-kwc6rmci/rule-kwc6rmci:S-1qanz01x-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/24lq19p6-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-mk0o8iox/23oy468y-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-miscg2h3/rule-miscg2h3:S-22gmbq1c-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrfjke/238p0old-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-m7ccsso5/re-m7ccsso5-1r0myjxa-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/19nl9wq2-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3xk9t-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ladyja6a/rule-ladyja6a:S-yl3vv5m-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/re-ln7j2nqp-22mx9lzd-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-ln7j2nqp/22mx87c8-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-licneppy/1mzwe7ht-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-ml3194ih/25jqt1j4-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-kxgrg7kf/227hshak-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13ua1p95-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-reactorexmachina/13uagam7-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x4cbv-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-grpvl9oypg/rule-grpvl9oypg:R-134x2fyl-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#re-lscjrws1/238p5c22-cons
[latest-26143]2026-05-31T15:23:44.547Z <default:INFO> Closing container Container#Predicate#rule-lbwr0jvq/1xkczf03-cons
[latest-26143]2026-05-31T15:23:44.547Z <Structure:NOTICE> Structure Structure#1 stopped
[latest-26143]2026-05-31T15:23:44.547Z <app:NOTICE> Closing APIs...
[latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: closing...
[latest-26143]2026-05-31T15:23:44.547Z <wsapi:NOTICE> wsapi: disconnecting from "192.168.1.23#82" (1001 service closing)
[latest-26143]2026-05-31T15:23:44.548Z <httpapi:NOTICE> HTTP API closing...
[latest-26143]2026-05-31T15:23:44.549Z <wsapi:NOTICE> wsapi: server closed
[latest-26143]2026-05-31T15:23:44.549Z <httpapi:INFO> HTTP server closed.
[latest-26143]2026-05-31T15:23:44.549Z <app:NOTICE> Stopping timers...
[latest-26143]2026-05-31T15:23:44.551Z <app:null> Shutdown complete, process ID 1
[latest-26143]2026-05-31T15:23:44.551Z <app:null> Closing logs...
[latest-26143]2026-05-31T15:23:44.551Z <default:null> Closing log

    I can SSH to the VM. Alas, I do not have the previous image for 26143 as I'm a little too quick sometimes on housekeeping.

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

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

    *Prod MSR in docker/portainer
    MSR: latest-26193-8dd8f854
    MQTTController: 25139
    ZWave Controller: 25139

    1 Reply Last reply
    0
    • G Offline
      G Offline
      gwp1
      wrote on last edited by gwp1
      #2

      Following up here, did a backup restore of my Portainer VM from 05/29 (most recent) and MSR is back on 26143.

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

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

      *Prod MSR in docker/portainer
      MSR: latest-26193-8dd8f854
      MQTTController: 25139
      ZWave Controller: 25139

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

        Huh. I'm running the 26150 amd64 container with no issue... sure would be nice to have logs. If you go for them, startup is where it's at, and you may need to look at the container syslog if an error is being thrown before the logger is up and running. Some early message get written to the console, and that usually ends up directed to the system logs.

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

        G 2 Replies Last reply
        0
        • toggledbitsT toggledbits

          Huh. I'm running the 26150 amd64 container with no issue... sure would be nice to have logs. If you go for them, startup is where it's at, and you may need to look at the container syslog if an error is being thrown before the logger is up and running. Some early message get written to the console, and that usually ends up directed to the system logs.

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

          @toggledbits if I have time here I'll try to pull the image again and capture logging.

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

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

          *Prod MSR in docker/portainer
          MSR: latest-26193-8dd8f854
          MQTTController: 25139
          ZWave Controller: 25139

          1 Reply Last reply
          0
          • toggledbitsT toggledbits

            Huh. I'm running the 26150 amd64 container with no issue... sure would be nice to have logs. If you go for them, startup is where it's at, and you may need to look at the container syslog if an error is being thrown before the logger is up and running. Some early message get written to the console, and that usually ends up directed to the system logs.

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

            @toggledbits Repulled, same thing happened: unreachable.

            2026-05-31T19:33:04.533976919Z     at wrapModuleLoad (node:internal/modules/cjs/loader:255:19)
2026-05-31T19:33:04.533978974Z     at Module.require (node:internal/modules/cjs/loader:1600:12)
2026-05-31T19:33:04.533980967Z     at require (node:internal/modules/helpers:153:16)
2026-05-31T19:33:04.533983008Z 
2026-05-31T19:33:04.533984917Z Node.js v24.16.0
2026-05-31T19:33:56.035775922Z Reactor latest-26150-7b86db04 app 26150 configuration from /var/reactor/config
2026-05-31T19:33:56.053129729Z NODE_PATH /opt/reactor:/opt/reactor/node_modules
2026-05-31T19:33:56.054371749Z Failed to parse /var/reactor/config/logging.yaml YAMLException: bad indentation of a mapping entry in "/var/reactor/config/logging.yaml" (56:34)
2026-05-31T19:33:56.054391711Z 
2026-05-31T19:33:56.054396228Z  53 |     - type: file  # filename is derived from rule ID
2026-05-31T19:33:56.054399741Z  54 |       keep: 2
2026-05-31T19:33:56.054402822Z  55 |       level: 999
2026-05-31T19:33:56.054405736Z  56 |       recycle: true#      recycle: true
2026-05-31T19:33:56.054408789Z ---------------------------------------^
2026-05-31T19:33:56.054456413Z At about line 55; near
2026-05-31T19:33:56.054461049Z    >    level: 5
2026-05-31T19:33:56.054464372Z    >    streams:
2026-05-31T19:33:56.054509289Z    >    - type: file  # filename is derived from rule ID
2026-05-31T19:33:56.054513314Z    >      keep: 2
2026-05-31T19:33:56.054515586Z    >      level: 999
2026-05-31T19:33:56.054517599Z    >      recycle: true#      recycle: true
2026-05-31T19:33:56.054478049Z Use https://yamlvalidator.com/ and correct all indicated errors.
2026-05-31T19:33:56.054522741Z failed to read configuration file /var/reactor/config/logging.yaml; attemping last-known-good
2026-05-31T19:33:56.054619109Z unable to load configuration data for logging
2026-05-31T19:33:56.056778406Z /opt/reactor/server/lib/Logger.js:429
2026-05-31T19:33:56.056793267Z         const _0x98a8e2 = a22_0xf250f4, _0x36af7e = log_config['getConfig'](_0x98a8e2(0x14d), _0x98a8e2(0xfd), {});
2026-05-31T19:33:56.056795940Z                                                               ^
2026-05-31T19:33:56.056798247Z 
2026-05-31T19:33:56.056800114Z TypeError: Cannot read properties of undefined (reading 'getConfig')
2026-05-31T19:33:56.056801991Z     at Logger.getLogger (/opt/reactor/server/lib/Logger.js:429:63)
2026-05-31T19:33:56.056803906Z     at Logger.getDefaultLogger (/opt/reactor/server/lib/Logger.js:460:40)
2026-05-31T19:33:56.056805752Z     at Object.<anonymous> (/opt/reactor/server/lib/Logger.js:761:619)
2026-05-31T19:33:56.056807789Z     at Module._compile (node:internal/modules/cjs/loader:1854:14)
2026-05-31T19:33:56.056809659Z     at Object..js (node:internal/modules/cjs/loader:1985:10)
2026-05-31T19:33:56.056811482Z     at Module.load (node:internal/modules/cjs/loader:1577:32)
2026-05-31T19:33:56.056813567Z     at Module._load (node:internal/modules/cjs/loader:1379:12)
2026-05-31T19:33:56.056815388Z     at wrapModuleLoad (node:internal/modules/cjs/loader:255:19)
2026-05-31T19:33:56.056817221Z     at Module.require (node:internal/modules/cjs/loader:1600:12)
2026-05-31T19:33:56.056819018Z     at require (node:internal/modules/helpers:153:16)
2026-05-31T19:33:56.056820871Z 
2026-05-31T19:33:56.056822616Z Node.js v24.16.0

            This is what the container logs show.

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

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

            *Prod MSR in docker/portainer
            MSR: latest-26193-8dd8f854
            MQTTController: 25139
            ZWave Controller: 25139

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

              Did you read the log entries? Pretty strong starting point there...

              The logs are showing that your logging.yaml has an unrecoverable error. First, check to make sure you have only spaces, no tabs, for indenting.

              If that's not it, indent the - type: file line two spaces, as well as the keep, level, and recycle lines that follow it.

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

              G 1 Reply Last reply
              1
              • toggledbitsT toggledbits

                Did you read the log entries? Pretty strong starting point there...

                The logs are showing that your logging.yaml has an unrecoverable error. First, check to make sure you have only spaces, no tabs, for indenting.

                If that's not it, indent the - type: file line two spaces, as well as the keep, level, and recycle lines that follow it.

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

                @toggledbits I checked, rechecked, RErechecked and couldn't find any issue with that YAML.

                That being said, I completely removed the extra rule logging I had added and restarted. Brought down the new image and everything is fine.

                So... my question NOW is: why did it run fine until this build? That logging has been there for several weeks.

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

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

                *Prod MSR in docker/portainer
                MSR: latest-26193-8dd8f854
                MQTTController: 25139
                ZWave Controller: 25139

                toggledbitsT 1 Reply Last reply
                0
                • G gwp1

                  @toggledbits I checked, rechecked, RErechecked and couldn't find any issue with that YAML.

                  That being said, I completely removed the extra rule logging I had added and restarted. Brought down the new image and everything is fine.

                  So... my question NOW is: why did it run fine until this build? That logging has been there for several weeks.

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

                  @gwp1 said in [Solved] build 26150 - engine not starting:

                  @toggledbits I checked, rechecked, RErechecked and couldn't find any issue with that YAML.

                  Upload it to me, I'd like to take a look.

                  @gwp1 said in [Solved] build 26150 - engine not starting:

                  So... my question NOW is: why did it run fine until this build? That logging has been there for several weeks.

                  No idea. But, having once gotten a clean startup, it now has a last known good version of that config file, so whatever it's not happy with won't prevent startup in future.

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

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

                  Recent Topics

                  • [MSR] Native fan capabilty
                    therealdbT
                    therealdb
                    1
                    1
                    28
                  • [MSR] Rule do not fire
                    therealdbT
                    therealdb
                    0
                    4
                    85
                  • Rule condition shows TRUE in UI but Rule never transitions to SET — survives full restart
                    N
                    noelab
                    0
                    8
                    166
                  • DynamicGroupController and attributes
                    toggledbitsT
                    toggledbits
                    1
                    9
                    293
                  • Reactor (Multi-System/Multi-Hub) Announcements
                    toggledbitsT
                    toggledbits
                    5
                    149
                    138.0k
                  • Unofficial thread for compatibility
                    tunnusT
                    tunnus
                    2
                    2
                    734
                  • Ooops - Deleted Reactor Ex Machina II
                    toggledbitsT
                    toggledbits
                    0
                    2
                    87
                  • Bail out of failed reaction?
                    T
                    tamorgen
                    0
                    3
                    143
                  • Arming Envisalink panel from MSR
                    T
                    tamorgen
                    0
                    7
                    366
                  • [Solved] DynamicGroupController updating members issue
                    CrilleC
                    Crille
                    0
                    5
                    260
                  • Upgrade Issues
                    T
                    tbully
                    0
                    9
                    396
                  • [SOLVED] Conflicting Set Reaction Groups Appear to Fire Simultaneously in Single Rule Evaluation
                    toggledbitsT
                    toggledbits
                    0
                    10
                    508
                  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