Navigation

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

    SmartHome Community
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Unsolved
    (Last Updated: January 2, 2022)

    • Dimming.set 'attribute' no longer available

      M

      Hass: 2022.11.4
      Hardware: Container
      MSR: stable-22310-3006e85c

      Hi,

      I have a number of rules where the reactions change the brightness of lights....that have been working for months. I upgraded MSR recently however I don't think that is issue as I spun up the old container and the the issue remains.

      This image illustrates the problem.

      bfe42fd7-e038-4aba-bd5a-9892946f7d33-image.png

      This what is now available in the dropdown menu

      8ec17afc-c23c-413d-956a-fc992881b0e7-image.png

      I can turn the light on/off from MSR and Hass however in Hass I can also control the dimming (saturation, colours, effects and so on).

      It seems MSR is no longer 'seeing' a number of 'attribute'. At a loss as to what has changed.

      Any suggestions most welcome.

      Thanks

      Multi-System Reactor

    • [Solved] latest-22328 restart fails

      Crille

      Solution: An update to openLuups MQTT implementation on handling acknowledge packets for QoS > 0 solved this issue.

      EDIT: Seems related to any restart without any configuration changes. If I revert to 22310 I can restart Reactor from UI and with systemd within seconds, but with 22328 it fails to restart., both from UI and systemd. I have to stop the service and then start again.

      I tested to comment out my http (not https) baseurl in the config on my bare metal Ubuntu install latest-22328 and triggered a restart from the UI but Reactor would not start after that.
      If I uncomment the key and restart the service, Reactor comes back to life.
      Is my setup an exceptional circumstance or is this only applicable on new installs?

      Multi-System Reactor

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

      toggledbits

      Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here.

      Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
      Multi-System Reactor

    • warning icons missing

      tunnus

      I've noticed lately (at least with build 22328) that in some cases these yellow warning / alert icons in front of rules are missing, although errors are otherwise visible:

      Screenshot 2022-11-29 at 22.33.16.png

      Screenshot 2022-11-29 at 22.31.15.png

      Multi-System Reactor

    • Issue with HTTP API

      E

      Hello @toggledbits I have a strange issue with the HTTP request that i send to Reactor.
      I have two reactors one on a Unraid server and one on Ubuntu server installed as a docker, when i send http get request to the Unraid server to control home assistant entity everything is going ok, but when i send the same request to the ubuntu modified accordingly it says "Request failed" but when i try to run reaction via http request it works.

      When i go to entities and try to control the entity manually its working.

      Any idea's?

      Best regards

      Multi-System Reactor

    • Running Reactions stuck in waiting from deleted rule

      Crille

      I probably messed things up trying to work around the shutdown timeout for Reactor 22328 when connected to openLuup MQTT server.

      I got a Reaction from a rule stuck in Running Reactions.

      running.PNG

      "Stop this reaction" unfortunately does nothing and in my attempt to get rid of them I deleted the rule but they were still there. I downgraded to 22310 to do a clean restart of Reactor, no success. I even tried to rename/edit/delete reaction_queue.json but they are recreated after each restart and I can't get those orphan Reactions to disappear.

      I need some advice from the guru, please.

      Multi-System Reactor

    • Bug: Unavailable Entities no Longer Showing as Unavailable in "Choose Entity"

      Pabla

      Hey Patrick, noticed a bug running latest-22328-bb674d9c on my Rpi. When I go to the entities tab I can see the entity that is no longer available has a line through the text and a question mark, but say if I try adding the entity to a rule set it no longer shows as unavailable. See the screenshots for more clarity.

      7d0593a9-c983-4a9f-abad-776a53b1dfe9-image.png

      Entity is correctly shown that is unavailable in the entities tab.

      1743d7e5-06d2-42b6-a774-2740f4eaee1a-image.png

      When I go to choose an entity in a rule set it no longer has a line through and a question mark showing that it is unavailable.

      PS: I am using the word unavailable in the context that it was deleted from my HA controller

      Multi-System Reactor

    • Action Pace Configuration MSR

      P

      Hello,
      I am using MS-Reactor with a Home Assistant hub running on a Synoogy NAS as well as a VERA Plus hub. So far MS-R works AMAZING! However I have one rule I use when cleaning the house that essentially turns all the lights on to 100% (25+ lights) and it takes sometime for the action to take effect. I noticed it worked slighlty faster when I had the items in a scene on the vera controller Vs. a rule triggered by a virtual switch in MS-R.

      I suspect I could address the issue by increasing the action pace value per the documentation however, I do not know where to edit this setting? Do I just add a line in the MS-R reactor.yaml config file below the VERA controller info that states: "ActionPace: 00500"?

      Please let me know where and how I can adjust he aforementioned setting.

      All the best,

      Phil

      Multi-System Reactor

    • Update from 22240 to 22310 failed. New Install also failed. (Windows)

      A

      So it was time to update MSR (and then HA but I got stuck here)
      Can't figure out what I have missed.

      My installed version of MSR was 22240.
      Node.js is version 16.15.1

      First I tried to update, following online manual.

      Spoiler

      Download a Reactor distribution ZIP from https://reactor.toggledbits.com/download/ and place it in the folder above your existing reactor (runtime) directory.
      Stop and remove any existing Reactor service:

      cd \path\to\reactor
      node tools\install_reactor_windows_service.js -u .
      Remove any existing package-lock.json file from your Reactor directory.

      Unzip the archive file and copy its contents over the contents of your existing Reactor install directory.
      From the Reactor install directory, re-install/upgrade all package dependencies:

      npm install --no-save --omit dev
      If you are running Reactor as a Windows service, repeat those steps above.

      Restart Reactor (restart the service).
      Hard-refresh all browsers that are displaying Reactor content.

      I found several (maybe it was 3) package-lock.json and I deleted all I could search in reactor folder.
      Unzip the new version and replaced old existing files.

      Install the reactor service again by instructions.

      Spoiler

      In a command prompt window, running as Administrator, change directory to your Reactor install directory.
      Install the node-windows package as a global package (it must be global or the service will not work, and you must install the specific version provided by the command below):

      npm uninstall node-windows
      npm uninstall -g node-windows
      npm install -g node-windows@1.0.0-beta.6
      npm link node-windows
      Run the script to install:

      node tools\install_reactor_windows_service.js -i .

      So this failed. Service wont start.

      Tried again.

      Then deleted everything exept my config folder and did a new install.
      Also downloaded 22310 again, but from "latest" build instead of "stable"
      When running node app.js in command promt i get some kind of error message:

      c:\reactor>node app.js Reactor latest-22310-a6da8097 app 22310 configuration from c:\reactor\config NODE_PATH C:\reactor [latest-22310]2022-11-23T22:18:43.030Z <app:null> Reactor build latest-22310-a6da8097 starting on v16.15.1 c:\reactor\app.js:277 log['always'](a0_0x3d42be(0x26a), BUILD_VERSION, process['version']), log['always']('Process\x20ID\x20%1\x20user/group\x20%2/%3;\x20%4;\x20platform\x20%5/%6\x20%7;\x20locale\x20%8', process['pid'], process[a0_0x3d42be(0x269)](), process[a0_0x3d42be(0x278)](), is_docker ? 'docker' : a0_0x3d42be(0x288), process[a0_0x3d42be(0x287)], process['arch'], os[a0_0x3d42be(0x263)](), sys_locale), log[a0_0x3d42be(0x28c)]('Basedir\x20%1;\x20data\x20in\x20%2', c[a0_0x3d42be(0x1f8)], c[a0_0x3d42be(0x27b)]), log[a0_0x3d42be(0x28c)](a0_0x3d42be(0x21b), process['env'][a0_0x3d42be(0x291)]); ^ TypeError: process[a0_0x3d42be(...)] is not a function at Object.<anonymous> (c:\reactor\app.js:277:226) at Module._compile (node:internal/modules/cjs/loader:1105:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10) at Module.load (node:internal/modules/cjs/loader:981:32) at Function.Module._load (node:internal/modules/cjs/loader:822:12) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12) at node:internal/main/run_main_module:17:47

      But I can't figure out what TypeError means?

      Also, before I tried a new install, there apperd an warning when installing reactor service.

      c:\reactor>npm install -g node-windows@1.0.0-beta.6 npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead. npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead. added 5 packages, and audited 6 packages in 3s 2 vulnerabilities (1 moderate, 1 critical) To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details.

      Running npm audit fix --force seems to broke something, because I could not install service after that.

      c:\reactor>npm audit fix --force npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead. npm WARN using --force Recommended protections disabled. up to date, audited 89 packages in 826ms 12 packages are looking for funding run `npm fund` for details found 0 vulnerabilities c:\reactor>node tools\install_reactor_windows_service.js -i . node:internal/modules/cjs/loader:936 throw err; ^ Error: Cannot find module 'node-windows' Require stack: - c:\reactor\tools\install_reactor_windows_service.js ←[90m at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)←[39m ←[90m at Function.Module._load (node:internal/modules/cjs/loader:778:27)←[39m ←[90m at Module.require (node:internal/modules/cjs/loader:1005:19)←[39m ←[90m at require (node:internal/modules/cjs/helpers:102:18)←[39m at Object.<anonymous> (c:\reactor\tools\install_reactor_windows_service.js:102:15) ←[90m at Module._compile (node:internal/modules/cjs/loader:1105:14)←[39m ←[90m at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)←[39m ←[90m at Module.load (node:internal/modules/cjs/loader:981:32)←[39m ←[90m at Function.Module._load (node:internal/modules/cjs/loader:822:12)←[39m ←[90m at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)←[39m { code: ←[32m'MODULE_NOT_FOUND'←[39m, requireStack: [ ←[32m'c:\\reactor\\tools\\install_reactor_windows_service.js'←[39m ] }
      Multi-System Reactor

    • Where Used Functionality?

      T

      Hello All -

      I'm still working on moving dozens of devices from Vera (internal Reactor) to HASS and (external - bare metal) Reactor.

      One thing I've noticed is sometimes I move a few ZWave/Vera devices and find myself digging through rules finding where a device was used. Has anyone found a good way to do this?

      I plan on digging in to this thread but thought I'd check to see if there's anything more recent.

      https://smarthome.community/topic/483/entities-where-used-and-what-triggered-it?_=1669137134654

      Multi-System Reactor

    • Using MSR with BrowserMod to change pages/dashboards

      C

      Hass: 2022.11.3
      Hardware: Pi
      MSR: latest-22310-a6da8097

      I'm trying to use MSR in automations to change the page displayed on a wall tablet (Windows and Edge in Kiosk mode)
      Example use would be motion detected will change to the security dashboard, or heating turns on, shows the heating dashboard.

      Screenshot_20221122_193138.png I have Browser Mod installed and working and the entities are present in MSR. My only option for the entity which controls the page/dashboard displayed is "x_hass.call_service"

      What I need to change is the state of the entity
      state.png state2.png

      Is this possible in MSR? Despite much searching i'm unsure what service to call to set the state?

      I have tried using service: browser_mod.navigate but get an error
      (this service detailed here https://smarthomescene.com/guides/how-to-setup-browser-mod-2-0-in-home-assistant/ )
      error1.png

      Also trying to lay the data out like this with/out quotes and other variations has not helped

      { "/home-overview/heating" }
      Multi-System Reactor

    • reactor-lgtv: LG TV Controller for Reactor

      therealdb

      Here's my second attempt at a Reactor Controller, this time to integrate LG TVs:

      GitHub - dbochicchio/reactor-lgtv: Reactor controller for LG TV (webos) GitHub - dbochicchio/reactor-lgtv: Reactor controller for LG TV (webos)

      Reactor controller for LG TV (webos). Contribute to dbochicchio/reactor-lgtv development by creating an account on GitHub.

      Standard capabilities are provided and TV volume, mute and switch status are controllable.
      There's also an action to send toast notifications on your TV.

      webos 5+ is required.

      Multi-System Reactor

    • MQTT templates for Reactor

      therealdb

      I've moved many of my MQTT devices to Reactor, so I've coded a couple of templates and I'm publishing them for anyone in the same boat:

      GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor

      Contrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.

      I'll add more in the future, since I still have a couple of things running in my own bridge that I'll eventually move to Reactor with dedicated templates.

      Let me know if you need other templates, I'll probably add a couple more for Shellies (button as scene controller and i3/i4 as scene controller).

      Multi-System Reactor

    • [MSR] More aggressive interval in timer trigger

      therealdb

      Before I'll open a feature request, I want a reality check, because this is maybe achievable in other ways.

      Long story short: I want to react to a device in quasi-real time, but 15 or 30 secs are enough (and will prevent the rule from throttling). Right now, I've moved to 1 min, but it's obviously too late to catch all the variations. 15 secs or 30 are OK, so my first reaction to circumvent this limitation was to host the timer myself and send it via MQTT, but it's obviously a not welcome complication.

      So, @toggledbits, is there any reason the minimum interval is 1 min and/or do you have any suggestion for my use case? Thanks Patrick!

      Multi-System Reactor

    • Pulse

      G

      I'm still trying to fully wrap my brain around Pulsing. Let's see if I have it:

      2a1da895-5170-499f-a1ff-708d3ded1f5c-image.png

      I believe this to indicate that this will wait five minutes, do the thing, wait five seconds and repeat.

      Backstory: this is a reset ruleset for my HVAC. Sometimes Honeywell is finicky about taking the original commands so this should follow along and submit a retry after five minutes... continuing until the setting is accepted.

      a24c656e-b5d1-4e22-b774-517184e70792-image.png

      Multi-System Reactor

    • Error message

      wmarcolin

      Hi @toggledbits !!

      Would it be possible to improve the error messages, and instead of showing the "technical name", show the name we assigned to the rule?

      a8298689-0c7b-43ef-a582-16baece4e4d1-image.png

      In the above case, I have no idea what rule is causing the problem.

      Thanks.

      Multi-System Reactor

    • [SOLVED] Hubitat / log data from new hub information device after deleting original?

      A

      MSR latest-22310, Raspberry Pi 4 / Docker

      While troubleshooting another issue, I deleted and recreated the hub information device on one of my Hubitat hubs. Reactor had been logging the old device information to InfluxDB, but it doesn't appear to have detected the new device. I made sure to enable the new device in Maker API, I've restarted reactor and done a 'docker-compose down' / 'docker-compose up - d'. Still no new data going to influxdb.

      My recollection is that the Hubitat hub device is baken into MSR and is auto-detected, and that it isn't manually configured anywhere. I checked the docs and searched the forum without success.

      Any advice on how I can get MSR to start logging the info from the new device?

      Multi-System Reactor

    • Have MSR as a shortcut in Home Assistant with duckdns?

      F

      Hi!
      I can't find the original post where it's stated that it's possible to make a shortcut i HA to MSR, but I remember trying it out, and it failed, probably because I have duckdns, and a https address, and not a http address, which give us the wss: instead of ws:. Maybe not, but that was my understanding. I finally gave it up, but now I want to try it again. Anyway, is there anyone with duckdns and https that have been able to set this up? How?
      Thanks in advance!
      /Fanan

      Multi-System Reactor

    • HTTP Request Max Response Limit

      S

      MSR has a parameter called "http_request_action_maxresponse" that can be updated within the properties. There is a good section describing this in the manual. However, the installation config file doesn't include the parameter out of the box. I was able to add the parameter (see below) and eventually got it to work after searching for a while.

      Suggestions:

      Include the parameter in the initial config file (or) Update the manual to state that the parameter should be added to the file

      Additional suggestion:
      I understand that it is potentially unsafe to have a large limit overall. However, some API calls unfortunately return large sizes which aren't necessarily problematic. The additional suggestion is to include a configurable max size within each HTTP Reaction in the UI. If it isn't populated then MSR could default to the config file like it does today. This way, we could have a reasonable default limit while allowing larger limit for certain HTTP calls.

      engine: # # enabled - Whether or not the rules engine runs. Change only when directed. enabled: true http_request_action_maxresponse: 10000
      Multi-System Reactor

    • REST API implementation

      M

      Hi,
      @toggledbits do you have any plans to implement the missing endpoints of the REST API in near future? Especially the rule and ruleset functionality (list/enable/disable etc. as documented) would be really useful. I know there must tons of feature requests and the REST API isn't probably on the top of the backlog, so I'm not holding my breath. But if it's right around the corner on your roadmap, it would be nice to know.

      I'm asking this because I need a clean way to enable and disable certain rules from my custom home automation UI. I don't want to expose the MSR UI to the rest of my family to make sure they don't accidentally mess up with the rules and settings.

      I could use a custom MQTT entity as a dynamic config object containing flags for different rules but it would be a lot cleaner to be toggle the rules thru the REST API.

      br,
      mgvra

      Reactor (Multi-hub) latest-22310-a6da8097
      MQTTController [0.1.22306]

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

    Power_switch.state - no change state - EzloPlus - Msr v. 21351-a3aef - Synology Docker

    Multi-System Reactor
    2
    22
    272
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      noelab last edited by

      Hi, Power Switch and Dimmer don't change state, but seems only for this manifacture that I have:
      Widom Dimmer and Double Switch.
      On Ezlo plus they change correctly state, but in MSR Entities they are always on power_switch.state=false also If I put them ON with a reaction.

      EzloPlus - Msr v. 21351-a3aef - Synology Docker

      [latest-21351]2021-12-18T15:48:52.612Z <EzloController:ERR> EzloController#ezlo ws_message handler failed: [ReferenceError]ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
[latest-21351]2021-12-18T15:48:52.612Z <EzloController:CRIT> ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
    at Entity.setAttribute (/opt/reactor/server/lib/Entity.js:314:19)
    at /opt/reactor/server/lib/EzloController.js:1057:257
    at Array.forEach (<anonymous>)
    at EzloController._update_entity (/opt/reactor/server/lib/EzloController.js:1001:55)
    at EzloController.ws_message (/opt/reactor/server/lib/EzloController.js:1386:815)
    at WebSocket.<anonymous> (/opt/reactor/server/lib/Controller.js:588:48)
    at WebSocket.emit (node:events:390:28)
    at WebSocket.emit (node:domain:475:12)
    at Receiver.receiverOnMessage (/opt/reactor/node_modules/ws/lib/websocket.js:1008:20)
    at Receiver.emit (node:events:390:28)
[latest-21351]2021-12-18T15:49:41.720Z <EzloController:ERR> EzloController#ezlo ws_message handler failed: [ReferenceError]ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
[latest-21351]2021-12-18T15:49:41.720Z <EzloController:CRIT> ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
    at Entity.setAttribute (/opt/reactor/server/lib/Entity.js:314:19)
    at /opt/reactor/server/lib/EzloController.js:1057:257
    at Array.forEach (<anonymous>)
    at EzloController._update_entity (/opt/reactor/server/lib/EzloController.js:1001:55)
    at EzloController.ws_message (/opt/reactor/server/lib/EzloController.js:1386:815)
    at WebSocket.<anonymous> (/opt/reactor/server/lib/Controller.js:588:48)
    at WebSocket.emit (node:events:390:28)
    at WebSocket.emit (node:domain:475:12)
    at Receiver.receiverOnMessage (/opt/reactor/node_modules/ws/lib/websocket.js:1008:20)
    at Receiver.emit (node:events:390:28)
[latest-21351]2021-12-18T15:50:22.258Z <EzloController:ERR> EzloController#ezlo ws_message handler failed: [ReferenceError]ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_61475325129e29124dfcd7e6
[latest-21351]2021-12-18T15:50:22.259Z <EzloController:CRIT> ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_61475325129e29124dfcd7e6
ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_61475325129e29124dfcd7e6
    at Entity.setAttribute (/opt/reactor/server/lib/Entity.js:314:19)
    at /opt/reactor/server/lib/EzloController.js:1057:257
    at Array.forEach (<anonymous>)
    at EzloController._update_entity (/opt/reactor/server/lib/EzloController.js:1001:55)
    at EzloController.ws_message (/opt/reactor/server/lib/EzloController.js:1386:815)
    at WebSocket.<anonymous> (/opt/reactor/server/lib/Controller.js:588:48)
    at WebSocket.emit (node:events:390:28)
    at WebSocket.emit (node:domain:475:12)
    at Receiver.receiverOnMessage (/opt/reactor/node_modules/ws/lib/websocket.js:1008:20)
    at Receiver.emit (node:events:390:28)
[latest-21351]2021-12-18T15:51:09.464Z <EzloController:ERR> EzloController#ezlo ws_message handler failed: [ReferenceError]ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
[latest-21351]2021-12-18T15:51:09.465Z <EzloController:CRIT> ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
    at Entity.setAttribute (/opt/reactor/server/lib/Entity.js:314:19)
    at /opt/reactor/server/lib/EzloController.js:1057:257
    at Array.forEach (<anonymous>)
    at EzloController._update_entity (/opt/reactor/server/lib/EzloController.js:1001:55)
    at EzloController.ws_message (/opt/reactor/server/lib/EzloController.js:1386:815)
    at WebSocket.<anonymous> (/opt/reactor/server/lib/Controller.js:588:48)
    at WebSocket.emit (node:events:390:28)
    at WebSocket.emit (node:domain:475:12)
    at Receiver.receiverOnMessage (/opt/reactor/node_modules/ws/lib/websocket.js:1008:20)
    at Receiver.emit (node:events:390:28)
[latest-21351]2021-12-18T15:51:09.514Z <EzloController:ERR> EzloController#ezlo ws_message handler failed: [ReferenceError]ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
[latest-21351]2021-12-18T15:51:09.515Z <EzloController:CRIT> ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
    at Entity.setAttribute (/opt/reactor/server/lib/Entity.js:314:19)
    at /opt/reactor/server/lib/EzloController.js:1057:257
    at Array.forEach (<anonymous>)
    at EzloController._update_entity (/opt/reactor/server/lib/EzloController.js:1001:55)
    at EzloController.ws_message (/opt/reactor/server/lib/EzloController.js:1386:815)
    at WebSocket.<anonymous> (/opt/reactor/server/lib/Controller.js:588:48)
    at WebSocket.emit (node:events:390:28)
    at WebSocket.emit (node:domain:475:12)
    at Receiver.receiverOnMessage (/opt/reactor/node_modules/ws/lib/websocket.js:1008:20)
    at Receiver.emit (node:events:390:28)
[latest-21351]2021-12-18T15:52:02.630Z <EzloController:ERR> EzloController#ezlo ws_message handler failed: [ReferenceError]ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
[latest-21351]2021-12-18T15:52:02.631Z <EzloController:CRIT> ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
    at Entity.setAttribute (/opt/reactor/server/lib/Entity.js:314:19)
    at /opt/reactor/server/lib/EzloController.js:1057:257
    at Array.forEach (<anonymous>)
    at EzloController._update_entity (/opt/reactor/server/lib/EzloController.js:1001:55)
    at EzloController.ws_message (/opt/reactor/server/lib/EzloController.js:1386:815)
    at WebSocket.<anonymous> (/opt/reactor/server/lib/Controller.js:588:48)
    at WebSocket.emit (node:events:390:28)
    at WebSocket.emit (node:domain:475:12)
    at Receiver.receiverOnMessage (/opt/reactor/node_modules/ws/lib/websocket.js:1008:20)
    at Receiver.emit (node:events:390:28)
[latest-21351]2021-12-18T15:52:02.680Z <EzloController:ERR> EzloController#ezlo ws_message handler failed: [ReferenceError]ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
[latest-21351]2021-12-18T15:52:02.681Z <EzloController:CRIT> ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
    at Entity.setAttribute (/opt/reactor/server/lib/Entity.js:314:19)
    at /opt/reactor/server/lib/EzloController.js:1057:257
    at Array.forEach (<anonymous>)
    at EzloController._update_entity (/opt/reactor/server/lib/EzloController.js:1001:55)
    at EzloController.ws_message (/opt/reactor/server/lib/EzloController.js:1386:815)
    at WebSocket.<anonymous> (/opt/reactor/server/lib/Controller.js:588:48)
    at WebSocket.emit (node:events:390:28)
    at WebSocket.emit (node:domain:475:12)
    at Receiver.receiverOnMessage (/opt/reactor/node_modules/ws/lib/websocket.js:1008:20)
    at Receiver.emit (node:events:390:28)
[latest-21351]2021-12-18T15:52:51.736Z <EzloController:ERR> EzloController#ezlo ws_message handler failed: [ReferenceError]ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
[latest-21351]2021-12-18T15:52:51.736Z <EzloController:CRIT> ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
    at Entity.setAttribute (/opt/reactor/server/lib/Entity.js:314:19)
    at /opt/reactor/server/lib/EzloController.js:1057:257
    at Array.forEach (<anonymous>)
    at EzloController._update_entity (/opt/reactor/server/lib/EzloController.js:1001:55)
    at EzloController.ws_message (/opt/reactor/server/lib/EzloController.js:1386:815)
    at WebSocket.<anonymous> (/opt/reactor/server/lib/Controller.js:588:48)
    at WebSocket.emit (node:events:390:28)
    at WebSocket.emit (node:domain:475:12)
    at Receiver.receiverOnMessage (/opt/reactor/node_modules/ws/lib/websocket.js:1008:20)
    at Receiver.emit (node:events:390:28)
[latest-21351]2021-12-18T15:52:51.764Z <EzloController:ERR> EzloController#ezlo ws_message handler failed: [ReferenceError]ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
[latest-21351]2021-12-18T15:52:51.764Z <EzloController:CRIT> ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
ReferenceError: Capability energy_sensor[electric_meter_kwh] not extended (ezlo>device_6187b203129e2912286888bf
    at Entity.setAttribute (/opt/reactor/server/lib/Entity.js:314:19)
    at /opt/reactor/server/lib/EzloController.js:1057:257
    at Array.forEach (<anonymous>)
    at EzloController._update_entity (/opt/reactor/server/lib/EzloController.js:1001:55)
    at EzloController.ws_message (/opt/reactor/server/lib/EzloController.js:1386:815)
    at WebSocket.<anonymous> (/opt/reactor/server/lib/Controller.js:588:48)
    at WebSocket.emit (node:events:390:28)
    at WebSocket.emit (node:domain:475:12)
    at Receiver.receiverOnMessage (/opt/reactor/node_modules/ws/lib/websocket.js:1008:20)
    at Receiver.emit (node:events:390:28)

      Thanks in advance

      1 Reply Last reply Reply Quote 0
      • N
        noelab last edited by

        At the moment the bulb is on, and this is what I see in Entities

        dimming.level=0
        dimming.step=0.1
        energy_sensor.units=null
        energy_sensor.value=null
        power_switch.state=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="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=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.492000013589859
        x_ezlo_item.electric_meter_watt=0
        x_ezlo_item.meter_reset=0
        x_ezlo_item.switch=false
        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_switch, toggle, 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, 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

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

          Thanks for the report and good info. I've posted a blind update 21352. Upgrade your container to that and let's see if those errors go away (spoiler: they should).

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

          1 Reply Last reply Reply Quote 0
          • N
            noelab last edited by noelab

            Hi, thanks... It is ok for power_switch.state when the bulb is on. This is what I see in entities:

            dimming.level=1
dimming.step=0.1
energy_sensor.units=null
energy_sensor.value=0.5
power_sensor.units=null
power_sensor.value=2.48000001907349
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.5
x_ezlo_item.electric_meter_watt=2.48000001907349
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, toggle, 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, 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

            but in log, there is stil this problem:

            [latest-21352]2021-12-19T22:26:48.725Z <wsapi:INFO> wsapi: connection from ::ffff:172.18.0.1
[latest-21352]2021-12-19T22:26:48.808Z <wsapi:INFO> wsapi: connection from ::ffff:172.18.0.1
[latest-21352]2021-12-19T22:26:48.830Z <wsapi:INFO> wsapi: connection from ::ffff:172.18.0.1
[latest-21352]2021-12-19T22:27:13.704Z <wsapi:INFO> client "172.18.0.1#3" closed, code=1001, reason=
[latest-21352]2021-12-19T22:27:14.191Z <wsapi:INFO> wsapi: connection from ::ffff:172.18.0.1
[latest-21352]2021-12-19T22:27:19.338Z <wsapi:INFO> client "172.18.0.1#1" closed, code=1001, reason=
[latest-21352]2021-12-19T22:27:19.749Z <wsapi:INFO> wsapi: connection from ::ffff:172.18.0.1
[latest-21352]2021-12-19T22:27:25.745Z <wsapi:INFO> client "172.18.0.1#2" closed, code=1001, reason=
[latest-21352]2021-12-19T22:29:32.187Z <EzloController:WARN> EzloController#ezlo failed to evaluate expression item.scale ?? 'KWh' for attribute units of energy_sensor#electric_meter_kwh (category=switch): [ReferenceError]ReferenceError: Invalid reference to member scale of null
[latest-21352]2021-12-19T22:29:32.187Z <EzloController:WARN> EzloController#ezlo failed to evaluate expression item.scale ?? 'W' for attribute units of power_sensor#electric_meter_watt (category=switch): [ReferenceError]ReferenceError: Invalid reference to member scale of null
[latest-21352]2021-12-19T22:29:32.237Z <EzloController:WARN> EzloController#ezlo failed to evaluate expression item.scale ?? 'KWh' for attribute units of energy_sensor#electric_meter_kwh (category=switch): [ReferenceError]ReferenceError: Invalid reference to member scale of null
[latest-21352]2021-12-19T22:29:32.237Z <EzloController:WARN> EzloController#ezlo failed to evaluate expression item.scale ?? 'W' for attribute units of power_sensor#electric_meter_watt (category=switch): [ReferenceError]ReferenceError: Invalid reference to member scale of null
[latest-21352]2021-12-19T22:29:32.289Z <EzloController:WARN> EzloController#ezlo failed to evaluate expression item.scale ?? 'KWh' for attribute units of energy_sensor#electric_meter_kwh (category=switch): [ReferenceError]ReferenceError: Invalid reference to member scale of null
[latest-21352]2021-12-19T22:29:32.289Z <EzloController:WARN> EzloController#ezlo failed to evaluate expression item.scale ?? 'W' for attribute units of power_sensor#electric_meter_watt (category=switch): [ReferenceError]ReferenceError: Invalid reference to member scale of null
[latest-21352]2021-12-19T22:29:32.389Z <EzloController:WARN> EzloController#ezlo failed to evaluate expression item.scale ?? 'KWh' for attribute units of energy_sensor#electric_meter_kwh (category=switch): [ReferenceError]ReferenceError: Invalid reference to member scale of null
[latest-21352]2021-12-19T22:29:32.389Z <EzloController:WARN> EzloController#ezlo failed to evaluate expression item.scale ?? 'W' for attribute units of power_sensor#electric_meter_watt (category=switch): [ReferenceError]ReferenceError: Invalid reference to member scale of null
[latest-21352]2021-12-19T22:29:44.819Z <EzloController:WARN> EzloController#ezlo failed to evaluate expression item.scale ?? 'KWh' for attribute units of energy_sensor#electric_meter_kwh (category=switch): [ReferenceError]ReferenceError: Invalid reference to member scale of null
[latest-21352]2021-12-19T22:29:44.820Z <EzloController:WARN> EzloController#ezlo failed to evaluate expression item.scale ?? 'W' for attribute units of power_sensor#electric_meter_watt (category=switch): [ReferenceError]ReferenceError: Invalid reference to member scale of null
[latest-21352]2021-12-19T22:29:58.871Z <Rule:5:Rule.js:771> Rule#rule-kthqmgb6 vR4 DLT 01 Bulb ID  requesting eval; entity-changed from Entity#vera>device_726
            1 Reply Last reply Reply Quote 0
            • toggledbits
              toggledbits last edited by

              OK. That's almost working as it should. At least it's not getting in the way of the state update. One more time... blind build 21353 is now available.

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

              1 Reply Last reply Reply Quote 0
              • N
                noelab last edited by

                I divide in two posts the log :

                [latest-21353]2021-12-19T23:08:39.981Z <Structure:INFO> Starting controller EzloController#ezlo
[latest-21353]2021-12-19T23:08:39.995Z <EzloController:INFO> EzloController#ezlo device mapping data loaded; checking...
[latest-21353]2021-12-19T23:08:39.997Z <EzloController:ERR> EzloController#ezlo implementation data references undefined capability power_sensor#electric_meter_watt
[latest-21353]2021-12-19T23:08:39.998Z <EzloController:ERR> EzloController#ezlo implementation data references undefined capability energy_sensor#electric_meter_kwh
[latest-21353]2021-12-19T23:08:39.999Z <EzloController:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
[latest-21353]2021-12-19T23:08:40.000Z <Structure:INFO> Starting controller OWMWeatherController#weather
[latest-21353]2021-12-19T23:08:40.028Z <Structure:INFO> Starting controller SystemController#reactor_system
[latest-21353]2021-12-19T23:08:40.030Z <SystemController:NOTICE> Controller SystemController#reactor_system is now online.
[latest-21353]2021-12-19T23:08:40.058Z <EzloController:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
[latest-21353]2021-12-19T23:08:40.065Z <app:INFO> Structure running; pausing for controllers' initial ready
[latest-21353]2021-12-19T23:08:40.163Z <VeraController:WARN> VeraController#vera ignoring geotag ([Object]{ "iduser": 1520131, "geotags": [ { "PK_User": 0, "id": 1, "accuracy": 0, "ishome": 1, "notify": 1, "radius": 100, "address": ", "color": "006e45", "latitude": "43.79130238128065", "longitude": "11.251052767038345", "name": "", "status": --null-- } ] }) for user 1520131, user not in user list
[latest-21353]2021-12-19T23:08:40.203Z <EzloController:INFO> EzloController#ezlo hub websocket connected (wss://10.0.4.119:17000)
[latest-21353]2021-12-19T23:08:40.204Z <EzloController:INFO> EzloController#ezlo hub websocket connected; inventory hub...
[latest-21353]2021-12-19T23:08:40.272Z <EzloController:INFO> EzloController#ezlo hub "90000464" is h2.1 (undefined) firmware "2.0.23.1817.1"
[latest-21353]2021-12-19T23:08:40.315Z <OWMWeatherController:INFO> OWMWeatherController#weather done; 1 locations, 0 failed
[latest-21353]2021-12-19T23:08:40.317Z <OWMWeatherController:NOTICE> Controller OWMWeatherController#weather is now online.
[latest-21353]2021-12-19T23:08:40.596Z <VeraController:NOTICE> Controller VeraController#vera is now online.
[latest-21353]2021-12-19T23:08:41.069Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "613e2959129e2912114c0982" (Entity#ezlo>device_613e2959129e2912114c0982); has [Array][ "613e2959129e2912114c0983", "basic", "613e2959129e2912114c0984", "battery", "613e2959129e2912114c0985", "tampering_cover_alarm", "613e2959129e2912114c0986", "acceleration_x_axis", "613e2959129e2912114c0987", "acceleration_y_axis", "613e2959129e2912114c0988", "acceleration_z_axis", "613e2959129e2912114c0989", "motion", "613e2959129e2912114c098a", "security_threat" ]
[latest-21353]2021-12-19T23:08:41.071Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "613e2959129e2912114c0982" (Entity#ezlo>device_613e2959129e2912114c0982); has [Array][ "613e2959129e2912114c0983", "basic", "613e2959129e2912114c0984", "battery", "613e2959129e2912114c0985", "tampering_cover_alarm", "613e2959129e2912114c0986", "acceleration_x_axis", "613e2959129e2912114c0987", "acceleration_y_axis", "613e2959129e2912114c0988", "acceleration_z_axis", "613e2959129e2912114c0989", "motion", "613e2959129e2912114c098a", "security_threat" ]
[latest-21353]2021-12-19T23:08:41.074Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "613e2959129e2912114c098d" (Entity#ezlo>device_613e2959129e2912114c098d); has [Array][ "613e2959129e2912114c098e", "temp" ]
[latest-21353]2021-12-19T23:08:41.074Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "613e2959129e2912114c098d" (Entity#ezlo>device_613e2959129e2912114c098d); has [Array][ "613e2959129e2912114c098e", "temp" ]
[latest-21353]2021-12-19T23:08:41.076Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "613e2959129e2912114c098f" (Entity#ezlo>device_613e2959129e2912114c098f); has [Array][ "613e2959129e2912114c0990", "lux" ]
[latest-21353]2021-12-19T23:08:41.076Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "613e2959129e2912114c098f" (Entity#ezlo>device_613e2959129e2912114c098f); has [Array][ "613e2959129e2912114c0990", "lux" ]
[latest-21353]2021-12-19T23:08:41.078Z <EzloController:WARN> EzloController#ezlo no implementation mapping for attributes from match category=level_sensor cap value_sensor
[latest-21353]2021-12-19T23:08:41.078Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "613e2959129e2912114c0991" (Entity#ezlo>device_613e2959129e2912114c0991); has [Array][ "613e2959129e2912114c0992", "seismic_intensity" ]
[latest-21353]2021-12-19T23:08:41.079Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "613e2959129e2912114c0991" (Entity#ezlo>device_613e2959129e2912114c0991); has [Array][ "613e2959129e2912114c0992", "seismic_intensity" ]
[latest-21353]2021-12-19T23:08:41.094Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "61425d55129e29124dfcd782" (Entity#ezlo>device_61425d55129e29124dfcd782); has [Array][ "61425d55129e29124dfcd783", "basic", "61425d56129e29124dfcd784", "battery", "61425d56129e29124dfcd785", "tampering_cover_alarm", "61425d56129e29124dfcd786", "acceleration_x_axis", "61425d56129e29124dfcd787", "acceleration_y_axis", "61425d56129e29124dfcd788", "acceleration_z_axis", "61425d56129e29124dfcd789", "motion", "61425d56129e29124dfcd78a", "security_threat" ]
[latest-21353]2021-12-19T23:08:41.094Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "61425d55129e29124dfcd782" (Entity#ezlo>device_61425d55129e29124dfcd782); has [Array][ "61425d55129e29124dfcd783", "basic", "61425d56129e29124dfcd784", "battery", "61425d56129e29124dfcd785", "tampering_cover_alarm", "61425d56129e29124dfcd786", "acceleration_x_axis", "61425d56129e29124dfcd787", "acceleration_y_axis", "61425d56129e29124dfcd788", "acceleration_z_axis", "61425d56129e29124dfcd789", "motion", "61425d56129e29124dfcd78a", "security_threat" ]
[latest-21353]2021-12-19T23:08:41.095Z <EzloController:WARN> EzloController#ezlo no implementation mapping for attributes from match category=level_sensor cap value_sensor
[latest-21353]2021-12-19T23:08:41.096Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "61425d56129e29124dfcd78b" (Entity#ezlo>device_61425d56129e29124dfcd78b); has [Array][ "61425d56129e29124dfcd78c", "seismic_intensity" ]
[latest-21353]2021-12-19T23:08:41.096Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "61425d56129e29124dfcd78b" (Entity#ezlo>device_61425d56129e29124dfcd78b); has [Array][ "61425d56129e29124dfcd78c", "seismic_intensity" ]
[latest-21353]2021-12-19T23:08:41.097Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "61425d56129e29124dfcd78d" (Entity#ezlo>device_61425d56129e29124dfcd78d); has [Array][ "61425d56129e29124dfcd78e", "temp" ]
[latest-21353]2021-12-19T23:08:41.097Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "61425d56129e29124dfcd78d" (Entity#ezlo>device_61425d56129e29124dfcd78d); has [Array][ "61425d56129e29124dfcd78e", "temp" ]
[latest-21353]2021-12-19T23:08:41.098Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "61425d56129e29124dfcd78f" (Entity#ezlo>device_61425d56129e29124dfcd78f); has [Array][ "61425d56129e29124dfcd790", "lux" ]
[latest-21353]2021-12-19T23:08:41.099Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "61425d56129e29124dfcd78f" (Entity#ezlo>device_61425d56129e29124dfcd78f); has [Array][ "61425d56129e29124dfcd790", "lux" ]
[latest-21353]2021-12-19T23:08:41.106Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "6145c693129e29124dfcd7a7" (Entity#ezlo>device_6145c693129e29124dfcd7a7); has [Array][ "6145c693129e29124dfcd7a8", "basic", "6145c693129e29124dfcd7a9", "battery", "6145c693129e29124dfcd7aa", "tampering_cover_alarm", "6145c693129e29124dfcd7ab", "acceleration_x_axis", "6145c693129e29124dfcd7ac", "acceleration_y_axis", "6145c694129e29124dfcd7ad", "acceleration_z_axis", "6145c694129e29124dfcd7ae", "motion", "6145c694129e29124dfcd7af", "security_threat" ]
[latest-21353]2021-12-19T23:08:41.107Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "6145c693129e29124dfcd7a7" (Entity#ezlo>device_6145c693129e29124dfcd7a7); has [Array][ "6145c693129e29124dfcd7a8", "basic", "6145c693129e29124dfcd7a9", "battery", "6145c693129e29124dfcd7aa", "tampering_cover_alarm", "6145c693129e29124dfcd7ab", "acceleration_x_axis", "6145c693129e29124dfcd7ac", "acceleration_y_axis", "6145c694129e29124dfcd7ad", "acceleration_z_axis", "6145c694129e29124dfcd7ae", "motion", "6145c694129e29124dfcd7af", "security_threat" ]
[latest-21353]2021-12-19T23:08:41.108Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "6145c694129e29124dfcd7b0" (Entity#ezlo>device_6145c694129e29124dfcd7b0); has [Array][ "6145c694129e29124dfcd7b1", "temp" ]
[latest-21353]2021-12-19T23:08:41.109Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "6145c694129e29124dfcd7b0" (Entity#ezlo>device_6145c694129e29124dfcd7b0); has [Array][ "6145c694129e29124dfcd7b1", "temp" ]
[latest-21353]2021-12-19T23:08:41.110Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "6145c694129e29124dfcd7b2" (Entity#ezlo>device_6145c694129e29124dfcd7b2); has [Array][ "6145c694129e29124dfcd7b3", "lux" ]
[latest-21353]2021-12-19T23:08:41.111Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "6145c694129e29124dfcd7b2" (Entity#ezlo>device_6145c694129e29124dfcd7b2); has [Array][ "6145c694129e29124dfcd7b3", "lux" ]
[latest-21353]2021-12-19T23:08:41.112Z <EzloController:WARN> EzloController#ezlo no implementation mapping for attributes from match category=level_sensor cap value_sensor
[latest-21353]2021-12-19T23:08:41.112Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "6145c694129e29124dfcd7b4" (Entity#ezlo>device_6145c694129e29124dfcd7b4); has [Array][ "6145c694129e29124dfcd7b5", "seismic_intensity" ]
[latest-21353]2021-12-19T23:08:41.112Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "6145c694129e29124dfcd7b4" (Entity#ezlo>device_6145c694129e29124dfcd7b4); has [Array][ "6145c694129e29124dfcd7b5", "seismic_intensity" ]
[latest-21353]2021-12-19T23:08:41.113Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "6145c7ca129e29124dfcd7ba" (Entity#ezlo>device_6145c7ca129e29124dfcd7ba); has [Array][ "6145c7ca129e29124dfcd7bb", "basic", "6145c7ca129e29124dfcd7bc", "battery", "6145c7ca129e29124dfcd7bd", "motion", "6145c7ca129e29124dfcd7be", "security_threat" ]
[latest-21353]2021-12-19T23:08:41.114Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "6145c7ca129e29124dfcd7ba" (Entity#ezlo>device_6145c7ca129e29124dfcd7ba); has [Array][ "6145c7ca129e29124dfcd7bb", "basic", "6145c7ca129e29124dfcd7bc", "battery", "6145c7ca129e29124dfcd7bd", "motion", "6145c7ca129e29124dfcd7be", "security_threat" ]
[latest-21353]2021-12-19T23:08:41.115Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "6145c7ca129e29124dfcd7bf" (Entity#ezlo>device_6145c7ca129e29124dfcd7bf); has [Array][ "6145c7ca129e29124dfcd7c0", "lux" ]
[latest-21353]2021-12-19T23:08:41.115Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "6145c7ca129e29124dfcd7bf" (Entity#ezlo>device_6145c7ca129e29124dfcd7bf); has [Array][ "6145c7ca129e29124dfcd7c0", "lux" ]
[latest-21353]2021-12-19T23:08:41.116Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "6145c7ca129e29124dfcd7c1" (Entity#ezlo>device_6145c7ca129e29124dfcd7c1); has [Array][ "6145c7ca129e29124dfcd7c2", "temp" ]
[latest-21353]2021-12-19T23:08:41.116Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "6145c7ca129e29124dfcd7c1" (Entity#ezlo>device_6145c7ca129e29124dfcd7c1); has [Array][ "6145c7ca129e29124dfcd7c2", "temp" ]
[latest-21353]2021-12-19T23:08:41.124Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "614755cd129e29124dfcd805" (Entity#ezlo>device_614755cd129e29124dfcd805); has [Array][ "614755cd129e29124dfcd806", "basic", "614755cd129e29124dfcd807", "battery", "614755cd129e29124dfcd808", "tampering_cover_alarm", "614755cd129e29124dfcd809", "acceleration_x_axis", "614755cd129e29124dfcd80a", "acceleration_y_axis", "614755cd129e29124dfcd80b", "acceleration_z_axis", "614755cd129e29124dfcd80c", "motion", "614755cd129e29124dfcd80d", "security_threat" ]
[latest-21353]2021-12-19T23:08:41.125Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "614755cd129e29124dfcd805" (Entity#ezlo>device_614755cd129e29124dfcd805); has [Array][ "614755cd129e29124dfcd806", "basic", "614755cd129e29124dfcd807", "battery", "614755cd129e29124dfcd808", "tampering_cover_alarm", "614755cd129e29124dfcd809", "acceleration_x_axis", "614755cd129e29124dfcd80a", "acceleration_y_axis", "614755cd129e29124dfcd80b", "acceleration_z_axis", "614755cd129e29124dfcd80c", "motion", "614755cd129e29124dfcd80d", "security_threat" ]
[latest-21353]2021-12-19T23:08:41.126Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "614755cd129e29124dfcd80e" (Entity#ezlo>device_614755cd129e29124dfcd80e); has [Array][ "614755ce129e29124dfcd80f", "temp" ]
[latest-21353]2021-12-19T23:08:41.126Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "614755cd129e29124dfcd80e" (Entity#ezlo>device_614755cd129e29124dfcd80e); has [Array][ "614755ce129e29124dfcd80f", "temp" ]
[latest-21353]2021-12-19T23:08:41.127Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "614755ce129e29124dfcd810" (Entity#ezlo>device_614755ce129e29124dfcd810); has [Array][ "614755ce129e29124dfcd811", "lux" ]
[latest-21353]2021-12-19T23:08:41.127Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "614755ce129e29124dfcd810" (Entity#ezlo>device_614755ce129e29124dfcd810); has [Array][ "614755ce129e29124dfcd811", "lux" ]
[latest-21353]2021-12-19T23:08:41.129Z <EzloController:WARN> EzloController#ezlo no implementation mapping for attributes from match category=level_sensor cap value_sensor
[latest-21353]2021-12-19T23:08:41.129Z <EzloController:WARN> EzloController#ezlo updating level for battery_power: item named battery not found on "614755ce129e29124dfcd812" (Entity#ezlo>device_614755ce129e29124dfcd812); has [Array][ "614755ce129e29124dfcd813", "seismic_intensity" ]
[latest-21353]2021-12-19T23:08:41.129Z <EzloController:WARN> EzloController#ezlo updating charging for x_ezlo_battery_state: item named battery_charging_state not found on "614755ce129e29124dfcd812" (Entity#ezlo>device_614755ce129e29124dfcd812); has [Array][ "614755ce129e29124dfcd813", "seismic_intensity" ]
[latest-21353]2021-12-19T23:08:41.132Z <EzloController:WARN> EzloController#ezlo updating red for rgb_color: item named rgbcolor not found on "614e0c30129e29124dfcd83b" (Entity#ezlo>device_614e0c30129e29124dfcd83b); has [Array][ "614e0c30129e29124dfcd83c", "switch", "614e0c30129e29124dfcd83d", "dimmer", "614e0c31129e29124dfcd83e", "dimmer_up", "614e0c31129e29124dfcd83f", "dimmer_down", "614e0c31129e29124dfcd840", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.132Z <EzloController:WARN> EzloController#ezlo updating green for rgb_color: item named rgbcolor not found on "614e0c30129e29124dfcd83b" (Entity#ezlo>device_614e0c30129e29124dfcd83b); has [Array][ "614e0c30129e29124dfcd83c", "switch", "614e0c30129e29124dfcd83d", "dimmer", "614e0c31129e29124dfcd83e", "dimmer_up", "614e0c31129e29124dfcd83f", "dimmer_down", "614e0c31129e29124dfcd840", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.132Z <EzloController:WARN> EzloController#ezlo updating blue for rgb_color: item named rgbcolor not found on "614e0c30129e29124dfcd83b" (Entity#ezlo>device_614e0c30129e29124dfcd83b); has [Array][ "614e0c30129e29124dfcd83c", "switch", "614e0c30129e29124dfcd83d", "dimmer", "614e0c31129e29124dfcd83e", "dimmer_up", "614e0c31129e29124dfcd83f", "dimmer_down", "614e0c31129e29124dfcd840", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.133Z <EzloController:WARN> EzloController#ezlo updating value for color_temperature: item named rgbcolor not found on "614e0c30129e29124dfcd83b" (Entity#ezlo>device_614e0c30129e29124dfcd83b); has [Array][ "614e0c30129e29124dfcd83c", "switch", "614e0c30129e29124dfcd83d", "dimmer", "614e0c31129e29124dfcd83e", "dimmer_up", "614e0c31129e29124dfcd83f", "dimmer_down", "614e0c31129e29124dfcd840", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.134Z <EzloController:WARN> EzloController#ezlo updating red for rgb_color: item named rgbcolor not found on "614e0c31129e29124dfcd841" (Entity#ezlo>device_614e0c31129e29124dfcd841); has [Array][ "614e0c31129e29124dfcd842", "switch", "614e0c31129e29124dfcd843", "dimmer", "614e0c31129e29124dfcd844", "dimmer_up", "614e0c31129e29124dfcd845", "dimmer_down", "614e0c31129e29124dfcd846", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.134Z <EzloController:WARN> EzloController#ezlo updating green for rgb_color: item named rgbcolor not found on "614e0c31129e29124dfcd841" (Entity#ezlo>device_614e0c31129e29124dfcd841); has [Array][ "614e0c31129e29124dfcd842", "switch", "614e0c31129e29124dfcd843", "dimmer", "614e0c31129e29124dfcd844", "dimmer_up", "614e0c31129e29124dfcd845", "dimmer_down", "614e0c31129e29124dfcd846", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.134Z <EzloController:WARN> EzloController#ezlo updating blue for rgb_color: item named rgbcolor not found on "614e0c31129e29124dfcd841" (Entity#ezlo>device_614e0c31129e29124dfcd841); has [Array][ "614e0c31129e29124dfcd842", "switch", "614e0c31129e29124dfcd843", "dimmer", "614e0c31129e29124dfcd844", "dimmer_up", "614e0c31129e29124dfcd845", "dimmer_down", "614e0c31129e29124dfcd846", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.134Z <EzloController:WARN> EzloController#ezlo updating value for color_temperature: item named rgbcolor not found on "614e0c31129e29124dfcd841" (Entity#ezlo>device_614e0c31129e29124dfcd841); has [Array][ "614e0c31129e29124dfcd842", "switch", "614e0c31129e29124dfcd843", "dimmer", "614e0c31129e29124dfcd844", "dimmer_up", "614e0c31129e29124dfcd845", "dimmer_down", "614e0c31129e29124dfcd846", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.135Z <EzloController:WARN> EzloController#ezlo updating red for rgb_color: item named rgbcolor not found on "614e0c31129e29124dfcd847" (Entity#ezlo>device_614e0c31129e29124dfcd847); has [Array][ "614e0c31129e29124dfcd848", "switch", "614e0c31129e29124dfcd849", "dimmer", "614e0c31129e29124dfcd84a", "dimmer_up", "614e0c31129e29124dfcd84b", "dimmer_down", "614e0c31129e29124dfcd84c", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.136Z <EzloController:WARN> EzloController#ezlo updating green for rgb_color: item named rgbcolor not found on "614e0c31129e29124dfcd847" (Entity#ezlo>device_614e0c31129e29124dfcd847); has [Array][ "614e0c31129e29124dfcd848", "switch", "614e0c31129e29124dfcd849", "dimmer", "614e0c31129e29124dfcd84a", "dimmer_up", "614e0c31129e29124dfcd84b", "dimmer_down", "614e0c31129e29124dfcd84c", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.136Z <EzloController:WARN> EzloController#ezlo updating blue for rgb_color: item named rgbcolor not found on "614e0c31129e29124dfcd847" (Entity#ezlo>device_614e0c31129e29124dfcd847); has [Array][ "614e0c31129e29124dfcd848", "switch", "614e0c31129e29124dfcd849", "dimmer", "614e0c31129e29124dfcd84a", "dimmer_up", "614e0c31129e29124dfcd84b", "dimmer_down", "614e0c31129e29124dfcd84c", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.136Z <EzloController:WARN> EzloController#ezlo updating value for color_temperature: item named rgbcolor not found on "614e0c31129e29124dfcd847" (Entity#ezlo>device_614e0c31129e29124dfcd847); has [Array][ "614e0c31129e29124dfcd848", "switch", "614e0c31129e29124dfcd849", "dimmer", "614e0c31129e29124dfcd84a", "dimmer_up", "614e0c31129e29124dfcd84b", "dimmer_down", "614e0c31129e29124dfcd84c", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.137Z <EzloController:WARN> EzloController#ezlo updating red for rgb_color: item named rgbcolor not found on "614e0c31129e29124dfcd84d" (Entity#ezlo>device_614e0c31129e29124dfcd84d); has [Array][ "614e0c31129e29124dfcd84e", "switch", "614e0c32129e29124dfcd84f", "dimmer", "614e0c32129e29124dfcd850", "dimmer_up", "614e0c32129e29124dfcd851", "dimmer_down", "614e0c32129e29124dfcd852", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.137Z <EzloController:WARN> EzloController#ezlo updating green for rgb_color: item named rgbcolor not found on "614e0c31129e29124dfcd84d" (Entity#ezlo>device_614e0c31129e29124dfcd84d); has [Array][ "614e0c31129e29124dfcd84e", "switch", "614e0c32129e29124dfcd84f", "dimmer", "614e0c32129e29124dfcd850", "dimmer_up", "614e0c32129e29124dfcd851", "dimmer_down", "614e0c32129e29124dfcd852", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.137Z <EzloController:WARN> EzloController#ezlo updating blue for rgb_color: item named rgbcolor not found on "614e0c31129e29124dfcd84d" (Entity#ezlo>device_614e0c31129e29124dfcd84d); has [Array][ "614e0c31129e29124dfcd84e", "switch", "614e0c32129e29124dfcd84f", "dimmer", "614e0c32129e29124dfcd850", "dimmer_up", "614e0c32129e29124dfcd851", "dimmer_down", "614e0c32129e29124dfcd852", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.138Z <EzloController:WARN> EzloController#ezlo updating value for color_temperature: item named rgbcolor not found on "614e0c31129e29124dfcd84d" (Entity#ezlo>device_614e0c31129e29124dfcd84d); has [Array][ "614e0c31129e29124dfcd84e", "switch", "614e0c32129e29124dfcd84f", "dimmer", "614e0c32129e29124dfcd850", "dimmer_up", "614e0c32129e29124dfcd851", "dimmer_down", "614e0c32129e29124dfcd852", "dimmer_stop" ]
[latest-21353]2021-12-19T23:08:41.145Z <EzloController:WARN> EzloController#ezlo updating red for rgb_color: 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.145Z <EzloController:WARN> EzloController#ezlo updating green for rgb_color: 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.146Z <EzloController:WARN> EzloController#ezlo updating blue for rgb_color: 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" ]
                1 Reply Last reply Reply Quote 0
                • N
                  noelab last edited by 

                  [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
                  1 Reply Last reply Reply Quote 0
                  • toggledbits
                    toggledbits last edited by toggledbits

                    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 logs directory? That will tell me what the devices are reporting more clearly.

                    Edit: the file is now called ezlo_inventory.json for the latest version.

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

                    1 Reply Last reply Reply Quote 0
                    • N
                      noelab last edited by

                      Hi, the file it is uploaded.

                      Thanks

                      1 Reply Last reply Reply Quote 0
                      • N
                        noelab last edited by

                        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 FALSE

                        energy_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
```
                        1 Reply Last reply Reply Quote 0
                        • toggledbits
                          toggledbits last edited by toggledbits

                          OK. If you would please, upload your ezlo_inventory.json file again.

                          I would also note that the switch item (seen in raw form in x_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.

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

                          1 Reply Last reply Reply Quote 0
                          • N
                            noelab last edited by

                            Hi, checking Ezlo app and the device is also in OFF state on Dashboard. So the problem is not Reactor but Ezlo.

                            Thanks!

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

                              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.

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

                              1 Reply Last reply Reply Quote 0
                              • N
                                noelab last edited by

                                Hi and Happy New Year!
                                Trying a new test between MSR capability vs. Ezlo attribute and they show different. At the moment all devices are ON in the room:

                                abe6c505-f852-494a-b222-b1b365f974c1-image.png

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

                                  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.

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

                                  1 Reply Last reply Reply Quote 0
                                  • N
                                    noelab last edited by

                                    Updating to the last version, and doing a hard-refresh (F5) on the page, comparing the two images: now there are two devices ON

                                    ![alt text](b4a4f3cc-d2d2-4512-b8b0-eea49f845e70-image.png image url)

                                    I will try to close the brower and to erase data on the browser.

                                    1 Reply Last reply Reply Quote 0
                                    • N
                                      noelab last edited by

                                      Now seems ok, no error in the log. It was related to Google Chrome. Thanks!

                                      ![alt text](28e558ac-598b-4063-b0f7-eb96de2f993c-image.png image url)

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

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

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

                                        1 Reply Last reply Reply Quote 0
                                        • N
                                          noelab last edited by

                                          eheh, I was hoping to go happy to sleep 🙂 Yes, they diverge:

                                          ![alt text](c32f3243-5ef7-48d4-a5e9-ef1b5d72df08-image.png image url)

                                          1 Reply Last reply Reply Quote 0
                                          • N
                                            noelab last edited by

                                            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_neighbors

                                            or 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
                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

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

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