I'm trying to allow anonymous access from a local network to /api/v1/log, but the problem now with the reverse proxy configuration is that this access is open via proxy to the internet. At least I wasn't able to configure ACL so that only an access from a local network would be permitted.
reactor.yaml:
baseurl: "http://192.168.1.12:8111"
proxy_baseurl: "https://external.com:30000"
trusted_proxy: "192.168.1.12"
Local traffic would originate from 192.168.1.0/24 network. Synology is acting as a reverse proxy and hosting MSR as a docker container (which has its own network and IP 172.18.0.5). MSR build is latest-26298-fbb75fb8
users.yaml:
- url: "/api/v1/log"
method: "GET"
source_ip: 172.18.0.0/24
allow: true
Using the above ACL works, but it enables access via proxy also. If I use source_ip: 192.168.1.0/24, then it doesn't work either locally or remotely. So I'm kinda lost what should I use as source_ip in this case?
I've seen many of you using Dynamic Group Controller. I'm using it myself for monitoring device battery levels. I've read and re-read the Dynamic Group Controller docs and still cannot come to an answer for my question so let me paint my scenario:
I've migrated from EchoSpeaks in Hubitat ('cause borked and seemingly unmaintained) to Alexa Devices in Home Assistant ('cause not borked in 2026.11.0) to be able to send TTS to my Echo devices.
In EchoSpeaks I could create groups. Sweet.
In Alexa Devices I don't seem to be able to do so. As such, my thought was "wait - isn't there a way in MSR?"
Is this an effective scenario that Dynamic Group Controller can be used for?
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'm trying to use MSR via reserve proxy in Synology DSM, but MSR page does not load
https://<public ip>:30000/reactor/en-US/
At the same time logging page loads normally
https://<public ip>:30000/api/v1/log
I thought maybe authentication was messing it up, but there was no deny entries in the log, and also disabling authentication did not make any difference. For this use case VPN is not an option (that works, but as said not an option for this particular use case).
Any ideas what could cause this? MSR build latest-26242-28d69aa8, Chrome browser
Nothing more to add. I see we have hvac_blower, but, anyway, maybe a native fan on the same assumptions of the fan from HASS could be reasonable.
I have a couple of them. ie, this is from ESPHome via HASS.
x_hass.domain="fan"
x_hass.entity_id="fan.kitchen_seashell_hood_ventilation_fan"
x_hass.floor_id=null
x_hass.services=["fan","esphome"]
x_hass.source="esphome"
x_hass.state="off"
x_hass_attr.friendly_name="Seashell Hood Ventilation Fan"
x_hass_attr.percentage=50
x_hass_attr.percentage_step=25
x_hass_attr.preset_mode=""
x_hass_attr.preset_modes=[]
x_hass_attr.supported_features=49
Thanks.
Build: latest-26221-b25bb3e3, Docker on Synology.
Hi, I have a Rule whose Trigger/Constraints reference other Rules via Rule State ... is TRUE. At some point it stops firing.
Expanding the rule's condition tree in the UI shows every Trigger and Constraint condition green/TRUE — confirmed live by walking into the room and watching Motion go true in real time. Rule History shows no new SET, just old reset entries.
Tried, on the same rule, same evening: recreating the trigger conditions with fresh IDs, recreating the constraint conditions with fresh IDs (flat and wrapped in a new Group — wrapping in a Group produced one SET, but it didn't reproduce on repeat attempts with the same structure), and finally a full container restart with a verified-correct saved rule. Still no SET, even with a fresh live motion event right after the restart.
Separately, I found that this rule (and its 10 per-room clones) share identical internal condition/group IDs with each other — leftover from a batch clone done months ago, never regenerated. Not sure if that's related, since fixing the IDs didn't reliably fix the symptom either.
Has anyone seen a Rule State condition show TRUE in the UI without the Rule ever producing a SET, surviving a clean restart?
Thanks in advance
Hey @toggledbits I'm back to trying to optimize a couple of things based on dynamic group.
First of all, I think I found a typo in the doc:
primary_attribute: "binary_sensor.state"
primary_attribute_value: |
d = false;
each id in members: d = getEntity(id)?.attributes?.power_switch?.state or d,
d
I think the correct code snippet is d = false,
All that said, my use case for dynamic groups is to group 3 different climate devices, so I could easily command them at the same time. Commands are good, but sometimes I want to check if any of the devices are on, and that's easily done with a similar snippet as the one you have in the docs. But this is limited to the primary attribute, while I want to have any of the attributes in the group to be driven by a similar logic (while all are null in the group). ie, access hvac_control.mode and see if any of the unit is set to cool, or heat. Is that possible, without re-defining an expression in each of my rules? Thanks!
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
Edit: Solved in latest-26221.
Bare-metal latest-26193
I have this group:
"OKforLarm":
name: OK för Larm
select:
- include_controller: vera
- include_capability: door_sensor
filter_expression: entity.attributes.door_sensor.state
It contains the entities I expect but behaves a bit odd. When I open vera>device_10097 the entity attribute door_sensor.state changes to true but it won't show up as member in the group, when I also open vera>device_10095 they both shows as members and when I close vera>device_10095 it disappear from the group but when I close vera>device_10097 it lingers in the group until I restart Reactor.
Support for Ezlo Atom controllers?
-
OK. You need to set the shell environment variable NODE_PATH to the install directory where Reactor lives (the directory that contains Reactor's app.js file).
@toggledbits . Thanks. Did that. Sadly it still don't work. Got this instead:
PS D:\msr> node app.js basedir D:\msr confdir D:\msr\config datadir D:\msr\storage logsdir D:\msr\logs plugindir D:\msr\ext module.paths [ 'D:\\msr\\node_modules', 'D:\\node_modules' ] NODE_PATH D:\MSR Logging stream path spec may be using pre-21075 form; please remove ./logs/ from the path! 2021-07-30T13:10:38.707Z <app:null> Reactor latest-21203-9503e5d starting on v15.11.0 2021-07-30T13:10:38.708Z <app:INFO> Process ID 16096; platform win32/x64 Windows 10 Pro 2021-07-30T13:10:38.709Z <app:INFO> Basedir D:\msr; data in D:\msr\storage 2021-07-30T13:10:38.709Z <app:INFO> NODE_PATH D:\MSR; module paths [ "D:\\msr\\node_modules", "D:\\node_modules" ] 2021-07-30T13:10:38.751Z <Plugin:null> Module Plugin v21173 2021-07-30T13:10:38.757Z <default:INFO> Module Entity v21177 2021-07-30T13:10:38.760Z <Controller:null> Module Controller v21191 2021-07-30T13:10:38.761Z <default:null> Module Structure v21196 2021-07-30T13:10:38.766Z <default:null> Module Ruleset v21096 2021-07-30T13:10:38.766Z <default:null> Module Rulesets v21096 2021-07-30T13:10:38.781Z <default:null> Module Rule v21168 2021-07-30T13:10:38.786Z <default:null> Module Engine v21197 2021-07-30T13:10:38.787Z <default:null> Module httpapi v21200 2021-07-30T13:10:38.790Z <default:null> Module httpproxy v21054 2021-07-30T13:10:38.806Z <default:null> Module wsapi v21196 2021-07-30T13:10:38.810Z <app:NOTICE> Starting Structure... 2021-07-30T13:10:38.814Z <Structure:INFO> Structure#1 starting controller interface vera (VeraController) 2021-07-30T13:10:38.820Z <Structure:INFO> Structure#1 starting controller interface ezlo (EzloController) 2021-07-30T13:10:38.822Z <Structure:INFO> Structure#1 starting controller interface hass (HassController) 2021-07-30T13:10:38.823Z <Structure:INFO> Structure#1 starting controller interface reactor_system (SystemController) 2021-07-30T13:10:38.860Z <default:null> Module VeraController v21202 2021-07-30T13:10:38.924Z <default:null> Module HassController v21191 2021-07-30T13:10:38.926Z <default:null> Module SystemController v21102 2021-07-30T13:10:38.929Z <VeraController:NOTICE> VeraController#vera starting 2021-07-30T13:10:38.960Z <VeraController:INFO> VeraController#vera loaded mapping ver 21202 rev 1 format 1 notice 2021-07-30T13:10:38.970Z <Controller:CRIT> Controller: failed to load ezlo implementation file:///D:/msr/server/lib/EzloController.js: TypeError: Cannot read property 'getConfig' of undefined 2021-07-30T13:10:38.970Z <Controller:CRIT> TypeError: Cannot read property 'getConfig' of undefined TypeError: Cannot read property 'getConfig' of undefined at Function.getInstance (D:\MSR\server\lib\Configuration.js:128:89) at Object.<anonymous> (D:\MSR\server\lib\Logger.js:154:49) at Module._compile (node:internal/modules/cjs/loader:1092:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1121:10) at Module.load (node:internal/modules/cjs/loader:972:32) at Function.Module._load (node:internal/modules/cjs/loader:813:14) at Module.require (node:internal/modules/cjs/loader:996:19) at require (node:internal/modules/cjs/helpers:92:18) at Object.<anonymous> (D:\MSR\server\lib\Capabilities.js:71:99) at Module._compile (node:internal/modules/cjs/loader:1092:14) TypeError: Cannot read property 'getConfig' of undefined at Function.getInstance (D:\MSR\server\lib\Configuration.js:128:89) at Object.<anonymous> (D:\MSR\server\lib\Logger.js:154:49) at Module._compile (node:internal/modules/cjs/loader:1092:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1121:10) at Module.load (node:internal/modules/cjs/loader:972:32) at Function.Module._load (node:internal/modules/cjs/loader:813:14) at Module.require (node:internal/modules/cjs/loader:996:19) at require (node:internal/modules/cjs/helpers:92:18) at Object.<anonymous> (D:\MSR\server\lib\Capabilities.js:71:99) at Module._compile (node:internal/modules/cjs/loader:1092:14) -
Fix the case on your NODE_PATH value so it matches the actual case of every element of the directory path and give it a try.
-
Fix the case on your NODE_PATH value so it matches the actual case of every element of the directory path and give it a try.
@toggledbits
I've tried and tried - but I can't get it to work (getting the Ezlo Plus to work in MSR). I've several times tried every step. I use the Windows 10 bare metal install (reactor-latest-21221-4a447cb).
I have repeatedly used:npm install --loglevel error --no-save set NODE_PATH=D:\reactorAll cases are correct.
This is what I get:
2021-08-12T17:45:38.541Z <Controller:CRIT> Controller: failed to load ezlo implementation file:///D:/reactor/server/lib/EzloController.js: Error: Cannot find module 'server/lib/Configuration' Require stack: - D:\reactor\server\lib\EzloController.js 2021-08-12T17:45:38.542Z <Controller:CRIT> Error: Cannot find module 'server/lib/Configuration' Require stack: - D:\reactor\server\lib\EzloController.js Error: Cannot find module 'server/lib/Configuration' Require stack: - D:\reactor\server\lib\EzloController.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15) at Function.Module._load (node:internal/modules/cjs/loader:778:27) at Module.require (node:internal/modules/cjs/loader:1005:19) at require (node:internal/modules/cjs/helpers:94:18) at Object.<anonymous> (D:\reactor\server\lib\EzloController.js:506:144) at Module._compile (node:internal/modules/cjs/loader:1101:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10) at Module.load (node:internal/modules/cjs/loader:981:32) at Function.Module._load (node:internal/modules/cjs/loader:822:12) at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:201:29) Error: Cannot find module 'server/lib/Configuration' Require stack: - D:\reactor\server\lib\EzloController.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15) at Function.Module._load (node:internal/modules/cjs/loader:778:27) at Module.require (node:internal/modules/cjs/loader:1005:19) at require (node:internal/modules/cjs/helpers:94:18) at Object.<anonymous> (D:\reactor\server\lib\EzloController.js:506:144) at Module._compile (node:internal/modules/cjs/loader:1101:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10) at Module.load (node:internal/modules/cjs/loader:981:32) at Function.Module._load (node:internal/modules/cjs/loader:822:12) at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:201:29) { code: 'MODULE_NOT_FOUND', requireStack: [ 'D:\\reactor\\server\\lib\\EzloController.js' ] }I do have the files that's MSR is asking for (eg. D:\reactor\server\lib\EzloController.js). So it's so strange! Do you know what could be wrong?
Best regards,
/Fanan -
Working for me:
C:\Users\Patrick\Documents\MSR>set NODE_PATH=C:\Users\Patrick\Documents\MSR C:\Users\Patrick\Documents\MSR>node app.js basedir C:\Users\Patrick\Documents\MSR confdir C:\Users\Patrick\Documents\MSR\config datadir C:\Users\Patrick\Documents\MSR\storage logsdir C:\Users\Patrick\Documents\MSR\logs plugindir C:\Users\Patrick\Documents\MSR\ext module.paths [ 'C:\\Users\\Patrick\\Documents\\MSR\\node_modules', 'C:\\Users\\Patrick\\Documents\\node_modules', 'C:\\Users\\Patrick\\node_modules', 'C:\\Users\\node_modules', 'C:\\node_modules' ] NODE_PATH C:\Users\Patrick\Documents\MSR 2021-08-12T18:39:38.096Z <app:null> Reactor ###BUILDVERSION### starting on v14.15.5 2021-08-12T18:39:38.097Z <app:INFO> Process ID 26416; platform win32/x64 Windows 10 Pro 2021-08-12T18:39:38.099Z <app:INFO> Basedir C:\Users\Patrick\Documents\MSR; data in C:\Users\Patrick\Documents\MSR\storage 2021-08-12T18:39:38.099Z <app:INFO> NODE_PATH C:\Users\Patrick\Documents\MSR; module paths [ "C:\\Users\\Patrick\\Documents\\MSR\\node_modules", "C:\\Users\\Patrick\\Documents\\node_modules", "C:\\Users\\Patrick\\node_modules", "C:\\Users\\node_modules", "C:\\node_modules" ] 2021-08-12T18:39:38.100Z <app:INFO> process.env=[object Object] 2021-08-12T18:39:38.100Z <app:INFO> process.env.TEST=(undefined) 2021-08-12T18:39:38.145Z <Plugin:null> Module Plugin v21173 2021-08-12T18:39:38.152Z <default:INFO> Module Entity v21177 2021-08-12T18:39:38.155Z <Controller:null> Module Controller v21191 2021-08-12T18:39:38.156Z <default:null> Module Structure v21216 2021-08-12T18:39:38.162Z <default:null> Module Ruleset v21096 2021-08-12T18:39:38.162Z <default:null> Module Rulesets v21096 2021-08-12T18:39:38.181Z <default:null> Module Rule v21221 2021-08-12T18:39:38.185Z <default:null> Module Engine v21213 2021-08-12T18:39:38.186Z <default:null> Module httpapi v21215 2021-08-12T18:39:38.189Z <default:null> Module httpproxy v21054 2021-08-12T18:39:38.209Z <default:null> Module wsapi v21196 2021-08-12T18:39:38.212Z <app:NOTICE> Starting Structure... 2021-08-12T18:39:38.214Z <Structure:NOTICE> Structure#1 plugin ID influx disabled; skipping 2021-08-12T18:39:38.216Z <Structure:INFO> Structure#1 starting controller interface ezlo (EzloController) 2021-08-12T18:39:38.220Z <Structure:INFO> Structure#1 starting controller interface reactor_system (SystemController) 2021-08-12T18:39:38.249Z <default:null> Module EzloController v21218 2021-08-12T18:39:38.251Z <default:null> Module SystemController v21102 2021-08-12T18:39:38.254Z <EzloController:null> EzloController#ezlo created, config { "source": "wss://192.168.0.67:17000", "serial": "900xxxxx", "username": "xxxxx", "password": "xxxxx", "auto_rediscover": false } 2021-08-12T18:39:38.255Z <EzloController:null> EzloController#ezlo instance log level (null) (4) 2021-08-12T18:39:38.269Z <Controller:INFO> EzloController#ezlo device mapping data loaded; checking... 2021-08-12T18:39:38.272Z <Controller:INFO> EzloController#ezlo performing cloud auth to get local access token 2021-08-12T18:39:38.324Z <Controller:NOTICE> Controller SystemController#reactor_system is now online. 2021-08-12T18:39:38.395Z <app:INFO> Structure running; pausing for controllers' initial ready 2021-08-12T18:39:39.934Z <Controller:INFO> EzloController#ezlo cloud auth phase complete (local access token acquired) 2021-08-12T18:39:39.936Z <Controller:INFO> EzloController#ezlo opening local hub connection to "900xxxxx" at wss://192.168.0.67:17000 2021-08-12T18:39:39.938Z <Controller:NOTICE> EzloController#ezlo configured to ignore host ("900xxxxx") certificate 2021-08-12T18:39:39.940Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://192.168.0.67:17000 2021-08-12T18:39:40.038Z <Controller:NOTICE> EzloController#ezlo successful hub login; performing inventory 2021-08-12T18:39:40.227Z <Controller:INFO> EzloController#ezlo data load complete; 21 devices received, 26 entities registered; 66 items. 2021-08-12T18:39:40.227Z <Controller:INFO> EzloController#ezlo hub inventory complete/successful; 187ms 2021-08-12T18:39:40.229Z <Controller:NOTICE> Controller EzloController#ezlo is now online. 2021-08-12T18:39:40.231Z <app:NOTICE> Starting Reaction Engine... 2021-08-12T18:39:40.233Z <Engine:INFO> Reaction Engine starting 2021-08-12T18:39:40.234Z <Engine:INFO> Checking rule sets... 2021-08-12T18:39:40.237Z <Engine:INFO> Checking rules... 2021-08-12T18:39:40.237Z <Engine:INFO> Data check complete; no corrections. 2021-08-12T18:39:40.240Z <Engine:NOTICE> Reaction Engine running! 2021-08-12T18:39:40.241Z <app:NOTICE> Starting HTTP server and API... 2021-08-12T18:39:40.245Z <app:NOTICE> Startup complete 2021-08-12T18:39:40.249Z <httpapi:NOTICE> HTTP API v1 21215 base URL http://192.168.0.164:8111; listening 2021-08-12T18:39:40.258Z <app:NOTICE> HTTP server running; registering proxy endpoints. 2021-08-12T18:39:40.259Z <app:NOTICE> Starting WSAPI... 2021-08-12T18:39:40.260Z <wsapi:NOTICE> wsapi: starting version 21196 2021-08-12T18:39:40.343Z <Engine:INFO> Engine#1 master timer tick, local time "8/12/2021, 2:39:40 PM" (TZ offset -240 mins from UTC)Your snippets don't show the current startup information, which would be useful. Make sure that NODE_PATH appears with the correct value in the startup messages, as shown in the log above.
Also works under PowerShell:
PS C:\Users\Patrick\Documents\MSR> $env:NODE_PATH = 'C:\Users\Patrick\Documents\MSR' PS C:\Users\Patrick\Documents\MSR> $env:NODE_PATH C:\Users\Patrick\Documents\MSR PS C:\Users\Patrick\Documents\MSR> node app.js basedir C:\Users\Patrick\Documents\MSR confdir C:\Users\Patrick\Documents\MSR\config datadir C:\Users\Patrick\Documents\MSR\storage logsdir C:\Users\Patrick\Documents\MSR\logs plugindir C:\Users\Patrick\Documents\MSR\ext module.paths [ 'C:\\Users\\Patrick\\Documents\\MSR\\node_modules', 'C:\\Users\\Patrick\\Documents\\node_modules', 'C:\\Users\\Patrick\\node_modules', 'C:\\Users\\node_modules', 'C:\\node_modules' ] NODE_PATH C:\Users\Patrick\Documents\MSR 2021-08-12T18:45:56.225Z <app:null> Reactor ###BUILDVERSION### starting on v14.15.5 2021-08-12T18:45:56.226Z <app:INFO> Process ID 25296; platform win32/x64 Windows 10 Pro 2021-08-12T18:45:56.227Z <app:INFO> Basedir C:\Users\Patrick\Documents\MSR; data in C:\Users\Patrick\Documents\MSR\storage 2021-08-12T18:45:56.227Z <app:INFO> NODE_PATH C:\Users\Patrick\Documents\MSR; module paths [ "C:\\Users\\Patrick\\Documents\\MSR\\node_modules", "C:\\Users\\Patrick\\Documents\\node_modules", "C:\\Users\\Patrick\\node_modules", "C:\\Users\\node_modules", "C:\\node_modules" ] 2021-08-12T18:45:56.228Z <app:INFO> process.env=[object Object] 2021-08-12T18:45:56.228Z <app:INFO> process.env.TEST=(undefined) 2021-08-12T18:45:56.271Z <Plugin:null> Module Plugin v21173 2021-08-12T18:45:56.279Z <default:INFO> Module Entity v21177 2021-08-12T18:45:56.282Z <Controller:null> Module Controller v21191 2021-08-12T18:45:56.283Z <default:null> Module Structure v21216 2021-08-12T18:45:56.287Z <default:null> Module Ruleset v21096 2021-08-12T18:45:56.287Z <default:null> Module Rulesets v21096 2021-08-12T18:45:56.303Z <default:null> Module Rule v21221 2021-08-12T18:45:56.310Z <default:null> Module Engine v21213 2021-08-12T18:45:56.310Z <default:null> Module httpapi v21215 2021-08-12T18:45:56.312Z <default:null> Module httpproxy v21054 2021-08-12T18:45:56.332Z <default:null> Module wsapi v21196 2021-08-12T18:45:56.334Z <app:NOTICE> Starting Structure... 2021-08-12T18:45:56.338Z <Structure:NOTICE> Structure#1 plugin ID influx disabled; skipping 2021-08-12T18:45:56.339Z <Structure:INFO> Structure#1 starting controller interface ezlo (EzloController) 2021-08-12T18:45:56.344Z <Structure:INFO> Structure#1 starting controller interface reactor_system (SystemController) 2021-08-12T18:45:56.370Z <default:null> Module EzloController v21218 2021-08-12T18:45:56.372Z <default:null> Module SystemController v21102 2021-08-12T18:45:56.375Z <EzloController:null> EzloController#ezlo created, config { "source": "wss://192.168.0.67:17000", "serial": "900xxxxx", "username": "xxxxx", "password": "xxxxx", "auto_rediscover": false } 2021-08-12T18:45:56.375Z <EzloController:null> EzloController#ezlo instance log level (null) (4) 2021-08-12T18:45:56.385Z <Controller:INFO> EzloController#ezlo device mapping data loaded; checking... 2021-08-12T18:45:56.386Z <Controller:INFO> EzloController#ezlo performing cloud auth to get local access token 2021-08-12T18:45:56.441Z <Controller:NOTICE> Controller SystemController#reactor_system is now online. 2021-08-12T18:45:56.518Z <app:INFO> Structure running; pausing for controllers' initial ready 2021-08-12T18:45:59.726Z <Controller:INFO> EzloController#ezlo cloud auth phase complete (local access token acquired) 2021-08-12T18:45:59.727Z <Controller:INFO> EzloController#ezlo opening local hub connection to "900xxxxx" at wss://192.168.0.67:17000 2021-08-12T18:45:59.727Z <Controller:NOTICE> EzloController#ezlo configured to ignore host ("900xxxxx") certificate 2021-08-12T18:45:59.729Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://192.168.0.67:17000 2021-08-12T18:45:59.823Z <Controller:NOTICE> EzloController#ezlo successful hub login; performing inventory 2021-08-12T18:46:00.006Z <Controller:INFO> EzloController#ezlo data load complete; 21 devices received, 26 entities registered; 66 items. 2021-08-12T18:46:00.006Z <Controller:INFO> EzloController#ezlo hub inventory complete/successful; 182ms 2021-08-12T18:46:00.007Z <Controller:NOTICE> Controller EzloController#ezlo is now online. 2021-08-12T18:46:00.008Z <app:NOTICE> Starting Reaction Engine... 2021-08-12T18:46:00.009Z <Engine:INFO> Reaction Engine starting 2021-08-12T18:46:00.009Z <Engine:INFO> Checking rule sets... 2021-08-12T18:46:00.012Z <Engine:INFO> Checking rules... 2021-08-12T18:46:00.012Z <Engine:INFO> Data check complete; no corrections. 2021-08-12T18:46:00.016Z <Engine:NOTICE> Reaction Engine running! 2021-08-12T18:46:00.017Z <app:NOTICE> Starting HTTP server and API... 2021-08-12T18:46:00.022Z <app:NOTICE> Startup complete 2021-08-12T18:46:00.026Z <httpapi:NOTICE> HTTP API v1 21215 base URL http://192.168.0.164:8111; listening 2021-08-12T18:46:00.039Z <app:NOTICE> HTTP server running; registering proxy endpoints. 2021-08-12T18:46:00.040Z <app:NOTICE> Starting WSAPI... 2021-08-12T18:46:00.042Z <wsapi:NOTICE> wsapi: starting version 21196 2021-08-12T18:46:00.123Z <Engine:INFO> Engine#1 master timer tick, local time "8/12/2021, 2:46:00 PM" (TZ offset -240 mins from UTC) -
Working for me:
C:\Users\Patrick\Documents\MSR>set NODE_PATH=C:\Users\Patrick\Documents\MSR C:\Users\Patrick\Documents\MSR>node app.js basedir C:\Users\Patrick\Documents\MSR confdir C:\Users\Patrick\Documents\MSR\config datadir C:\Users\Patrick\Documents\MSR\storage logsdir C:\Users\Patrick\Documents\MSR\logs plugindir C:\Users\Patrick\Documents\MSR\ext module.paths [ 'C:\\Users\\Patrick\\Documents\\MSR\\node_modules', 'C:\\Users\\Patrick\\Documents\\node_modules', 'C:\\Users\\Patrick\\node_modules', 'C:\\Users\\node_modules', 'C:\\node_modules' ] NODE_PATH C:\Users\Patrick\Documents\MSR 2021-08-12T18:39:38.096Z <app:null> Reactor ###BUILDVERSION### starting on v14.15.5 2021-08-12T18:39:38.097Z <app:INFO> Process ID 26416; platform win32/x64 Windows 10 Pro 2021-08-12T18:39:38.099Z <app:INFO> Basedir C:\Users\Patrick\Documents\MSR; data in C:\Users\Patrick\Documents\MSR\storage 2021-08-12T18:39:38.099Z <app:INFO> NODE_PATH C:\Users\Patrick\Documents\MSR; module paths [ "C:\\Users\\Patrick\\Documents\\MSR\\node_modules", "C:\\Users\\Patrick\\Documents\\node_modules", "C:\\Users\\Patrick\\node_modules", "C:\\Users\\node_modules", "C:\\node_modules" ] 2021-08-12T18:39:38.100Z <app:INFO> process.env=[object Object] 2021-08-12T18:39:38.100Z <app:INFO> process.env.TEST=(undefined) 2021-08-12T18:39:38.145Z <Plugin:null> Module Plugin v21173 2021-08-12T18:39:38.152Z <default:INFO> Module Entity v21177 2021-08-12T18:39:38.155Z <Controller:null> Module Controller v21191 2021-08-12T18:39:38.156Z <default:null> Module Structure v21216 2021-08-12T18:39:38.162Z <default:null> Module Ruleset v21096 2021-08-12T18:39:38.162Z <default:null> Module Rulesets v21096 2021-08-12T18:39:38.181Z <default:null> Module Rule v21221 2021-08-12T18:39:38.185Z <default:null> Module Engine v21213 2021-08-12T18:39:38.186Z <default:null> Module httpapi v21215 2021-08-12T18:39:38.189Z <default:null> Module httpproxy v21054 2021-08-12T18:39:38.209Z <default:null> Module wsapi v21196 2021-08-12T18:39:38.212Z <app:NOTICE> Starting Structure... 2021-08-12T18:39:38.214Z <Structure:NOTICE> Structure#1 plugin ID influx disabled; skipping 2021-08-12T18:39:38.216Z <Structure:INFO> Structure#1 starting controller interface ezlo (EzloController) 2021-08-12T18:39:38.220Z <Structure:INFO> Structure#1 starting controller interface reactor_system (SystemController) 2021-08-12T18:39:38.249Z <default:null> Module EzloController v21218 2021-08-12T18:39:38.251Z <default:null> Module SystemController v21102 2021-08-12T18:39:38.254Z <EzloController:null> EzloController#ezlo created, config { "source": "wss://192.168.0.67:17000", "serial": "900xxxxx", "username": "xxxxx", "password": "xxxxx", "auto_rediscover": false } 2021-08-12T18:39:38.255Z <EzloController:null> EzloController#ezlo instance log level (null) (4) 2021-08-12T18:39:38.269Z <Controller:INFO> EzloController#ezlo device mapping data loaded; checking... 2021-08-12T18:39:38.272Z <Controller:INFO> EzloController#ezlo performing cloud auth to get local access token 2021-08-12T18:39:38.324Z <Controller:NOTICE> Controller SystemController#reactor_system is now online. 2021-08-12T18:39:38.395Z <app:INFO> Structure running; pausing for controllers' initial ready 2021-08-12T18:39:39.934Z <Controller:INFO> EzloController#ezlo cloud auth phase complete (local access token acquired) 2021-08-12T18:39:39.936Z <Controller:INFO> EzloController#ezlo opening local hub connection to "900xxxxx" at wss://192.168.0.67:17000 2021-08-12T18:39:39.938Z <Controller:NOTICE> EzloController#ezlo configured to ignore host ("900xxxxx") certificate 2021-08-12T18:39:39.940Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://192.168.0.67:17000 2021-08-12T18:39:40.038Z <Controller:NOTICE> EzloController#ezlo successful hub login; performing inventory 2021-08-12T18:39:40.227Z <Controller:INFO> EzloController#ezlo data load complete; 21 devices received, 26 entities registered; 66 items. 2021-08-12T18:39:40.227Z <Controller:INFO> EzloController#ezlo hub inventory complete/successful; 187ms 2021-08-12T18:39:40.229Z <Controller:NOTICE> Controller EzloController#ezlo is now online. 2021-08-12T18:39:40.231Z <app:NOTICE> Starting Reaction Engine... 2021-08-12T18:39:40.233Z <Engine:INFO> Reaction Engine starting 2021-08-12T18:39:40.234Z <Engine:INFO> Checking rule sets... 2021-08-12T18:39:40.237Z <Engine:INFO> Checking rules... 2021-08-12T18:39:40.237Z <Engine:INFO> Data check complete; no corrections. 2021-08-12T18:39:40.240Z <Engine:NOTICE> Reaction Engine running! 2021-08-12T18:39:40.241Z <app:NOTICE> Starting HTTP server and API... 2021-08-12T18:39:40.245Z <app:NOTICE> Startup complete 2021-08-12T18:39:40.249Z <httpapi:NOTICE> HTTP API v1 21215 base URL http://192.168.0.164:8111; listening 2021-08-12T18:39:40.258Z <app:NOTICE> HTTP server running; registering proxy endpoints. 2021-08-12T18:39:40.259Z <app:NOTICE> Starting WSAPI... 2021-08-12T18:39:40.260Z <wsapi:NOTICE> wsapi: starting version 21196 2021-08-12T18:39:40.343Z <Engine:INFO> Engine#1 master timer tick, local time "8/12/2021, 2:39:40 PM" (TZ offset -240 mins from UTC)Your snippets don't show the current startup information, which would be useful. Make sure that NODE_PATH appears with the correct value in the startup messages, as shown in the log above.
Also works under PowerShell:
PS C:\Users\Patrick\Documents\MSR> $env:NODE_PATH = 'C:\Users\Patrick\Documents\MSR' PS C:\Users\Patrick\Documents\MSR> $env:NODE_PATH C:\Users\Patrick\Documents\MSR PS C:\Users\Patrick\Documents\MSR> node app.js basedir C:\Users\Patrick\Documents\MSR confdir C:\Users\Patrick\Documents\MSR\config datadir C:\Users\Patrick\Documents\MSR\storage logsdir C:\Users\Patrick\Documents\MSR\logs plugindir C:\Users\Patrick\Documents\MSR\ext module.paths [ 'C:\\Users\\Patrick\\Documents\\MSR\\node_modules', 'C:\\Users\\Patrick\\Documents\\node_modules', 'C:\\Users\\Patrick\\node_modules', 'C:\\Users\\node_modules', 'C:\\node_modules' ] NODE_PATH C:\Users\Patrick\Documents\MSR 2021-08-12T18:45:56.225Z <app:null> Reactor ###BUILDVERSION### starting on v14.15.5 2021-08-12T18:45:56.226Z <app:INFO> Process ID 25296; platform win32/x64 Windows 10 Pro 2021-08-12T18:45:56.227Z <app:INFO> Basedir C:\Users\Patrick\Documents\MSR; data in C:\Users\Patrick\Documents\MSR\storage 2021-08-12T18:45:56.227Z <app:INFO> NODE_PATH C:\Users\Patrick\Documents\MSR; module paths [ "C:\\Users\\Patrick\\Documents\\MSR\\node_modules", "C:\\Users\\Patrick\\Documents\\node_modules", "C:\\Users\\Patrick\\node_modules", "C:\\Users\\node_modules", "C:\\node_modules" ] 2021-08-12T18:45:56.228Z <app:INFO> process.env=[object Object] 2021-08-12T18:45:56.228Z <app:INFO> process.env.TEST=(undefined) 2021-08-12T18:45:56.271Z <Plugin:null> Module Plugin v21173 2021-08-12T18:45:56.279Z <default:INFO> Module Entity v21177 2021-08-12T18:45:56.282Z <Controller:null> Module Controller v21191 2021-08-12T18:45:56.283Z <default:null> Module Structure v21216 2021-08-12T18:45:56.287Z <default:null> Module Ruleset v21096 2021-08-12T18:45:56.287Z <default:null> Module Rulesets v21096 2021-08-12T18:45:56.303Z <default:null> Module Rule v21221 2021-08-12T18:45:56.310Z <default:null> Module Engine v21213 2021-08-12T18:45:56.310Z <default:null> Module httpapi v21215 2021-08-12T18:45:56.312Z <default:null> Module httpproxy v21054 2021-08-12T18:45:56.332Z <default:null> Module wsapi v21196 2021-08-12T18:45:56.334Z <app:NOTICE> Starting Structure... 2021-08-12T18:45:56.338Z <Structure:NOTICE> Structure#1 plugin ID influx disabled; skipping 2021-08-12T18:45:56.339Z <Structure:INFO> Structure#1 starting controller interface ezlo (EzloController) 2021-08-12T18:45:56.344Z <Structure:INFO> Structure#1 starting controller interface reactor_system (SystemController) 2021-08-12T18:45:56.370Z <default:null> Module EzloController v21218 2021-08-12T18:45:56.372Z <default:null> Module SystemController v21102 2021-08-12T18:45:56.375Z <EzloController:null> EzloController#ezlo created, config { "source": "wss://192.168.0.67:17000", "serial": "900xxxxx", "username": "xxxxx", "password": "xxxxx", "auto_rediscover": false } 2021-08-12T18:45:56.375Z <EzloController:null> EzloController#ezlo instance log level (null) (4) 2021-08-12T18:45:56.385Z <Controller:INFO> EzloController#ezlo device mapping data loaded; checking... 2021-08-12T18:45:56.386Z <Controller:INFO> EzloController#ezlo performing cloud auth to get local access token 2021-08-12T18:45:56.441Z <Controller:NOTICE> Controller SystemController#reactor_system is now online. 2021-08-12T18:45:56.518Z <app:INFO> Structure running; pausing for controllers' initial ready 2021-08-12T18:45:59.726Z <Controller:INFO> EzloController#ezlo cloud auth phase complete (local access token acquired) 2021-08-12T18:45:59.727Z <Controller:INFO> EzloController#ezlo opening local hub connection to "900xxxxx" at wss://192.168.0.67:17000 2021-08-12T18:45:59.727Z <Controller:NOTICE> EzloController#ezlo configured to ignore host ("900xxxxx") certificate 2021-08-12T18:45:59.729Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://192.168.0.67:17000 2021-08-12T18:45:59.823Z <Controller:NOTICE> EzloController#ezlo successful hub login; performing inventory 2021-08-12T18:46:00.006Z <Controller:INFO> EzloController#ezlo data load complete; 21 devices received, 26 entities registered; 66 items. 2021-08-12T18:46:00.006Z <Controller:INFO> EzloController#ezlo hub inventory complete/successful; 182ms 2021-08-12T18:46:00.007Z <Controller:NOTICE> Controller EzloController#ezlo is now online. 2021-08-12T18:46:00.008Z <app:NOTICE> Starting Reaction Engine... 2021-08-12T18:46:00.009Z <Engine:INFO> Reaction Engine starting 2021-08-12T18:46:00.009Z <Engine:INFO> Checking rule sets... 2021-08-12T18:46:00.012Z <Engine:INFO> Checking rules... 2021-08-12T18:46:00.012Z <Engine:INFO> Data check complete; no corrections. 2021-08-12T18:46:00.016Z <Engine:NOTICE> Reaction Engine running! 2021-08-12T18:46:00.017Z <app:NOTICE> Starting HTTP server and API... 2021-08-12T18:46:00.022Z <app:NOTICE> Startup complete 2021-08-12T18:46:00.026Z <httpapi:NOTICE> HTTP API v1 21215 base URL http://192.168.0.164:8111; listening 2021-08-12T18:46:00.039Z <app:NOTICE> HTTP server running; registering proxy endpoints. 2021-08-12T18:46:00.040Z <app:NOTICE> Starting WSAPI... 2021-08-12T18:46:00.042Z <wsapi:NOTICE> wsapi: starting version 21196 2021-08-12T18:46:00.123Z <Engine:INFO> Engine#1 master timer tick, local time "8/12/2021, 2:46:00 PM" (TZ offset -240 mins from UTC)@toggledbits
Thanks! I now seem to have overcome the NODE_PATH.... So the next problem arise. I now get a message related to the Ezlo plus: "... ezlo failed to authenticate: Error: Request failed: 404 NOT FOUND."I did a screenshot, so that I could easily hide my credentials. I have used my username as I use for both my Vera and Ezlo. I have checked them over and over - and they are correct. Is it something connected to the " "? Or what could it be?
The last lines are:
2021-08-13T12:04:13.950Z <Controller:ERR> EzloController#ezlo failed to authenticate: Error: Request failed: 404 NOT FOUND 2021-08-13T12:04:13.951Z <Controller:ERR> EzloController#ezlo failed to log in: auth failed 2021-08-13T12:04:15.034Z <VeraController:NOTICE> Controller VeraController#vera is now online. 2021-08-13T12:04:18.963Z <Controller:INFO> EzloController#ezlo performing cloud auth to get local access token 2021-08-13T12:04:19.460Z <Controller:ERR> EzloController#ezlo failed to authenticate: Error: Request failed: 404 NOT FOUND 2021-08-13T12:04:19.461Z <Controller:ERR> EzloController#ezlo failed to log in: auth failed 2021-08-13T12:04:24.470Z <Controller:INFO> EzloController#ezlo performing cloud auth to get local access token 2021-08-13T12:04:24.955Z <Controller:ERR> EzloController#ezlo failed to authenticate: Error: Request failed: 404 NOT FOUND 2021-08-13T12:04:24.956Z <Controller:ERR> EzloController#ezlo failed to log in: auth failed -
Username or password is incorrect. The "NOT FOUND" it is referring to is you.
-
Username or password is incorrect. The "NOT FOUND" it is referring to is you.
@toggledbits
I also thought so. But it's not incorrect. I even tried to create another user profile. The profile is able to log in to Vera/Ezlo. But when I use the profiles credentials, I get the same error. I changed between my true profile and the test profile - and always get the same result. So it's more to the story.
This is from my yaml file. I guess it looks alright?
-
Are there any special characters in the password, like international characters? Also what region are you in?
-
Yes, there is a @ in my password. I'm in Europe/Sweden.
Vera/Ezlo has these demands on the passwords:
Password must be at least 8 characters long and include:- at least one lowercase letter;
- at least one special character;
- uppercase letters or numbers.
-
Is your username capitalized?
-
Is your username capitalized?
@toggledbits
Yes. Everywhere. -
OK. That's probably it. Try creating an account with an all lower-case username. Password is fine.
-
Excellent news. That's a bug I can fix, so I'll make sure that's in the next build and you can use your username the way you want it to be.
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
Excellent news. That's a bug I can fix, so I'll make sure that's in the next build and you can use your username the way you want it to be.
"Note that Generation 1 Atoms are supported in this version, but only through the remote access API (so it's cloud-dependent). Gen2 and later Atoms/PlugHubs can run with local/LAN access (no cloud dependency)."
Did you hear back from the Ezlo devs with the needed information for this? Or have you just gone ahead and used the learned knowledge from the forum ?
My Atom is now at firmware version 0.8.539. However I am not totally sure if its a gen1 or gen2 Atom? I think its gen2 but not sure.
Its still not appearing in the MSR Entities area however.
I have tried with "set_anonymous_access: true" commented out and not commented out in the reactor.yaml file.
I can't see anything in the MSR log to do with the Atom controller only the Ezlo Plus controller.
Thanks
-
I have heard nothing from the eZLO devs on anything. That's business as usual. Everything I've done, everything that everyone has done, in this respect has been done based on hearsay and tribal knowledge, no specifications or documentation from eZLO. May stop working at any time.
Sounds like you have a Gen1 atom. You have to configure for cloud/remote access, it doesn't switch back and forth automatically. That involves just commenting out the
sourcefield. If thesourcefield is not present, then theEzloControlleruses remote access to get to the device. But, there's bug that leaked in the remote access login that I just fixed. Are you on a docker container or bare metal install?The
set_anonymous_accessfield is not available for Atom and PlugHub; it is not supported on these platforms.Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
I have heard nothing from the eZLO devs on anything. That's business as usual. Everything I've done, everything that everyone has done, in this respect has been done based on hearsay and tribal knowledge, no specifications or documentation from eZLO. May stop working at any time.
Sounds like you have a Gen1 atom. You have to configure for cloud/remote access, it doesn't switch back and forth automatically. That involves just commenting out the
sourcefield. If thesourcefield is not present, then theEzloControlleruses remote access to get to the device. But, there's bug that leaked in the remote access login that I just fixed. Are you on a docker container or bare metal install?The
set_anonymous_accessfield is not available for Atom and PlugHub; it is not supported on these platforms.Bare metal Linux Debian install.
I did try to comment out the source line earlier. I just tried again now. I also have set_anonymous_access commented out.
The serial number of the Atom and the username and password look OK. Restarted MSR but still nothing in entities.
If I login to https://home.getvera.com/ with same username and password I can see that Atom listed in the controllers.
- id: ezlo-atom enabled: false implementation: EzloController name: Ezlo Atom config: # source: "wss://192.168.0.243:17000" # change the IP address serial: "70060304" # put your hub's serial here username: "myusername" # put your username here between quotes password: "mypassword" # and password # set_anonymous_access: trueIn the MSR log I see no mention of the word "atom"
Maybe I need your bug fix first then.
Cheers.
EDIT:
Bugger just spotted it says enabled "false" maybe that's why.
-
Looking in the log I now see this, I have changed some sensitive items:
2021-08-25T14:54:50.826Z <EzloController:null> EzloController#ezlo-atom account server replied { "PK_Device": "70060304", "NMAControllerStatus": 1, "NMAUuid": "a12bgd83-96b3-22d9-ad44-533df5564f44", "firmware_upgrade_progress": 100, "firmware_upgrade_status": "finished", "public_key_android": "", "public_key_ios": "", "Server_Relay": "wss://nma-server6-ui-cloud.ezlo.com:443", "MacAddress": "54:F5:4E:A4:5E:E5", "FK_Branding": "1", "HasWifi": "0", "HasAlarmPanel": "0", "UI": "4", "EngineStatus": "0", "LinuxFirmware": 1 } 2021-08-25T14:54:50.828Z <EzloController:INFO> EzloController#ezlo-atom cloud auth succeeded 2021-08-25T14:54:50.829Z <EzloController:6:EzloController.js:660> EzloController#ezlo-atom authinfo { } 2021-08-25T14:54:50.830Z <EzloController:INFO> EzloController#ezlo-atom opening hub connection to "70060304" at wss://nma-server6-ui-cloud.ezlo.com:443 2021-08-25T14:54:50.832Z <EzloController:NOTICE> EzloController#ezlo-atom connecting via WS to wss://nma-server6-ui-cloud.ezlo.com:443 2021-08-25T14:54:50.834Z <EzloController:5:Controller.js:537> EzloController#ezlo-atom websocket options { "maxPayload": 268435456, "followRedirects": true, "pingInterval": 60000, "agent": [object Object], "handshakeTimeout": 30000 } 2021-08-25T14:54:51.518Z <EzloController:6:Controller.js:554> EzloController#ezlo-atom websocket connected to wss://nma-server6-ui-cloud.ezlo.com:443; starting ping check timer Timer#ezlo-atom-ping 2021-08-25T14:54:51.519Z <EzloController:INFO> EzloController#ezlo-atom hub websocket connected (wss://nma-server6-ui-cloud.ezlo.com:443) 2021-08-25T14:54:51.520Z <EzloController:INFO> EzloController#ezlo-atom sending remote hub login 2021-08-25T14:54:51.522Z <EzloController:7:EzloController.js:1848> EzloController#ezlo-atom sending tracked request "17c8dcd8491" payload { "api": "1.0", "id": "17b7dce8481", "method": "loginUserMios", "params": { "MMSAuth": --undef--, "MMSAuthSig": --undef-- } } 2021-08-25T14:54:51.523Z <EzloController:5:EzloController.js:1856> EzloController#ezlo-atom created tracked request "17c8dcd8491" with payload { "api": "1.0", "id": "17b7dce8481", "method": "loginUserMios", "params": { "MMSAuth": --undef--, "MMSAuthSig": --undef-- } } 2021-08-25T14:54:51.675Z <EzloController:5:EzloController.js:1419> EzloController#ezlo-atom received message 144 bytes 2021-08-25T14:54:51.676Z <EzloController:5:EzloController.js:1419> EzloController#ezlo-atom message data {"id":"17b7dce8481","method":"loginUserMios","error":{"code":2,"data":"cloud.error.failed_to_get_mms_autha_token","description":""},"result":{}} 2021-08-25T14:54:51.678Z <EzloController:7:EzloController.js:1423> EzloController#ezlo-atom tracked request result slot { "req_id": "17c8dcd8491", "req_method": "loginUserMios", "expires": 1629903306521, "resolve": --function--, "reject": --function--, "promise": [object Promise] } 2021-08-25T14:54:51.679Z <EzloController:ERR> EzloController#ezlo-atom request "17c8dcd8491" (loginUserMios) failed: { "code": 2, "data": "cloud.error.failed_to_get_mms_autha_token", "description": "" } 2021-08-25T14:54:51.680Z <EzloController:7:EzloController.js:1855> EzloController#ezlo-atom removing resolved tracked request "17c8dcd8491" 2021-08-25T14:54:51.681Z <EzloController:ERR> EzloController#ezlo-atom hub login failed: { "code": 2, "data": "cloud.error.failed_to_get_mms_autha_token", "description": "" } 2021-08-25T14:54:51.685Z <EzloController:5:Controller.js:560> EzloController#ezlo-atom got websocket close 2021-08-25T14:54:51.686Z <EzloController:NOTICE> EzloController#ezlo-atom websocket closing, 1006And as I said no devices from the Atom are being pulled in to MSR. Maybe at this stage I need your bug fix then..
It was the low-case username that did the trick!
