Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. EzloControler access credentials timeout?
Copying a global reaction
tunnusT
With build 25328, if you copy a global reaction, a new reaction does not appear in the UI unless you do a refresh. I recall this used to work without needing this page refresh? Anyway, only a minor nuisance.
Multi-System Reactor
[Reactor] Bug when sending MQTT boolean payloads
therealdbT
Topic thumbnail image
Multi-System Reactor
Difficulty defining repeating annual period
R
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Multi-System Reactor
Need help with sequence
T
Good evening all, For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time. Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed. Thanks.
Multi-System Reactor
Possible feature request?
CatmanV2C
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations. Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction? Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for. I guess it's something of an edge case so no huge issue. TIA! C
Multi-System Reactor
Logic Assistance: Exterior Lights on when Illuminance Below Threshold
PablaP
Topic thumbnail image
Multi-System Reactor
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
MQTT templates for ZIgbee scene controller, or a better way?
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reset a delay
CatmanV2C
I'm sure this has been asked, and answered, but damned if I can figure it out Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage. Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts. After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!) What I would like is for the 3 minute delay until the lights go off to start from the latest door open event. That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity. I've tried 'hacking' with a virtual switch, but can't seem to stop the delay. Any pointers? TIA C
Multi-System Reactor
Reactor Loading Screen Safari
S
Topic thumbnail image
Multi-System Reactor
Constraints states visually do not match actual
S
Topic thumbnail image
Multi-System Reactor
[MSR] Feature request: For Each action on arrays/groups
therealdbT
Topic thumbnail image
Multi-System Reactor
[Solved] Error: Command timeout
G
at _ClientAPI._commandTimeout (http://192.168.1.100:8111/client/ClientAPI.js:807:179 Seeing this randomly when returning to open browser tab after being away awhile. Once, maybe twice a day. "What did you do to trigger it?" Literally nothing, just walked away and returned and there it was. Actions taken in reasonably close proximity to this particular instance of it popping up: I'd restarted the MSR container in Portainer. I'll try to grab some logs here shortly.
Multi-System Reactor
Issue with MSR UI becoming unresponsive
S
I'm having an issue with MSR's UI being very unresponsive. It started happening a couple days ago and I didn't make any changes that would have caused this except adding some meross lan devices in HA. When I go into an entity action and use the search functionality, it usually will start filtering and then get to a place after a few letters are entered where it will take 30 seconds or more (sometimes minutes) for the UI to show what I am typing. During this time MSR ui is completely unresponsive. I've tried multiple browsers and multiple computers. HA and MSR are both deployed in docker. I have run HTOP on the host and when the problem happens there are no CPU/Memory spikes at all. From a functionality standpoint MSR is working perfectly. This seems to be an UI issue only. Do i need to ditch Docker and run MSR on a Proxmox VM? I have both stand alone Docker and Proxmox environments. I dont mind doing that I just want to be able to use the UI again... Installation method Home Assistant Container Core 2025.7.3 Frontend 20250702.3 nothing crazy in the logs except some openweather map stuff that doesn't make any sense as it is working fine in MSR Any help would be greatly appreciated Reactor latest-25328-b2ed1365 app 25328 configuration from /var/reactor/config NODE_PATH /opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.843Z <app:null> Reactor build latest-25328-b2ed1365 starting on v24.11.1 /usr/local/bin/node [latest-25328]2025-11-30T20:01:53.844Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #161-Ubuntu SMP Tue Jul 22 14:25:40 UTC 2025; locale (undefined) [latest-25328]2025-11-30T20:01:53.844Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-25328]2025-11-30T20:01:53.844Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.865Z <app:null> Resolved timezone=America/New_York, environment TZ=America/New_York; offset minutes from UTC=-300 [latest-25328]2025-11-30T20:01:53.867Z <default:null> Module i18n v25141 [latest-25328]2025-11-30T20:01:53.867Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8 [latest-25328]2025-11-30T20:01:53.879Z <app:null> Loaded locale en-US for en-US [latest-25328]2025-11-30T20:01:53.879Z <app:null> Local date/time using configured timezone and locale formatting is "11/30/2025, 3:01:53 PM" [latest-25328]2025-11-30T20:01:53.889Z <Structure:null> Module Structure v25326 [latest-25328]2025-11-30T20:01:53.890Z <Capabilities:null> Module Capabilities v24312 [latest-25328]2025-11-30T20:01:53.904Z <Plugin:null> Module Plugin v25141 [latest-25328]2025-11-30T20:01:53.923Z <Timer:null> Module Timer v25279 [latest-25328]2025-11-30T20:01:53.924Z <TimerBroker:null> Module TimerBroker v25314 [latest-25328]2025-11-30T20:01:53.927Z <Entity:null> Module Entity v25251 [latest-25328]2025-11-30T20:01:53.929Z <Controller:null> Module Controller v25253 [latest-25328]2025-11-30T20:01:53.930Z <AlertManager:null> Module AlertManager v25318 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Ruleset v25283 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Rulesets v25141 [latest-25328]2025-11-30T20:01:53.942Z <GlobalExpression:null> Module GlobalExpression v25258 [latest-25328]2025-11-30T20:01:53.953Z <Predicate:null> Module Predicate v25328 [latest-25328]2025-11-30T20:01:53.956Z <Rule:null> Module Rule v25323 [latest-25328]2025-11-30T20:01:53.958Z <GlobalReaction:null> Module GlobalReaction v25292 [latest-25328]2025-11-30T20:01:53.959Z <Engine:null> Module Engine v25325 [latest-25328]2025-11-30T20:01:53.964Z <httpapi:null> Module httpapi v25328 [latest-25328]2025-11-30T20:01:53.972Z <wsapi:null> Module wsapi v25328 [latest-25328]2025-11-30T20:01:53.994Z <TaskQueue:null> Module TaskQueue 24138 [latest-25328]2025-11-30T20:01:53.994Z <VeraController:null> Module VeraController v25141 [latest-25328]2025-11-30T20:01:54.179Z <HassController:null> Module HassController v25325 [latest-25328]2025-11-30T20:02:13.797Z <OWMWeatherController:null> Module OWMWeatherController v25268 [latest-25328]2025-11-30T20:02:13.800Z <SystemController:null> Module SystemController v25323 [latest-25328]2025-11-30T20:02:13.807Z <MQTTController:null> Module MQTTController v22092 [latest-25328]2025-11-30T20:02:20.630Z <OWMWeatherController:CRIT> FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxx&lon=-xxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxxxxxxxxx&units=standard&_r=1xxxxxxxxxxxxxxfailed, reason: [-] FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxxx&lon=-xxxxxxxxxxxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxx&units=standard&_r=xxxxxxxxxxxxxxxfailed, reason: at ClientRequest.<anonymous> (/opt/reactor/node_modules/node-fetch/lib/index.js:1501:11) at ClientRequest.emit (node:events:508:28) at ClientRequest.emit (node:domain:489:12) at emitErrorEvent (node:_http_client:108:11) at TLSSocket.socketErrorListener (node:_http_client:575:5) at TLSSocket.emit (node:events:508:28) at TLSSocket.emit (node:domain:489:12) at emitErrorNT (node:internal/streams/destroy:170:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at processTicksAndRejections (node:internal/process/task_queues:89:21
Multi-System Reactor
Date/time condition
tunnusT
Topic thumbnail image
Multi-System Reactor
Device log?
G
@toggledbits is there a log that will show me what rule is turning on a specific device? I've got a switch that has been kicking on at 2200 ET for several nights now and the reactor.log doesn't have a thing in it that I can see on a device level (it being more rules-based).
Multi-System Reactor
Midnight crossing not working in date/time condition (build 25325)
tunnusT
Topic thumbnail image
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here. Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
[Solved] Local expression in Rule does not evaluate as they used to do
CrilleC
Topic thumbnail image
Multi-System Reactor
Home Assistant 2025.11.2 and latest-25315
CrilleC
Topic thumbnail image
Multi-System Reactor

EzloControler access credentials timeout?

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

    I have Multi-System reactor set to with both my Vera Plus and Ezlo Plus - and up to a while ago, both were working. Recently, however, I noticed that it didn't seem to be communicating with my Ezlo Plus correctly. Looking at the logs, I see this:

    [latest-22337]2022-12-09T03:44:49.980Z <EzloController:INFO> EzloController#ezlo: connecting to hub "90XXXXXX"
    [latest-22337]2022-12-09T03:44:49.980Z <EzloController:ERR> EzloController#ezlo: failed to get access credentials: [FetchError] network timeout at: https://vera-us-oem-autha11.mios.com/autha/auth/username/reactor?SHA1Password=<long_string>c&PK_Oem=1&TokenVersion=2 [-]
    [latest-22337]2022-12-09T03:44:49.980Z <EzloController:INFO> EzloController#ezlo will retry in 75000ms; this was attempt 17
    

    So apparently it is getting a timeout when trying to connect to vera to authorize? How can I fix this, or does it simply not work any more?

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

      Is your Ezlo username really reactor? That seems a bit odd...

      Edit: I'm having no trouble connecting with (my own) correct account credentials.

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

      1 Reply Last reply
      0
      • I Offline
        I Offline
        ibrewster
        wrote on last edited by
        #3

        Yes, I set up a user specifically for reactor to use, with a username of reactor. Also, as I mentioned, when I originally set this up a while ago, it did work - only recently has it stopped working. Of course, if the user/password WAS wrong, (or something changed so it wouldn't work any more) I would expect a different error than "network timeout" 🙂

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

          OK. Well, not having any problems with my regular access credentials. EzloController is working.

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

          1 Reply Last reply
          0
          • I Offline
            I Offline
            ibrewster
            wrote on last edited by
            #5

            Checking the log again this morning, I now have a different error - apparently whatever was causing the network timeout was resolved, but now I'm getting this (after a restart of reactor):

            [latest-22337]2022-12-09T14:29:41.939Z <EzloController:INFO> EzloController#ezlo successful local connection (authenticated) to "90000478"
            [latest-22337]2022-12-09T14:29:41.940Z <EzloController:INFO> EzloController#ezlo starting hub inventory
            [latest-22337]2022-12-09T14:29:41.980Z <EzloController:INFO> EzloController#ezlo hub "90000478" is h2.1 (undefined) firmware "2.0.33.2116.2"
            [latest-22337]2022-12-09T14:29:41.980Z <System:WARN> System#ezlo>system attempt by caller to set attribute value to undefined
            [latest-22337]2022-12-09T14:29:41.980Z <System:CRIT> Error: traceback [-]
            Error: traceback
                at System.setAttribute (/opt/reactor/server/lib/Entity.js:454:152)
                at EzloController._process_hub_info (/opt/reactor/server/lib/EzloController.js:1516:768)
                at /opt/reactor/server/lib/EzloController.js:1354:48
                at processTicksAndRejections (node:internal/process/task_queues:96:5)
            [latest-22337]2022-12-09T14:29:42.138Z <EzloController:ERR> EzloController#ezlo error creating entity Switch#ezlo>device_5f5199de12a3b716d5ba2969: [ReferenceError] Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 [-]
            [latest-22337]2022-12-09T14:29:42.138Z <EzloController:CRIT> ReferenceError: Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 [-]
            ReferenceError: Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24
                at Group.setAttribute (/opt/reactor/server/lib/Entity.js:460:19)
                at Group.setAttributes (/opt/reactor/server/lib/Entity.js:511:39)
                at Group._syncAttribute (/opt/reactor/server/lib/entities/Group.js:110:31)
                at Group.addMember (/opt/reactor/server/lib/entities/Group.js:118:227)
                at /opt/reactor/server/lib/EzloController.js:1612:61
                at Array.forEach (<anonymous>)
                at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226)
                at /opt/reactor/server/lib/EzloController.js:1413:48
                at processTicksAndRejections (node:internal/process/task_queues:96:5)
            [latest-22337]2022-12-09T14:29:42.139Z <EzloController:ERR> EzloController#ezlo error creating entity Switch#ezlo>device_5f5199de12a3b716d5ba296c: [ReferenceError] Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 [-]
            [latest-22337]2022-12-09T14:29:42.139Z <EzloController:CRIT> ReferenceError: Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 [-]
            ReferenceError: Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24
                at Group.setAttribute (/opt/reactor/server/lib/Entity.js:460:19)
                at Group.setAttributes (/opt/reactor/server/lib/Entity.js:511:39)
                at Group._syncAttribute (/opt/reactor/server/lib/entities/Group.js:110:31)
                at Group.addMember (/opt/reactor/server/lib/entities/Group.js:118:227)
                at /opt/reactor/server/lib/EzloController.js:1612:61
                at Array.forEach (<anonymous>)
                at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226)
                at /opt/reactor/server/lib/EzloController.js:1413:48
                at processTicksAndRejections (node:internal/process/task_queues:96:5)
            [latest-22337]2022-12-09T14:29:42.141Z <EzloController:ERR> EzloController#ezlo error creating entity Switch#ezlo>device_5f5199de12a3b716d5ba296e: [ReferenceError] Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 [-]
            [latest-22337]2022-12-09T14:29:42.141Z <EzloController:CRIT> ReferenceError: Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 [-]
            ReferenceError: Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24
                at Group.setAttribute (/opt/reactor/server/lib/Entity.js:460:19)
                at Group.setAttributes (/opt/reactor/server/lib/Entity.js:511:39)
                at Group._syncAttribute (/opt/reactor/server/lib/entities/Group.js:110:31)
                at Group.addMember (/opt/reactor/server/lib/entities/Group.js:118:227)
                at /opt/reactor/server/lib/EzloController.js:1612:61
                at Array.forEach (<anonymous>)
                at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226)
                at /opt/reactor/server/lib/EzloController.js:1413:48
                at processTicksAndRejections (node:internal/process/task_queues:96:5)
            [latest-22337]2022-12-09T14:29:42.142Z <EzloController:ERR> EzloController#ezlo error creating entity Switch#ezlo>device_5f5199de12a3b716d5ba2970: [ReferenceError] Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 [-]
            [latest-22337]2022-12-09T14:29:42.142Z <EzloController:CRIT> ReferenceError: Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 [-]
            ReferenceError: Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24
                at Group.setAttribute (/opt/reactor/server/lib/Entity.js:460:19)
                at Group.setAttributes (/opt/reactor/server/lib/Entity.js:511:39)
                at Group._syncAttribute (/opt/reactor/server/lib/entities/Group.js:110:31)
                at Group.addMember (/opt/reactor/server/lib/entities/Group.js:118:227)
                at /opt/reactor/server/lib/EzloController.js:1612:61
                at Array.forEach (<anonymous>)
                at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226)
                at /opt/reactor/server/lib/EzloController.js:1413:48
                at processTicksAndRejections (node:internal/process/task_queues:96:5)
            [latest-22337]2022-12-09T14:29:42.143Z <EzloController:ERR> EzloController#ezlo error creating entity Switch#ezlo>device_5f63e44712a3b715b80ffcd2: [ReferenceError] Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 [-]
            [latest-22337]2022-12-09T14:29:42.143Z <EzloController:CRIT> ReferenceError: Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 [-]
            ReferenceError: Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24
                at Group.setAttribute (/opt/reactor/server/lib/Entity.js:460:19)
                at Group.setAttributes (/opt/reactor/server/lib/Entity.js:511:39)
                at Group._syncAttribute (/opt/reactor/server/lib/entities/Group.js:110:31)
                at Group.addMember (/opt/reactor/server/lib/entities/Group.js:118:227)
                at /opt/reactor/server/lib/EzloController.js:1612:61
                at Array.forEach (<anonymous>)
                at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226)
                at /opt/reactor/server/lib/EzloController.js:1413:48
                at processTicksAndRejections (node:internal/process/task_queues:96:5)
            [latest-22337]2022-12-09T14:29:42.146Z <EzloController:ERR> EzloController#ezlo error creating entity SecuritySensor#ezlo>device_618063af12a3b712364c7dc8: [ReferenceError] Capability sys_group not extended (ezlo>room_5f451f8012a3b72072c17b25 [-]
            [latest-22337]2022-12-09T14:29:42.146Z <EzloController:CRIT> ReferenceError: Capability sys_group not extended (ezlo>room_5f451f8012a3b72072c17b25 [-]
            ReferenceError: Capability sys_group not extended (ezlo>room_5f451f8012a3b72072c17b25
                at Group.setAttribute (/opt/reactor/server/lib/Entity.js:460:19)
                at Group.setAttributes (/opt/reactor/server/lib/Entity.js:511:39)
                at Group._syncAttribute (/opt/reactor/server/lib/entities/Group.js:110:31)
                at Group.addMember (/opt/reactor/server/lib/entities/Group.js:118:227)
                at /opt/reactor/server/lib/EzloController.js:1612:61
                at Array.forEach (<anonymous>)
                at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226)
                at /opt/reactor/server/lib/EzloController.js:1413:48
                at processTicksAndRejections (node:internal/process/task_queues:96:5)
            [latest-22337]2022-12-09T14:29:42.148Z <EzloController:ERR> EzloController#ezlo error creating entity ValueSensor#ezlo>device_618063af12a3b712364c7dcf: [ReferenceError] Capability sys_group not extended (ezlo>room_5f451f8012a3b72072c17b25 [-]
            [latest-22337]2022-12-09T14:29:42.149Z <EzloController:CRIT> ReferenceError: Capability sys_group not extended (ezlo>room_5f451f8012a3b72072c17b25 [-]
            ReferenceError: Capability sys_group not extended (ezlo>room_5f451f8012a3b72072c17b25
                at Group.setAttribute (/opt/reactor/server/lib/Entity.js:460:19)
                at Group.setAttributes (/opt/reactor/server/lib/Entity.js:511:39)
                at Group._syncAttribute (/opt/reactor/server/lib/entities/Group.js:110:31)
                at Group.addMember (/opt/reactor/server/lib/entities/Group.js:118:227)
                at /opt/reactor/server/lib/EzloController.js:1612:61
                at Array.forEach (<anonymous>)
                at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226)
                at /opt/reactor/server/lib/EzloController.js:1413:48
                at processTicksAndRejections (node:internal/process/task_queues:96:5)
            [latest-22337]2022-12-09T14:29:42.150Z <EzloController:ERR> EzloController#ezlo error creating entity ValueSensor#ezlo>device_618063af12a3b712364c7dd1: [ReferenceError] Capability sys_group not extended (ezlo>room_5f451f8012a3b72072c17b25 [-]
            [latest-22337]2022-12-09T14:29:42.150Z <EzloController:CRIT> ReferenceError: Capability sys_group not extended (ezlo>room_5f451f8012a3b72072c17b25 [-]
            ReferenceError: Capability sys_group not extended (ezlo>room_5f451f8012a3b72072c17b25
                at Group.setAttribute (/opt/reactor/server/lib/Entity.js:460:19)
                at Group.setAttributes (/opt/reactor/server/lib/Entity.js:511:39)
                at Group._syncAttribute (/opt/reactor/server/lib/entities/Group.js:110:31)
                at Group.addMember (/opt/reactor/server/lib/entities/Group.js:118:227)
                at /opt/reactor/server/lib/EzloController.js:1612:61
                at Array.forEach (<anonymous>)
                at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226)
                at /opt/reactor/server/lib/EzloController.js:1413:48
                at processTicksAndRejections (node:internal/process/task_queues:96:5)
            [latest-22337]2022-12-09T14:29:42.153Z <EzloController:ERR> EzloController#ezlo error creating entity ValueSensor#ezlo>device_618063af12a3b712364c7dd3: [ReferenceError] Capability sys_group not extended (ezlo>room_5f451f8012a3b72072c17b25 [-]
            [latest-22337]2022-12-09T14:29:42.154Z <EzloController:CRIT> ReferenceError: Capability sys_group not extended (ezlo>room_5f451f8012a3b72072c17b25 [-]
            ReferenceError: Capability sys_group not extended (ezlo>room_5f451f8012a3b72072c17b25
                at Group.setAttribute (/opt/reactor/server/lib/Entity.js:460:19)
                at Group.setAttributes (/opt/reactor/server/lib/Entity.js:511:39)
                at Group._syncAttribute (/opt/reactor/server/lib/entities/Group.js:110:31)
                at Group.addMember (/opt/reactor/server/lib/entities/Group.js:118:227)
                at /opt/reactor/server/lib/EzloController.js:1612:61
                at Array.forEach (<anonymous>)
                at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226)
                at /opt/reactor/server/lib/EzloController.js:1413:48
                at processTicksAndRejections (node:internal/process/task_queues:96:5)
            [latest-22337]2022-12-09T14:29:42.155Z <EzloController:ERR> EzloController#ezlo error creating entity Light#ezlo>device_6182b52012a3b7121fd6594b: [ReferenceError] Capability sys_group not extended (ezlo>room_5fed146312a3b716fad9f58d [-]
            [latest-22337]2022-12-09T14:29:42.155Z <EzloController:CRIT> ReferenceError: Capability sys_group not extended (ezlo>room_5fed146312a3b716fad9f58d [-]
            ReferenceError: Capability sys_group not extended (ezlo>room_5fed146312a3b716fad9f58d
                at Group.setAttribute (/opt/reactor/server/lib/Entity.js:460:19)
                at Group.setAttributes (/opt/reactor/server/lib/Entity.js:511:39)
                at Group._syncAttribute (/opt/reactor/server/lib/entities/Group.js:110:31)
                at Group.addMember (/opt/reactor/server/lib/entities/Group.js:118:227)
                at /opt/reactor/server/lib/EzloController.js:1612:61
                at Array.forEach (<anonymous>)
                at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226)
                at /opt/reactor/server/lib/EzloController.js:1413:48
                at processTicksAndRejections (node:internal/process/task_queues:96:5)
            [latest-22337]2022-12-09T14:29:42.157Z <EzloController:ERR> EzloController#ezlo error creating entity Switch#ezlo>device_618ff90912a3b7122edeaccd: [ReferenceError] Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 [-]
            [latest-22337]2022-12-09T14:29:42.157Z <EzloController:CRIT> ReferenceError: Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24 [-]
            ReferenceError: Capability sys_group not extended (ezlo>room_5f451f7512a3b72072c17b24
                at Group.setAttribute (/opt/reactor/server/lib/Entity.js:460:19)
                at Group.setAttributes (/opt/reactor/server/lib/Entity.js:511:39)
                at Group._syncAttribute (/opt/reactor/server/lib/entities/Group.js:110:31)
                at Group.addMember (/opt/reactor/server/lib/entities/Group.js:118:227)
                at /opt/reactor/server/lib/EzloController.js:1612:61
                at Array.forEach (<anonymous>)
                at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226)
                at /opt/reactor/server/lib/EzloController.js:1413:48
                at processTicksAndRejections (node:internal/process/task_queues:96:5)
            [latest-22337]2022-12-09T14:29:42.158Z <EzloController:ERR> EzloController#ezlo error creating entity Switch#ezlo>device_61901ff112a3b71209e73282: [ReferenceError] Capability sys_group not extended (ezlo>room_6190206412a3b71209e7328a [-]
            [latest-22337]2022-12-09T14:29:42.159Z <EzloController:CRIT> ReferenceError: Capability sys_group not extended (ezlo>room_6190206412a3b71209e7328a [-]
            ReferenceError: Capability sys_group not extended (ezlo>room_6190206412a3b71209e7328a
                at Group.setAttribute (/opt/reactor/server/lib/Entity.js:460:19)
                at Group.setAttributes (/opt/reactor/server/lib/Entity.js:511:39)
                at Group._syncAttribute (/opt/reactor/server/lib/entities/Group.js:110:31)
                at Group.addMember (/opt/reactor/server/lib/entities/Group.js:118:227)
                at /opt/reactor/server/lib/EzloController.js:1612:61
                at Array.forEach (<anonymous>)
                at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226)
                at /opt/reactor/server/lib/EzloController.js:1413:48
                at processTicksAndRejections (node:internal/process/task_queues:96:5)
            [latest-22337]2022-12-09T14:29:42.160Z <EzloController:ERR> EzloController#ezlo error creating entity Switch#ezlo>device_6190203012a3b71209e73286: [ReferenceError] Capability sys_group not extended (ezlo>room_6190206412a3b71209e7328a [-]
            [latest-22337]2022-12-09T14:29:42.160Z <EzloController:CRIT> ReferenceError: Capability sys_group not extended (ezlo>room_6190206412a3b71209e7328a [-]
            ReferenceError: Capability sys_group not extended (ezlo>room_6190206412a3b71209e7328a
                at Group.setAttribute (/opt/reactor/server/lib/Entity.js:460:19)
                at Group.setAttributes (/opt/reactor/server/lib/Entity.js:511:39)
                at Group._syncAttribute (/opt/reactor/server/lib/entities/Group.js:110:31)
                at Group.addMember (/opt/reactor/server/lib/entities/Group.js:118:227)
                at /opt/reactor/server/lib/EzloController.js:1612:61
                at Array.forEach (<anonymous>)
                at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226)
                at /opt/reactor/server/lib/EzloController.js:1413:48
                at processTicksAndRejections (node:internal/process/task_queues:96:5)
            [latest-22337]2022-12-09T14:29:42.161Z <EzloController:ERR> [TypeError] Cannot read properties of undefined (reading 'switch') [-] failed to process devices: [undefined2]
            [latest-22337]2022-12-09T14:29:42.161Z <EzloController:CRIT> TypeError: Cannot read properties of undefined (reading 'switch') [-]
            TypeError: Cannot read properties of undefined (reading 'switch')
                at EzloController._match_criterion (/opt/reactor/server/lib/EzloController.js:1119:84)
                at EzloController._map_device (/opt/reactor/server/lib/EzloController.js:1171:48)
                at /opt/reactor/server/lib/EzloController.js:1592:58
                at Array.forEach (<anonymous>)
                at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226)
                at /opt/reactor/server/lib/EzloController.js:1413:48
                at processTicksAndRejections (node:internal/process/task_queues:96:5)
            [latest-22337]2022-12-09T14:29:42.162Z <EzloController:ERR> EzloController#ezlo failed to complete inventory: [TypeError] Cannot read properties of undefined (reading 'switch') [-]
            [latest-22337]2022-12-09T14:29:42.162Z <EzloController:CRIT> TypeError: Cannot read properties of undefined (reading 'switch') [-]
            TypeError: Cannot read properties of undefined (reading 'switch')
                at EzloController._match_criterion (/opt/reactor/server/lib/EzloController.js:1119:84)
                at EzloController._map_device (/opt/reactor/server/lib/EzloController.js:1171:48)
                at /opt/reactor/server/lib/EzloController.js:1592:58
                at Array.forEach (<anonymous>)
                at EzloController._process_hub_devices (/opt/reactor/server/lib/EzloController.js:1576:226)
                at /opt/reactor/server/lib/EzloController.js:1413:48
                at processTicksAndRejections (node:internal/process/task_queues:96:5)
            [latest-22337]2022-12-09T14:29:42.172Z <EzloController:NOTICE> EzloController#ezlo connection closed: 1002 
            [latest-22337]2022-12-09T14:29:42.173Z <EzloController:INFO> EzloController#ezlo will retry in 5000ms; this was attempt 1
            
            1 Reply Last reply
            0
            • I Offline
              I Offline
              ibrewster
              wrote on last edited by
              #6

              So perhaps the network timeout errors were some sort of temporary ban on my IP due to repeated logins? Just a thought, may not make any sense.

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

                OK. Your post is, unfortunately, short of the posting guidelines, so please review those. I'd like to know what platform you are running on, and how you install/run (docker, bare-metal, etc.) (and that on every new post you create, please -- see the guidelines in this category).

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

                1 Reply Last reply
                0
                • I Offline
                  I Offline
                  ibrewster
                  wrote on last edited by
                  #8

                  Reactor version: latest-22337-1a0a685f
                  OS: Ubuntu 22.04.1 LTS
                  Reactor installed vis Docker (docker-compose to be exact), version 20.10.12, build 20.10.12-0ubuntu4
                  Hub involved: Ezlo Plus Firmware 2.0.33.2116.2 Advanced Scenes 1.56

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

                    Intel processor?

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

                    1 Reply Last reply
                    0
                    • I Offline
                      I Offline
                      ibrewster
                      wrote on last edited by
                      #10

                      AMD EPYC 7262

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

                        OK. If you update your docker image and container, you should get version 22343. You apparently have an Ezlo device that is mentioning in its inventory an "item" (data element), but the item doesn't exist (it looks like an inconsistency in device data from Ezlos API). This version should complete inventory (unless there are other data consistency problems we haven't seen yet). There will continue to be warnings for setting undefined on an attribute, and possibly device match failing. Don't worry about those. I will be unavailable the rest of the day. I will contact you later to get a data collection from you so I can analyze their API responses in more detail and see if there's anything more I need to do about it.

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

                        I 1 Reply Last reply
                        0
                        • toggledbitsT toggledbits

                          OK. If you update your docker image and container, you should get version 22343. You apparently have an Ezlo device that is mentioning in its inventory an "item" (data element), but the item doesn't exist (it looks like an inconsistency in device data from Ezlos API). This version should complete inventory (unless there are other data consistency problems we haven't seen yet). There will continue to be warnings for setting undefined on an attribute, and possibly device match failing. Don't worry about those. I will be unavailable the rest of the day. I will contact you later to get a data collection from you so I can analyze their API responses in more detail and see if there's anything more I need to do about it.

                          I Offline
                          I Offline
                          ibrewster
                          wrote on last edited by ibrewster
                          #12

                          Reactor version: latest-22343-ef2b8f75
                          OS: Ubuntu 22.04.1 LTS, AMD EPYC 7262
                          Reactor installed vis Docker (docker-compose to be exact), version 20.10.12, build 20.10.12-0ubuntu4
                          Hub involved: Ezlo Plus Firmware 2.0.33.2116.2 Advanced Scenes 1.56

                          Yes, much better - things seem to be working now. I'd attach a log (as you mentioned there were warnings about setting undefined, among other things), but apparently I can't do that yet, so I'll stand by for directions on the data collection.

                          Thanks for your help.

                          1 Reply Last reply
                          1
                          • toggledbitsT toggledbits locked this topic on
                          Reply
                          • Reply as topic
                          Log in to reply
                          • Oldest to Newest
                          • Newest to Oldest
                          • Most Votes


                          Recent Topics

                          • Copying a global reaction
                            toggledbitsT
                            toggledbits
                            0
                            3
                            75

                          • [HowTo] Using HABridge with Reactor
                            CatmanV2C
                            CatmanV2
                            0
                            9
                            370

                          • [Reactor] Bug when sending MQTT boolean payloads
                            toggledbitsT
                            toggledbits
                            0
                            4
                            122

                          • Genuinely impressed with Zigbee and HA / Reactor
                            therealdbT
                            therealdb
                            1
                            8
                            281

                          • Difficulty defining repeating annual period
                            G
                            gwp1
                            0
                            5
                            81

                          • Need help with sequence
                            therealdbT
                            therealdb
                            0
                            3
                            53

                          • Possible feature request?
                            therealdbT
                            therealdb
                            0
                            5
                            160

                          • Logic Assistance: Exterior Lights on when Illuminance Below Threshold
                            CatmanV2C
                            CatmanV2
                            0
                            11
                            325

                          • Time series documentation
                            tunnusT
                            tunnus
                            0
                            11
                            385

                          • MQTT templates for ZIgbee scene controller, or a better way?
                            CatmanV2C
                            CatmanV2
                            0
                            3
                            154

                          • Reset a delay
                            CatmanV2C
                            CatmanV2
                            0
                            8
                            213
                          Powered by NodeBB | Contributors
                          Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                          • Login

                          • Don't have an account? Register

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