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)

    • [SOLVED] Expressions not auto-updating when dependencies change (22022)

      A

      Reactor 22022, Raspberry PI4 Buster, Docker

      What is expected: When an expression value changes, dependent expression values will also change

      What is occurring: When an expression changes, dependent expressions only update if I click "Try this expression".

      After updating to 22021 and then 22022 I noticed that my Thermostat routine started having issues. While looking into the cause I found that dependent expression were not updating automatically.

      My specific application is as follows: I have MSR poll the Lennox "iComfort" API to get the current state of the Thermostat via an HTTP request every minute.
      The request returns a JSON response. The polling rule captures that response to an expression:

      a398c3ff-2735-4116-8038-de74a9ea270c-image.png

      That expression is being updated as expected:

      65884882-389a-4497-b125-e28a6e7ccf30-image.png

      Other expressions are set to the values of various parts of the g_iComfort response. For example the cool set point expression is set as follows:

      397cea16-6af4-4919-b858-add26fc53d0d-image.png

      These screen shots show that g_iComfort has the cool set point at 74, but g_tstat_csp is still 72 as I hadn't clicked the "Try this expression" button.

      I have additional expressions set up for the heat set point, the operation mode, the humidity, etc.

      Since g_tstat_csp is dependent on g_iComfort, if g_iComfort changes g_tstat_csp should change. When the polling rule runs each minute the g_iComfort expression updates, but none of the expressions that are dependent on g_iComfort update. If I click the "Try this expression" button, they update. On versions before 22021 they updated as expected.

      As a test I set up two simpler expressions, one a string and one set to mirror that string:

      b7f5cd4a-e1de-4b86-81d5-2ef79a65996c-image.png

      The attached screen shot was after I set g_test3 to "bar" and clicked Save, then clicked "Try this expression" on g_test4 which caused it to update to "bar". I then changed g_test4 to "foo" and clicked Save which resulted in this screen shot where g_test3 is "foo" but g_test4 is still showing "bar".

      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

    • [SOLVED]. API poll doesn't un-SET or populate child expressions (bare metal install)

      G

      This is tough to explain, saying that right up front.

      HTTP Request GET to Ambient Weather API, capturing to ambient_api and the subsequent expressions for temp, UV, wind, etc. . It should be noted, this ruleset has been in place for months, working as intended.

      Disclaimer: I'm not pointing the finger at build 22021/22022 - but - using Tech Support rule #1 ("What changed?") it's in my peripheral vision.

      Initial Observations:

      Upgraded from build 22004

      The ruleset runs every five minutes, like usual, resetting when the call is done. It is NOT updating the global expressions. The data is stale. It is also not returning NULL (which sometimes the Ambient API flakes and does that and I have failover rulesets to cover that.)

      Running the ruleset manually with the Reset button returns either an API 429 or 421 error, NULL as the result which triggers the failover as it should.

      On the next scheduled run the ruleset the API errors go away and we're back to the first bullet point.

      rolling back to build 22004 resolves the issue, everything goes back to working as intended, proven multiple times yesterday working thru the unrelated issues build 220021 had.

      Other APIs appear to be working as intended. UPDATE: this is not the case, all three APIs are behaving the same as far as updating their children.

      Troubleshooting:

      I've copied the URL directly from the original ruleset and run it in a browser, no 429/421 errors no matter how many times I hammer on it.

      I've copied the URL and used it to create a duplicate replacement ruleset.

      Copied a working non-Ambient ruleset and updated the URL to make it an Ambient ruleset, which has picked up it's own oddities (noted below).

      Current oddities:

      The replacement ruleset runs on five minute schedule - and stays SET, prohibiting it from doing anything at the next five minute interval. (This only appears in build 22022.)

      because of the above, I turned off that ruleset and re-enabled the original which immediately performed the GET 100% as expected - only to fail to update the child expressions after updating the ambient_api expression on the very next scheduled run.

      Logs:
      The first screenshots are the scheduled run at 0900 ET.

      log-0900ET-part1.png log-0900ET-part2.png log-0900ET-part3.png log-0900ET-part4.png log-0900ET-part5.png log-0900ET-part6.png

      The next screenshot is the manual (via Reset) at 0905 ET

      log-0905ET.png

      The next screenshot is the scheduled run at 0910 ET after the last run set the ruleset to SET

      log-0910ET.png

      The last screenshot is the rulesets including the new one that is stuck in SET

      rulesets.png

      I have the actual logs that go with the screenshots and can provide if necessary.

      UPDATE: solved here https://smarthome.community/topic/872/expressions-not-auto-updating-when-dependencies-change-22022/8

      Multi-System Reactor

    • Opening curtains with a motion sensor but only once?

      cw-kid

      Hi

      I've just put a motion sensor under my bed so when I get up in a morning it will open the curtains.

      However how do you make it so that action only happens once until the next morning?

      For example if I later in the day enter the bedroom again, I don't want this rule to be triggered again and its action run again etc.

      Thanks

      Multi-System Reactor

    • While action group in MSR 22022

      therealdb

      Engine: New and very experimental Repeat While action group, repeats as long as its conditions are met. The group must have at least one condition or it will not run at all. The repeat will stop if either (a) the conditions result in false, or (b) if it's in a rule-based reaction, the contra-reaction is started by a change of rule state. It is quite possible to make reaction groups that never stop, so be careful with your logic here.

      @toggledbits I'm struggling to find this - I'd like to test it for a couple of interval-based rules, but I'm not able to find it. Thanks!

      Multi-System Reactor

    • npm ERR! code EBADPLATFORM reactor 20022

      Elcid

      i get the following error when i run
      ~/reactor $ npm i --no-save --omit dev
      Reactor is running and i see no ill effects so far
      Thought i would report for info.

      ~/reactor $ npm i --no-save --omit dev npm ERR! code EBADPLATFORM npm ERR! notsup Unsupported platform for inotify@1.4.6: wanted {"os":"linux","arch":"any"} (current: {"os":"android","arch":"arm"}) npm ERR! notsup Valid OS: linux npm ERR! notsup Valid Arch: any npm ERR! notsup Actual OS: android

      and here is log for more info

      0 info it worked if it ends with ok 1 verbose cli [ 1 verbose cli '/data/data/com.termux/files/usr/bin/node', 1 verbose cli '/data/data/com.termux/files/usr/bin/npm', 1 verbose cli 'i', 1 verbose cli '--no-save', 1 verbose cli '--omit', 1 verbose cli 'dev' 1 verbose cli ] 2 info using npm@6.14.10 3 info using node@v14.15.4 4 verbose npm-session e65bf5b70b2ee3fd 5 silly install loadCurrentTree 6 silly install readLocalPackageData 7 http fetch GET 200 https://registry.npmjs.org/dev 1079ms 8 http fetch GET 200 https://registry.npmjs.org/dev/-/dev-0.1.3.tgz 161ms 9 silly pacote tag manifest for dev@latest fetched in 1336ms 10 timing stage:loadCurrentTree Completed in 2965ms 11 silly install loadIdealTree 12 silly install cloneCurrentTreeToIdealTree 13 timing stage:loadIdealTree:cloneCurrentTree Completed in 11ms 14 silly install loadShrinkwrap 15 timing stage:loadIdealTree:loadShrinkwrap Completed in 316ms 16 silly install loadAllDepsIntoIdealTree 17 silly resolveWithNewModule dev@0.1.3 checking installable status 18 http fetch GET 200 https://registry.npmjs.org/inotify 788ms 19 http fetch GET 200 https://registry.npmjs.org/inotify/-/inotify-1.4.6.tgz 796ms 20 silly pacote range manifest for inotify@>= 0.1.6 fetched in 1636ms 21 silly resolveWithNewModule inotify@1.4.6 checking installable status 22 timing stage:rollbackFailedOptional Completed in 2ms 23 timing stage:runTopLevelLifecycles Completed in 4975ms 24 verbose stack Error: Unsupported platform for inotify@1.4.6: wanted {"name":"inotify","version":"1.4.6","engines":{"node":">=0.8"},"os":["linux"],"dependencies":{"bindings":"^1.3.1","nan":"^2.12.1"},"optionalDependencies":{},"peerDependenciesMeta":{},"devDependencies":{},"bundleDependencies":false,"peerDependencies":{},"deprecated":false,"_resolved":"https://registry.npmjs.org/inotify/-/inotify-1.4.6.tgz","_integrity":"sha512-WW8/uqIA04O3AePQVe/Ms3ZLR0yGamaz8YOEpaXc4WBAGOPZfzu58wWErEPSUYaPyDrJRIeCn6PEIQgC1ZyQ5w==","_shasum":"c5a51852df1647d1a589d46c4baa2771ed36b8d2","_shrinkwrap":null,"_id":"inotify@1.4.6","_from":"inotify@>= 0.1.6","_requested":{"type":"range","registry":true,"raw":"inotify@>= 0.1.6","name":"inotify","escapedName":"inotify","rawSpec":">= 0.1.6","saveSpec":null,"fetchSpec":">= 0.1.6"},"_spec":"inotify@>= 0.1.6","_where":"/data/data/com.termux/files/home/reactor/node_modules/dev"} (current: {"os":"android","cpu":"arm"}) 24 verbose stack at checkPlatform (/data/data/com.termux/files/usr/lib/node_modules/npm/node_modules/npm-install-checks/index.js:46:14) 24 verbose stack at thenWarnEngineIssues (/data/data/com.termux/files/usr/lib/node_modules/npm/lib/install/validate-args.js:63:5) 24 verbose stack at /data/data/com.termux/files/usr/lib/node_modules/npm/node_modules/iferr/iferr.js:3:64 24 verbose stack at checkEngine (/data/data/com.termux/files/usr/lib/node_modules/npm/node_modules/npm-install-checks/index.js:25:10) 24 verbose stack at module.exports.isInstallable (/data/data/com.termux/files/usr/lib/node_modules/npm/lib/install/validate-args.js:60:3) 24 verbose stack at resolveWithNewModule (/data/data/com.termux/files/usr/lib/node_modules/npm/lib/install/deps.js:677:10) 24 verbose stack at /data/data/com.termux/files/usr/lib/node_modules/npm/lib/install/deps.js:600:7 24 verbose stack at /data/data/com.termux/files/usr/lib/node_modules/npm/node_modules/iferr/iferr.js:3:64 24 verbose stack at /data/data/com.termux/files/usr/lib/node_modules/npm/node_modules/call-limit/call-limit.js:28:43 24 verbose stack at processTicksAndRejections (internal/process/task_queues.js:75:11) 25 verbose pkgid inotify@1.4.6 26 verbose cwd /data/data/com.termux/files/home/reactor 27 verbose Linux 4.9.76 28 verbose argv "/data/data/com.termux/files/usr/bin/node" "/data/data/com.termux/files/usr/bin/npm" "i" "--no-save" "--omit" "dev" 29 verbose node v14.15.4 30 verbose npm v6.14.10 31 error code EBADPLATFORM 32 error notsup Unsupported platform for inotify@1.4.6: wanted {"os":"linux","arch":"any"} (current: {"os":"android","arch":"arm"}) 33 error notsup Valid OS: linux 33 error notsup Valid Arch: any 33 error notsup Actual OS: android 33 error notsup Actual Arch: arm 34 verbose exit [ 1, true ]

      Depandencies

      {"dependencies": { "@influxdata/influxdb-client": "^1.18.0", "@mdi/font": "^5.9.55", "body-parser": "^1.19.0", "bootstrap": "4.6.0", "bootstrap-icons": "1.5.0", "cookie": "^0.4.1", "digest-fetch": "^1.2.1", "diskusage-ng": "^1.0.1", "express": "^4.17.1", "feather-icons": "^4.28.0", "font-awesome": "^4.7.0", "gridstack": "^5.0.0", "jquery": "3.6.0", "jquery-ui-dist": "1.12.1", "js-yaml": "^3.14.1", "node-fetch": "^2.6.7", "nodemailer": "^6.5.0", "qs": "^6.10.1", "serve-static": "^1.14.1", "uuid": "^8.3.2", "ws": "^7.5.6" }
      Multi-System Reactor

    • `npm install --no-save --omit dev` gives vulnerability warning (node-fetch)

      toggledbits

      The node-fetch package, which is used by Reactor for several purposes, was reported to have a security vulnerability, and when you update packages (as is required for the recent 22021 release), you get a warning about it.

      NIST currently reports that all versions of node-fetch prior to 3.1.1 are vulnerable, but since the 2.x and 3.x release paths are incompatible, I cannot easily or quickly update Reactor to use 3.1.1. Further, the author of the package now reports that version 2.6.7 is patched against the vulnerability. It may take some time before NIST lists this fact on their web site and npm's audit info is also updated. His patch was made a week ago, so it's clearly not an instantaneous process.

      If you do npm ls in your Reactor install directory (bare metal users only), you will see what version you currently have installed.

      DO NOT run npm audit fix as recommended by npm. This will just break your Reactor installation by installing the incompatible 3.1.1 version. If you do this, you can undo it by running npm install --no-save --omit dev again. If that doesn't do it, delete your entire node_modules subdirectory and any package-lock.json file in the Reactor install directory, and run the command again.

      Multi-System Reactor

    • Release 22021 Windows Bare-metal won't load

      W

      Hi

      I have the same situation as the Reactor interface wouldn't load in the browser, I use Windows bare-metal installation.

      Unlike the previous comment, looking at the log file I have no error, everything is loaded, and I see that the Reactor is operating, the actions are happening, only the interface in the browser that does not open.

      Thanks

      Multi-System Reactor

    • OW-SERVER: 1-Wire to Ethernet Server - MSR Functionality

      T

      Could the temperature values be pulled into MSR from one of these devices: OW-SERVER: 1-Wire to Ethernet Server

      71.57 GBP OW server (Ethernet) OW server (Ethernet)

      Description The OW-SERVER is an inexpensive Ethernet to 1-Wire interface that is designed to efficiently monitor and control 1-Wire devices. The OW-SERVER will allow you to use industry standard Ethernet products (switches, hubs, etc.) to build the backbone of your 1-Wire based sensor / control...

      Thanks.

      Multi-System Reactor

    • [SOLVED] Fatal error on upgrade to 22021 / Raspberry Pi4 Docker

      A

      I attempted to upgrade my Docker container to "toggledbits/reactor:latest-raspbian-armv7l" and the container started but the Reactor interface wouldn't load in the browser. The logs showed this:

      # # Fatal error in , line 0 # unreachable code # # # #FailureMessage Object: 0xbec2458c # # Fatal error in , line 0 # unreachable code # # # #FailureMessage Object: 0xbedec58c # # Fatal error in , line 0 # unreachable code # # # #FailureMessage Object: 0xbed3358c # # Fatal error in , line 0 # unreachable code # # # #FailureMessage Object: 0xbef7f58c # # Fatal error in , line 0 # unreachable code # # # #FailureMessage Object: 0xbedd958c # # Fatal error in , line 0 # unreachable code # # # #FailureMessage Object: 0xbe86958c

      The logs continued throwing errors with different object IDs.

      I removed the container and tried to install again using toggledbits/reactor:1.0.2-raspbian-armv7l and now the container won't start and the logs show this:

      NODE_PATH /opt/reactor FileLogStream { type: 'file', name: 'reactor.log', mode: 438, maxsize: 2, keep: 5 } [1.0.2-21350]2022-01-22T14:35:21.715Z <app:null> Reactor "1.0.2-21350-252f948" starting on v16.11.1 [1.0.2-21350]2022-01-22T14:35:21.717Z <app:INFO> Process ID 1; platform linux/arm #1457 SMP Tue Sep 28 11:26:14 BST 2021; locale (undefined) [1.0.2-21350]2022-01-22T14:35:21.718Z <app:INFO> Basedir /opt/reactor; data in /var/reactor/storage [1.0.2-21350]2022-01-22T14:35:21.719Z <app:INFO> NODE_PATH=/opt/reactor [1.0.2-21350]2022-01-22T14:35:21.727Z <app:INFO> Configured locale (undefined); selected locale(s) en-US.UTF-8 [1.0.2-21350]2022-01-22T14:35:21.786Z <app:INFO> Loaded locale en-US [1.0.2-21350]2022-01-22T14:35:21.812Z <Capabilities:null> Module Capabilities v21333 [1.0.2-21350]2022-01-22T14:35:21.890Z <Plugin:null> Module Plugin v21186 [1.0.2-21350]2022-01-22T14:35:21.902Z <TimerBroker:null> Module TimerBroker v21333 [1.0.2-21350]2022-01-22T14:35:21.908Z <default:INFO> Module Entity v21334 [1.0.2-21350]2022-01-22T14:35:21.916Z <Controller:null> Module Controller v21333 [1.0.2-21350]2022-01-22T14:35:21.917Z <default:null> Module Structure v21338 [1.0.2-21350]2022-01-22T14:35:21.934Z <default:null> Module Ruleset v21096 [1.0.2-21350]2022-01-22T14:35:21.935Z <default:null> Module Rulesets v21096 [1.0.2-21350]2022-01-22T14:35:21.956Z <GlobalExpression:null> Module GlobalExpression v21333 [1.0.2-21350]2022-01-22T14:35:21.986Z <default:null> Module Rule v21348 [1.0.2-21350]2022-01-22T14:35:21.994Z <GlobalReaction:null> Module GlobalReaction v21333 [1.0.2-21350]2022-01-22T14:35:21.997Z <AlertManager:null> Module AlertManager v21333 [1.0.2-21350]2022-01-22T14:35:21.998Z <default:null> Module Engine v21346 [1.0.2-21350]2022-01-22T14:35:21.999Z <default:null> Module httpapi v21345 [1.0.2-21350]2022-01-22T14:35:22.004Z <default:null> Module httpproxy v21333 [1.0.2-21350]2022-01-22T14:35:22.037Z <default:null> Module wsapi v21334 [1.0.2-21350]2022-01-22T14:35:22.048Z <app:NOTICE> Starting Structure... [1.0.2-21350]2022-01-22T14:35:22.131Z <InfluxFeed:null> Module InfluxFeed v21345 [1.0.2-21350]2022-01-22T14:35:22.135Z <Structure:INFO> Structure#1 starting plugin influx (InfluxFeed) [1.0.2-21350]2022-01-22T14:35:22.137Z <Structure:INFO> Structure#1 loading controller interface hubitat (HubitatController) [1.0.2-21350]2022-01-22T14:35:22.162Z <HubitatController:null> Module HubitatController v21338 [1.0.2-21350]2022-01-22T14:35:22.174Z <Structure:INFO> Structure#1 loading controller interface hubitat_11705 (HubitatController) [1.0.2-21350]2022-01-22T14:35:22.180Z <Structure:INFO> Structure#1 loading controller interface weather (OWMWeatherController) [1.0.2-21350]2022-01-22T14:35:22.194Z <OWMWeatherController:null> Module OWMWeatherController v21313 [1.0.2-21350]2022-01-22T14:35:22.198Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController) [1.0.2-21350]2022-01-22T14:35:22.205Z <SystemController:null> Module SystemController v21345 [1.0.2-21350]2022-01-22T14:35:22.211Z <Structure:INFO> Structure#1 loading controller interface mqtt (MQTTController) [1.0.2-21350]2022-01-22T14:35:22.223Z <MQTTController:null> Module MQTTController v21361 [1.0.2-21350]2022-01-22T14:35:22.227Z <Controller:CRIT> Controller: failed to load mqtt implementation file:///var/reactor/ext/MQTTController/MQTTController.js: [TypeError]TypeError: require(...).requires is not a function [1.0.2-21350]2022-01-22T14:35:22.229Z <Controller:CRIT> TypeError: require(...).requires is not a function TypeError: require(...).requires is not a function at Object.<anonymous> (/var/reactor/ext/MQTTController/MQTTController.js:14:53) at Module._compile (node:internal/modules/cjs/loader:1101:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10) at Module.load (node:internal/modules/cjs/loader:981:32) at Function.Module._load (node:internal/modules/cjs/loader:822:12) at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:196:29) at ModuleJob.run (node:internal/modules/esm/module_job:183:25) at async Loader.import (node:internal/modules/esm/loader:178:24) at async importModuleDynamicallyWrapper (node:internal/vm/module:437:15) Trapped unhandled Promise rejection TypeError: require(...).requires is not a function at Object.<anonymous> (/var/reactor/ext/MQTTController/MQTTController.js:14:53) at Module._compile (node:internal/modules/cjs/loader:1101:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10) at Module.load (node:internal/modules/cjs/loader:981:32) at Function.Module._load (node:internal/modules/cjs/loader:822:12) at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:196:29) at ModuleJob.run (node:internal/modules/esm/module_job:183:25) at async Loader.import (node:internal/modules/esm/loader:178:24) at async importModuleDynamicallyWrapper (node:internal/vm/module:437:15) TypeError: require(...).requires is not a function at Object.<anonymous> (/var/reactor/ext/MQTTController/MQTTController.js:14:53) at Module._compile (node:internal/modules/cjs/loader:1101:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10) at Module.load (node:internal/modules/cjs/loader:981:32) at Function.Module._load (node:internal/modules/cjs/loader:822:12) at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:196:29) at ModuleJob.run (node:internal/modules/esm/module_job:183:25) at async Loader.import (node:internal/modules/esm/loader:178:24) at async importModuleDynamicallyWrapper (node:internal/vm/module:437:15)  { <rejected> TypeError: require(...).requires is not a function at Object.<anonymous> (/var/reactor/ext/MQTTController/MQTTController.js:14:53) at Module._compile (node:internal/modules/cjs/loader:1101:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10) at Module.load (node:internal/modules/cjs/loader:981:32) at Function.Module._load (node:internal/modules/cjs/loader:822:12) at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:196:29) at ModuleJob.run (node:internal/modules/esm/module_job:183:25) at async Loader.import (node:internal/modules/esm/loader:178:24) at async importModuleDynamicallyWrapper (node:internal/vm/module:437:15) } Trace at process.<anonymous> (/opt/reactor/app.js:267:142) at process.emit (node:events:390:28) at process.emit (node:domain:475:12) at emit (node:internal/process/promises:136:22) at processPromiseRejections (node:internal/process/promises:242:25) at processTicksAndRejections (node:internal/process/task_queues:97:32) [1.0.2-21350]2022-01-22T14:35:22.234Z <app:ERR> Trapped unhandled Promise rejection: [TypeError]TypeError: require(...).requires is not a function [1.0.2-21350]2022-01-22T14:35:22.234Z <app:ERR> Please refer to the console log for trace

      I noticed the reference to MQTT so I changed MQTT controller to enabled:False in my reactor.yaml file. I tried reinstalling latest with the same results as before. I was then able to install 1.0.2 successfully and Reactor is running. I'm only getting this error on the status page:

      An Entity Attribute condition in rule "Notify when Reactor Alert is raised" failed because the referenced entity Reactor System (reactor_system>system) does not have attribute reactor_system.alert_last

      I assume that 1.0.2 was prior to that feature being implemented.

      Any advice on how to successfully upgrade to 22021 would be appreciated. I saw the instructions for bare metal, but I don't think that applies when I'm pulling the docker image and creating a new container.

      Multi-System Reactor

    • Anybody Installed MSR on unRaid Docker

      D

      Greetings,

      I'm not a Docker expert hence the choice of using unRaid but I would like to install MSR in a Docker and I'm looking for details on the settings used as I have not installed one manually yet.

      I have installed MSR on Windows Server 2019 but I'm receiving (3 vulnerabilities (1 low, 2 high)) error messages with 'npm' and the audit fix breaks it ('npm').

      Thanks for any help you can provide.

      David

      Multi-System Reactor

    • Recently Changed Entities doesn't update on 22021

      X

      The recently changed entities no longer updates when added to the status page. It does display some initial entries. Other widgets do update as do Entities. (Docker)

      Multi-System Reactor

    • [Solved] Column width for Entities in MSR UI

      Crille

      I could not find a post or PR for this so apologies if it has been answered.
      There seems to be a fixed width for the columns in the Entities page making it impossible to see the full Canonical ID of long ID's and a lot of white space in the Entity Name column.
      I tried to adjust the width in Chrome and Edge without success, is it a feature or or am I doing it wrong?

      columns.PNG

      latest-22004-6d6c6b7 bare metal.

      Multi-System Reactor

    • [SOLVED]. Build 22021-f83a39c Status page is blank

      G

      Using Brave browser (which triggers on nothing shield-wise) clicking thru to Status page nets me a blank main portion of the page. Left pane all good, top bar all good. Doubled-check with Safari browser, same outcome.

      The notification bell is also red... but I can't get to the Status page to see what it's on about! 🙂
      90d62b31-2737-4ec0-b9d9-928000f41584-image.png

      I did go re-read the release notes just in case I missed a "and do this thing" but didn't see anything. I do have a log I pulled after doing a Restart Reactor but I see nothing jumping out at me.

      Multi-System Reactor

    • InfluxFeed configuration support for (global) expressions

      tunnus

      There are "select_entities" and "select_capabilities" configuration keys in InfluxFeed, but is it currently possible to select & export global expression values? If not, hoping that this capability would be implemented in some point.

      Multi-System Reactor

    • MSR support for openHAB?

      tunnus

      Could MSR at some point support openHAB as a controller?

      Multi-System Reactor

    • Trying to setup InfluxDB breaks my MSR install

      cw-kid

      Hi

      I've just done a clean install of Bullseye OS on my Raspberry Pi and I am trying to setup MSR with InfluxDB.

      I have managed to get the old VeraFlux plugin working OK with the new InfluxDB installation on the Pi, so think I have the InfluxDB installation correct and working.

      However ideally I'd like to use MSR instead. I created a "reactor" database and created a username and password.

      In the reactor config file I added this at the end of it

      plugins: - id: influx name: InfluxDB 1.x Feed enabled: true implementation: InfluxFeed config: influx_url: http://192.168.0.36:8086 influx_database: reactor influx_username: myuser influx_password: "mypassword" # note use of quotes

      However when I restart MSR it doesn't come back up again. If I comment out all of that plugins section in the config file and restart the box, then MSR loads OK again. So I must be doing something wrong?

      Influx running on the Pi is version 1.8.10.

      MSR is running on a different Linux Debian box.

      Not sure how to update to InfluxDB 2.0, maybe I should do that?

      I looked in the log file and searched for "Influx" but nothing was found.

      Thanks

      Multi-System Reactor

    • "Plugins"/firm-coded rulesets in MSR?

      PerH

      I know I have mentioned this before somewhere, but i simply can't find the thread..

      Plugins like Auto Virtual Thermostat and Delaylight from Vera/openLuup are functions that whould be lovely to have in MSR - is there any possibility to implement these in some way?

      I could offcourse program them myself and copy them to where i want to use them, but if i'm not wrong that would be a fairly advanced ruleset that in any case would be beneficial to share with the community in some way when they are made and done.

      Multi-System Reactor

    • MQTT interface... time for some testing. Where are my experts?

      toggledbits

      I'm probably going to release my first pass at the MQTTController for Reactor (aka MSR) this week. It doesn't yet intrinsically know about a lot of devices, but you can train it for pretty much anything, I think, and it would be great if a couple of our heavy MQTT users could help check it out and maybe help contribute some device templates.

      I'm hoping to package it up for mid-week, assuming the rest of life stays on track.

      Success factors for the test: solid familiarity with MQTT, a big mix of devices, and comfortable editing YAML (for creating the templates/mappings).

      Multi-System Reactor

    • [How-To] Map a thermostat from Home Assistant to Vera

      therealdb

      I've recently moved my Nest Thermostats from Vera to Home Assistant, using the official integration. This is a how-to migrate it completely on Home Assistant, thus retaining control and status in your Vera (i.e.: because you have code/scenes/Reactor rules/whatever to maintain - in my case it was all the above and more).

      Prerequisite: goto https://github.com/dbochicchio/vera-VirtualDevices and install the virtual heater/thermostats files. Follow instructions, if in doubt.

      First, go to your Vera, enter your thermostat Advanced Settings, under Params be sure to remove the plugin, by setting its value to 0. Then

      change device_file to D_VirtualThermostat1.xml change impl_file to I_VirtualHeater1.xml change device_json to D_VirtualThermostat1.json change subcategory_num to 1 (if necessary)

      Repeat for other thermostats - you could use the first as master, so look for the doc for more info on this point. Be sure to remove the plugin from humidity sensors as well.

      After the luup reload, hard refresh (CTRL+F5) your browser and then set all these variables to skip (we will not execute actions on setpoint/mode changes, we'll just save variables).

      SetPowerURL SetPowerOffURL SetSetpointURL

      At this point, the actions to change mode/setpoint will write your desired value to SetpointTarget and ModeTarget variables. We will use them in MSR to get the actions and execute them in Home Assistant.

      Under MSR, be sure to write two rules.
      One rule is watching for SetpointTarget and ModeTarget variables under the Vera Virtual Thermostat, to execute the actions on your thermostat.

      f70a6c94-df72-4b89-8d69-0edced1c5440-image.png

      You'll need to translate the values from Vera's mode (Off, HeatOn, CoolOn) to HASS one (off, heat, cool). Since this thermostat is heating only, I'm just translating the ones I have. Repeat these steps for every device you have.

      Then, you'll need to write a rule looking for temperature, setpoints, mode and so on. I have a unique rule to synchronize all of them, so I'm looking for humidity entity, temperature entity, and thermostat to update the Vera's variable. I have a set of expressions to translate to Vera's friendly variables:

      730b32f0-d232-4bc4-9981-26dfaa00d56c-image.png

      You'll need to just set the variables like this:
      890083b3-ccd6-4039-99cb-1c90d64f00d5-image.png

      Variables involved:

      Service Variables Value urn:upnp-org:serviceId:TemperatureSensor1 CurrentTemperature ${{temperature}} urn:micasaverde-com:serviceId:HumiditySensor1 CurrentLevel ${{humidity}} urn:upnp-org:serviceId:TemperatureSetpoint1 CurrentSetpoint ${{setpoint}} urn:upnp-org:serviceId:TemperatureSetpoint1_Heat CurrentSetpoint ${{setpoint}} urn:upnp-org:serviceId:TemperatureSetpoint1 SetpointAchieved ${{setpointachieved}} urn:upnp-org:serviceId:TemperatureSetpoint1_Heat SetpointAchieved ${{setpointachieved}} urn:upnp-org:serviceId:HVAC_UserOperatingMode1 ModeStatus ${{modestatus}} urn:micasaverde-com:serviceId:HVAC_OperatingState1 ModeState ${{modestate}} urn:upnp-org:serviceId:HVAC_UserOperatingMode1 EnergyModeStatus ${{energymodestatus}}

      Just repeat these steps for every thermostat and you should be good to go. It could be adapted for a different mix of devices/systems, of course. I hope this will help someone else achieving the same results! Now we can control the thermostat from both point and everything is in sync!

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