@toggledbits I understand that you do not perform testing on Mac computers but thought I'd share the following with you in case something can be done.
I started seeing these errors with version 24302. I thought that upgrading to 24343 would have fixed the issue but unfortunately not. I either have to close the browser or clear the cache for the errors to stop popping-up but they slowly come back.
I see these errors on the following browsers:
Safari 16.6.1 on macOS Big Sur Safari 18.1.1 on MacOS Sonoma DuckDuckGo 1.118.0 on macOS Big Sur and Sonoma Firefox 133.0.3 on macOS Big Sur Chrome 131.0.6778 on macOS Big SurHere are the errors
Safari while creating/updating an expression
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:543:91 makeExprMenu@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:537:28 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:92:64 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:68 each@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:3133 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:35 @http://192.168.0.13:8111/client/MessageBus.js:98:44 forEach@[native code] @http://192.168.0.13:8111/client/MessageBus.js:95:54 @http://192.168.0.13:8111/client/MessageBus.js:106:44 @http://192.168.0.13:8111/client/Observable.js:78:28 signalModified@http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:146:21 signalModified@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:40:29 reindexExpressions@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:71:32 @http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:608:40 dispatch@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:40040DuckDuckGo while clicking on status
http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-status.js:789:44 asyncFunctionResume@[native code] saveGridLayout@[native code] dispatchEvent@[native code] _triggerEvent@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:1401:30 _triggerAddEvent@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:1383:31 makeWidget@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:968:30 addWidget@http://192.168.0.13:8111/node_modules/gridstack/dist/gridstack.js:388:24 placeWidgetAdder@http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-status.js:183:44Firefox while updating a rule
@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:543:91 makeExprMenu@http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:537:28 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:92:64 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:68 each@http://192.168.0.13:8111/node_modules/jquery/dist/jquery.min.js:2:3133 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reaction-editor.js:89:35 @http://192.168.0.13:8111/client/MessageBus.js:98:44 forEach@[native code] @http://192.168.0.13:8111/client/MessageBus.js:95:54 @http://192.168.0.13:8111/client/MessageBus.js:106:44 @http://192.168.0.13:8111/client/Observable.js:78:28 notifySaved@http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:82:21 notifySaved@http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:47:26 @http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-rules.js:1460:39 forEach@[native code] @http://192.168.0.13:8111/reactor/en-ca/lib/js/reactor-ui-rules.js:1459:58Chrome while creating/updating an expression
TypeError: Cannot read properties of undefined (reading 'getEditor') at RuleEditor.makeExprMenu (http://192.168.0.13:8111/reactor/en-ca/lib/js/rule-editor.js:1788:86) at Object.handler (http://192.168.0.13:8111/reactor/en-ca/lib/js/rule-editor.js:2174:54) at http://192.168.0.13:8111/client/MessageBus.js:98:44 at Array.forEach (<anonymous>) at MessageBus._sendToBus (http://192.168.0.13:8111/client/MessageBus.js:95:54) at MessageBus.send (http://192.168.0.13:8111/client/MessageBus.js:106:44) at ExpressionEditor.publish (http://192.168.0.13:8111/client/Observable.js:78:28) at ExpressionEditor.signalModified (http://192.168.0.13:8111/reactor/en-ca/lib/js/ee.js:146:14) at ExpressionEditor.signalModified (http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:40:15) at ExpressionEditor.reindexExpressions (http://192.168.0.13:8111/reactor/en-ca/lib/js/expression-editor.js:71:18) ``Thanks to @toggledbits for adding a custom CSS. I've started doing a darker Reactor style.
Here's the file: https://gist.github.com/dbochicchio/825098ac13b7f8cac22012eae37ff7ce
A couple of things are still too bright and I'll eventually catch-up. Just place it under your /config directory, naming the file as customstyles.css. Hard refresh your browser.
Hi
Having to rebuild my Linux Debian box as the SSD failed. And I have forgotten exactly what I did the first time to get it all setup.
I have Debian 12 up and running on the new SSD, I only have console no Desktop GUI.
I am trying to do the bare metal install for MSR. However I am not sure if I am meant to install nodejs whlist logged in as the root user or as the none root user with my name ?
I used putty and connected via SSH and logged in as root and I installed nodejs but I think this was wrong as when logged in as my user name and I do a node -v command it says node is not installed or doesn't show any version number anyway.
But when logged in as root and I do a node -v command it does show me its installed and displays the version number. maybe its a path issue for my username and he can't see node is installed?
So now I am thinking I should of installed node whilst logged in as my user name and not as the root user.
This is how I installed nodejs as whilst logged in as root
ac7bf6c3-23ad-46fc-8ada-44af6704e63e-image.png
Thanks in advance.
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.As the title says, here's my OpenAI Controller for Reactor:
OpenAI Controller per Reactor. Contribute to dbochicchio/reactor-openai development by creating an account on GitHub.
It supports both OpenAI and Azure OpenAI endpoints. You'll need keys/endpoints, according to each service.
The controller supports multiple models, and each one could be mapped as an entity.
It's quite easy to use, and responses can be stored in variables, for easy access. Or sent to another action (Text To Speech, another endpoint, etc).
9013ae50-fd68-42a2-87c3-97479132e465-image.png
80a88eec-7c89-464a-8196-690b4b72d044-image.png
Have fun with LLM into your scenes!
In Home Assistant I have an integration that if I add entities to it, I will get the following error in MSR as certain entity values I'm using in expressions are null for a moment. This is more or less cosmetic issue and happens very rarely as I rarely modify that integration on the hass side.
Screenshot 2024-11-28 at 22.20.41.png
And the expression is
Screenshot 2024-11-28 at 22.38.19.png
Could I "wrap" hass-entity shown above somewhat differently to prevent this error from happening? Using build 24302.
Hello
I am trying to set up Multi System Reactor to automate routines across multiple smart home devices & platforms (e.g., Home Assistant, SmartThings, and Hubitat). While I have successfully linked the systems; I am facing issues with:
-Delays in triggering actions on secondary devices.
-Inconsistent execution of complex logic conditions.
-Synchronization of states between devices when one system updates.
Is there a recommended way to optimize performance & confirm seamless state sharing across systems?
I have checked https://smarthome.community/category/22/multi-system-reactor-msbi guide for reference but still need advice.
Any tips on debugging or log analysis to pinpoint where the issue arises would also be appreciated.
Thank you !
I've managed to use MSR UI on iOS devices to some degree*, so that although UI elements (e.g. rule sets) are not visible in portrait mode, you've seen them in landscape. Now with recents builds (24302) this does not work anymore, elements (rule sets, entities) are not anymore visible in landscape mode.
Does anyone have similar experiences? Using iOS 18 and Safari/Chrome browser.
( *Drag & drop of rule conditions have never worked on a mobile)
@toggledbits Since I have upgraded ZWaveJSController to 24293 from 24257 I am seeing entries related to registering action set_volume, but action is not defined by the capability 143 every time I restart Reactor.
The Siren seems to be doing what it is supposed to do. The volume levels are fine. Should I worry about it?
Reactor version 24302
ZWaveJSController version 24293
Z-Wave JS UI version 9.27.4
zwave-js version 14.3.4
I have the following ACL defined:
groups: admin: users: - admin applications: true api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: trueAnd I have authenticated to MSR as "admin" user. However, I'm getting "access denied" when trying to access http://*******:8111/api/v1/log
So what I'm missing, is my ACL incorrectly defined?
Using build 24302 on Docker.
Hi
I have just connected a bunch of EzloPi controllers to MSR to import some ESP based devices etc.
They all seemed to have worked and imported in to MSR apart from I have one missing device. It is a Digital Gas Sensor device.
This is how that device looks in the Ezlo API.
Devices Info:
_id: "10696001" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "level_sensor" subcategory: "" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Digital" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"Items Info:
_id: "20696001" deviceId: "10696001" hasGetter: true hasSetter: false name: "smoke_density" show: true valueType: "substance_amount" scale: "parts_per_million" value: 2.7472610473632812 valueFormatted: "2.75" status: "idle"There is also an Analog Gas sensor that one did import in to MSR OK.
68d63dab-b871-4f44-912b-cf6e0b9eb4c6-image.png
Devices Info:
_id: "10696000" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "security_sensor" subcategory: "gas" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Analog" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"Items Info:
_id: "20696000" deviceId: "10696000" hasGetter: true hasSetter: false name: "gas_alarm" show: true valueType: "token" enum: 0: "no_gas" 1: "combustible_gas_detected" 2: "toxic_gas_detected" 3: "unknown" valueFormatted: "no_gas" value: "no_gas" status: "idle"And this is how this MQ2 Gas Sensor looks like on their dashboard:
Digital
cb77dfa3-4af5-4d06-9635-89207a716a89-image.png
Analog
4fb4da1b-e946-4b89-876c-bcd9f5699b6c-image.png
They have an EzloPi website here you can create your own sensor projects using ESP boards, which is very interesting stuff!
And I just wrote on the Ezlo forum here, how to connect an EzloPi controller to MSR.
THANKS.
A couple of things for you @toggledbits, since you mentioned that this release has new features and some tweaks are expected.
Local expressions cannot be deleted. Pushing the X button has no effect for me.
When cloning an entity action, the result is strange (first is cloned one, second is the original action):
a92ea094-9e2c-4aaa-bf47-2d07a6ffdbd0-image.png
When changing the action on the cloned element, the params are added to the original one. See screenshot:
92ac3011-83c8-466b-bd23-47d483ad7a52-image.png
Dark theme has a couple of strange contrasts. One is visible in the previous screenshots (white text on yellow background). Another one is in groups (blue text on blue background):
9b3c4988-53ef-44e6-9672-30e744cacb75-image.png
Overall, I found blue, yellow, red and green (in buttons and forms) to be too bright.
On the bright side:
I love the new script action: thank you! The dark theme is a great start to avoid getting blinded at night I promise I'll try very soon the new features around actions. Thanks!@toggledbits
I just upgraded to version MSR 24293, bare metal running on Fedora. Upon restart, I am getting a error banner:
I followed the new directions about npm
npm i --no-save --no-package-lock --omit dev
Any idea what the issue is?
Seems like switching the UI to the newly added dark mode (thank you for this) does nothing. The UI stays in light mode and only a few buttons turn into dark mode (see screenshot)
Things I have tried:
Hard refresh
Different browser
Different computer
Restarting Reactor
Failed troubleshooting attempts:
No errors in Chrome console
No relevant errors in Reactor log (can still PM the full log file)
Reactor version: latest-24293-ea42a81d
Hardware: Odroid N2+
Linux version: Ubuntu 24.04.1 LTS
3df2806f-9146-485b-9ec1-d056e91cefe5-image.png Dark mode enabled
ff823023-c079-4684-b01f-d6ac6527d31a-image.png Light mode enabled
Good morning,
I have a service MQTT service that needs a restart occasionally. The add-on (Smartbed MQTT) is for the smart bed base for my bed. It has a "safety light" that I can control from HAAS & MSR as a light entity, and also moves the head of the bed to a preset at bedtime, and then lies it back flat in the morning The problem is, from time to time, the light becomes "unavailable" Restarting from the Add-ons tab in HAAS always fixes it, but I should be able to detect when it happens when "light.tempur_pedic_safety_lights" is not true or false, i.e., unavailable.
What I don't know how to do is how to restart that service. Does anybody have experience in restarting add-ons from MSR?
Running:
Reactor (Multi-hub) latest-24212-3ce15e25 ZWaveJSController [0.1.24232]HAAS:
RPi5-64 (8GB) Core 2024.7.3 Supervisor 2024.08.0 Operating System 13.0 Frontend 20240710.0Alerts - (vera>device_699) does not have attribute ?attr?
-
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
sdata
forstatus
and 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?
-
-
@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
DeviceNum
parameter, and please don't edit any of the response when posting:http://vera-ip:3480/data_request?id=status&DeviceNum=699
The 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.
-