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
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.
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.
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).
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
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.
@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.
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.
Power_switch.state - no change state - EzloPlus - Msr v. 21351-a3aef - Synology Docker
-
[latest-21353]2021-12-19T23:08:41.146Z <EzloController:WARN> EzloController#ezlo updating value for color_temperature: item named rgbcolor not found on "61508730129e29124787e30c" (Entity#ezlo>device_61508730129e29124787e30c); has [Array][ "61508730129e29124787e30d", "switch", "61508730129e29124787e30e", "dimmer", "61508730129e29124787e30f", "dimmer_up", "61508730129e29124787e310", "dimmer_down", "61508730129e29124787e311", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.147Z <EzloController:WARN> EzloController#ezlo updating red for rgb_color: item named rgbcolor not found on "61508730129e29124787e312" (Entity#ezlo>device_61508730129e29124787e312); has [Array][ "61508730129e29124787e313", "switch", "61508730129e29124787e314", "dimmer", "61508730129e29124787e315", "dimmer_up", "61508730129e29124787e316", "dimmer_down", "61508730129e29124787e317", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.147Z <EzloController:WARN> EzloController#ezlo updating green for rgb_color: item named rgbcolor not found on "61508730129e29124787e312" (Entity#ezlo>device_61508730129e29124787e312); has [Array][ "61508730129e29124787e313", "switch", "61508730129e29124787e314", "dimmer", "61508730129e29124787e315", "dimmer_up", "61508730129e29124787e316", "dimmer_down", "61508730129e29124787e317", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.148Z <EzloController:WARN> EzloController#ezlo updating blue for rgb_color: item named rgbcolor not found on "61508730129e29124787e312" (Entity#ezlo>device_61508730129e29124787e312); has [Array][ "61508730129e29124787e313", "switch", "61508730129e29124787e314", "dimmer", "61508730129e29124787e315", "dimmer_up", "61508730129e29124787e316", "dimmer_down", "61508730129e29124787e317", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.148Z <EzloController:WARN> EzloController#ezlo updating value for color_temperature: item named rgbcolor not found on "61508730129e29124787e312" (Entity#ezlo>device_61508730129e29124787e312); has [Array][ "61508730129e29124787e313", "switch", "61508730129e29124787e314", "dimmer", "61508730129e29124787e315", "dimmer_up", "61508730129e29124787e316", "dimmer_down", "61508730129e29124787e317", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.149Z <EzloController:WARN> EzloController#ezlo updating red for rgb_color: item named rgbcolor not found on "61508730129e29124787e318" (Entity#ezlo>device_61508730129e29124787e318); has [Array][ "61508730129e29124787e319", "switch", "61508730129e29124787e31a", "dimmer", "61508730129e29124787e31b", "dimmer_up", "61508730129e29124787e31c", "dimmer_down", "61508731129e29124787e31d", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.149Z <EzloController:WARN> EzloController#ezlo updating green for rgb_color: item named rgbcolor not found on "61508730129e29124787e318" (Entity#ezlo>device_61508730129e29124787e318); has [Array][ "61508730129e29124787e319", "switch", "61508730129e29124787e31a", "dimmer", "61508730129e29124787e31b", "dimmer_up", "61508730129e29124787e31c", "dimmer_down", "61508731129e29124787e31d", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.150Z <EzloController:WARN> EzloController#ezlo updating blue for rgb_color: item named rgbcolor not found on "61508730129e29124787e318" (Entity#ezlo>device_61508730129e29124787e318); has [Array][ "61508730129e29124787e319", "switch", "61508730129e29124787e31a", "dimmer", "61508730129e29124787e31b", "dimmer_up", "61508730129e29124787e31c", "dimmer_down", "61508731129e29124787e31d", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.150Z <EzloController:WARN> EzloController#ezlo updating value for color_temperature: item named rgbcolor not found on "61508730129e29124787e318" (Entity#ezlo>device_61508730129e29124787e318); has [Array][ "61508730129e29124787e319", "switch", "61508730129e29124787e31a", "dimmer", "61508730129e29124787e31b", "dimmer_up", "61508730129e29124787e31c", "dimmer_down", "61508731129e29124787e31d", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.151Z <EzloController:WARN> EzloController#ezlo updating red for rgb_color: item named rgbcolor not found on "61508731129e29124787e31e" (Entity#ezlo>device_61508731129e29124787e31e); has [Array][ "61508731129e29124787e31f", "switch", "61508731129e29124787e320", "dimmer", "61508731129e29124787e321", "dimmer_up", "61508731129e29124787e322", "dimmer_down", "61508731129e29124787e323", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.151Z <EzloController:WARN> EzloController#ezlo updating green for rgb_color: item named rgbcolor not found on "61508731129e29124787e31e" (Entity#ezlo>device_61508731129e29124787e31e); has [Array][ "61508731129e29124787e31f", "switch", "61508731129e29124787e320", "dimmer", "61508731129e29124787e321", "dimmer_up", "61508731129e29124787e322", "dimmer_down", "61508731129e29124787e323", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.152Z <EzloController:WARN> EzloController#ezlo updating blue for rgb_color: item named rgbcolor not found on "61508731129e29124787e31e" (Entity#ezlo>device_61508731129e29124787e31e); has [Array][ "61508731129e29124787e31f", "switch", "61508731129e29124787e320", "dimmer", "61508731129e29124787e321", "dimmer_up", "61508731129e29124787e322", "dimmer_down", "61508731129e29124787e323", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.152Z <EzloController:WARN> EzloController#ezlo updating value for color_temperature: item named rgbcolor not found on "61508731129e29124787e31e" (Entity#ezlo>device_61508731129e29124787e31e); has [Array][ "61508731129e29124787e31f", "switch", "61508731129e29124787e320", "dimmer", "61508731129e29124787e321", "dimmer_up", "61508731129e29124787e322", "dimmer_down", "61508731129e29124787e323", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.154Z <EzloController:WARN> EzloController#ezlo updating red for rgb_color: item named rgbcolor not found on "61522118129e291232d6d9fd" (Entity#ezlo>device_61522118129e291232d6d9fd); has [Array][ "61522118129e291232d6d9fe", "switch", "61522118129e291232d6d9ff", "dimmer", "61522118129e291232d6da00", "dimmer_up", "61522118129e291232d6da01", "dimmer_down", "61522118129e291232d6da02", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.155Z <EzloController:WARN> EzloController#ezlo updating green for rgb_color: item named rgbcolor not found on "61522118129e291232d6d9fd" (Entity#ezlo>device_61522118129e291232d6d9fd); has [Array][ "61522118129e291232d6d9fe", "switch", "61522118129e291232d6d9ff", "dimmer", "61522118129e291232d6da00", "dimmer_up", "61522118129e291232d6da01", "dimmer_down", "61522118129e291232d6da02", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.155Z <EzloController:WARN> EzloController#ezlo updating blue for rgb_color: item named rgbcolor not found on "61522118129e291232d6d9fd" (Entity#ezlo>device_61522118129e291232d6d9fd); has [Array][ "61522118129e291232d6d9fe", "switch", "61522118129e291232d6d9ff", "dimmer", "61522118129e291232d6da00", "dimmer_up", "61522118129e291232d6da01", "dimmer_down", "61522118129e291232d6da02", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.155Z <EzloController:WARN> EzloController#ezlo updating value for color_temperature: item named rgbcolor not found on "61522118129e291232d6d9fd" (Entity#ezlo>device_61522118129e291232d6d9fd); has [Array][ "61522118129e291232d6d9fe", "switch", "61522118129e291232d6d9ff", "dimmer", "61522118129e291232d6da00", "dimmer_up", "61522118129e291232d6da01", "dimmer_down", "61522118129e291232d6da02", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.156Z <EzloController:WARN> EzloController#ezlo updating red for rgb_color: item named rgbcolor not found on "61522118129e291232d6da03" (Entity#ezlo>device_61522118129e291232d6da03); has [Array][ "61522118129e291232d6da04", "switch", "61522118129e291232d6da05", "dimmer", "61522118129e291232d6da06", "dimmer_up", "61522119129e291232d6da07", "dimmer_down", "61522119129e291232d6da08", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.157Z <EzloController:WARN> EzloController#ezlo updating green for rgb_color: item named rgbcolor not found on "61522118129e291232d6da03" (Entity#ezlo>device_61522118129e291232d6da03); has [Array][ "61522118129e291232d6da04", "switch", "61522118129e291232d6da05", "dimmer", "61522118129e291232d6da06", "dimmer_up", "61522119129e291232d6da07", "dimmer_down", "61522119129e291232d6da08", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.157Z <EzloController:WARN> EzloController#ezlo updating blue for rgb_color: item named rgbcolor not found on "61522118129e291232d6da03" (Entity#ezlo>device_61522118129e291232d6da03); has [Array][ "61522118129e291232d6da04", "switch", "61522118129e291232d6da05", "dimmer", "61522118129e291232d6da06", "dimmer_up", "61522119129e291232d6da07", "dimmer_down", "61522119129e291232d6da08", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.157Z <EzloController:WARN> EzloController#ezlo updating value for color_temperature: item named rgbcolor not found on "61522118129e291232d6da03" (Entity#ezlo>device_61522118129e291232d6da03); has [Array][ "61522118129e291232d6da04", "switch", "61522118129e291232d6da05", "dimmer", "61522118129e291232d6da06", "dimmer_up", "61522119129e291232d6da07", "dimmer_down", "61522119129e291232d6da08", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.158Z <EzloController:WARN> EzloController#ezlo updating red for rgb_color: item named rgbcolor not found on "61522119129e291232d6da09" (Entity#ezlo>device_61522119129e291232d6da09); has [Array][ "61522119129e291232d6da0a", "switch", "61522119129e291232d6da0b", "dimmer", "61522119129e291232d6da0c", "dimmer_up", "61522119129e291232d6da0d", "dimmer_down", "61522119129e291232d6da0e", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.159Z <EzloController:WARN> EzloController#ezlo updating green for rgb_color: item named rgbcolor not found on "61522119129e291232d6da09" (Entity#ezlo>device_61522119129e291232d6da09); has [Array][ "61522119129e291232d6da0a", "switch", "61522119129e291232d6da0b", "dimmer", "61522119129e291232d6da0c", "dimmer_up", "61522119129e291232d6da0d", "dimmer_down", "61522119129e291232d6da0e", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.159Z <EzloController:WARN> EzloController#ezlo updating blue for rgb_color: item named rgbcolor not found on "61522119129e291232d6da09" (Entity#ezlo>device_61522119129e291232d6da09); has [Array][ "61522119129e291232d6da0a", "switch", "61522119129e291232d6da0b", "dimmer", "61522119129e291232d6da0c", "dimmer_up", "61522119129e291232d6da0d", "dimmer_down", "61522119129e291232d6da0e", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.159Z <EzloController:WARN> EzloController#ezlo updating value for color_temperature: item named rgbcolor not found on "61522119129e291232d6da09" (Entity#ezlo>device_61522119129e291232d6da09); has [Array][ "61522119129e291232d6da0a", "switch", "61522119129e291232d6da0b", "dimmer", "61522119129e291232d6da0c", "dimmer_up", "61522119129e291232d6da0d", "dimmer_down", "61522119129e291232d6da0e", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.161Z <EzloController:WARN> EzloController#ezlo updating red for rgb_color: item named rgbcolor not found on "61522119129e291232d6da0f" (Entity#ezlo>device_61522119129e291232d6da0f); has [Array][ "61522119129e291232d6da10", "switch", "61522119129e291232d6da11", "dimmer", "61522119129e291232d6da12", "dimmer_up", "61522119129e291232d6da13", "dimmer_down", "61522119129e291232d6da14", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.162Z <EzloController:WARN> EzloController#ezlo updating green for rgb_color: item named rgbcolor not found on "61522119129e291232d6da0f" (Entity#ezlo>device_61522119129e291232d6da0f); has [Array][ "61522119129e291232d6da10", "switch", "61522119129e291232d6da11", "dimmer", "61522119129e291232d6da12", "dimmer_up", "61522119129e291232d6da13", "dimmer_down", "61522119129e291232d6da14", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.162Z <EzloController:WARN> EzloController#ezlo updating blue for rgb_color: item named rgbcolor not found on "61522119129e291232d6da0f" (Entity#ezlo>device_61522119129e291232d6da0f); has [Array][ "61522119129e291232d6da10", "switch", "61522119129e291232d6da11", "dimmer", "61522119129e291232d6da12", "dimmer_up", "61522119129e291232d6da13", "dimmer_down", "61522119129e291232d6da14", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.162Z <EzloController:WARN> EzloController#ezlo updating value for color_temperature: item named rgbcolor not found on "61522119129e291232d6da0f" (Entity#ezlo>device_61522119129e291232d6da0f); has [Array][ "61522119129e291232d6da10", "switch", "61522119129e291232d6da11", "dimmer", "61522119129e291232d6da12", "dimmer_up", "61522119129e291232d6da13", "dimmer_down", "61522119129e291232d6da14", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.173Z <EzloController:WARN> EzloController#ezlo updating state for power_switch: item named switch not found on "6198168b129e2918c5ce97bc" (Entity#ezlo>device_6198168b129e2918c5ce97bc); has [Array][ "6198168b129e2918c5ce97bd", "dimmer", "6198168b129e2918c5ce97be", "dimmer_up", "6198168b129e2918c5ce97bf", "dimmer_down", "6198168b129e2918c5ce97c0", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.174Z <EzloController:WARN> EzloController#ezlo updating state for power_switch: item named switch not found on "619816bb129e2918c5ce97c1" (Entity#ezlo>device_619816bb129e2918c5ce97c1); has [Array][ "619816bb129e2918c5ce97c2", "dimmer", "619816bb129e2918c5ce97c3", "dimmer_up", "619816bc129e2918c5ce97c4", "dimmer_down", "619816bc129e2918c5ce97c5", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.175Z <EzloController:WARN> EzloController#ezlo updating state for power_switch: item named switch not found on "6198173f129e2918c5ce97c6" (Entity#ezlo>device_6198173f129e2918c5ce97c6); has [Array][ "6198173f129e2918c5ce97c7", "dimmer", "6198173f129e2918c5ce97c8", "dimmer_up", "6198173f129e2918c5ce97c9", "dimmer_down", "6198173f129e2918c5ce97ca", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.176Z <EzloController:WARN> EzloController#ezlo updating state for power_switch: item named switch not found on "61981760129e2918c5ce97cb" (Entity#ezlo>device_61981760129e2918c5ce97cb); has [Array][ "61981760129e2918c5ce97cc", "dimmer", "61981760129e2918c5ce97cd", "dimmer_up", "61981760129e2918c5ce97ce", "dimmer_down", "61981760129e2918c5ce97cf", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.177Z <EzloController:WARN> EzloController#ezlo updating state for power_switch: item named switch not found on "61981770129e2918c5ce97d0" (Entity#ezlo>device_61981770129e2918c5ce97d0); has [Array][ "61981770129e2918c5ce97d1", "dimmer", "61981770129e2918c5ce97d2", "dimmer_up", "61981770129e2918c5ce97d3", "dimmer_down", "61981770129e2918c5ce97d4", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.178Z <EzloController:WARN> EzloController#ezlo updating state for power_switch: item named switch not found on "6198177e129e2918c5ce97d5" (Entity#ezlo>device_6198177e129e2918c5ce97d5); has [Array][ "6198177e129e2918c5ce97d6", "dimmer", "6198177e129e2918c5ce97d7", "dimmer_up", "6198177e129e2918c5ce97d8", "dimmer_down", "6198177e129e2918c5ce97d9", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.179Z <EzloController:WARN> EzloController#ezlo updating state for power_switch: item named switch not found on "6198178b129e2918c5ce97da" (Entity#ezlo>device_6198178b129e2918c5ce97da); has [Array][ "6198178b129e2918c5ce97db", "dimmer", "6198178b129e2918c5ce97dc", "dimmer_up", "6198178b129e2918c5ce97dd", "dimmer_down", "6198178b129e2918c5ce97de", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.183Z <EzloController:WARN> EzloController#ezlo updating state for power_switch: item named switch not found on "6198179b129e2918c5ce97df" (Entity#ezlo>device_6198179b129e2918c5ce97df); has [Array][ "6198179b129e2918c5ce97e0", "dimmer", "6198179b129e2918c5ce97e1", "dimmer_up", "6198179b129e2918c5ce97e2", "dimmer_down", "6198179b129e2918c5ce97e3", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.184Z <EzloController:WARN> EzloController#ezlo updating state for power_switch: item named switch not found on "619817a6129e2918c5ce97e4" (Entity#ezlo>device_619817a6129e2918c5ce97e4); has [Array][ "619817a6129e2918c5ce97e5", "dimmer", "619817a7129e2918c5ce97e6", "dimmer_up", "619817a7129e2918c5ce97e7", "dimmer_down", "619817a7129e2918c5ce97e8", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.185Z <EzloController:WARN> EzloController#ezlo updating state for power_switch: item named switch not found on "619817b2129e2918c5ce97e9" (Entity#ezlo>device_619817b2129e2918c5ce97e9); has [Array][ "619817b2129e2918c5ce97ea", "dimmer", "619817b3129e2918c5ce97eb", "dimmer_up", "619817b3129e2918c5ce97ec", "dimmer_down", "619817b3129e2918c5ce97ed", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.186Z <EzloController:WARN> EzloController#ezlo updating state for power_switch: item named switch not found on "619817c2129e2918c5ce97ee" (Entity#ezlo>device_619817c2129e2918c5ce97ee); has [Array][ "619817c3129e2918c5ce97ef", "dimmer", "619817c3129e2918c5ce97f0", "dimmer_up", "619817c3129e2918c5ce97f1", "dimmer_down", "619817c3129e2918c5ce97f2", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.187Z <EzloController:WARN> EzloController#ezlo updating state for power_switch: item named switch not found on "619817d0129e2918c5ce97f3" (Entity#ezlo>device_619817d0129e2918c5ce97f3); has [Array][ "619817d0129e2918c5ce97f4", "dimmer", "619817d0129e2918c5ce97f5", "dimmer_up", "619817d0129e2918c5ce97f6", "dimmer_down", "619817d0129e2918c5ce97f7", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.190Z <EzloController:WARN> EzloController#ezlo updating state for power_switch: item named switch not found on "619817de129e2918c5ce97f8" (Entity#ezlo>device_619817de129e2918c5ce97f8); has [Array][ "619817de129e2918c5ce97f9", "dimmer", "619817de129e2918c5ce97fa", "dimmer_up", "619817de129e2918c5ce97fb", "dimmer_down", "619817de129e2918c5ce97fc", "dimmer_stop" ] [latest-21353]2021-12-19T23:08:41.192Z <EzloController:WARN> EzloController#ezlo no implementation mapping for attributes from match category=door_lock cap keypad [latest-21353]2021-12-19T23:08:41.196Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "619903e9129e29123e89442e" (Entity#ezlo>device_619903e9129e29123e89442e); has [Array][ "619903e9129e29123e89442f", "basic", "619903e9129e29123e894430", "battery", "619903e9129e29123e894431", "tampering_cover_alarm", "619903e9129e29123e894432", "battery_maintenance_state", "619903e9129e29123e894433", "dw_state", "619903e9129e29123e894434", "security_threat" ] [latest-21353]2021-12-19T23:08:41.196Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "619903e9129e29123e89442e" (Entity#ezlo>device_619903e9129e29123e89442e); has [Array][ "619903e9129e29123e89442f", "basic", "619903e9129e29123e894430", "battery", "619903e9129e29123e894431", "tampering_cover_alarm", "619903e9129e29123e894432", "battery_maintenance_state", "619903e9129e29123e894433", "dw_state", "619903e9129e29123e894434", "security_threat" ] [latest-21353]2021-12-19T23:08:41.198Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "619903e9129e29123e894437" (Entity#ezlo>device_619903e9129e29123e894437); has [Array][ "619903ea129e29123e894438", "heat_alarm", "619903ea129e29123e894439", "security_threat" ] [latest-21353]2021-12-19T23:08:41.198Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "619903e9129e29123e894437" (Entity#ezlo>device_619903e9129e29123e894437); has [Array][ "619903ea129e29123e894438", "heat_alarm", "619903ea129e29123e894439", "security_threat" ] [latest-21353]2021-12-19T23:08:41.200Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "619903ea129e29123e89443a" (Entity#ezlo>device_619903ea129e29123e89443a); has [Array][ "619903ea129e29123e89443b", "temp" ] [latest-21353]2021-12-19T23:08:41.200Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "619903ea129e29123e89443a" (Entity#ezlo>device_619903ea129e29123e89443a); has [Array][ "619903ea129e29123e89443b", "temp" ] [latest-21353]2021-12-19T23:08:41.239Z <EzloController:INFO> EzloController#ezlo hub inventory complete/successful; 1034ms -
OK. Those are benign, but I'd still like to try and clean them up. There are devices listed that aren't in the previous upload you gave me, so can I ask that you use that upload link previously sent (in DM to you here) and upload the latest [data--see edit below] file from your
logsdirectory? That will tell me what the devices are reporting more clearly.Edit: the file is now called
ezlo_inventory.jsonfor the latest version. -
If can help, today I added another zwave device "Widom Smart Plug" https://www.widom.it/wp-content/uploads/2019/08/Widom-Smart-Plug_EN_20190404_0.pdf
At the moment it is ON and in Entities power.switch_state is FALSEenergy_sensor.units="kilo_watt_hour" energy_sensor.value=0.0230000000447035 power_sensor.units="watt" power_sensor.value=36.7000007629395 power_switch.state=false x_ezlo_device.battery_powered=false x_ezlo_device.category="switch" x_ezlo_device.manufacturer="Unknown" x_ezlo_device.model="Unknown" x_ezlo_device.parent="" x_ezlo_device.reachable=true x_ezlo_device.ready=true x_ezlo_device.room="613e2037129e2912114c093e" x_ezlo_device.status="idle" x_ezlo_device.subcategory="interior_plugin" x_ezlo_device.type_id="329_4628_1792" x_ezlo_item.electric_meter_kwh=0.0230000000447035 x_ezlo_item.electric_meter_volt=230.399993896484 x_ezlo_item.electric_meter_watt=36.7000007629395 x_ezlo_item.meter_reset=0 x_ezlo_item.switch=false x_ezlo_object.id="61c18f96129e291255528096" zwave_device.capabilities=null zwave_device.failed=false zwave_device.manufacturer_info=["Unknown","Unknown",null] zwave_device.node_id=60 zwave_device.version_info=null Capabilities: energy_sensor, power_sensor, power_switch, toggle, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device Actions: power_switch.off, power_switch.on, power_switch.set, toggle.toggle, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighbors ``` -
OK. If you would please, upload your
ezlo_inventory.jsonfile again.I would also note that the
switchitem (seen in raw form inx_ezlo_item.switch) also says false, so check in the (Vera/Ezlo) mobile app what it reports for state. It's not relevant what state the switch is physically in, only what state the hub thinks its in. If they don't agree, neither will Reactor. -
OK. New data maps with no further changes to previous work, so I'm going to go ahead and build. Watch for the update announcement in that topic.
-
Any errors in the log? You know you always need to look there whenever things don't seem right, yes?
Also, I would do a hard-refresh of the browser and open that page again. I have seen it get out of sync once in a while but I haven't been able to figure out why as yet.
-
Not so sure... try changing the switch state of one of them (toggle one of them manually), see if both attributes follow... I'm guessing they'll diverge...
-
what I can notice in "Entities" is that at the moment this device is OFF, but dimmer_level is =1
L Bulb Spot Widom Dimmer ezlo>device_61475325129e29124dfcd7e6 1 2:16:40 AM dimming.level=1 dimming.step=0.1 dimming.undefined=0 energy_sensor.undefined="KWh" energy_sensor.units="KWh" energy_sensor.value=0.994000017642975 power_sensor.undefined="W" power_sensor.units="W" power_sensor.value=7.96000003814697 power_switch.state=true power_switch.undefined=false x_ezlo_device.battery_powered=false x_ezlo_device.category="dimmable_light" x_ezlo_device.manufacturer="Unknown" x_ezlo_device.model="Unknown" x_ezlo_device.parent="" x_ezlo_device.reachable=true x_ezlo_device.ready=true x_ezlo_device.room="613e2024129e2912114c093b" x_ezlo_device.status="idle" x_ezlo_device.subcategory="dimmable_in_wall" x_ezlo_device.type_id="329_4628_2560" x_ezlo_item.dimmer=0 x_ezlo_item.dimmer_down=0 x_ezlo_item.dimmer_stop=0 x_ezlo_item.dimmer_up=0 x_ezlo_item.electric_meter_kwh=0.996999979019165 x_ezlo_item.electric_meter_watt=0 x_ezlo_item.meter_reset=0 x_ezlo_item.switch=false x_ezlo_object.id="61475325129e29124dfcd7e6" zwave_device.capabilities=null zwave_device.failed=false zwave_device.manufacturer_info=["Unknown","Unknown",null] zwave_device.node_id=38 zwave_device.version_info=null Capabilities: dimming, energy_sensor, power_sensor, power_switch, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighborsor this other one, dimmer level diverge from msr to ezlo
K Bulb Domitech ezlo>device_61423589129e29124dfcd756 0 2:30:41 AM dimming.level=0 dimming.step=0.1 dimming.undefined=0.25 power_switch.state=false power_switch.undefined=true x_ezlo_device.battery_powered=false x_ezlo_device.category="dimmable_light" x_ezlo_device.manufacturer="Domitech" x_ezlo_device.model="ZE27EU" x_ezlo_device.parent="" x_ezlo_device.reachable=true x_ezlo_device.ready=true x_ezlo_device.room="613e2020129e2912114c093a" x_ezlo_device.status="idle" x_ezlo_device.subcategory="dimmable_bulb" x_ezlo_device.type_id="526_19522_12596" x_ezlo_item.dimmer=25 x_ezlo_item.dimmer_down=0 x_ezlo_item.dimmer_stop=0 x_ezlo_item.dimmer_up=0 x_ezlo_item.switch=true x_ezlo_object.id="61423589129e29124dfcd756" zwave_device.capabilities=null zwave_device.failed=false zwave_device.manufacturer_info=["Domitech","ZE27EU",null] zwave_device.node_id=26 zwave_device.version_info=null Capabilities: dimming, power_switch, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighbors -
The real give-away there is the
power_switch.undefinedattribute in the list. I can reproduce the issue. I won't be able to roll a fix tonight, but I'll have something out tomorrow. -
Hi, it seems working ok. Thanks! If you need more infos to test, just tell me how I can produce them.
L Bulb FibaroDimmer2 ezlo>device_61425874129e29124dfcd75e 0.65 7:30:07 PM dimming.level=0.65 dimming.step=0.1 energy_sensor.units="KWh" energy_sensor.value=11.3400001525879 power_sensor.units="W" power_sensor.value=6.90000009536743 power_switch.state=true x_ezlo_device.battery_powered=false x_ezlo_device.category="dimmable_light" x_ezlo_device.manufacturer="Fibaro" x_ezlo_device.model="FGD-212" x_ezlo_device.parent="" x_ezlo_device.reachable=true x_ezlo_device.ready=true x_ezlo_device.room="613e2024129e2912114c093b" x_ezlo_device.status="idle" x_ezlo_device.subcategory="dimmable_in_wall" x_ezlo_device.type_id="271_258_4096" x_ezlo_item.dimmer=65 x_ezlo_item.dimmer_down=0 x_ezlo_item.dimmer_stop=0 x_ezlo_item.dimmer_up=0 x_ezlo_item.electric_meter_kwh=11.3400001525879 x_ezlo_item.electric_meter_watt=6.90000009536743 x_ezlo_item.hw_state="hardware_failure" x_ezlo_item.load_error_state="unknown" x_ezlo_item.meter_reset=0 x_ezlo_item.over_current_state="unknown" x_ezlo_item.over_load_state="unknown" x_ezlo_item.power_surge_state="no_surge" x_ezlo_item.switch=true x_ezlo_item.voltage_drop_drift_state="unknown" x_ezlo_object.id="61425874129e29124dfcd75e" zwave_device.capabilities=null zwave_device.failed=false zwave_device.manufacturer_info=["Fibaro","FGD-212",null] zwave_device.node_id=27 zwave_device.version_info=null Capabilities: dimming, energy_sensor, power_sensor, power_switch, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighborsanother
K Bulb Domitech ezlo>device_61423589129e29124dfcd756 0.65 7:35:42 PM dimming.level=0.65 dimming.step=0.1 power_switch.state=true x_ezlo_device.battery_powered=false x_ezlo_device.category="dimmable_light" x_ezlo_device.manufacturer="Domitech" x_ezlo_device.model="ZE27EU" x_ezlo_device.parent="" x_ezlo_device.reachable=true x_ezlo_device.ready=true x_ezlo_device.room="613e2020129e2912114c093a" x_ezlo_device.status="idle" x_ezlo_device.subcategory="dimmable_bulb" x_ezlo_device.type_id="526_19522_12596" x_ezlo_item.dimmer=65 x_ezlo_item.dimmer_down=0 x_ezlo_item.dimmer_stop=0 x_ezlo_item.dimmer_up=0 x_ezlo_item.switch=true x_ezlo_object.id="61423589129e29124dfcd756" zwave_device.capabilities=null zwave_device.failed=false zwave_device.manufacturer_info=["Domitech","ZE27EU",null] zwave_device.node_id=26 zwave_device.version_info=null Capabilities: dimming, power_switch, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighborsanother
H Bulb Widom dimmer ezlo>device_6147578c129e29124dfcd814 1 7:36:56 PM dimming.level=1 dimming.step=0.1 energy_sensor.units="KWh" energy_sensor.value=0.651000022888184 power_sensor.units="W" power_sensor.value=2.47000002861023 power_switch.state=true x_ezlo_device.battery_powered=false x_ezlo_device.category="dimmable_light" x_ezlo_device.manufacturer="Unknown" x_ezlo_device.model="Unknown" x_ezlo_device.parent="" x_ezlo_device.reachable=true x_ezlo_device.ready=true x_ezlo_device.room="613e2012129e2912114c0938" x_ezlo_device.status="idle" x_ezlo_device.subcategory="dimmable_in_wall" x_ezlo_device.type_id="329_4628_2560" x_ezlo_item.dimmer=100 x_ezlo_item.dimmer_down=0 x_ezlo_item.dimmer_stop=0 x_ezlo_item.dimmer_up=0 x_ezlo_item.electric_meter_kwh=0.651000022888184 x_ezlo_item.electric_meter_watt=2.47000002861023 x_ezlo_item.meter_reset=0 x_ezlo_item.switch=true x_ezlo_object.id="6147578c129e29124dfcd814" zwave_device.capabilities=null zwave_device.failed=false zwave_device.manufacturer_info=["Unknown","Unknown",null] zwave_device.node_id=41 zwave_device.version_info=null Capabilities: dimming, energy_sensor, power_sensor, power_switch, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighbors -
T toggledbits locked this topic on
Yes, they diverge:
