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. Reactor (running in HA as Addon) Rules not seeing Entitiy Attribute updates on Envisalink Keypad entity
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Advice reqeusted to migrate MSR from Bare Metal to Container
T
Good day all, I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing. I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container. Has anyone done this? Any advice?
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
Can´t restart or upgrade/deploy MSR
F
Topic thumbnail image
Multi-System Reactor
[Solved] Limit HA Entity in MSR
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Organizing/ structuring rule sets and rules
R
Hi guys, Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular. Maybe there are better ways to organize my rule sets. I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT
Topic thumbnail image
Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M
Topic thumbnail image
Multi-System Reactor
Need help reducing false positive notifications
T
Topic thumbnail image
Multi-System Reactor
Deleting widgets
tunnusT
Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266
Multi-System Reactor
MQTT configuration question
tunnusT
I have the following yaml configuration in local_mqtt_devices file x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }' While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Multi-System Reactor
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

Reactor (running in HA as Addon) Rules not seeing Entitiy Attribute updates on Envisalink Keypad entity

Scheduled Pinned Locked Moved Solved Multi-System Reactor
7 Posts 2 Posters 396 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.
  • C Offline
    C Offline
    cd12172
    wrote on last edited by
    #1

    I am ~6hrs into a Vera to HA migration. Lots to learn - and I will never make 5 steps to hit a light switch..

    This example is exploratory - not the end workflow I am looking for. This is not a logic concern, the issue is I may not be reading attributes on entities correctly.

    End Goal -
    Dim/control on lights based on alarm states

    Environment-
    HA running in Virtualbox
    MSR running as Addon in HA
    Alarm connected to Envisalink EVL 3 card in a DSC alarm panel

    Functionality that works
    I can arm/disarm the house from the HA dash
    I can read attribute status in entity viewer attribute pull down
    I have working rule sets for other devices (lutron) on network

    Problem-
    As I "Arm" the house using a button on the HA Dashboard, I see attributes update in realtime.

    In MSR, the attributes are not updating. In the MSR entity viewr, I can see updates were observed much earlier in the day.

    I fear I cannot articulate the issue as I am so new to HA. I used Reactor in Vera, but very new to MSR and HA. The attached screenshot will show the side by side dialogs that are not staying in sync.

    Thanks in advance for any insight.
    HA-MSR Screeshot.JPG

    1 Reply Last reply
    0
    • PablaP Offline
      PablaP Offline
      Pabla
      wrote on last edited by
      #2

      Going to need to know a few more things like what version of MSR and HA you are running and some logs

      1 Reply Last reply
      0
      • C Offline
        C Offline
        cd12172
        wrote on last edited by
        #3

        Versions…
        Core
        2023.12.3
        Supervisor
        2023.11.6
        Operating System
        11.2
        Frontend
        20231208.2

        Reactor 0.0.8

        I lack the privileges to upload logs, sorry for the paste…

        2023-12-18 02:11:24,170 CRIT Supervisor is running as root. Privileges were not dropped because no user is specified in the config file. If you intend to run as root, you can set user=root in the config file to avoid this message.
        2023-12-18 02:11:24,204 INFO RPC interface 'supervisor' initialized
        2023-12-18 02:11:24,206 CRIT Server 'unix_http_server' running without any HTTP authentication checking
        2023-12-18 02:11:24,207 INFO supervisord started with pid 1
        2023-12-18 02:11:25,218 INFO spawned: 'nginx' with pid 8
        2023-12-18 02:11:25,224 INFO spawned: 'reactor' with pid 9
        Using existing set-up
        Reactor Token is set, updating config
        symlink does not exist, create it
        2023-12-18 02:11:26,683 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
        2023-12-18 02:11:26,684 INFO success: reactor entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
        Reactor latest-23063-c464b685 app 22364 configuration from /config/reactor
        NODE_PATH /opt/reactor:/opt/reactor/node_modules
        [latest-23063]2023-12-18T02:11:27.249Z app:null Reactor build latest-23063-c464b685 starting on v16.15.1
        [latest-23063]2023-12-18T02:11:27.254Z app:null Process ID 24 user/group 0/0; docker; platform linux/x64 #1 SMP PREEMPT_DYNAMIC Mon Dec 4 15:31:27 UTC 2023; locale (undefined)
        [latest-23063]2023-12-18T02:11:27.256Z app:null Basedir /opt/reactor; data in /var/reactor/storage
        [latest-23063]2023-12-18T02:11:27.257Z app:null NODE_PATH=/opt/reactor:/opt/reactor/node_modules
        [latest-23063]2023-12-18T02:11:27.725Z Structure:null Module Structure v22323
        [latest-23063]2023-12-18T02:11:27.730Z Capabilities:null Module Capabilities v22356
        [latest-23063]2023-12-18T02:11:28.213Z Plugin:null Module Plugin v22300
        [latest-23063]2023-12-18T02:11:28.230Z TimerBroker:null Module TimerBroker v22283
        [latest-23063]2023-12-18T02:11:28.243Z Entity:null Module Entity v22353
        [latest-23063]2023-12-18T02:11:28.253Z Controller:null Module Controller v23044
        [latest-23063]2023-12-18T02:11:28.287Z default:null Module Ruleset v22293
        [latest-23063]2023-12-18T02:11:28.294Z default:null Module Rulesets v22146
        [latest-23063]2023-12-18T02:11:28.323Z GlobalExpression:null Module GlobalExpression v22146
        [latest-23063]2023-12-18T02:11:28.363Z Predicate:null Module Predicate v22345
        [latest-23063]2023-12-18T02:11:28.400Z AlertManager:null Module AlertManager v22283
        [latest-23063]2023-12-18T02:11:28.407Z Rule:null Module Rule v22345
        [latest-23063]2023-12-18T02:11:28.420Z GlobalReaction:null Module GlobalReaction v22324
        [latest-23063]2023-12-18T02:11:28.425Z Engine:null Module Engine v23001
        [latest-23063]2023-12-18T02:11:28.434Z httpapi:null Module httpapi v23058
        [latest-23063]2023-12-18T02:11:28.593Z wsapi:null Module wsapi v23053
        [latest-23063]2023-12-18T02:11:28.910Z TaskQueue:null Module TaskQueue 21351
        [latest-23063]2023-12-18T02:11:28.912Z VeraController:null Module VeraController v22325
        [latest-23063]2023-12-18T02:11:29.355Z HassController:null Module HassController v23060
        [latest-23063]2023-12-18T02:11:29.958Z DynamicGroupController:null Module DynamicGroupController v22313
        [latest-23063]2023-12-18T02:11:29.974Z SystemController:null Module SystemController v22306

        1 Reply Last reply
        0
        • PablaP Offline
          PablaP Offline
          Pabla
          wrote on last edited by
          #4

          excellent thanks, could you post a clearer screenshot of your rule? Its a little blurry can't really see much

          1 Reply Last reply
          0
          • C Offline
            C Offline
            cd12172
            wrote on last edited by
            #5

            HI /Thanks. The rule is attached as asked.

            There are some relevant facts that "might" be at the root-
            A) I moved this HA via backup/restore. The IP Addr of HA changed. It was in a HyperV VM previously, I don't know if the attributes were updating in that enviro, but the entity history view indicate it was wired up at some point. It 'may' have broken in the restore - but I am also unsure if history comes over in a restore...

            😎 My environment seems to be rubbish. In HASS I have the Vera integration, exposing the devices/scenes. In MSR (AddOn under HASS) I have a pointer to the external Vera. I think MSR wants to live in its own environment, and be the overwatch marrying Vera and HASS, i.e. I can lose the Vera integration in HASS. As long as you are reviewing the issue I will leave all as is, but the plan is to seperate these components.

            c) Between your last response and now, considering "A" above. The new HASS instance has a new IP Addr, I updated Reactor.YAML in the controllers section as below. After restarting, I can confirm Reactor is wired to Lutron devices connected direct to HASS through an integration (not through Vera). The Envisalink Alarm is still not wired to MSR.

            Reactor.YAML changes made are below

            • id: hass
              enabled: true
              implementation: HassController
              name: This Home Assistant
              config:
              source: "ws://192.168.1.243:8123"
              access_token:
              Capture.JPG
            1 Reply Last reply
            0
            • C Offline
              C Offline
              cd12172
              wrote on last edited by
              #6

              This is now resolved. There were a few issues.

              1- The Envisalink hardware EVL3 only sends alerts to a single listener (TPI). It needed a reboot
              2-My Backup Restore resulted in the incorrect IP address in Reactor.YAML contributed.

              Thanks/Sorry

              1 Reply Last reply
              1
              • PablaP Offline
                PablaP Offline
                Pabla
                wrote on last edited by
                #7

                Happy to hear it worked out!! Just a tip if you chose to control your Envisalink through HA-Envisalink and not HA-Vera-Enivsalink take a look at this integration. It has a few more features than the native Envisalink integration.

                1 Reply Last reply
                0
                • C cd12172 marked this topic as a question on
                • C cd12172 has marked this topic as solved on
                • toggledbitsT toggledbits locked this topic on
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes

                Recent Topics

                • Set Reaction > Script Action
                  CrilleC
                  Crille
                  0
                  2
                  9
                • Advice reqeusted to migrate MSR from Bare Metal to Container
                  T
                  tamorgen
                  0
                  5
                  71
                • Reactor (Multi-System/Multi-Hub) Announcements
                  toggledbitsT
                  toggledbits
                  5
                  122
                  37.3k
                • Z-Wave Future....
                  CatmanV2C
                  CatmanV2
                  0
                  5
                  160
                • Can´t restart or upgrade/deploy MSR
                  toggledbitsT
                  toggledbits
                  0
                  4
                  111
                • [Solved] Limit HA Entity in MSR
                  wmarcolinW
                  wmarcolin
                  0
                  7
                  230
                • Disaster recovery and virtualisation
                  CatmanV2C
                  CatmanV2
                  0
                  5
                  685
                • Remote access of Zwave stick from Z-wave server
                  CatmanV2C
                  CatmanV2
                  0
                  3
                  402
                • Organizing/ structuring rule sets and rules
                  G
                  gwp1
                  0
                  5
                  396
                • Moving MSR from a QNAP container to RP 5 - some issues
                  G
                  gwp1
                  0
                  5
                  373
                • Widget deletion does not work and landing page (status) is empy
                  G
                  gwp1
                  0
                  4
                  361
                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