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.
I
ibrewster
@ibrewster
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI:
An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status
Last 11:20:37
My MQTT configuration (local_mqtt_devices.yaml) for the related entity is:
layzspa_message:
type: ValueSensor
capabilities: ["temperature_sensor", "value_sensor", "power_sensor"]
primary_attribute: power_sensor.value
events:
"layzspa/message":
"power_sensor.value":
json_payload: true
if_expr: '! isnull( payload?.PWR )'
expr: "float(payload.PWR)"
"value_sensor.air":
json_payload: true
if_expr: '! isnull( payload?.AIR )'
expr: "float(payload.AIR)"
"value_sensor.pump":
json_payload: true
if_expr: '! isnull( payload?.FLT )'
expr: "float(payload.FLT)"
"value_sensor.god":
json_payload: true
if_expr: '! isnull( payload?.GOD )'
expr: "float(payload.GOD)"
"value_sensor.lock":
json_payload: true
if_expr: '! isnull( payload?.LCK )'
expr: "float(payload.LCK)"
"value_sensor.unit":
json_payload: true
if_expr: '! isnull( payload?.UNT )'
expr: "float(payload.UNT)"
"value_sensor.error":
json_payload: true
if_expr: '! isnull( payload?.ERR )'
expr: "float(payload.ERR)"
"temperature_sensor.green":
json_payload: true
if_expr: '! isnull( payload?.GRN )'
expr: "float(payload.GRN)"
"temperature_sensor.red":
json_payload: true
if_expr: '! isnull( payload?.RED )'
expr: "float(payload.RED)"
"temperature_sensor.target":
json_payload: true
if_expr: '! isnull( payload?.TGT )'
expr: "float(payload.TGT)"
"temperature_sensor.value":
json_payload: true
if_expr: '! isnull( payload?.TMP )'
expr: "float(payload.TMP)"
"temperature_sensor.virtual":
json_payload: true
if_expr: '! isnull( payload?.VTM )'
expr: "round(float(payload.VTM), 1)"
"temperature_sensor.ambient":
json_payload: true
if_expr: '! isnull( payload?.AMB )'
expr: "float(payload.AMB)"
"layzspa/Status":
"value_sensor.status":
if_expr: '! isnull( payload )'
expr: "payload"
"layzspa/button":
"value_sensor.button":
if_expr: '! isnull( payload )'
expr: "payload"
and in reactor.yaml I have:
"layzspa_states":
name: "Lay-Z-Spa States"
friendly_name: 'Lay-Z-Spa States'
include: layzspa_message
I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Hi Smart Home Community.
I have used a Sonos inline WiFi switch to make one of my light fittings smart, but it requires a hard reset for WiFi changes, plus it isn't zigbee compatible, which means I can't use the Hue app to control it with the rest of the lights.
To that end I bought a Samotech SM308-S as it is recommended as the better than the Sonos equivalent.
I am however not exactly sure how to wire it in.
The manual is available here
Can anyone help me by clarifying which ports I need to use, and whether I should be using the live or switched live line for live etc.
I will be keeping using standard switches for a while, although hope to upgrade to tap dials once I have all the fittings upgraded.
Thanks
Good day all,
I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing.
I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container.
Has anyone done this? Any advice?
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.
Following on from my last thread, some progress has been made over the weekend.
With 18G of spanky RAM in my Synology DS224+. I've jumped into the murky world of virtualisation and already eliminated the need for two Raspberry Pi's from my system.
Home Assistant: In theory they provide an OVA file which is supported by the Synology. I couldn't get it to work, however, so grabbed a copy of the .img file they supply, renamed it .iso and imported it as a VM. Restored from my full back up and that all seems fantastic.
Minidnla Music server: Trivial. Grabbed a Debian .iso for Bookworm and copied that onto the NAS. Created a new machine which mirrored the specs of the Raspberry Pi, booted from the ISO then did an expert install. Once that was all stable with a basic core of stuff and networking, I've made a copy of that as a good base system. Then fired up minidnla on it, mounted my media and that's also woking. Not bad for a short weekend's work.
Still not sure about the main NUC though. I'm thinking of buying a new USB stick so I can mess around getting it working on the Synology before I do anything drastic.
Once that hurdle is sorted I'm torn between:
Using a brand new install of Bookworm, re-installing Z-way server, OpenLuup, AltUI, MSR and HA bridge, then restoring across or
Making an ISO of the current system, importing that and upgrading in place (which will be pretty risk free since I can snapshot everything before I make any changes.)
Decisions, decisions.
C
Hi guys,
Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular.
Maybe there are better ways to organize my rule sets.
I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
I have the following yaml configuration in local_mqtt_devices file
x_mqtt_device:
set_speed:
arguments:
speed:
type: str
topic: "command/%friendly_name%"
payload:
type: json
expr: '{ "fan": parameters.speed }'
While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Hi!
I get this message when I'm on the status tab:
System Configuration Check
The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds.
I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6.
HA versions are:
Core 2025.3.4
Supervisor 2025.03.4
Operating System 15.1
I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version.
Do anyone know what I can try?
Thanks in advance!
Let's Be Careful Out There (Hill Street reference...)
/Fanan
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB.
While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed.
So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response.
While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits
Thanks!
Hi ,
I'm on
-Reactor (Multi-hub) latest-25067-62e21a2d
-Docker on Synology NAS
-ZWaveJSUI 9.31.0.6c80945
Problem with ZwaveJSUI:
When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white.
I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui.
I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb".
After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color.
This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite.
x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33}
The "cold white" and "warm white" settings interfer with the rgb color settings.
Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white
are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white.
So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have
x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33}
14/03/2025, 16:43:57 - value updated
Arg 0:
└─commandClassName: Color Switch
└─commandClass: 51
└─property: targetColor
└─endpoint: 0
└─newValue
└──red: 235
└──green: 33
└──blue: 33
└─prevValue
└──red: 235
└──green: 33
└──blue: 33
└─propertyName: targetColor
14/03/2025, 16:43:57 - value updated
Arg 0:
└─commandClassName: Color Switch
└─commandClass: 51
└─property: currentColor
└─endpoint: 0
└─newValue
└──warmWhite: 204
└──coldWhite: 0
└──red: 235
└──green: 33
└──blue: 33
└─prevValue
└──warmWhite: 204
└──coldWhite: 0
└──red: 235
└──green: 33
└──blue: 33
└─propertyName: currentColor
In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set.
x_zwave_values.Color_Switch_currentColor_0=204
x_zwave_values.Color_Switch_currentColor_1=0
x_zwave_values.Color_Switch_currentColor_2=235
x_zwave_values.Color_Switch_currentColor_3=33
x_zwave_values.Color_Switch_currentColor_4=33
Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this?
x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33}
Thanks in advance.
Posts
-
Run rule on dimmer change? -
Run rule on dimmer change?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
-
Run rule on dimmer change?@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!
-
Run rule on dimmer change?@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:
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.levelAnd a Set Reaction to set the LR Fan Light to the same level:
Entity Action -- LR Fan Light -- dimming.set -- ${{SwitchLevel}}- We start with the switch at 0 (off), and the rule is reset as expected
- 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. - 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.
-
Run rule on dimmer change?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...
-
Run rule on dimmer change?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)
-
Run rule on dimmer change?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)
-
EzloControler access credentials timeout?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.56Yes, 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.
-
EzloControler access credentials timeout?AMD EPYC 7262
-
EzloControler access credentials timeout?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 -
EzloControler access credentials timeout?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.
-
EzloControler access credentials timeout?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 -
EzloControler access credentials timeout?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"
-
EzloControler access credentials timeout?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 17So 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?