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
Gradually turn on lights.
Tom_DT
I have several lights that I would like to turn on very gradually over 15 or 20 seconds. from 0 to .25 in .01 increments. I have tried a few things that came nowhere near working, so here I am.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor
Error After Upgrade
T
Topic thumbnail image
Multi-System Reactor
Reset attribute value of entity in event handler
R
Topic thumbnail image
Multi-System Reactor
Need help figuring out how to delay a reset on reaction
T
Topic thumbnail image
Multi-System Reactor
Way to search for rules (rule state) in other rules
T
@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of. Thanks.
Multi-System Reactor
Links to MSR from HA
Tom_DT
I am using Home Assistant a lot recently. On a dashboard showing the devices, I would like to show a link to the MSR rule that controls the devices. Is there a way to link directly into MSR?
Multi-System Reactor
Set Reaction > Script Action
wmarcolinW
Topic thumbnail image
Multi-System Reactor
Errors after updating to MQTTController build 25139
tunnusT
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI: An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump Last 11:20:37 An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status Last 11:20:37 My MQTT configuration (local_mqtt_devices.yaml) for the related entity is: layzspa_message: type: ValueSensor capabilities: ["temperature_sensor", "value_sensor", "power_sensor"] primary_attribute: power_sensor.value events: "layzspa/message": "power_sensor.value": json_payload: true if_expr: '! isnull( payload?.PWR )' expr: "float(payload.PWR)" "value_sensor.air": json_payload: true if_expr: '! isnull( payload?.AIR )' expr: "float(payload.AIR)" "value_sensor.pump": json_payload: true if_expr: '! isnull( payload?.FLT )' expr: "float(payload.FLT)" "value_sensor.god": json_payload: true if_expr: '! isnull( payload?.GOD )' expr: "float(payload.GOD)" "value_sensor.lock": json_payload: true if_expr: '! isnull( payload?.LCK )' expr: "float(payload.LCK)" "value_sensor.unit": json_payload: true if_expr: '! isnull( payload?.UNT )' expr: "float(payload.UNT)" "value_sensor.error": json_payload: true if_expr: '! isnull( payload?.ERR )' expr: "float(payload.ERR)" "temperature_sensor.green": json_payload: true if_expr: '! isnull( payload?.GRN )' expr: "float(payload.GRN)" "temperature_sensor.red": json_payload: true if_expr: '! isnull( payload?.RED )' expr: "float(payload.RED)" "temperature_sensor.target": json_payload: true if_expr: '! isnull( payload?.TGT )' expr: "float(payload.TGT)" "temperature_sensor.value": json_payload: true if_expr: '! isnull( payload?.TMP )' expr: "float(payload.TMP)" "temperature_sensor.virtual": json_payload: true if_expr: '! isnull( payload?.VTM )' expr: "round(float(payload.VTM), 1)" "temperature_sensor.ambient": json_payload: true if_expr: '! isnull( payload?.AMB )' expr: "float(payload.AMB)" "layzspa/Status": "value_sensor.status": if_expr: '! isnull( payload )' expr: "payload" "layzspa/button": "value_sensor.button": if_expr: '! isnull( payload )' expr: "payload" and in reactor.yaml I have: "layzspa_states": name: "Lay-Z-Spa States" friendly_name: 'Lay-Z-Spa States' include: layzspa_message I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Multi-System Reactor
🎉 My very first MSR controller: OpenSprinkler
therealdbT
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded). Get it at (install is similar to MQTTController and such): https://github.com/dbochicchio/reactor-opensprinkler Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty. Since I've learnt a lot from this controller, I'll explore new controllers soon.
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

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 457 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

                • Gradually turn on lights.
                  G
                  gwp1
                  0
                  4
                  132

                • Stop the MSR by an external switch on Hubitat.
                  wmarcolinW
                  wmarcolin
                  0
                  1
                  30

                • Error After Upgrade
                  G
                  gwp1
                  0
                  4
                  103

                • Reset attribute value of entity in event handler
                  R
                  RHCPNG
                  0
                  5
                  201

                • Need help figuring out how to delay a reset on reaction
                  G
                  gwp1
                  0
                  22
                  925

                • Way to search for rules (rule state) in other rules
                  T
                  tamorgen
                  0
                  3
                  99

                • Links to MSR from HA
                  Tom_DT
                  Tom_D
                  0
                  1
                  90

                • Set Reaction > Script Action
                  wmarcolinW
                  wmarcolin
                  0
                  11
                  433

                • Wiring Samotech SM308-S into light fitting
                  akbooerA
                  akbooer
                  0
                  2
                  146

                • Errors after updating to MQTTController build 25139
                  toggledbitsT
                  toggledbits
                  0
                  6
                  236

                • 🎉 My very first MSR controller: OpenSprinkler
                  therealdbT
                  therealdb
                  5
                  13
                  917

                • Advice reqeusted to migrate MSR from Bare Metal to Container
                  T
                  tamorgen
                  0
                  5
                  260
                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