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
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
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
[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
Reactor Loading Screen Safari
S
Topic thumbnail image
Multi-System Reactor
Constraints states visually do not match actual
S
Topic thumbnail image
Multi-System Reactor
[MSR] Feature request: For Each action on arrays/groups
therealdbT
Topic thumbnail image
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 876 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

                • Access control - allowing anonymous user to dashboard
                  toggledbitsT
                  toggledbits
                  0
                  2
                  43
                • VEC Virtual Switch Auto Off
                  S
                  SweetGenius
                  1
                  1
                  34
                • Upcoming Storage Change -- Got Back-ups?
                  toggledbitsT
                  toggledbits
                  2
                  1
                  29
                • Oddness in Copy/Move of Reactions
                  G
                  gwp1
                  0
                  1
                  63
                • [Solved] function isRuleEnabled() issue
                  CrilleC
                  Crille
                  0
                  4
                  91
                • [Reactor] Problem with Global Reactions and groups
                  therealdbT
                  therealdb
                  0
                  3
                  106
                • Possible feature request 2?
                  CatmanV2C
                  CatmanV2
                  0
                  3
                  78
                • Reactor (Multi-System/Multi-Hub) Announcements
                  toggledbitsT
                  toggledbits
                  5
                  133
                  80.1k
                • Genuinely impressed with Zigbee and HA / Reactor
                  CatmanV2C
                  CatmanV2
                  1
                  9
                  391
                • Copying a global reaction
                  toggledbitsT
                  toggledbits
                  0
                  3
                  117
                • [HowTo] Using HABridge with Reactor
                  CatmanV2C
                  CatmanV2
                  0
                  9
                  452
                • [Reactor] Bug when sending MQTT boolean payloads
                  toggledbitsT
                  toggledbits
                  0
                  4
                  173
                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