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

ibrewster

@ibrewster
[Reactor] Variables not updating correctly in latest-25201-2aa18550
therealdbT
Topic thumbnail image
Multi-System Reactor
Do you Matter?
akbooerA
Is anyone using the Matter protocol to connect devices?
General Discussion
Caution: zwave-js-ui docker 11.4.0 is broken
toggledbitsT
About 20 hours ago, the author of zwave-js-ui posted build 11.4.0 of that product, and it contains an error and won't start (at all) under docker. The author is aware and working on a fix. In the meanwhile, stick with 11.3.1 or earlier. Ref: Issue 4401
Software
Shelly Wall Display XL
therealdbT
I don't know if you guys are into dashboards, but I am. For a second home I tried the Shelly Wall Display 2, and while not so big, it worked well over the summer. Since we're remodeling our house, I just swapped my old Fire Tablet (with its own problems) with two new Shelly Wall Display XL. I just removed the standard firmware, and I added mine (https://github.com/dbochicchio/ShellyElevate), forked from https://github.com/RapierXbox/ShellyElevate I just managed to support buttons (this thing has 4 of them) and it's all auto-discovered by Home Assistant and accessible via Reactor. I also have a new build in the works with support for buttons inside HA. I added a bonus Javascript interface sending events (screen/screensaver status, buttons, motion) to automatically drive the dashboard (all doing in HTML+Javascript and monitoring Reactor's variable). This specifical thing excluded, go get one of them, the device has a decent CPU for HA dashboards and blends wonderfully in the decor.
Hardware
Handling Dead Entities and Renamed Entities
PablaP
Hello all.. been a minute! I recently rebuilt my Z wave network and migrated to a new z wave stick. In order to prevent any downtime I kept my original z wave network up and ran a docker version of Z Wave JS UI with my new controller. This way I could add device by device without having any devices down. I finally moved all the devices over to my new stick today. The final step was to migrate everything from my Docker instance of Z Wave JS UI to the HA add-on of Z Wave JS UI. However during this migration some of the names didn't populate correctly which I later managed to import back into Z Wave JS UI. The issue was in Reactor it is stuck on the default names and the entities are not updating. I removed the controller from Reactor, restarted, hard refreshed, and added the controller back however the new entity names have not updated. Also it seems like the old entities from my previous instance of Z Wave JS UI are lingering and not being marked as dead (I believe a certain amount of time needs to lapse before they're marked as dead in Reactor). My goal is to basically purge all the entities for the 'ZWaveJS' controller in Reactor so it can pull all the updated entity names and only the entities that exist in Z Wave JS UI. I cannot find a quick way to do this, I know entities can be deleted one by one, but with over 100 entities this would take long I am guessing that if I added the controller with a new name in in the Reactor config it would pull the updated entities and names but I think that would break my rules since the entity IDs would change (I made sure to name all the entities the exact same as they were previously to prevent this issue).
Multi-System Reactor
Strange behavior for MQTT templates using payload and attributes
therealdbT
Topic thumbnail image
Multi-System Reactor
[MSR] reactor-mqtt-contrib package for additional MQTT templates
therealdbT
I'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only). Anyway, here's my reactor-mqtt-contrib package: https://github.com/dbochicchio/reactor-mqtt-contrib Simply download yaml files (everything or just the ones you need) and you're good to go. I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them. The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression. Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests
Multi-System Reactor
HA 2025.9.4 Supported Yet?
CatmanV2C
Tangentially did I miss 2025.9.4 getting blessed in MSR? I've been holding off Cheers C
Multi-System Reactor
The reaction stopped working (Google Nest max playing a video)
F
Topic thumbnail image
Multi-System Reactor
Rule Set UI bug - RESOLVED
3
Topic thumbnail image
Multi-System Reactor
[Reactor] Copy&Paste of Rules
therealdbT
I don't know if I'm the only one, but managing more than one Reactor installs, the need to have some sort of copy&paste for rules has grown on me. While I understand the technical challenges, I'm wondering if a "god mode" where I could copy the raw JSON rule and paste it into another rule could be an advanced, flag only feature that could benefit power users. I know I can copy the JSON file and proceed, but I must stop Reactor and when doing maintenance, it's more clicks to do. Just an idea
Multi-System Reactor
[Reactor] Help with screne controller cycling logic
therealdbT
I’ve added a couple of Shelly Wave i4 as scene controllers and I’m planning to add more, since I can just use standard buttons instead of battery-powered scene controllers, which also looks better aesthetically. That said, I’m struggling to figure out how to write a simple rule that cycles between states every time I press a button. Example: Light 1 ON → OFF, then Light 2 ON → OFF. The part I can’t get right is handling the case where Light 1 or Light 2 might already be ON independently of the rule. Maybe it’s just too much sun and relaxation clouding my brain, but any hint would be appreciated.
Multi-System Reactor
Stop the MSR by an external switch on Hubitat.
wmarcolinW
Use case: When performing home maintenance, such as air conditioning, I want all rules involving air conditioning to be disabled. To do this, to day, I have a virtual switch that I placed within all rules involving air conditioning, meaning that if I turn it off, none of them work. Then another situation: the water pump system and garden irrigation, another switch. In short, I had to create several virtual switches in Hubitat to disable rules in MSR. Unfortunately, however, I was unable to cover all scenarios, so I wondered if it would be possible for MSR to support a virtual MSR switch, which, when configured in the reactor settings, would function as a general on/off switch for MSR. If it is configured and turned off, the entire rules and actions in MSR stops working, except for the status change reading process, specifically for this switch, which, when turned on, would restart the MSR. Would it be possible to do something like this? Any recommendations from the experts?
Multi-System Reactor
Expose MSR entities
CatmanV2C
Probably a really dumb question. Currently I am using the owntracks_sensor for tracking phones being in region in MSR and it works great. Digging around with Home Assistant and toying with some dashboards, is there any way of exposing that sensor to HA trivially? I could set MSR to trip a virtual switch in OpenLuup which can then be exposed to HA (with all my other Vera devices) but that feels a bit in-elegant if I can do it directly. Any thoughts? Apologies if the ask is not clear/ TIA C
Multi-System Reactor
Comment in Globa Expressions
Tom_DT
I have several Global Expressions that are set by a rule so the definition area is blank. I'd like to add a comment in this area that explains what is setting the value. Commenting in this area breaks the remote setting. Any way to document what is setting the GE?
Multi-System Reactor
Little Bobby tables...
CatmanV2C
...is back.... https://arstechnica.com/google/2025/08/researchers-use-calendar-events-to-hack-gemini-control-smart-home-gadgets/?utm_source=facebook&utm_medium=social&utm_campaign=dhfacebook&utm_content=null&fbclid=IwY2xjawMBq-pleHRuA2FlbQIxMQABHlSqIalzbz1IxcJFzlw8GBE6nC3FwvxcHgR370nJhogU6JjqbmRxG-lysqgh_aem_lx9XboYFKw9tpHnedGQKUA C
General Discussion
Home Assistant Voice TTS is Easy
toggledbitsT
Topic thumbnail image
Home Assistant
Play Audio through Home Assistant Voice Unit
toggledbitsT
Topic thumbnail image
Home Assistant
Home Assistant Voice
CatmanV2C
Has anyone had a play with the local voice control for HA? I've got one on order because... https://www.home-assistant.io/voice-pe/ C
Home Assistant
Unofficial thread for compatibility
tunnusT
As there are statements about compatibility for home assistant versions in MSR new version announcements (e.g. "HassController: Bless Hass to 2025.7.3"), I thought it would be good idea to track other controllers as well. As an example, I can confirm that build "latest-25208-c53e8513" works with Hubitat Elevation C-8 platform version 2.4.2.134 using Maker API. Updates: (the latest versions first in the list) OK: build "latest-25264-2fbe9217" with Hubitat C-8 platform v. 2.4.3.123
Multi-System Reactor
About
Posts
14
Topics
2
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Run rule on dimmer change?
    I ibrewster

    Ok, now I'm really confused. As part of my attempt to update reactor, the docker container obviously got restarted - and now the rule is working as expected, with only the change condition. I have no idea why the change in behavior, but at least it is now working as you guys expected.

    Multi-System Reactor

  • Run rule on dimmer change?
    I ibrewster

    Reactor latest-23302-b7def56a; docker on Ubuntu 20.04; With Vera Plus and Ezlo Plus controllers

    Nope, the delay reset box is empty (nor have I tried to make any modifications in that section of the rule).

    Although now that you mention it, it does seem odd, since while the rule remains set, if I toggle the rule open in the Rule Set list, the condition is evaluating to false, which (I would think) should reset the rule...right?

    I have updated reactor recently, but let me try again in case 23302-b7def56a isn't the latest, and has a bug here...

    EDIT: Nope, doesn't appear there are any updates available

    Multi-System Reactor

  • Run rule on dimmer change?
    I ibrewster

    @tunnus said in Run rule on dimmer change?:

    If you only have a single trigger with changes -operator, the rule is immediately reset after the change

    That is not the behavior I am seeing. Sorry! 🤷

    Multi-System Reactor

  • Run rule on dimmer change?
    I ibrewster

    @toggledbits said in Run rule on dimmer change?:

    Please show your work (post screen shots of your rules).

    As I mentioned, I tried to do so, but the forum gives me errors. Specifically, it will show the image as uploading, get to 100%, pause, drop back to 60% (or so), give me a message stating "Looks like your connection to SmartHome Community was lost, please wait while we try to reconnect", the progress goes up to 100% again, and then I get an error stating "Something went wrong while parsing server response", and the image is not uploaded, leaving me with something like this:

    ![Screenshot 2023-12-01 at 8.55.28 AM.png]([[error:parse-error]])
    

    So as far as I can tell, no screen shot posting is possible.

    Perhaps walking through the steps of what happens will help?
    The rule is set up with a single Trigger:

    Entity Attribue -- Inovelli 2-in-1 (the switch) -- dimming.level -- changes -- from <blank> to <blank>
    

    A local expression is set up with the following code that gets the current dimming.level value:

    SwitchLevel = getEntity( "ezlo>device_65655fb712a3b714bdbcb935" ).attributes.dimming.level
    

    And a Set Reaction to set the LR Fan Light to the same level:

    Entity Action -- LR Fan Light -- dimming.set -- ${{SwitchLevel}}
    
    1. We start with the switch at 0 (off), and the rule is reset as expected
    2. We then set the switch to some other value (say, 50% or .5)
      2a. The rule is now set, and the Set Reaction runs as expected.
      2b. The rule remains set at this point - only going back to a dimming level of 0 will reset it.
    3. We then set the switch to another value, say 75% or .75
      3a. Since the rule is already in a set state, the Set Reaction does not run again, meaning the LR Fan light does not change dimming level

    Adding in the rule of the LR Fan Light level <> SwitchLevel allows the rule to drop back to a reset state after setting the LR Fan Light Level, thereby allowing it to run again the next time the switch level changes.

    Multi-System Reactor

  • Run rule on dimmer change?
    I ibrewster

    Ahhhh, I think I finally got it! If I add a second condition of device.dimming.level <> switch.dimming.level, then the rule is set whenever the switch changes, and quickly reset once the device is set to the same level, allowing the next change in switch level to properly trigger the rule again.

    Only took me two days and a forum post to figure that one out... 😆

    Multi-System Reactor

  • Run rule on dimmer change?
    I ibrewster

    That is correct, yes - and it works when going from 0-->any. After that, however, the condition evaluates to true, the rule is set, and so further changes do not trigger it again, as per the documentation (once true it remains true and the rule is not run again until it evaluates to false, i.e. 0)

    Multi-System Reactor

  • Run rule on dimmer change?
    I ibrewster

    Reactor latest-23302-b7def56a; docker on Ubuntu 20.04; With Vera Plus and Ezlo Plus controllers

    I'm trying to tie the dimmer level of a dimmer switch to the dimmer level of a dimmable device (fan canopy light controller). In the triggers section of the rule I can select "dimming.level changes" as the condition, and I can get said dimming level in an expression that I then use to set the dimming.set attribute of the dimming device in the Set Reaction section, but this only works when going from 0--><some value>. When going from <some value> --> <some other value> or <some value>-->0, this does not work, because the rule is already set (it went true with the first change, and hasn't gone false yet - this is expected behavior as per the documentation)

    I can fix the <some value>-->0 issue by setting the Reset Reaction, but how can I get the rule to run - and set the entity dimming level - every time the switch value changes?

    (I tired to upload a screen shot of what I have, but I just kept getting errors)

    Multi-System Reactor

  • EzloControler access credentials timeout?
    I ibrewster

    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.

    Multi-System Reactor

  • EzloControler access credentials timeout?
    I ibrewster

    AMD EPYC 7262

    Multi-System Reactor

  • EzloControler access credentials timeout?
    I ibrewster

    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

    Multi-System Reactor

  • EzloControler access credentials timeout?
    I ibrewster

    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.

    Multi-System Reactor

  • EzloControler access credentials timeout?
    I ibrewster

    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
    
    Multi-System Reactor

  • EzloControler access credentials timeout?
    I ibrewster

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

    Multi-System Reactor

  • EzloControler access credentials timeout?
    I ibrewster

    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?

    Multi-System Reactor
  • Login

  • Don't have an account? Register

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