Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. Alerts - (vera>device_699) does not have attribute ?attr?
Reactor Loading Screen Safari
S
Topic thumbnail image
Multi-System Reactor
Constraints states visually do not match actual
S
Topic thumbnail image
Multi-System Reactor
[MSR] Feature request: For Each action on arrays/groups
therealdbT
Topic thumbnail image
Multi-System Reactor
[Solved] Error: Command timeout
G
at _ClientAPI._commandTimeout (http://192.168.1.100:8111/client/ClientAPI.js:807:179 Seeing this randomly when returning to open browser tab after being away awhile. Once, maybe twice a day. "What did you do to trigger it?" Literally nothing, just walked away and returned and there it was. Actions taken in reasonably close proximity to this particular instance of it popping up: I'd restarted the MSR container in Portainer. I'll try to grab some logs here shortly.
Multi-System Reactor
Issue with MSR UI becoming unresponsive
S
I'm having an issue with MSR's UI being very unresponsive. It started happening a couple days ago and I didn't make any changes that would have caused this except adding some meross lan devices in HA. When I go into an entity action and use the search functionality, it usually will start filtering and then get to a place after a few letters are entered where it will take 30 seconds or more (sometimes minutes) for the UI to show what I am typing. During this time MSR ui is completely unresponsive. I've tried multiple browsers and multiple computers. HA and MSR are both deployed in docker. I have run HTOP on the host and when the problem happens there are no CPU/Memory spikes at all. From a functionality standpoint MSR is working perfectly. This seems to be an UI issue only. Do i need to ditch Docker and run MSR on a Proxmox VM? I have both stand alone Docker and Proxmox environments. I dont mind doing that I just want to be able to use the UI again... Installation method Home Assistant Container Core 2025.7.3 Frontend 20250702.3 nothing crazy in the logs except some openweather map stuff that doesn't make any sense as it is working fine in MSR Any help would be greatly appreciated Reactor latest-25328-b2ed1365 app 25328 configuration from /var/reactor/config NODE_PATH /opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.843Z <app:null> Reactor build latest-25328-b2ed1365 starting on v24.11.1 /usr/local/bin/node [latest-25328]2025-11-30T20:01:53.844Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #161-Ubuntu SMP Tue Jul 22 14:25:40 UTC 2025; locale (undefined) [latest-25328]2025-11-30T20:01:53.844Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-25328]2025-11-30T20:01:53.844Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.865Z <app:null> Resolved timezone=America/New_York, environment TZ=America/New_York; offset minutes from UTC=-300 [latest-25328]2025-11-30T20:01:53.867Z <default:null> Module i18n v25141 [latest-25328]2025-11-30T20:01:53.867Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8 [latest-25328]2025-11-30T20:01:53.879Z <app:null> Loaded locale en-US for en-US [latest-25328]2025-11-30T20:01:53.879Z <app:null> Local date/time using configured timezone and locale formatting is "11/30/2025, 3:01:53 PM" [latest-25328]2025-11-30T20:01:53.889Z <Structure:null> Module Structure v25326 [latest-25328]2025-11-30T20:01:53.890Z <Capabilities:null> Module Capabilities v24312 [latest-25328]2025-11-30T20:01:53.904Z <Plugin:null> Module Plugin v25141 [latest-25328]2025-11-30T20:01:53.923Z <Timer:null> Module Timer v25279 [latest-25328]2025-11-30T20:01:53.924Z <TimerBroker:null> Module TimerBroker v25314 [latest-25328]2025-11-30T20:01:53.927Z <Entity:null> Module Entity v25251 [latest-25328]2025-11-30T20:01:53.929Z <Controller:null> Module Controller v25253 [latest-25328]2025-11-30T20:01:53.930Z <AlertManager:null> Module AlertManager v25318 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Ruleset v25283 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Rulesets v25141 [latest-25328]2025-11-30T20:01:53.942Z <GlobalExpression:null> Module GlobalExpression v25258 [latest-25328]2025-11-30T20:01:53.953Z <Predicate:null> Module Predicate v25328 [latest-25328]2025-11-30T20:01:53.956Z <Rule:null> Module Rule v25323 [latest-25328]2025-11-30T20:01:53.958Z <GlobalReaction:null> Module GlobalReaction v25292 [latest-25328]2025-11-30T20:01:53.959Z <Engine:null> Module Engine v25325 [latest-25328]2025-11-30T20:01:53.964Z <httpapi:null> Module httpapi v25328 [latest-25328]2025-11-30T20:01:53.972Z <wsapi:null> Module wsapi v25328 [latest-25328]2025-11-30T20:01:53.994Z <TaskQueue:null> Module TaskQueue 24138 [latest-25328]2025-11-30T20:01:53.994Z <VeraController:null> Module VeraController v25141 [latest-25328]2025-11-30T20:01:54.179Z <HassController:null> Module HassController v25325 [latest-25328]2025-11-30T20:02:13.797Z <OWMWeatherController:null> Module OWMWeatherController v25268 [latest-25328]2025-11-30T20:02:13.800Z <SystemController:null> Module SystemController v25323 [latest-25328]2025-11-30T20:02:13.807Z <MQTTController:null> Module MQTTController v22092 [latest-25328]2025-11-30T20:02:20.630Z <OWMWeatherController:CRIT> FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxx&lon=-xxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxxxxxxxxx&units=standard&_r=1xxxxxxxxxxxxxxfailed, reason: [-] FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxxx&lon=-xxxxxxxxxxxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxx&units=standard&_r=xxxxxxxxxxxxxxxfailed, reason: at ClientRequest.<anonymous> (/opt/reactor/node_modules/node-fetch/lib/index.js:1501:11) at ClientRequest.emit (node:events:508:28) at ClientRequest.emit (node:domain:489:12) at emitErrorEvent (node:_http_client:108:11) at TLSSocket.socketErrorListener (node:_http_client:575:5) at TLSSocket.emit (node:events:508:28) at TLSSocket.emit (node:domain:489:12) at emitErrorNT (node:internal/streams/destroy:170:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at processTicksAndRejections (node:internal/process/task_queues:89:21
Multi-System Reactor
Date/time condition
tunnusT
Topic thumbnail image
Multi-System Reactor
Device log?
G
@toggledbits is there a log that will show me what rule is turning on a specific device? I've got a switch that has been kicking on at 2200 ET for several nights now and the reactor.log doesn't have a thing in it that I can see on a device level (it being more rules-based).
Multi-System Reactor
Midnight crossing not working in date/time condition (build 25325)
tunnusT
Topic thumbnail image
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
[Solved] Local expression in Rule does not evaluate as they used to do
CrilleC
Topic thumbnail image
Multi-System Reactor
Home Assistant 2025.11.2 and latest-25315
CrilleC
Topic thumbnail image
Multi-System Reactor
Notice to Docker + ARM Users (RPi 3/4/5 and others)
toggledbitsT
This post does not apply to users of Intel/AMD-based systems. If you are using a Reactor image tagged latest-amd64 or stable-amd64, then this post does not apply to you. It also does not apply to bare-metal installs; it's for users of docker images on ARM-based systems only (principally Raspberry Pi hosts, but could be others). After January 15, 2026, I will no longer produce the aarch64-tagged docker image for Reactor. The ARM images will be arm64 for 64-bit operating systems, and armv7l for 32-bit operating systems. For those of you running a container from the aarch64 image today, this will be a relatively simple change: you just need to switch the image used for your docker container to a differently-tagged image. If you are using docker-compose, then this is a relatively simple matter of changing the image line in your docker-compose.yaml file and then stopping (docker-compose down) and restarting (docker-compose up -d) your Reactor daemon. But there's a catch... not all of you can safely just switch from the aarch64 image to the arm64 image. And, you can't just trust the output of uname -m, for example, because this exposes the CPU architecture, but not the word size of the OS running on that CPU. For Raspberry Pi systems, the transition to 64-bit operating systems was long (starting in 2016) and not always obvious — although there was a first "official" 64-bit OS for RPis in 2020, it did not become a default recommendation in the Raspberry Pi Imager until 2021, and then that was only the default for Pi 3/4 systems with >4GB RAM; it was 2022 before it was universally recommended for all 64-bit CPUs regardless of RAM size. Depending on when you first imaged your RPi system and what default you may have been offered/chosen, you could today easily have a 64-bit CPU Raspberry Pi running a 32-bit version of the operating system. Upgrades along the way would not change this; changing it to fully 64-bit requires a full reimage of the system. To establish if your OS is 64- or 32-bit, log in to your Pi and run: sudo dpkg-architecture -q DEB_HOST_ARCH. If the response is arm64 or aarch64, then you are running a 64-bit OS and you should use the arm64-tagged image. If it's anything else, you are running a 32-bit OS, and you should use the armv7l-tagged image. pi@rpi4-1:~ $ sudo dpkg-architecture -q DEB_HOST_ARCH armhf pi@rpi4-1:~ $ uname -m aarch64 pi@rpi4-1:~ $ In the example above, the uname command reports that the CPU is 64-bit architecture (aarch64), which is true for the host on which I ran these commands, but the DEB_HOST_ARCH value is armhf, indicating a 32-bit operating system. This system has to use the armv7l-tagged image. Other systems will have their own ways of determining the word size of the running OS. Since the majority of Reactor users running ARM systems are on Raspberry Pis, I am able to supply the above instructions, but if you happen to have a different ARM system, you'll need to do some web searching to figure out how to expose that information. Or, you can just try the arm64 image, and if it doesn't start up, try the armv7l image. Remember to always back up your system before making any changes. For everyone, please make this change as soon as possible, and if you have any trouble finding a working image, please (1) go back to the current aarch64 image; and (2) let me know in this thread along with as much detail about your host system as you can offer (including the output of the dpkg-architecture command mentioned above).
Multi-System Reactor
Requesting a proper ARM64/aarch64 Docker image (Pi 5 support)
M
Hi, I'm in the process of migrating from a Raspberry Pi 4 (ARMv7) to a Raspberry Pi 5 (ARMv8/aarch64), but I’ve run into an issue: there is no proper ARMv8/aarch64 image available. None of the existing images run on the Pi 5 - they all exit immediately with code 139 (segmentation fault), which typically indicates that the binaries inside the image are not compatible with the ARM64/aarch64 architecture used by the Pi 5. Would it be possible to publish a correct ARMv8/aarch64 (linux/arm64) image? Building one should be relatively straightforward using docker buildx with multi-arch support. For example, my own Node.js images are built this way: docker buildx build --push \ -t <localrepo>/<project>:<tag> \ --platform=linux/arm64,linux/amd64 \ --file ./apps/<project>/Dockerfile . This produces both the AMD64 and ARM64/v8 variants automatically. Also, as a side note, it may be best to avoid using Alpine as the base image for the ARM64 build, since musl-based builds often cause compatibility issues and unnecessary headaches. A glibc-based base image (e.g., Debian or Ubuntu) tends to work far more reliably on ARM64, especially for Node.js applications. @toggledbits - tagging you in case you missed this. Thanks, mgvra
Multi-System Reactor
Script action and custom timers
therealdbT
Sorry to write here without trying, but I’m flying today. Am I correct if i say that script action with alarm() makes it possible to execute a reaction in a given interval, lets say 15 seconds or 3.5 minutes? That sounds amazing, since I’ve used weird tricks, including a custom controller, just to do this.
Multi-System Reactor
Help resolve change in behaviour post update
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reactor w/HA 2025.11 error on set_datetime service call setting only time
CrilleC
@toggledbits Do you know if this is related to that PR or is it a change they made in 2025.11.1? [latest-25310]2025-11-11T13:16:24.319Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag with { "time": "10:45" } [latest-25310]2025-11-11T13:16:24.320Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_dag action: { "type": "call_service", "service_data": { "date": (null), "time": "10:45", "datetime": (null), "timestamp": (null) }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_dag" } } [latest-25310]2025-11-11T13:16:24.321Z <HassController:ERR> HassController#hass request 1762866984320<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.321Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "10:45" }) on Entity#hass>input_datetime_vvb_dag failed! [latest-25310]2025-11-11T13:16:24.321Z <HassController:INFO> Service call payload: {"type":"call_service","service_data":{"date":null,"time":"10:45","datetime":null,"timestamp":null},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_dag"},"id":1762866984320} [latest-25310]2025-11-11T13:16:24.322Z <HassController:INFO> Service data: {"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}} [latest-25310]2025-11-11T13:16:24.322Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 0 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Engine#1 action args: { "time": "10:45" } [latest-25310]2025-11-11T13:16:24.322Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 1 [latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass perform x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt with { "time": "03:00", "timestamp": 0 } [latest-25310]2025-11-11T13:16:24.323Z <HassController:INFO> HassController#hass: sending payload for x_hass_input_datetime.set_datetime on Entity#hass>input_datetime_vvb_natt action: { "type": "call_service", "service_data": { "date": (null), "time": "03:00", "datetime": (null), "timestamp": 0 }, "domain": "input_datetime", "service": "set_datetime", "target": { "entity_id": "input_datetime.vvb_natt" } } [latest-25310]2025-11-11T13:16:24.324Z <HassController:ERR> HassController#hass request 1762866984323<2025-11-11 14:16:24> (call_service) failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.324Z <HassController:WARN> HassController#hass action x_hass_input_datetime.set_datetime({ "time": "03:00", "timestamp": 0 }) on Entity#hass>input_datetime_vvb_natt failed! [latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service call payload: {"type":"call_service","service_data":{"date":null,"time":"03:00","datetime":null,"timestamp":0},"domain":"input_datetime","service":"set_datetime","target":{"entity_id":"input_datetime.vvb_natt"},"id":1762866984323} [latest-25310]2025-11-11T13:16:24.324Z <HassController:INFO> Service data: {"fields":{"date":{"example":"\"2019-04-20\"","selector":{"text":{"multiline":false,"multiple":false}}},"time":{"example":"\"05:04:20\"","selector":{"time":{}}},"datetime":{"example":"\"2019-04-20 05:04:20\"","selector":{"text":{"multiline":false,"multiple":false}}},"timestamp":{"selector":{"number":{"min":0,"max":9223372036854776000,"mode":"box","step":1}}}},"target":{"entity":[{"domain":["input_datetime"]}]}} [latest-25310]2025-11-11T13:16:24.324Z <Engine:ERR> Engine#1 reaction rule-mgb8pfhs:S step 1 perform x_hass_input_datetime.set_datetime failed: [Error] Not a parseable type for dictionary value @ data['date'] [-] [latest-25310]2025-11-11T13:16:24.324Z <Engine:INFO> Engine#1 action args: { "time": "03:00", "timestamp": 0 } [latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Resuming reaction Sätt Schema VVB i Home Assistant<AKTIV> (rule-mgb8pfhs:S) from step 2 [latest-25310]2025-11-11T13:16:24.325Z <Engine:INFO> Sätt Schema VVB i Home Assistant<AKTIV> all actions completed.
Multi-System Reactor
Reactor Version 25310 : Office Light control via rule in reactor no longer working since last update.
P
Hello, I currently have an office light (connected via a Leviton Zwave Dimmer switch) controlled from a Gen5 Aeotech Zwave switch installed on my Synology 720+ NAS. I run HA(2025.11.10) in a virtual machine from my NAS and Reactor on the container manager of the same NAS. Prior to updating to 25304 the rule I had set to turn the light on to a specific dimming value worked correctly. Now the rule appears to follow the decision tree, however the reaction does not trigger setting the dimming or turning on the office light? Strangely I can still turn the light on and off as well as dim it directly from HASS..? I have tried using the ''try this action'' button in the rules reaction setting and it will not control the light and does not throw an error flagÉ Please help, P.S Reactor has been rock steady for me over the last few years and I'm a big fan of this solution.
Multi-System Reactor
[Solved] alarm() in global expression throws error in log.
CrilleC
Topic thumbnail image
Multi-System Reactor
[Solved] Define function issue in latest-25304
CrilleC
Topic thumbnail image
Multi-System Reactor
No Upgrade Notification for Build 25308?
CatmanV2C
FWIW I'm no longer getting a notification from MSR that there's an update. Just thought I'd mention it C
Multi-System Reactor

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

Scheduled Pinned Locked Moved Multi-System Reactor
32 Posts 2 Posters 4.5k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by toggledbits
    #20

    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-kidC 1 Reply Last reply
    0
    • toggledbitsT 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.

      cw-kidC Offline
      cw-kidC Offline
      cw-kid
      wrote on last edited by
      #21

      @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.

      1 Reply Last reply
      0
      • toggledbitsT Offline
        toggledbitsT Offline
        toggledbits
        wrote on last edited by toggledbits
        #22

        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.

        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
        0
        • cw-kidC Offline
          cw-kidC Offline
          cw-kid
          wrote on last edited by cw-kid
          #23

          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.

          1 Reply Last reply
          0
          • toggledbitsT Offline
            toggledbitsT Offline
            toggledbits
            wrote on last edited by
            #24

            Change out sdata for status and 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.

            cw-kidC 1 Reply Last reply
            0
            • toggledbitsT toggledbits

              Change out sdata for status and see what it reports.

              cw-kidC Offline
              cw-kidC Offline
              cw-kid
              wrote on last edited by cw-kid
              #25

              @toggledbits

              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

              1 Reply Last reply
              0
              • toggledbitsT Offline
                toggledbitsT Offline
                toggledbits
                wrote on last edited by
                #26

                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.

                cw-kidC 2 Replies Last reply
                0
                • toggledbitsT toggledbits

                  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?

                  cw-kidC Offline
                  cw-kidC Offline
                  cw-kid
                  wrote on last edited by
                  #27

                  @toggledbits

                  http://Vera-IP:3480/data_request?id=status

                  1 Reply Last reply
                  0
                  • toggledbitsT toggledbits

                    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?

                    cw-kidC Offline
                    cw-kidC Offline
                    cw-kid
                    wrote on last edited by
                    #28

                    @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.

                    1 Reply Last reply
                    0
                    • toggledbitsT Offline
                      toggledbitsT Offline
                      toggledbits
                      wrote on last edited by toggledbits
                      #29

                      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.

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

                      cw-kidC 1 Reply Last reply
                      0
                      • toggledbitsT toggledbits

                        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.

                        cw-kidC Offline
                        cw-kidC Offline
                        cw-kid
                        wrote on last edited by
                        #30

                        @toggledbits

                        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" }
                        
                        1 Reply Last reply
                        0
                        • cw-kidC Offline
                          cw-kidC Offline
                          cw-kid
                          wrote on last edited by cw-kid
                          #31

                          "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.

                          1 Reply Last reply
                          0
                          • toggledbitsT Offline
                            toggledbitsT Offline
                            toggledbits
                            wrote on last edited by toggledbits
                            #32

                            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.

                            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
                            0
                            • toggledbitsT toggledbits locked this topic on
                            Reply
                            • Reply as topic
                            Log in to reply
                            • Oldest to Newest
                            • Newest to Oldest
                            • Most Votes


                            Recent Topics

                            • Any thoughts on which is better
                              CatmanV2C
                              CatmanV2
                              0
                              7
                              86

                            • Reactor Loading Screen Safari
                              S
                              SweetGenius
                              0
                              10
                              85

                            • Constraints states visually do not match actual
                              S
                              SweetGenius
                              0
                              3
                              37

                            • Oh the joy of pairing
                              CatmanV2C
                              CatmanV2
                              2
                              1
                              31

                            • HDMI oddness
                              CatmanV2C
                              CatmanV2
                              0
                              1
                              29

                            • Home Assistant Connect ZWA-2 & ZBT-2
                              therealdbT
                              therealdb
                              4
                              14
                              608

                            • [MSR] Feature request: For Each action on arrays/groups
                              therealdbT
                              therealdb
                              0
                              7
                              185

                            • [Solved] Error: Command timeout
                              toggledbitsT
                              toggledbits
                              0
                              10
                              474

                            • Issue with MSR UI becoming unresponsive
                              S
                              sethlampman
                              0
                              7
                              183

                            • Date/time condition
                              tunnusT
                              tunnus
                              0
                              3
                              132

                            • Is there a way to turn this section (image in post) off?
                              toggledbitsT
                              toggledbits
                              0
                              1
                              91
                            Powered by NodeBB | Contributors
                            Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                            • Login

                            • Don't have an account? Register

                            • Login or register to search.
                            • First post
                              Last post
                            0
                            • Categories
                            • Recent
                            • Tags
                            • Popular
                            • Unsolved