Alerts - (vera>device_699) does not have attribute ?attr?
-
@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.
@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.
-
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:
@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 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
^^^^^^^^^^^^^^^^@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.
-
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
armingservice, 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. -
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.
-
The other issue, found that, will be fixed in today's build (restart reporting system entity missing).
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:
SecuritySensor1.Armed is the last item in the list in the drop down box.
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.
-
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
armingcapability will make sure that itsstateattribute always exists with a value of true, false, or null, the first two following the value ofSecuritySensor1/Armedwhen 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
Armedvariable appear on the device. It can't do that. It only affects how it reads the device data that is available. So something createdArmedon 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.
-
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
armingcapability will make sure that itsstateattribute always exists with a value of true, false, or null, the first two following the value ofSecuritySensor1/Armedwhen 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
Armedvariable appear on the device. It can't do that. It only affects how it reads the device data that is available. So something createdArmedon the Vera side in the interim, perhaps Vera itself.@toggledbits said in Alerts - (vera>device_699) does not have attribute ?attr?:
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
But I still can't see the "Armed" variable listed in Vera. I have hard refreshed the browser.
-
Well, it would not be listed if it hadn't come back in user_data. If, since the last MSR restart, the Vera reported that variable even once, MSR would have it. If it later is missing, there's actually no way for MSR to know it's missing, it thinks it's just not being updated/no updates for it, so it keeps it at the last value it got. The only way to reset that cached state is to restart MSR.
-
This is confusing.
This is the SDATA for this device, "armed" is indeed present:
{ "name": "Deck Floodlight", "altid": "133", "id": 699, "category": 3, "subcategory": 0, "room": 5, "parent": 1, "status": "0", "configured": "1", "armedtripped": "0", "lasttrip": "1617376314", "tripped": "0", "armed": "0" },However I cannot see that variable in the Vera UI7 web GUI even after reloading the LUUP engine and hard refreshing the browser.
-
Change out
sdataforstatusand see what it reports.Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
Change out
sdataforstatusand see what it reports.Status output:
{ "id": 699, "service": "urn:micasaverde-com:serviceId:ZWaveDevice1", "variable": "SensorMlType", "value": "1" }{ "id": 699, "states": [ { "id": 466, "service": "urn:upnp-org:serviceId:SwitchPower1", "variable": "Status", "value": "0" }The name of the device "Deck Floodlight" cannot be found, so I searched for its ID number 699 instead and that's all I could see.
I don't know what ID 466 is ? There is no device with that ID.
Its not its altid / node id that is 133
-
That does not look like a complete status output. Can you post the URL you used for that query? I assume you're doing that as an HTTP request?
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
That does not look like a complete status output. Can you post the URL you used for that query? I assume you're doing that as an HTTP request?
-
That does not look like a complete status output. Can you post the URL you used for that query? I assume you're doing that as an HTTP request?
@toggledbits said in Alerts - (vera>device_699) does not have attribute ?attr?:
I assume you're doing that as an HTTP request?
I just ran it in Chrome browser.
-
Try adding
DeviceNumparameter, and please don't edit any of the response when posting:http://vera-ip:3480/data_request?id=status&DeviceNum=699The 466 you were asking about earlier is the state's ID number. It's not relevant to anything, just an internal value for Luup.
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
Try adding
DeviceNumparameter, and please don't edit any of the response when posting:http://vera-ip:3480/data_request?id=status&DeviceNum=699The 466 you were asking about earlier is the state's ID number. It's not relevant to anything, just an internal value for Luup.
There's a lot of it:
{ "Device_Num_699": { "states": [ { "id": 583, "service": "urn:upnp-org:serviceId:SwitchPower1", "variable": "Status", "value": "0" }, { "id": 584, "service": "urn:upnp-org:serviceId:SwitchPower1", "variable": "Target", "value": "0" }, { "id": 585, "service": "urn:micasaverde-com:serviceId:HaDevice1", "variable": "Configured", "value": "1" }, { "id": 586, "service": "urn:micasaverde-com:serviceId:HaDevice1", "variable": "LastUpdate", "value": "1616525032" }, { "id": 587, "service": "urn:micasaverde-com:serviceId:HaDevice1", "variable": "FirstConfigured", "value": "1616524758" }, { "id": 588, "service": "urn:micasaverde-com:serviceId:HaDevice1", "variable": "ChildrenSameRoom", "value": "1" }, { "id": 589, "service": "urn:micasaverde-com:serviceId:HaDevice1", "variable": "PollRatings", "value": "5.00" }, { "id": 590, "service": "urn:micasaverde-com:serviceId:HaDevice1", "variable": "ModeSetting", "value": "1:;2:;3:;4:" }, { "id": 591, "service": "urn:micasaverde-com:serviceId:ZWaveDevice1", "variable": "Capabilities", "value": "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," }, { "id": 592, "service": "urn:micasaverde-com:serviceId:ZWaveDevice1", "variable": "NodeInfo", "value": "55,5e,98,9f," }, { "id": 593, "service": "urn:micasaverde-com:serviceId:ZWaveDevice1", "variable": "Neighbors", "value": "1,12,28,31,32,33,40,44,45,47,52,56,58,67,70,72,79,85,87,112," }, { "id": 594, "service": "urn:micasaverde-com:serviceId:ZWaveDevice1", "variable": "LastReset", "value": "1616524754" }, { "id": 595, "service": "urn:micasaverde-com:serviceId:ZWaveDevice1", "variable": "VariablesSet", "value": "1-PIR Trigger Off period,2d,60,2-Lux sensor threshold,2d,30,3-Lux auto report,2d,1" }, { "id": 596, "service": "urn:micasaverde-com:serviceId:ZWaveDevice1", "variable": "SecurityFailed", "value": "0" }, { "id": 597, "service": "urn:micasaverde-com:serviceId:ZWaveDevice1", "variable": "ManufacturerInfo", "value": "96,18,1" }, { "id": 598, "service": "urn:micasaverde-com:serviceId:ZWaveDevice1", "variable": "VersionInfo", "value": "3,4,61,1,1" }, { "id": 599, "service": "urn:micasaverde-com:serviceId:ZWaveDevice1", "variable": "AlarmType", "value": "0x7,0x8," }, { "id": 600, "service": "urn:micasaverde-com:serviceId:ZWaveDevice1", "variable": "AlarmVersion", "value": "0,2" }, { "id": 601, "service": "urn:micasaverde-com:serviceId:ZWaveDevice1", "variable": "SubscribedAlarms", "value": ",0x7,0x8," }, { "id": 602, "service": "urn:micasaverde-com:serviceId:ZWaveDevice1", "variable": "SensorMlType", "value": "3" }, { "id": 603, "service": "urn:micasaverde-com:serviceId:ZWaveDevice1", "variable": "PlusInfo", "value": "1,5,0,12,7,12,7" }, { "id": 604, "service": "urn:micasaverde-com:serviceId:ZWaveDevice1", "variable": "FirmwareInfo", "value": "96,4609,29529" }, { "id": 605, "service": "urn:micasaverde-com:serviceId:ZWaveDevice1", "variable": "AgiInfo", "value": "X" }, { "id": 606, "service": "urn:micasaverde-com:serviceId:ZWaveDevice1", "variable": "ConfiguredAssoc", "value": "" }, { "id": 607, "service": "urn:micasaverde-com:serviceId:ZWaveDevice1", "variable": "ConfiguredVariable", "value": "1-PIR Trigger Off period,2d,60,2-Lux sensor threshold,2d,30,3-Lux auto report,2d,1" }, { "id": 608, "service": "urn:micasaverde-com:serviceId:ZWaveDevice1", "variable": "PollSettings", "value": "60" }, { "id": 609, "service": "urn:micasaverde-com:serviceId:ZWaveDevice1", "variable": "VariablesGet", "value": "1,60,2,30,3,1," }, { "id": 610, "service": "urn:micasaverde-com:serviceId:ZWaveDevice1", "variable": "PollOk", "value": "2" }, { "id": 611, "service": "urn:micasaverde-com:serviceId:ZWaveDevice1", "variable": "AssociationNum", "value": "0" }, { "id": 612, "service": "urn:micasaverde-com:serviceId:ZWaveDevice1", "variable": "LastRouteUpdate", "value": "1616525092" }, { "id": 613, "service": "urn:micasaverde-com:serviceId:ZWaveDevice1", "variable": "LastNnu", "value": "1617238807,7" }, { "id": 614, "service": "urn:micasaverde-com:serviceId:ZWaveDevice1", "variable": "LastArr", "value": "1617238811,7" }, { "id": 615, "service": "urn:micasaverde-com:serviceId:ZWaveNetwork1", "variable": "LastPollSuccess", "value": "1616525034" }, { "id": 616, "service": "urn:micasaverde-com:serviceId:ZWaveNetwork1", "variable": "ConsecutivePollFails", "value": "0" }, { "id": 617, "service": "urn:micasaverde-com:serviceId:SecuritySensor1", "variable": "IgnoreTripTime", "value": "2" }, { "id": 618, "service": "urn:micasaverde-com:serviceId:SecuritySensor1", "variable": "ArmedTripped", "value": "0" }, { "id": 619, "service": "urn:micasaverde-com:serviceId:SecuritySensor1", "variable": "LastTrip", "value": "1617376314" }, { "id": 620, "service": "urn:micasaverde-com:serviceId:SecuritySensor1", "variable": "Tripped", "value": "0" }, { "id": 621, "service": "urn:micasaverde-com:serviceId:SecuritySensor1", "variable": "Armed", "value": "0" } ], "Jobs": [ ], "PendingJobs": 0, "tooltip": { "display": 0 }, "status": -1 }, "Using_2G": 0, "LoadTime": 1617383774, "DataVersion": 383787633, "UserData_DataVersion": 383774040, "TimeStamp": 1617390782, "lights_on": 13, "lights_off": 43, "doors_locked": 0, "doors_unlocked": 0, "sensors_tripped": 0, "sensors_not_tripped": 24, "failed_devices": 0, "visible_devices": 149, "partitions_active": 0, "partitions_notactive": 0, "alerts": [ { "PK_Device": 331, "Room": 1, "DeviceName": "Lounge Motion", "DeviceType": "urn:schemas-micasaverde-com:device:MotionSensor:1", "PK_Alert": "35995388862", "LocalDate": "2021-03-31 06:24:21", "EventType": 16, "SourceType": 5, "Argument": 1, "Filesize": 0, "Severity": 5, "LocalTimestamp": 1617168261, "Code": "offline", "NewValue": "1", "Description": "Device NOT responding", "Users": "", "Server_Storage": "", "Key": "", "Icon": "error.png", "PK_Store": "0" }, { "PK_Device": 331, "Room": 1, "DeviceName": "Lounge Motion", "DeviceType": "urn:schemas-micasaverde-com:device:MotionSensor:1", "PK_Alert": "35995486322", "LocalDate": "2021-03-31 07:30:55", "EventType": 16, "SourceType": 5, "Argument": 0, "Filesize": 0, "Severity": 5, "LocalTimestamp": 1617172255, "Code": "offline", "NewValue": "0", "Description": "Device responding again", "Users": "", "Server_Storage": "", "Key": "", "Icon": "error.png", "PK_Store": "0" }, { "PK_Device": 331, "Room": 1, "DeviceName": "Lounge Motion", "DeviceType": "urn:schemas-micasaverde-com:device:MotionSensor:1", "PK_Alert": "36007081772", "LocalDate": "2021-03-31 23:15:25", "EventType": 3, "SourceType": 3, "Argument": 0, "Filesize": 0, "Severity": 1, "LocalTimestamp": 1617228925, "Code": "DL_ARMEDTRIPPED", "NewValue": "1", "Description": "Lounge Motion", "Users": "", "Server_Storage": "", "Key": "", "Icon": "", "PK_Store": "0" }, { "PK_Device": 331, "Room": 1, "DeviceName": "Lounge Motion", "DeviceType": "urn:schemas-micasaverde-com:device:MotionSensor:1", "PK_Alert": "36007090092", "LocalDate": "2021-03-31 23:15:58", "EventType": 4, "SourceType": 4, "Argument": 0, "Filesize": 0, "Severity": 1, "LocalTimestamp": 1617228958, "Code": "DL_ARMEDTRIPPED", "NewValue": "0", "Description": "Lounge Motion", "Users": "", "Server_Storage": "", "Key": "", "Icon": "", "PK_Store": "0" }, { "PK_Device": 290, "Room": 5, "DeviceName": "Deck Motion", "DeviceType": "urn:schemas-micasaverde-com:device:MotionSensor:1", "PK_Alert": "36034063812", "LocalDate": "2021-04-02 12:54:57", "EventType": 12, "SourceType": 3, "Argument": 0, "Filesize": 0, "Severity": 0, "LocalTimestamp": 1617364497, "Code": "", "NewValue": "1", "Description": "Deck Motion", "Users": "", "Server_Storage": "", "Key": "", "Icon": "burglar.png", "PK_Store": "0" }, { "PK_Device": 290, "Room": 5, "DeviceName": "Deck Motion", "DeviceType": "urn:schemas-micasaverde-com:device:MotionSensor:1", "PK_Alert": "36034387302", "LocalDate": "2021-04-02 13:23:04", "EventType": 12, "SourceType": 3, "Argument": 0, "Filesize": 0, "Severity": 0, "LocalTimestamp": 1617366184, "Code": "", "NewValue": "1", "Description": "Deck Motion", "Users": "", "Server_Storage": "", "Key": "", "Icon": "burglar.png", "PK_Store": "0" }, { "PK_Device": 694, "Room": 3, "DeviceName": "Porch Motion Sensor", "DeviceType": "urn:schemas-micasaverde-com:device:MotionSensor:1", "PK_Alert": "36034718782", "LocalDate": "2021-04-02 13:53:19", "EventType": 12, "SourceType": 3, "Argument": 0, "Filesize": 0, "Severity": 0, "LocalTimestamp": 1617367999, "Code": "", "NewValue": "1", "Description": "Porch Motion Sensor", "Users": "", "Server_Storage": "", "Key": "", "Icon": "burglar.png", "PK_Store": "0" }, { "PK_Device": 290, "Room": 5, "DeviceName": "Deck Motion", "DeviceType": "urn:schemas-micasaverde-com:device:MotionSensor:1", "PK_Alert": "36034775722", "LocalDate": "2021-04-02 13:58:47", "EventType": 12, "SourceType": 3, "Argument": 0, "Filesize": 0, "Severity": 0, "LocalTimestamp": 1617368327, "Code": "", "NewValue": "1", "Description": "Deck Motion", "Users": "", "Server_Storage": "", "Key": "", "Icon": "burglar.png", "PK_Store": "0" }, { "PK_Device": 290, "Room": 5, "DeviceName": "Deck Motion", "DeviceType": "urn:schemas-micasaverde-com:device:MotionSensor:1", "PK_Alert": "36034882632", "LocalDate": "2021-04-02 14:08:12", "EventType": 12, "SourceType": 3, "Argument": 0, "Filesize": 0, "Severity": 0, "LocalTimestamp": 1617368892, "Code": "", "NewValue": "1", "Description": "Deck Motion", "Users": "", "Server_Storage": "", "Key": "", "Icon": "burglar.png", "PK_Store": "0" }, { "PK_Device": 290, "Room": 5, "DeviceName": "Deck Motion", "DeviceType": "urn:schemas-micasaverde-com:device:MotionSensor:1", "PK_Alert": "36034926972", "LocalDate": "2021-04-02 14:12:02", "EventType": 12, "SourceType": 3, "Argument": 0, "Filesize": 0, "Severity": 0, "LocalTimestamp": 1617369122, "Code": "", "NewValue": "1", "Description": "Deck Motion", "Users": "", "Server_Storage": "", "Key": "", "Icon": "burglar.png", "PK_Store": "0" } ], "ZWaveStatus": 1, "Mode": 1, "LocalTime": "2021-04-02 20:13:02 N" } -
"Lounge Motion" not sure why that is referenced in there? That is a motion sensor in the lounge room.
"Deck Motion" is the virtual motion sensor I created to work with this Everspring Flood light parent device #699
Can see "Porch Motion Sensor" mentioned as well, that is an outdoor Everspring motion sensor not related.
-
You only care about what's in the "Device_Num_699" section of the file. You can "pretty up" the format in jsonlint.com, and if you look at that section, you'll find Armed is in there, state ID 621 at the very end of the states array.
}, { "id": 621, "service": "urn:micasaverde-com:serviceId:SecuritySensor1", "variable": "Armed", "value": "0" }],The other devices are in the alerts section of the response, which isn't relevant to our work here.
-
T toggledbits locked this topic on
