Navigation

    Discussion Forum to share and further the development of home control and automation, independent of platforms.

    SmartHome Community

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Unsolved
    (Last Updated: April 2, 2021)
    • MSR No longer Setting Reactions

      T

      Hello Everyone -

      I have a peculiar situation that I'm hoping to get some help with.

      Running Vera which is still handling my Zwave, MySensors, Zigbee, and still a balance of my Reactors.

      However, I've also been running MSR for several months in preparation for an eventual move off of Vera.

      Vera had one of its meltdowns this morning related to my Opensprinkler plug in.

      After getting that straightened out, I added the OpenSprinkler plugin to HAAS and that's when I started having issues.

      My existing MSR reactors (even simple ones) don't seem to fire their reactions. I can see the conditions go "true". If I manually fire the Reaction, it works fine.

      I do see this a lot in the logs:

      [1.0.2-21350]2022-05-16T19:02:44.518Z <Rule:INFO> Rule#rule-460 evaluation in progress; waiting for completion

      (Various rules - 460 is just an example)

      Is there anything I can do to further troubleshoot?

      Multi-System Reactor
    • Reactor (Multi-System/Multi-Hub) Announcements

      toggledbits

      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
    • MSR Telegram Messages Stopped Working

      T

      My MSR has been working flawlessly until a couple of days ago when it stopped sending Telegram Messages (or should I say they stopped getting through!). I have updated to MSR version 22004. The reactor.log is updating and is showing no errors:

      [latest-22004]2022-05-15T17:52:31.417Z Engine:NOTICE Starting reaction Message Test (re-l37h2fkj)
      [latest-22004]2022-05-15T17:52:31.417Z Engine:INFO Message Test all actions completed.
      [latest-22004]2022-05-15T17:52:31.704Z Engine:INFO Enqueueing "Message Test" (re-l37h2fkj)
      [latest-22004]2022-05-15T17:52:31.735Z Engine:NOTICE Starting reaction Message Test (re-l37h2fkj)
      [latest-22004]2022-05-15T17:52:31.736Z Engine:INFO Message Test all actions completed.
      [latest-22004]2022-05-15T17:52:32.007Z Engine:INFO Enqueueing "Message Test" (re-l37h2fkj)
      [latest-22004]2022-05-15T17:52:32.035Z Engine:NOTICE Starting reaction Message Test (re-l37h2fkj)
      [latest-22004]2022-05-15T17:52:32.036Z Engine:INFO Message Test all actions completed.
      [latest-22004]2022-05-15T17:52:41.324Z Engine:INFO Enqueueing "Variable Telegram Test" (re-kvnm57c3)

      If I use the following in my web browser the telegram message gets through:

      https://api.telegram.org/botxxxxx......./sendMessage?chat_id=xxxxx......&text=Test Message HTTPS

      I am running MSR on my QNAP network attached storage. Any assistance would be appreciated.

      Just another question...... I would like to post in the HOME HARDWARE VERA section of Smarthome, but I do not have the option to set up a new post. Do I need to request access for this?

      Multi-System Reactor
    • SSL Certificate for Multi System Reactor via LetsEncrypt

      W

      Details of runtime environment:

      Reactor (Multi-hub) stable-22055-9b40e12 Running as a service on Windows Server 2022 Std 21H2 Connecting to HASS (HASSOS) Is a migration WIP from OpenLuup/Reactor

      A complete description of your objective:

      Using LetsEncrypt, application "certifyTheWeb", retrieve and apply SSL certificate to Multi System Reactor

      A description of your approach/solution/implementation so far:

      Reviewed Config files, can't seen mention of certificate files in there

      Actual Question:

      How do I apply a certificate to whatever web server Reactor uses? I'm familiar with managing certificates on IIS and Apache but Reactor doesn't use either of these and I have not been able to locat ethe config file that Reactor uses for this. Which config file needs editing to apply a certificate? Does it use the computer certificate store or it's own store (e.g. pem files)

      The reason I want to achieve this, other than the general goodness of having everything I can in TLS is that I have Reactor as an IFRAME in my HASS console and as HASS is HTTPS and Reactor is HTTP then the iframe refuses to open.

      Search for "certificate" or "ssl" did not reveal anything relevant in this forum.

      Multi-System Reactor
    • MSR ZEN32 weird behavior

      R

      @toggledbits
      Hi Patrick,
      Running HASS 2022.5.3
      MSR zwavejs-22126-834c3e9

      Seeing weird behavior in MSR with regards to my Zen32's. Not sure how to capture info that might be relevent but will describe what I am seeing.
      In the example below I pressed scene 001 4 times. It flashed and changed the primary value to "4". The remaining buttons were previously showing the PV as "double" I pushed each button one time and they flashed and displayed the PV as 4.
      zen32.JPG

      In the zwavejs2mqtt debug screen that sequence looks like this.

      2022-05-10 09:38:44.078 INFO ZWAVE: Node 45: value notification: 91-0-scene-001 5 2022-05-10T16:38:44.081Z CNTRLR « [Node 045] received CentralScene notification { "nodeId": 45, "ccId": "Central Scene", "ccCommand": "0x03", "payload": "0x898501" } 2022-05-10 09:38:45.982 INFO ZWAVE: Node 45: value notification: 91-0-scene-002 0 2022-05-10T16:38:45.984Z CNTRLR « [Node 045] received CentralScene notification { "nodeId": 45, "ccId": "Central Scene", "ccCommand": "0x03", "payload": "0x8a8002" } 2022-05-10 09:38:47.807 INFO ZWAVE: Node 45: value notification: 91-0-scene-003 0 2022-05-10T16:38:47.810Z CNTRLR « [Node 045] received CentralScene notification { "nodeId": 45, "ccId": "Central Scene", "ccCommand": "0x03", "payload": "0x8b8003" } 2022-05-10 09:38:48.858 INFO ZWAVE: Node 45: value notification: 91-0-scene-004 0 2022-05-10T16:38:48.861Z CNTRLR « [Node 045] received CentralScene notification { "nodeId": 45, "ccId": "Central Scene", "ccCommand": "0x03", "payload": "0x8c8004" }

      Let me know what other info you would like me to supply.
      I have played around with a bunch of other key stroke combo's and it looks like buttons 2-5 display what ever button 1 is set to.
      Have tested this on 4 different ZEN32's and it is same on all.

      Multi-System Reactor
    • HASS 2022.5 issue with ZwaveJS in MSR

      R

      Running zwavejs-22118-baab576 in MSR, HASSOS 2022.5.1

      Due to an unreported issue in HASS, when I upgraded the 2022.5 yesterday, it dropped ZwaveJS2MQTT from my HASSOS build. Finally got it reinstalled and it appears to be working the way it was previously.
      MSR is now showing zwavejs down and in entities, nothing is updating.

      Seeing this in the logs:
      ZWaveJSController#zwavejs ws_open caught [Error]Error: connect ECONNREFUSED 192.168.0.16:3000

      Are there additional steps needed that are not mentioned in the manual?
      At a loss to figure out what is causing issue.

      Multi-System Reactor
    • Global Expression – Reference Error

      wmarcolin

      Hi!

      After several tests, restarting the computer where the MSR is, and the MSR itself by Tools > Restart, I have a persistent error in the logs.

      32d45bc3-51f8-4718-a113-3381e9d7edf2-image.png

      Looking at the global expression (screen below), I see that it is highlighted as an error, however, if I look at two other expressions above that have the same structure, they do not present an error, so I do not think the problem is with the expression's code.

      ca8a7867-4ac7-4f9a-9913-15a80da18f05-image.png

      This expression uses a group, which validates 4 devices of type door sensor, whether the status is true or false, door open or closed.

      "dgc_entrance_open": name: DGC Entrance Open select: - include_entity: - "hubitat>37" - "hubitat>38" - "hubitat>99" - "hubitat>130" filter_expression: > entity.attributes?.door_sensor?.state == true

      I also compared it with other groups, the structure is identical.

      Looking at the 4 devices in this group, I see that all are active in the MSR, have similar variables, are used in other groups and rules that do not present a problem.

      52b099f4-b9c4-46cb-ad3d-c873b09b7e13-image.png

      Looking at the log, I understand that it refers to some object that would be null, at which point I am lost on what to actually look at.

      [latest-22118]2022-05-02T22:33:11.711Z <Engine:INFO> Reaction Engine starting [latest-22118]2022-05-02T22:33:11.719Z <Engine:INFO> Checking rule sets... [latest-22118]2022-05-02T22:33:11.746Z <Engine:INFO> Checking rules... [latest-22118]2022-05-02T22:33:11.748Z <Engine:INFO> Data check complete; no corrections. [latest-22118]2022-05-02T22:33:11.892Z <Engine:ERR> [Engine]Engine#1: error evaluating expression EntranceOPEN: [ReferenceError]ReferenceError: Invalid scope in reference to member attributes of (object)null [latest-22118]2022-05-02T22:33:11.893Z <Engine:ERR> [Engine]Engine#1: expression: sort(each id in ( getEntity('groups>dgc_entrance_open').attributes.sys_group.members ): getEntity(id).name) [latest-22118]2022-05-02T22:33:11.894Z <Engine:CRIT> ReferenceError: Invalid scope in reference to member attributes of (object)null ReferenceError: Invalid scope in reference to member attributes of (object)null at _run (C:\MSR\reactor\common\lexp.js:1449:31) at _run (C:\MSR\reactor\common\lexp.js:1443:33) at _run (C:\MSR\reactor\common\lexp.js:1443:33) at _run (C:\MSR\reactor\common\lexp.js:1536:38) at _run (C:\MSR\reactor\common\lexp.js:1480:33) at C:\MSR\reactor\common\lexp.js:1283:29 at Array.forEach (<anonymous>) at _run (C:\MSR\reactor\common\lexp.js:1282:28) at run (C:\MSR\reactor\common\lexp.js:1663:22) at Object.evaluate (C:\MSR\reactor\common\lexp.js:1699:20) [latest-22118]2022-05-02T22:33:12.232Z <Engine:NOTICE> Reaction Engine running! [latest-22118]2022-05-02T22:33:12.233Z <Rule:INFO> Rule#rule-kxjp2el2 (Mode DAY) started [latest-22118]2022-05-02T22:33:12.234Z <Rule:INFO> Rule#rule-kxjp7kc8 (Mode EVENING) started [latest-22118]2022-05-02T22:33:12.234Z <Rule:INFO> Rule#rule-kxjparz7 (Mode NIGHT) started [latest-22118]2022-05-02T22:33:12.234Z <Rule:INFO> Rule#rule-kxjpd0d6 (Mode AWAY ∆) started [latest-22118]2022-05-02T22:33:12.235Z <Rule:INFO> Rule#rule-kxjqrcr9 (Mode PARTY) started [latest-22118]2022-05-02T22:33:12.235Z <Rule:INFO> Rule#rule-kxjqyhnu (Mode VACATION ∆) started

      Finally, if I return the expression and press the Try This Expression button, it is executed and the error disappears.

      102e5013-b9aa-4c26-98f5-1ae545f8897f-image.png

      This situation started to occur on the latest version of Reactor 22118, on a Windows 10 Bare Metal installation. Does anyone have a similar scenario?

      Sorry for the long post, I tried to document as best as possible to try to identify the problem.

      Thanks.

      Multi-System Reactor
    • Cheapest platform on which to run MSR

      T

      Please can anyone give me advice on a cheap way to run MSR (both initial cost and ongoing electricity cost). I currently run it on my QNAP network drive (which works very well incidentally). However, this draws a constant 35Watts (£90/yr @ 30p/kWh) and given the recent rise in fuel costs I am evaluating the best way forwards. Note, I only really need to turn my QNAP on for an hour a week to back-up my computer data. I understand that MSR can run on a Raspberry PI, but I am not competent with Linux! Thanks.

      Multi-System Reactor
    • Build 22118 - entity updates

      G

      I just noticed that the new hotness picked up the entities from when I added an integration temporarily to my Home Assistant and popped a lovely info notice into the Alerts pane.

      I know the info is new - but when did MSR suddenly become more real-time with devices being added to hubs? This is great!

      Multi-System Reactor
    • [Solved] Is there a cap or max number of devices a Global Reaction should not exceed?

      G

      Noticed in the last few nights that my Global Reaction to turn on a mere six lights in the evenings the same two devices no longer turn on. One is a dimming smart bulb, the other is a wall outlet.

      This has been running flawlessly for months - just in the last few nights I've noticed these two devices being left behind and yes, it's always these two devices only.

      "What changed?"

      No Hubitat firmware updates No new devices added to Hubitat list itemTwo MSR updates (the last two, I keep up with the latest) list itemHome Assistant releases (should have zero bearing, HA is nothing more than pretty dashboards) list itemAdded MQTT to MSR

      I did do a z-wave "repair" last night and am waiting to see if this helps.

      Is there any maximum or cap on number of devices that should be included in a Global Reaction?

      *Marked as solved as the question asked was answered. The issue persists but the question was answered.

      Multi-System Reactor
    • [Solved] Which version of npm should we be running for reactor-latest-22118-0f0772c.tar.gz

      G

      I've borked my install of reactor-latest-22118-0f0772c.tar.gz for some reason and am retracing steps. Running npm i --no-save --omit dev prompted to update npm and I did (current version now 8.6.0). Currently, attempts to load via browser/s (Brave and Safari) result in "This site can’t be reached192.168.1.xxx refused to connect." I am still able to SSH into the RPi.

      I haven't panicked yet but did just pull my config and storage directories - I believe I read where that's enough for a back-up if a clean install ends up being needed.

      So the question of the day: which version of nmp should we be running on for the latest Reactor?

      Multi-System Reactor
    • Is a global timestamp expression possible ?

      B

      I’ve looked and can’t find the answer which concerns me that the answer is obvious and thats why I can't find the answer to this.

      I’m new to MSR and this is my first post, so please bare with me 🙂

      What I’m trying to do is have a global expression that contains the current time so I can use it in Global reactions as well as Rulesets as part of my syslog messages.

      Example of what I’m experiencing:
      In Expressions, create a global expression: gMyTOD = strftime("%T %D”)
      In Rulesets, in a rule, create a local expression: MyTOD = strftime("%T %D”)

      In that same rule create a Notify type of Syslog.
      Set syslog message to: gMyTOD time is ${{gMyTOD}} and MyTOD time is ${{MyTOD}}
      Trigger the rule.

      The result is that the local expression (MyTOD) contains the correct time but the global expression (gMyTOD) does not update and reflects the wrong time in the final syslog message.

      Is there a different approach I should be using?

      Thank you in advance for any insight.

      -bh

      Multi-System Reactor
    • Restart router when it's gone offline?

      F

      Hi!
      Once a month or so, my internet access is lost, and I have to cut the power to the router, to restart it. When I'm away this become a problem, so I thought that if I got a zigbee switch (in Home Assistant), problem is solved. But how do I (MSR) know if it's offline?

      What's the easiest and most effective way to make this work? Do I ping a few websites every ten minutes or so, or is there a better approch? If I'm going to ping, what URL is recommended?

      For information, I have a set up with Asus routers, Home Assistent with zigbee-, z-wave and wifi devices (a total of appr. 150) and every of my 60-70 automation is done by MSR.
      I run MSR ver. 22080-ae7212f (docker on my Home Assistant blue). HA ver 2022.4.6.
      Thanks in advance.
      Take care, you all!
      /Fanan

      Multi-System Reactor
    • MSR for Scene Controllers

      therealdb

      I still have some code running on my Vera that I want to port and it's related to scene controllers.

      I'm mostly using Fibaro's switch/roller shutter and on the Vera side I'm getting sl_CentralScene/sl_CentralSceneAttr, but it seems too fast to be intercepted by MSR.

      What's anyone using? Thanks.

      Multi-System Reactor
    • Best strategy to get the difference between pulses in MSR

      therealdb

      So, I have a rule set that it's triggered when a local variable changes. Since it's tied to my solar production, it could change very frequently, so I've just added a reset delay to calm it down, but it's not working as intended.

      What I really need is a way to, let's say, define a percentage and define a variable to understand if the new value has changed +/- 10% before going true.

      I've tried a couple of ways, but I'm posting here anyway, in case anyone has found a better way to tackle this. Thanks!

      Multi-System Reactor
    • Status of MSR in Home Assistant

      Matohl

      Perhaps a dumb question. Can I check from Home Assistant that MSR is up and running? I would like to see that in a status page in HA. I can of course ping the other Pi but it doesn't say anything about the MSR status.

      Skärmavbild 2022-04-23 kl. 18.23.03.png

      Multi-System Reactor
    • Notifications from Alerts

      Crille

      @toggledbits Is there a way to get Current Alerts as an entity so I could monitor those and send notifications if needed.
      My usecase is sometimes openLuup crashes and MSR picks that up pretty quick, sending a pushover notification to me would get my attention to restart it.
      Of course there are many ways to monitor connectivity but since MSR already is doing that it would be neat to take advantage of it.

      Multi-System Reactor
    • Invocable rules via MQTT

      therealdb

      Hey @toggledbits.
      From the docs:

      You cannot control the state of rules via MQTT. Rule state is driven exclusively by the result of its conditions.

      And I'm OK when rules are triggered by something else, but I've built a couple of rules to be used by other rules, to streamline the logic, and it'll be useful to invoke a rule via MQTT. It's probably close to what rule/:id/restart is doing in the HTTP api.

      Thanks!

      Multi-System Reactor
    • Home Assistant Script, Reaction requires seclection that isnt there

      S

      I'm trying to create some automation so I can control my pool variable speed pump from reactor rather than iAqualink (which sucks). My controller is MQTT enabled so I created several scripts for my desired speeds. (I know reactor has MQTT ability but honestly I read the docs and could not make much sense of it and since I already have it set up in Home Assistant, I figured I would just leverage that instead)

      So I created all of my scripts and tested them, they worked perfectly. The I created a rule in reactor and set running the script as the action. The problem is that reactor is telling me that I have to make a selection. I try to click the dropdown and there is nothing to select. I cant save the rule, the only option is to exit.

      9e0a3147-5058-4893-9860-2f0d759dfe3c-image.png

      Here is my script in Home Assistant. Any advice on how to get this to work? If I am looking at this the wrong way I am open to suggestions (I would rather be able to call a specific action and specify a speed value but I cannot figure out how to do that). Thanks in advance.

      bfc7ba89-70a5-47d3-a111-0c2927ac3c73-image.png

      Multi-System Reactor
    • Installed latest MSR container and host time is wrong

      M

      Hi, I've been using msr for a while now and haven't had timezone issues until today when I updated to latest docker image (latest-22080-ae7212f)

      both docker date command and my local date command show the same time, same timezone, but for some reason MSR shows the host time as 2 hours in the past as a result all my timed rules run 2 hours late.

      my locale is set correctly in the host machine and is bound into the container as well.

      One possible hint I get is maybe this from the container startup log, but other than timezone stuff everything else seems to be working fine and all my settings loaded up just fine.

      [latest-22080]2022-04-07T07:52:52.423Z <SystemController:null> Module SystemController v22080 root {} CommonJS loading [latest-22080]2022-04-07T07:52:57.236Z <Engine:CRIT> SyntaxError: Unexpected end of JSON input SyntaxError: Unexpected end of JSON input at JSON.parse (<anonymous>) at IndividualFileStrategy.getDataObject (/opt/reactor/server/lib/IndividualFileStrategy.js:121:46) at Container.getDataObject (/opt/reactor/server/lib/Container.js:102:53) at new GlobalExpression (/opt/reactor/server/lib/GlobalExpression.js:105:179) at Function.getInstance (/opt/reactor/server/lib/GlobalExpression.js:123:89) at /opt/reactor/server/lib/Engine.js:1349:67 at Array.forEach (<anonymous>) at Engine.initializeGlobalExpressions (/opt/reactor/server/lib/Engine.js:1345:145) at Engine.start (/opt/reactor/server/lib/Engine.js:590:285) at /opt/reactor/app.js:362:103

      Let me know if I can provide further info to help debug this.

      Thanks

      Multi-System Reactor
    For those who registered but didn't received the confirmation email, please send an email to support@smarthome.community with the email you used

    Alerts - (vera>device_699) does not have attribute ?attr?

    Multi-System Reactor
    2
    32
    94
    Loading More Posts
    • 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.
    • cw-kid
      cw-kid last edited by cw-kid

      After restarting MSR I now have four alerts:

      Three of them are referring to an Everspring EH403 outdoor flood light.

      (vera>device_699) does not have attribute ?attr?

      2017212b-4b6d-4996-b5b5-e7bb55a5855e-image.png

      In the rules trigger I am using this:

      x_vera_srv_micasaverde_com_SecuritySensor1.Tripped

      6d8c52c4-6818-4e52-a862-2ca6df4860a2-image.png

      This is a bit of an odd ball device in Vera as it doesn't create a motion sensor child device natively.

      The parent device I have configured as a Binary Light, but it does have a "Tripped" variable for the PIR motion sensor portion of the device.

      These rules have been working OK however.

      As a test now, if I manually set the "Tripped" variable to 1 then my rules actions are run OK.

      9fbabbeb-32db-4dd1-8e9a-2db96445951c-image.png

      toggledbits 1 Reply Last reply Reply Quote 0
      • toggledbits
        toggledbits @cw-kid last edited by toggledbits

        @cw-kid The alert may be new, but the error being thrown in the log file would not be, so you probably didn't notice (i.e. the new alert is generated in the same breath as the log message that's been there for a while now).

        Just to clarify, are you testing the action device or is this a virtual device you are copying to?

        If it comes up again, go the rule editor right away and see if it exists there or not. That would be instructive. Then go look on the Vera side (hard refresh your browser first to make sure the UI Variables tab is showing you current data, it rarely does). If it's there, it would be good to know what value it has.

        And a device dump from a startup may also provide a clue:

        1. Under the config section for the vera controller in reactor.yaml, add a dump_entity: line indented two spaces relative to the config.
        2. After the dump_entity: line, add "device_699": true and make sure that's indented two space from dump_entity.

        It will look like this:

        controller:
          - id: vera
            # other config redacted for clarity
            config:
              # your source and other stuff redacted for clarity
              dump_entity:              <---- add this
                "device_699": true    <--- and this
        

        Make sure you only use spaces for indenting. The restart MSR. Wait a moment, and a file called vera-device_699.json will be created in your logs directory. Grab and post here.

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

        cw-kid 1 Reply Last reply Reply Quote 0
        • cw-kid
          cw-kid @toggledbits last edited by

          @toggledbits said in Alerts - (vera>device_699) does not have attribute ?attr?:

          Just to clarify, are you testing the actual device or is this a virtual device you are copying to?

          In MSR my rules trigger is looking at the "real" device the parent device and its "Tripped" variable, this is device ID 699, this is configured as a Binary Light device.

          546e69dc-6a53-4764-9289-b1541d8c420f-image.png

          The virtual motion sensor device I created and that I am copying the tripped status to from the parent, I am not using this device in MSR as a trigger. But I guess I could do instead.

          Virtual Motion Sensor:

          301060e8-c331-4186-83ef-3d07be70d671-image.png

          And this is an actual child device of the parent, which is a LUX sensor.

          2a9d24bb-7550-4e12-b84c-c88b7a79f936-image.png

          You can download the device dump for the parent device 699 here.

          1 Reply Last reply Reply Quote 0
          • cw-kid
            cw-kid last edited by

            I had to restart MSR a few times to do that device dump, after the first restart the alerts went away and cleared. After the second restart they are back again.

            Not sure I know what you mean here?

            "If it comes up again, go the rule editor right away and see if it exists there or not."

            a96f9d18-b56b-40ed-a3a1-0c53e4db3d33-image.png

            fcdb803e-f2a4-42be-b029-12a1b1b9a381-image.png

            1 Reply Last reply Reply Quote 0
            • cw-kid
              cw-kid last edited by

              Device 699 information from the Entities area:

              power_switch.state=false
              x_vera_device.configured=true
              x_vera_device.device_number=699
              x_vera_device.device_type="urn:schemas-upnp-org:device:BinaryLight:1"
              x_vera_device.failed=null
              x_vera_device.mapped_by="*;device_type=urn:schemas-upnp-org:device:BinaryLight:1"
              x_vera_device.mapped_class="generic_switch"
              x_vera_svc_micasaverde_com_HaDevice1.ChildrenSameRoom="1"
              x_vera_svc_micasaverde_com_HaDevice1.Configured="1"
              x_vera_svc_micasaverde_com_HaDevice1.FirstConfigured="1616524758"
              x_vera_svc_micasaverde_com_HaDevice1.LastUpdate="1616525032"
              x_vera_svc_micasaverde_com_HaDevice1.ModeSetting="1:;2:;3:;4:"
              x_vera_svc_micasaverde_com_HaDevice1.PollRatings="5.00"
              x_vera_svc_micasaverde_com_SecuritySensor1.Armed="0"
              x_vera_svc_micasaverde_com_SecuritySensor1.ArmedTripped="0"
              x_vera_svc_micasaverde_com_SecuritySensor1.IgnoreTripTime="2"
              x_vera_svc_micasaverde_com_SecuritySensor1.LastTrip="1617297343"
              x_vera_svc_micasaverde_com_SecuritySensor1.Tripped="0"
              x_vera_svc_micasaverde_com_ZWaveDevice1.AgiInfo="X"
              x_vera_svc_micasaverde_com_ZWaveDevice1.AlarmType="0x7,0x8,"
              x_vera_svc_micasaverde_com_ZWaveDevice1.AlarmVersion="0,2"
              x_vera_svc_micasaverde_com_ZWaveDevice1.AssociationNum="0"
              x_vera_svc_micasaverde_com_ZWaveDevice1.Capabilities="211,156,1,4,7,1,L,R,B,RS,|37S,49S:5,85,89S,90S,94,108S,112S,113S:4,114S,115S,122S,133S,134S,152,159,"
              x_vera_svc_micasaverde_com_ZWaveDevice1.ConfiguredAssoc=""
              x_vera_svc_micasaverde_com_ZWaveDevice1.ConfiguredVariable="1-PIR Trigger Off period,2d,60,2-Lux sensor threshold,2d,30,3-Lux auto report,2d,1"
              x_vera_svc_micasaverde_com_ZWaveDevice1.FirmwareInfo="96,4609,29529"
              x_vera_svc_micasaverde_com_ZWaveDevice1.LastArr="1617238811,7"
              x_vera_svc_micasaverde_com_ZWaveDevice1.LastNnu="1617238807,7"
              x_vera_svc_micasaverde_com_ZWaveDevice1.LastReset="1616524754"
              x_vera_svc_micasaverde_com_ZWaveDevice1.LastRouteUpdate="1616525092"
              x_vera_svc_micasaverde_com_ZWaveDevice1.ManufacturerInfo="96,18,1"
              x_vera_svc_micasaverde_com_ZWaveDevice1.NodeInfo="55,5e,98,9f,"
              x_vera_svc_micasaverde_com_ZWaveDevice1.PlusInfo="1,5,0,12,7,12,7"
              x_vera_svc_micasaverde_com_ZWaveDevice1.PollOk="2"
              x_vera_svc_micasaverde_com_ZWaveDevice1.PollSettings="60"
              x_vera_svc_micasaverde_com_ZWaveDevice1.SecurityFailed="0"
              x_vera_svc_micasaverde_com_ZWaveDevice1.SensorMlType="3"
              x_vera_svc_micasaverde_com_ZWaveDevice1.SubscribedAlarms=",0x7,0x8,"
              x_vera_svc_micasaverde_com_ZWaveDevice1.VariablesGet="1,60,2,30,3,1,"
              x_vera_svc_micasaverde_com_ZWaveDevice1.VariablesSet="1-PIR Trigger Off period,2d,60,2-Lux sensor threshold,2d,30,3-Lux auto report,2d,1"
              x_vera_svc_micasaverde_com_ZWaveDevice1.VersionInfo="3,4,61,1,1"
              x_vera_svc_micasaverde_com_ZWaveNetwork1.ConsecutivePollFails="0"
              x_vera_svc_micasaverde_com_ZWaveNetwork1.LastPollSuccess="1616525034"
              x_vera_svc_upnp_org_SwitchPower1.Status="0"
              x_vera_svc_upnp_org_SwitchPower1.Target="0"
              zwave_device.capabilities="211,156,1,4,7,1,L,R,B,RS,|37S,49S:5,85,89S,90S,94,108S,112S,113S:4,114S,115S,122S,133S,134S,152,159,"
              zwave_device.failed=null
              zwave_device.manufacturer_info="96,18,1"
              zwave_device.node_id=133
              zwave_device.version_info="3,4,61,1,1"
              Capabilities: power_switch, toggle, x_vera_device, x_vera_svc_micasaverde_com_EnergyMetering1, x_vera_svc_micasaverde_com_HaDevice1, x_vera_svc_micasaverde_com_SecuritySensor1, x_vera_svc_micasaverde_com_ZWaveDevice1, x_vera_svc_micasaverde_com_ZWaveNetwork1, x_vera_svc_upnp_org_SwitchPower1, zwave_device
              Actions: power_switch.off, power_switch.on, toggle.toggle, x_vera_device.set_variable, x_vera_svc_micasaverde_com_EnergyMetering1.ResetKWH, x_vera_svc_micasaverde_com_HaDevice1.AllowPairing, x_vera_svc_micasaverde_com_HaDevice1.Poll, x_vera_svc_micasaverde_com_HaDevice1.Reconfigure, x_vera_svc_micasaverde_com_HaDevice1.Remove, x_vera_svc_micasaverde_com_HaDevice1.SetPollFrequency, x_vera_svc_micasaverde_com_HaDevice1.StressTest, x_vera_svc_micasaverde_com_HaDevice1.ToggleState, x_vera_svc_micasaverde_com_SecuritySensor1.SetArmed, x_vera_svc_micasaverde_com_ZWaveNetwork1.AddNodes, x_vera_svc_micasaverde_com_ZWaveNetwork1.BackupDongle, x_vera_svc_micasaverde_com_ZWaveNetwork1.DownloadNetwork, x_vera_svc_micasaverde_com_ZWaveNetwork1.HealNetwork, x_vera_svc_micasaverde_com_ZWaveNetwork1.PollAllNodes, x_vera_svc_micasaverde_com_ZWaveNetwork1.PutByte, x_vera_svc_micasaverde_com_ZWaveNetwork1.ReconfigureAllNodes, x_vera_svc_micasaverde_com_ZWaveNetwork1.RemoveNodes, x_vera_svc_micasaverde_com_ZWaveNetwork1.ResetNetwork, x_vera_svc_micasaverde_com_ZWaveNetwork1.SendData, x_vera_svc_micasaverde_com_ZWaveNetwork1.SetPolling, x_vera_svc_micasaverde_com_ZWaveNetwork1.SimulateIncomingData, x_vera_svc_micasaverde_com_ZWaveNetwork1.UpdateNeighbors, x_vera_svc_micasaverde_com_ZWaveNetwork1.UpdateNetwork, x_vera_svc_upnp_org_SwitchPower1.SetTarget, zwave_device.poll
              
              1 Reply Last reply Reply Quote 0
              • cw-kid
                cw-kid last edited by cw-kid

                I just updated to the latest version of MSR 21091 and now I have some more new alerts regarding this particular device:

                An Entity Attribute condition in rule Deck Floodlight (Disarmed) - Tripped (Day) - Send Alert failed because the referenced entity Deck Floodlight (vera>device_699) does not have attribute x_vera_svc_micasaverde_com_SecuritySensor1.Armed

                Not sure what I can do about this Everspring flood light device and these alerts ?

                So I have edited my rules to use the virtual motion sensor device instead for their triggers instead of the parent device (Binary Light).

                Also this is a new but similar Alert regarding the Vera Day or Night plugin

                An Entity Attribute condition in rule Night - Day / Night Plugin failed because the referenced entity Day or Night (vera>device_43) does not have attribute ?attr?

                Status 1 or 0 appears to have gone missing for this rule:

                78391548-5ee2-4054-802d-9a97d6cc3038-image.png

                https://reactor.toggledbits.com/mantisbt/view.php?id=159

                toggledbits 1 Reply Last reply Reply Quote 0
                • toggledbits
                  toggledbits last edited by toggledbits

                  All x_vera_state attributes were removed several builds ago. You'll find a x_vera_svc replacement for it. You could also just use the native date/time and sunrise/sunset conditions, rather than relying on yet another plugin.

                  And by the way, the alerts from 21090 will persist until you dismiss them. You should not see any {attr} in messages from 21091, but alerts from 21090, if they were not dismissed, would still have them. With a few exceptions (controller up/down), alerts don't go away until you dismiss them.

                  So I have edited my rules to use the virtual motion sensor device instead for their triggers instead of the parent device (Binary Light).

                  This isn't going to help the troubleshooting. Please go back to the prior configuration, and let's continue trying to figure this out.

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

                  cw-kid 1 Reply Last reply Reply Quote 0
                  • cw-kid
                    cw-kid @toggledbits last edited by cw-kid

                    @toggledbits said in Alerts - (vera>device_699) does not have attribute ?attr?:

                    ou could also just use the native date/time and sunrise/sunset conditions, rather than relying on yet another plugin.

                    I think I added it just as a test to see if I could use the status of the Day or Night plugin. I've changed it to use x_vera_svc...status I didn't see that earlier when I looked.

                    All my other rules are using the MSR inbuilt sunrise/sunset conditions.

                    I've cleared the other Alerts and restarted MSR, as yet none have come back.

                    Thanks

                    1 Reply Last reply Reply Quote 0
                    • toggledbits
                      toggledbits last edited by toggledbits

                      Now that we know exactly what state variable it was complaining about, I took a look at the vera-device_699.json file you posted earlier, and sure enough the state variable Armed is missing (go check my work, please). So that seems like there's an odd device implementation thing going on in Luup.

                      I think we can work around it, though, and make it stable for your rules, by telling MSR that the device is special and instead of letting just have default Vera-specific capabilities, give it additional MSR-native capabilities. These will give you null when the variable is missing, but you can handle (or ignore) that more easily and it won't throw an error or alert. So you'll just test your device using the MSR-native attributes instead of the Vera service ones.

                      I'll make up the changes to the device configuration file and PM it to you, and you can try it. It should work.

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

                      cw-kid 1 Reply Last reply Reply Quote 0
                      • cw-kid
                        cw-kid @toggledbits last edited by

                        @toggledbits

                        On the Everspring Flood light parent device (Binary Light) I've just looked in Vera and there is no "Armed" variable.

                        There is this variable however which is strange.

                        "urn:micasaverde-com:serviceId:SecuritySensor1 / ArmedTripped"

                        I could add an "Armed" variable to the device using the "New Service" function in Vera, think I know how to do that.

                        toggledbits 1 Reply Last reply Reply Quote 0
                        • cw-kid
                          cw-kid last edited by cw-kid

                          New Alert just appeared

                          "An Entity Attribute condition in rule Vera Luup Reloads failed because the referenced entity vera>system could not be found"

                          The rule looks to be OK however:

                          76522677-1f76-40d4-96ab-07b12f5a30e0-image.png

                          EDIT: Actually I think this Alert might happen if I manually reload the LUUP engine on Vera.

                          This rule is meant to keep track of the number of LUUP engine reloads.

                          1 Reply Last reply Reply Quote 0
                          • toggledbits
                            toggledbits @cw-kid last edited by

                            @cw-kid said in Alerts - (vera>device_699) does not have attribute ?attr?:

                            On the Everspring Flood light parent device (Binary Light) I've just looked in Vera and there is no "Armed" variable.

                            It would have to have been there at some point or you could not have chosen it for your rule. The list in the rule editor only shows what exists on the device/entity, not what it thinks would normally be there. So it was there at one point, and disappeared later, and this is not that unusual in the Vera world, sadly.

                            You can try re-creating it. It would be educational to see if it "sticks" after a reload, and after changing house mode, which aside from user action are the principal ways that variable gets played with.

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

                            cw-kid 1 Reply Last reply Reply Quote 0
                            • cw-kid
                              cw-kid @toggledbits last edited by

                              @toggledbits said in Alerts - (vera>device_699) does not have attribute ?attr?:

                              It would have to have been there at some point or you could not have chosen it for your rule

                              "Tripped" I was using "Tripped" as the trigger in the rule not "Armed".

                              Looking in the device dump .json file I did the other day I can't see "Armed" in there either. So maybe this device never had it in the first place.

                              1 Reply Last reply Reply Quote 0
                              • toggledbits
                                toggledbits @cw-kid last edited by toggledbits

                                @cw-kid said in Alerts - (vera>device_699) does not have attribute ?attr?:

                                An Entity Attribute condition in rule Deck Floodlight (Disarmed) - Tripped (Day) - Send Alert failed because the referenced entity Deck Floodlight (vera>device_699) does not have attribute x_vera_svc_micasaverde_com_SecuritySensor1.Armed

                                                                      ^^^^^^^^^^^^^^^^
                                

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

                                cw-kid 1 Reply Last reply Reply Quote 0
                                • cw-kid
                                  cw-kid @toggledbits last edited by

                                  @toggledbits said in Alerts - (vera>device_699) does not have attribute ?attr?:

                                  An Entity Attribute condition in rule Deck Floodlight (Disarmed) - Tripped (Day) - Send Alert failed because the referenced entity Deck Floodlight (vera>device_699) does not have attribute x_vera_svc_micasaverde_com_SecuritySensor1.Armed

                                  oh LOL that was a Constraint. So yes looks like I was using "Armed" also at some point.

                                  So it has vanished as you suggested.

                                  1 Reply Last reply Reply Quote 0
                                  • toggledbits
                                    toggledbits last edited by

                                    Whew! OK... that's good (no, really). So, I have the changes for the device def. I'll send that via PM. You can drop it into your reactor/server/lib directory and restart Reactor. It should give you the standard arming service, with a value report of null (if it's still missing at that point -- hope so, don't change anything on the Vera yet!). Even if you don't use it, I'd like to confirm this approach would work if it comes up for other devices.

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

                                    1 Reply Last reply Reply Quote 0
                                    • cw-kid
                                      cw-kid last edited by

                                      OK I won't do anything on the Vera side or attempt to add back in the "Armed" variable using the New Service function.

                                      1 Reply Last reply Reply Quote 0
                                      • toggledbits
                                        toggledbits last edited by

                                        The other issue, found that, will be fixed in today's build (restart reporting system entity missing).

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

                                        cw-kid 1 Reply Last reply Reply Quote 1
                                        • cw-kid
                                          cw-kid @toggledbits last edited by cw-kid

                                          @toggledbits

                                          OK I have uploaded the vera_devices.yaml file and restarted MSR.

                                          For the Everspring Flood light parent device this is what I am now seeing:

                                          07ac2434-ea57-4241-a721-22d27d39dea6-image.png

                                          ddce6d79-c6fa-46c3-b10f-f09a66ce0fda-image.png

                                          a3998565-12ff-4b98-8589-06f9f99a32c8-image.png

                                          SecuritySensor1.Armed is the last item in the list in the drop down box.

                                          276b330b-7557-4007-8f5f-614539a1fa17-image.png

                                          So what does this mean ?

                                          It can't see the actual "Armed" state if that variable has now vanished off Vera.

                                          It seems to think its "false" not null.

                                          1 Reply Last reply Reply Quote 0
                                          • toggledbits
                                            toggledbits last edited by toggledbits

                                            Your other snip shows the variable is there now, at the bottom of the list, therefore it has appeared and has a value, and null is not to be expected. This is exactly why I am taking this approach: the arming capability will make sure that its state attribute always exists with a value of true, false, or null, the first two following the value of SecuritySensor1/Armed when it is present on the device, or getting null if it is not. This is easier to handle in rules/conditions than getting an error thrown; you can treat null and false as equivalent, in all likelihood, which is exactly what a simple is TRUE condition operation would do.

                                            For the sake of clarity, the update did not make the Armed variable appear on the device. It can't do that. It only affects how it reads the device data that is available. So something created Armed on the Vera side in the interim, perhaps Vera itself.

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

                                            cw-kid 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Welcome. If you’d like to participate in the discussion, rather than just read, then you can join the forum. As a member, you can interact with others here to share your experience and ask the questions you need answered.

                                            Powered by NodeBB | Contributors
                                            Hosted freely by PointPub Media Communications Inc. | Contact us