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.
C

cd12172

@cd12172
Access control - allowing anonymous user to dashboard
tunnusT
Using build 25328 and having the following users.yaml configuration: users: # This section defines your valid users. admin: ******* groups: # This section defines your user groups. Optionally, it defines application # and API access restrictions (ACLs) for the group. Users may belong to # more than one group. Again, no required or special groups here. admin_group: users: - admin applications: true # special form allows access to ALL applications guests: users: "*" applications: - dashboard api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin_group allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: true session: timeout: 7200 # (seconds) rolling: true # activity extends timeout when true # If log_acls is true, the selected ACL for every API access is logged. log_acls: true # If debug_acls is true, even more information about ACL selection is logged. debug_acls: true My goal is to allow anonymous user to dashboard, but MSR is still asking for a password when trying to access that. Nothing in the logs related to dashboard access. Probably an error in the configuration, but help needed to find that. Tried to put url: "/dashboard" under api_acls, but that was a long shot and didn't work.
Multi-System Reactor
VEC Virtual Switch Auto Off
S
I use Virtual Entity Controller virtual switches which I turn on via webhooks from other applications. Once a switch triggers and turns on, I can then activate associated rules. I would like each virtual switch to automatically turn off after a configurable time (e.g., 5 seconds, 10 seconds). Is there a better way to achieve this auto-off behavior instead of creating a separate rule for each switch that uses the 'Condition must be sustained for' option to turn it off? With a large number of these switches (and the associated turn-off rules), I'm checking to see if there is a simpler approach.If not, could this be a feature request to add an auto-off timer directly to the virtual switches. Thanks Reactor (Multi-hub) latest-26011-c621bbc7 VirtualEntityController v25356 Synology Docker
Multi-System Reactor
Upcoming Storage Change -- Got Back-ups?
toggledbitsT
TL;DR: Format of data in storage directory will soon change. Make sure you are backing up the contents of that directory in its entirety, and you preserve your backups for an extended period, particularly the backup you take right before upgrading to the build containing this change (date of that is still to be determined, but soon). The old data format will remain readable (so you'll be able to read your pre-change backups) for the foreseeable future. In support of a number of other changes in the works, I have found it necessary to change the storage format for Reactor objects in storage at the physical level. Until now, plain, standard JSON has been used to store the data (everything under the storage directory). This has served well, but has a few limitations, including no real support for native JavaScript objects like Date, Map, Set, and others. It also is unable to store data that contains "loops" — objects that reference themselves in some way. I'm not sure exactly when, but in the not-too-distant future I will publish a build using the new data format. It will automatically convert existing JSON data to the new format. For the moment, it will save data in both the new format and the old JSON format, preferring the former when loading data from storage. I have been running my own home with this new format for several months, and have no issues with data loss or corruption. A few other things to know: If you are not already backing up your storage directory, you should be. At a minimum, back this directory up every time you make big changes to your Rules, Reactions, etc. Your existing JSON-format backups will continue to be readable for the long-term (years). The code that loads data from these files looks for the new file format first (which will have a .dval suffix), and if not found, will happily read (and convert) a same-basenamed .json file (i.e. it looks for ruleid.dval first, and if it doesn't find it, it tries to load ruleid.json). I'll publish detailed instructions for restoring from old backups when the build is posted (it's easy). The new .dval files are not directly human-readable or editable as easily as the old .json files. A new utility will be provided in the tools directory to convert .dval data to .json format, which you can then read or edit if you find that necessary. However, that may not work for all future data, as my intent is to make more native JavaScript objects directly storable, and many of those objects cannot be stored in JSON. You may need to modify your backup tools/scripts to pick up the new files: if you explicitly name .json files (rather than just specifying the entire storage directory) in your backup configuration, you will need to add .dval files to get a complete, accurate backup. I don't think this will be an issue for any of you; I imagine that you're all just backing up the entire contents of storage regardless of format/name, that is the safest (and IMO most correct) way to go (if that's not what you're doing, consider changing your approach). The current code stores the data in both the .dval form and the .json form to hedge against any real-world problems I don't encounter in my own use. Some future build will drop this redundancy (i.e. save only to .dval form). However, the read code for the .json form will remain in any case. This applies only to persistent storage that Reactor creates and controls under the storage tree. All other JSON data files (e.g. device data for Controllers) are unaffected by this change and will remain in that form. YAML files are also unaffected by this change. This thread is open for any questions or concerns.
Multi-System Reactor
Oddness in Copy/Move of Reactions
G
Topic thumbnail image
Multi-System Reactor
[Solved] function isRuleEnabled() issue
CrilleC
Topic thumbnail image
Multi-System Reactor
[Reactor] Problem with Global Reactions and groups
therealdbT
Topic thumbnail image
Multi-System Reactor
Possible feature request 2?
CatmanV2C
Just another thought. Adding devices from my Home Assistant / Zigbee2MQTT integration. Works perfectly but they always add as their IEEE address. Some of these devices have up to 10 entities associated, and the moment they are renamed to something sensible, each of those entities 'ceases to exist' in MSR. I like things tidy, and deleting each defunct entity needs 3 clicks. Any chance of a 'bulk delete' option? No biggy as I've pretty much finished my Z-wave migration and I don't expect to be adding more than 2 new Zigbee devices Cheers C
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
Genuinely impressed with Zigbee and HA / Reactor
CatmanV2C
Just for the record, in case anyone is following, I'm really rather impressed. I have installed one of these: https://www.amazon.co.uk/dp/B0B6P22YJC?ref=ppx_yo2ov_dt_b_fed_asin_title&th=1 That's connected (physically) to the VM running on my Synology, with a 2m USB extension. The same host also runs Openluup, Mosquito, HA Bridge. Yesterday I installed Zigbee2mqtt. That was a bit of a PITA but mostly because of ports and permissions. Once up and running, and the correct boxes ticked, immediately visible in Home Assistant via the MQTT integration, and thence into Reactor I've only got two devices. I bought the cheapest sensor I could find, which is a door sensor. Dead easy to add to ZIgbee2mqtt and again, immediately visible in HA. https://www.amazon.co.uk/dp/B0FPQLWRW1?ref=ppx_yo2ov_dt_b_fed_asin_title The dongle is on the top floor of the house, and I wanted the sensor on the back door (just about as far apart as it's possible to get short of going into the garage) When I moved the sensor downstairs it dropped out pretty instantly (which wasn't a huge surprise) so quick bit of research found out that smart plugs will act as routers so... https://www.amazon.co.uk/dp/B0FDQDPGBB?ref=ppx_yo2ov_dt_b_fed_asin_title Took me about 30 seconds to connect. Updated the name. Instantly visible in Reactor with the new name pushed over from Zigbee2mqtt. And lo, the door sensor now has a signal of 140 and works as far as I can tell perfectly and instantly (unlike my z-wave one). A few more of those will be purchased and used to replace the Tuya wifi cloud devices and the (continually failing) Z-wave plugs (yeah, they were TKB so....) Commended to the house. Thanks for everyone that got me on the right lines. C
Zigbee
Copying a global reaction
tunnusT
With build 25328, if you copy a global reaction, a new reaction does not appear in the UI unless you do a refresh. I recall this used to work without needing this page refresh? Anyway, only a minor nuisance.
Multi-System Reactor
[HowTo] Using HABridge with Reactor
therealdbT
If you’re like me and still running HABridge to control your devices locally via Alexa, you might need to tweak your endpoints to call Reactor via HTTP. Here’s the best way to do it, IMO: Insert the Reactor Canonical ID (e.g., zwavejs>71-1) into the MapID field, but make sure it’s URL-encoded like this: zwavejs%3E71-1. Then, configure these endpoints as needed: On: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.on Off: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/power_switch.off Dim: For lights: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/dimming.set?level=${intensity.decimal_percent} For roller shutters: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/position.set?value=${intensity.decimal_percent} Color: http://[ReactorIP]:8111/api/v1/entity/${device.mapId}/perform/rgb_color.set_rgb?red=${color.r}&green=${color.g}&blue=${color.b} Just replace [ReactorIP] with your actual IP address. By using these placeholders, you can standardize your endpoints across all devices, making maintenance easier. This setup works with any device mapped under MSR, regardless of the controller (ZWaveJS, Vera, HASS, OpenSprinkler, virtual, MQTT, DynamicEntities, etc.). If you need different calls, just go to the entities, get the action and parameters, and adjust accordingly. Enjoy super fast access to your devices via Alexa! If you're migrating from Vera, the endpoints are (URL-encoded) in a file called device.db, in JSON format, under your config. You'd write a script to align the new endpoints to the new one, if you prefer to do it automatically. YMMV.
How-To
[Reactor] Bug when sending MQTT boolean payloads
therealdbT
Topic thumbnail image
Multi-System Reactor
Difficulty defining repeating annual period
R
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Multi-System Reactor
Need help with sequence
T
Good evening all, For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time. Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed. Thanks.
Multi-System Reactor
Possible feature request?
CatmanV2C
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations. Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction? Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for. I guess it's something of an edge case so no huge issue. TIA! C
Multi-System Reactor
Logic Assistance: Exterior Lights on when Illuminance Below Threshold
PablaP
Topic thumbnail image
Multi-System Reactor
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
MQTT templates for ZIgbee scene controller, or a better way?
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reset a delay
CatmanV2C
I'm sure this has been asked, and answered, but damned if I can figure it out Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage. Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts. After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!) What I would like is for the 3 minute delay until the lights go off to start from the latest door open event. That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity. I've tried 'hacking' with a virtual switch, but can't seem to stop the delay. Any pointers? TIA C
Multi-System Reactor
Zigbee2mqtt installed! sytemctl not happy :(
CatmanV2C
Hello oh great ones. After a couple of hours messing with ports and permissions I have Zigbee2mqtt installed and running on my virtual pi Can connect to the front end and everything Odd one though, simply cannot get systemctl to work and the error is, well, unhelpful. The service file is this: [Unit] Description=zigbee2mqtt After=network.target [Service] Environment=NODE_ENV=production Type=notify ExecStart=/usr/local/bin/node index.js WorkingDirectory=/opt/zigbee2mqtt StandardOutput=inherit # Or use StandardOutput=null if you don't want Zigbee2MQTT messages filling syslog, for more options see systemd.exec(5) StandardError=inherit WatchdogSec=10s Restart=always RestartSec=10s User=pi [Install] WantedBy=multi-user.target Straight out of the docs with the change to point to my local node install (which we know works as it's the same as the very fine Reactor is using. Running manually pnpm start in /opt/zigbee2mqtt works fine However: catman@openluup:/etc/systemd/system$ sudo systemctl start zigbee2mqtt.service Job for zigbee2mqtt.service failed because the control process exited with error code. See "systemctl status zigbee2mqtt.service" and "journalctl -xe" for details. Which I have catman@openluup:/etc/systemd/system$ sudo systemctl status zigbee2mqtt.service ● zigbee2mqtt.service - zigbee2mqtt Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; disabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Tue 2025-12-16 12:32:42 GMT; 4s ago Process: 3093 ExecStart=/usr/local/bin/node index.js (code=exited, status=217/USER) Main PID: 3093 (code=exited, status=217/USER) and -- A start job for unit zigbee2mqtt.service has begun execution. -- -- The job identifier is 17477. Dec 16 12:35:16 openluup systemd[3178]: zigbee2mqtt.service: Failed to determine user credentials: No such process Dec 16 12:35:16 openluup systemd[3178]: zigbee2mqtt.service: Failed at step USER spawning /usr/local/bin/node: No such process -- Subject: Process /usr/local/bin/node could not be executed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The process /usr/local/bin/node could not be executed and failed. -- -- The error number returned by this process is ERRNO. Dec 16 12:35:16 openluup systemd[1]: zigbee2mqtt.service: Main process exited, code=exited, status=217/USER -- Subject: Unit process exited -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- An ExecStart= process belonging to unit zigbee2mqtt.service has exited. -- -- The process' exit code is 'exited' and its exit status is 217. Dec 16 12:35:16 openluup systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit zigbee2mqtt.service has entered the 'failed' state with result 'exit-code'. Dec 16 12:35:16 openluup systemd[1]: Failed to start zigbee2mqtt. -- Subject: A start job for unit zigbee2mqtt.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit zigbee2mqtt.service has finished with a failure. Which strikes me as very odd. Any blindingly obvious things I'm missing? TIA! C
Zigbee
About
Posts
13
Topics
6
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial
  • Is there a method to ignore a specific entity attribute (flapping)
    C cd12172

    Hi-

    I have an android media player entity publishing from HA. I watch for changes in transport state and media title to trigger some actions.

    Though those attributes report as expected, the set rule is being throttled for possible flapping.

    There is an attribute for media position that continually updates, I suspect it is causing the evaluations to run constantly.

    The workaround I am seeking is to ignore those attributes in HA or MSR. Anyone know how, or have a better idea??

    Thx
    Btw- this problem has spanned versions of HA and reactor, but I am current on both. Too current on HA for transparency, but the issue has survived several updates.

    Multi-System Reactor
  • JS Zwave / Kwikset PIN codes
    C cd12172

    Hi- looking for a hint in where to start. My goal is to set a PIN code in a zwave kwikset lock triggered in a rule.

    The device isn’t exposing methods to help. The x-hass.call-service looks promising, but what would the service name be?

    Plan b would be send the zwave controller a config command- I don’t see any way to explicitly send a command through JS Zwave in my environment.

    Running reactor bare metal. JS Zwave is running as an add on inside HASS OS.

    Any tips are appreciated.

    Multi-System Reactor
  • Reaction using Shell Command SSH
    C cd12172

    Update ot anyone trying to SSH from Multihub Reactor...

    I went to a linux bare metal install. Installing through the Add On store reset the docker image with every HASS restart. This means openSSH and the shared keys would disappear.

    Also - at time of writting the AddOn store version is out of date with no appearant activty. Likely to change, but I moved on to give more flexability to MSR.

    I look forward to the unintended consequences 🙂

    Multi-System Reactor
  • Reaction using Shell Command SSH
    C cd12172

    Hi (fourth draft to simplify as I solve problems...)

    My MSR is installed from the HASS add on store.

    The Docker container did not have SSH client installed.

    I was able to get SSH installed and setup keys on a remote worker server for password free SSH logins.

    I now have a shell command that sends commands to the remote worker server. It renders content to a tidbyt LED matrix display.

    Does anyone know if this will survive an update of the Reactor addon? Will the updated docker image wipe SSH and the private keys stored in the Reactor Docker Container?

    Also - is it better to just move Reactor over to the worker server and manage my own updates?

    I am using HAOS - Core-2024.1.2, Supervisor 2023.12.0, OS 11.3

    Multi-System Reactor
  • Bind Zooz Zen32 (HASS/ ZWAVE JS UI) Zwave events to MSR Conditions
    C cd12172

    Thanks - I referred to that post and a predesseor in my original post. I also went through the API documentation, still unable to trap events as a button.

    Multi-System Reactor zen32
  • Bind Zooz Zen32 (HASS/ ZWAVE JS UI) Zwave events to MSR Conditions
    C cd12172

    HI -

    Direct question-

    • is there anything obvious wrong with my configuration below
    • since the ZEN32 scene controller really has no on/off state (for btn 1-4), and I am using it as a toggle without concern for long press or multi press - am I better off just looking for any change to x_hass.state in a rule condition to trap a toggle?

    Detailed Use case -
    A-Use ZEN32 scene controller to group and control sonos players
    B-Keep ZEN32 lights sync'd with real world sonos states. [B is alread working in my implementation by controlling the always on/always off led parms on the ZEN32]

    Environment
    Reactor - latest-23063-c464b68
    hass - 2023.12.3 core / 2023.12.0 Supervisor
    Zwave JS UI - 9.3.2

    • the add ons are running on the hass instance in a virtualbox vm

    prior reading:
    Using Zooz ZEN32 Scene Controller as Trigger
    Adding remotes, scene controllers as entities to MSR
    MSR Manual - Handling Home Assistant Events

    **Current ZEN32 zwave description to MSR - reactor.yaml **

          event_targets:
        "event.sonos_scene_controller_scene_001":
          name: "ZEN32 Button 1"
          capabilities:
            - button
          events:
            - event:
                event_type: zwave_js_value_notification
                data:
                  node_id: 008 # Put your ZWaveJS node ID here
                  property: scene
                  property_key: "001" #  001=button 1, 002=button 2, etc.
              response:
                button.since:
                  from: event.context.id
                button.state:
                  from: event.data.value
                  map:
                    KeyHeldDown: hold
                    KeyPressed: single
                    KeyPressed2x: double
                    KeyPressed3x: triple
                    KeyReleased: release
        "event.sonos_scene_controller_scene_002":
          name: "ZEN32 Button 2"
          capabilities:
            - button
          events:
            - event:
                event_type: zwave_js_value_notification
                data:
                  node_id: 008 # Put your ZWaveJS node ID here
                  property: scene
                  property_key: "002" #  001=button 1, 002=button 2, etc.
              response:
                button.since:
                  from: event.context.id
                button.state:
                  from: event.data.value
                  map:
                    KeyHeldDown: hold
                    KeyPressed: single
                    KeyPressed2x: double
                    KeyPressed3x: triple
                    KeyReleased: release
                    #
                    # dump_all_states - This is for troubleshooting. Do not enable unless asked.
                    #dump_all_states: false

    Findings-
    -The Hass logbook is seeing the events - also seen in the screenshot below

    • no update to the MSR created "ZEN32 Button 1"
    • The MSR manual indicates my HASS version is newer than supported (2023.11.3). I am assuming the issue is in my config.

    Area of interest:

    • Is my cannonical names correct in the Reactor.YAML code above - I took it from the Reactor entity dialog screenshoted below i.e. event.sonos_scene_controller_scene_001

    Capture.JPG

    Multi-System Reactor zen32
  • Run 'Set Reaction' or 'Reset Reaction' from LAN (HTTP)
    C cd12172

    Nice- very flexible.

    Multi-System Reactor
  • Run 'Set Reaction' or 'Reset Reaction' from LAN (HTTP)
    C cd12172

    Great- thanks, it works

    Multi-System Reactor
  • Run 'Set Reaction' or 'Reset Reaction' from LAN (HTTP)
    C cd12172

    Hi - hoping someone can share the url syntax to force MSR to run a specific set or reset action of a Rule.

    Use case=
    -use MSR actions to set a scene
    -fire the reaction from a homebridge system on same LAN to manage voice commands

    I have done this in Vera, can't find the correct syntax for MSR.

    The command I tried from research is:
    http://192.168.1.243:8111/api/v1/reaction/re-lq8bnkvf/run

    I received "Not Found" using chrome No log entry - so I must be off on the URL.

    Reactor = latest-23063-c464b685
    MSR and Hass run on same ip addr
    Reactor port =8111
    HASS port=8123 (I tried this too)
    screen shot attached

    Capture.JPG

    Multi-System Reactor
  • Reactor (running in HA as Addon) Rules not seeing Entitiy Attribute updates on Envisalink Keypad entity
    C cd12172

    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

    Multi-System Reactor
  • Reactor (running in HA as Addon) Rules not seeing Entitiy Attribute updates on Envisalink Keypad entity
    C cd12172

    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
    Multi-System Reactor
  • Reactor (running in HA as Addon) Rules not seeing Entitiy Attribute updates on Envisalink Keypad entity
    C cd12172

    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

    Multi-System Reactor
  • Reactor (running in HA as Addon) Rules not seeing Entitiy Attribute updates on Envisalink Keypad entity
    C cd12172

    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

    Multi-System Reactor
  • Login
  • Don't have an account? Register
  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved