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
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
Afternoon, all.
In my continued attempts to virtualise my system, I'm in the last (I hope throes)
I don't fancy relying on Synology not to break more USB activities, so decided to set up ser2net on a Raspberry pi and plug in a spare Z-wave.me stick
So on the Raspberry pi: ser2net. yaml
catman@Zwave:/etc $ cat ser2net.yaml %YAML 1.1 --- # This is a ser2net configuration file, tailored to be rather # simple. # # Find detailed documentation in ser2net.yaml(5) # A fully featured configuration file is in # /usr/share/doc/ser2net/examples/ser2net.yaml.gz # # If you find your configuration more useful than this very simple # one, please submit it as a bugreport define: &banner \r\nser2net port \p device \d [\B] (Debian GNU/Linux)\r\n\r\n connection: &zwave0 # Bind to TCP port accepter: tcp,4000 enable: on options: kickolduser: true # Ensure mDNS is disabled mdns: false connector: serialdev, /dev/ttyACM0,115200N81,nobreak,localAnd if I telnet to it from anywhere:
catman@ChrisMBP15-2018 ~ % telnet 192.168.70.128 4000 Trying 192.168.70.128... Connected to 192.168.70.128. Escape character is '^]'.Which makes me think that ser2net is doing its thing.
Now in my virtualised Z-wave server I have this:
Screenshot 2025-04-10 at 17.36.52.png
(I've tried with a colon and a space between the ip and the port)
The result:
An unexpected error occurred during loading data. Try to reload the page. Please check 1.) if the controller is plugged in correctly, 2.) that in the app 'Z-Wave Network Access' the right port is entered (UZB: '/dev/ttyACM0', RaZberry shield: '/dev/ttyAMA0', UZB-Windows: '\\.\COM3', Z-Stick: '/dev/ttyUSB0', embedded boxes: '/dev/ttyS0' or '/dev/ttyS1') 3.) the app is aktiv. If not you could activate it under Menu > Apps > Active or add a new one under Menu > Apps > Local. The Setting 'Expert View' needs to be active under Menu > My Settings.Any pointers as to what I'm doing wrong?
TIA!
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 installed MSR on a RP5 bare metal and then copied the config and store files. Everything seems to be on the RP5 but I am missing all global expression and I don't see the controller time.
Screenshot 2025-04-06 201446.png
My browser is Microsoft Edge Version 135.0.3179.54 (Official build) (64-bit)
I have probably done something stupid or missed a step but I am stuck.
Thanks for any help.
Hi,
It seems that the widget deletion does not work. I tried to drag the widget to the left (as explained in here https://smarthome.community/topic/1071/deleting-widgets?_=1744037333660)
but it does not delete it. Anyone else experiencing the same problem?
Also the landing page after login is empty and seems be have some JS issues on the dev console:
Screenshot from 2025-04-07 18-06-19.png
fd7f0424-debb-49d3-86d8-9a3b09ad3868-image.png
Using dockerized version of Reactor (Multi-hub) latest-25082-3c348de6 on Chromium 135.0.7049.52 (Official Build) snap (64-bit)
br,
mgvra
Good day all,
I have an notification set up for my washing machine to let me know when it's complete. I have a templete sensor set up in HAAS to let me know if it's Washing, in Standby, or off, based upon the power consumption (Shelly 1PM on outlets)
The MSR code is relatively simple. I have a built in false positive attribute for if MSR gets rebooted, because I would suddenly get tons of notifications when I upgraded MSR.
6774565a-06cc-443f-99c1-e71301b33d83-image.png
What I'm trying to introduce, is a way to verify that I just didn't bump the knob on the washing machine when transferring loads from the washer to the dryer, which turns on the display and brings the power above the Standby threshold.
The power goes up to 3.7W for about 4 minutes if the selector knob is bumped/turned.
What would the best way to do this be? I have most of my MSR code set up for a couple of years now, and my coding logic is struggling a bit.
I think I need a power threshold to be substained for a minimum time period (say 2 or 3 minutes, above 10W), before the other triggers can act. What would the best way to do that be?
Running: latest-25082-3c348de6
Fedora 41 Server
HAAS:
Core
2025.3.4
Supervisor
2025.03.4
Operating System
15.1
Frontend
20250306.0
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.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: currentColorIn 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=33Is 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.
Good day all,
I have a reaction set up, that I use for both troubleshooting and changing home modes when one of my family members either arrive or are leaving. I use the companion app for HAAS on our iPhones, and HAAS reports if the person associated with the iPhone enters or leaves the geofenced area around my home. I'm sure most MSR and HAAS users are familiar with this.
I use this rule set mainly as a condition for other rules, however, as part of troubleshooting, a notification is sent through HAAS to the companion app when the rule becomes true. The problem is that I'm getting notifications now for both arriving and departing simultaneously.
96b3f7db-ba09-499e-a78c-86903b603857-image.png
36903cdd-a87f-473b-82ef-af9ef96d3c44-image.png It used to work fine as intended. I'm not sure exactly when it changed, but now I'm getting two notifications when either of these conditions change.
Any idea what could be happening?
Edit:
Running: latest-25082-3c348de6, bare-metal Linux
ZWaveJSControllerr [0.1.25082]
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem?
I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Similarly as for local expressions, global expressions evaluate and update fine when getEntity(...) structure is used. However, at least when certain functions are in use, expressions do not update.
Consider the following test case:
Screenshot 2025-03-13 at 16.29.42.png
Even though auto-evaluation is active, value does not change (it changes only if that expression is manually run). MSR restarts do not help.
Screenshot 2025-03-13 at 16.31.43.png
Note: Tested using build 25067 on Docker. I have also a PR open (but couldn't now get details or PR number as my Mantis account was somehow expired?).
Trying to understand what cause a local expresssion to be evaluated. I have read the manual but I am still not clear about it. Using the test rule below, I can see in the log that the rule is being automatically evaluated every time the temperature entity is changing. That is great...
What I am trying to understand is why the expression is not evaluated based on time as well since the "case" statement has time dependencies.
Any help would be appreciated
I have the following test rule:
eba6a3ea-ff61-4610-88c9-9b9864f11ff8-Screenshot 2025-01-21 095244.png
2d9c1ff5-7b73-4005-b324-9029c2709db9-Screenshot 2025-01-21 095302.png
Here is the expressioncode:
vFrom1 = "09:25:00", vFrom2 = "09:30:00", vFrom3 = "09:41:00", vTo = "10:55:00", # Get current time (format HH:MM:SS) vToDay = strftime("%H:%M:%S"), #Get current house temperature CurrentHouseTemp = getEntity( "hass>Thermostat2 " ).attributes.temperature_sensor.value, case when CurrentHouseTemp <= 19 and vToDay >= vFrom1 && vToDay <= vTo: "true1" # From1 when CurrentHouseTemp <= 20 and vToDay >= vFrom2 && vToDay <= vTo: "true2" # From2 when CurrentHouseTemp < 26 and vToDay >= vFrom3 && vToDay <= vTo: "true3" # From3 else "false" endI am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved.
The Runtime Error is different in the two browsers
Safari v18.3
Google Chrome 133.0.6943.142
TypeError: self.editor.isModified is not a function at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34) You may report this error, but do not screen shot it. Copy-paste the complete text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community.Steps to reproduce:
Click the pencil to edit a global reaction with a group.
Click the Exit button.
Runtime error appears.
or
Click Create Reaction
Click Add Action
Select Group
Add Condition such as Entity Attribute.
Add an Action.
Click Save
Click Exit
Runtime error appears.
I don’t know how long the error has been there as I haven’t edited the global reaction in a long time.
Reactor (Multi-hub) latest-25060-f32eaa46
Docker
Mac OS: 15.3.1
Thanks
I am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons.
I have not created a global expression for some times and just noticed this while doing some clean-up.
I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success.
Here's what the log shows.
[latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay [latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" }Reactor latest-25067-62e21a2d
Docker on Synology NAS
Hello all, after seeing Catman's posts about their disaster recovery and move to Docker I took that as a sign to migrate everything (aside from HA) to Docker. After a small learning curve I had Docker+Portainer up and running in a few days.
Instead of using named Volumes I opted to use Bind Mounts so I can easily edit conf files and any other file needed. I do understand the nuances that come with bind mounts, such as migration to a different host may require changing file structures, the possibility of someone editing the bind mount files and permissions but to me those aren't too big of a deal.
My question is what is the best way to keep a back up of these bind mounts? I currently have them stored in the /etc directory in another directory named on a per container basis. I was thinking to move it all to a /home/user/docker/ directory so that I can use a simple cp command to my mounted SMB share to backup all the container data files. Anyone else do it differently?
Side note: I finally got to flex the benefits of Docker with updating Reactor.. it was dead simple. I had no idea what I was missing out on lol!
Morning, experts. Hard on learning about the internet check script in MSR tools, I was wondering what suggestions anyone has about a local (i.e. non-internet dependent) notification method.
This was prompted by yesterday's fun and games with my ISP.
I've got the script Cronned and working properly but short of flashing a light on and off, I'm struggling to think of a way of alerting me (ideally to my phone)
I guess I could set up a Discord server at home, but that feels like overkill for a rare occasion. Any other suggestions?
TIA
C
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?