I've managed to use MSR UI on iOS devices to some degree*, so that although UI elements (e.g. rule sets) are not visible in portrait mode, you've seen them in landscape. Now with recents builds (24302) this does not work anymore, elements (rule sets, entities) are not anymore visible in landscape mode.
Does anyone have similar experiences? Using iOS 18 and Safari/Chrome browser.
( *Drag & drop of rule conditions have never worked on a mobile)
Hi @toggledbits,
I have lots of logs with this:
<Engine:ERR> Assignment to alarm ignored -- expression-driven global cannot be set by assignmentAny hints to where look at to avoid this? Thanks.
Hi @toggledbits
I'd like to update my controllers with these new features, but I'm struggling to find any guidance in the docs - and in general to understand the context.
Could you please elaborate more? Thanks.
I have the following ACL defined:
groups: admin: users: - admin applications: true api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: trueAnd I have authenticated to MSR as "admin" user. However, I'm getting "access denied" when trying to access http://*******:8111/api/v1/log
So what I'm missing, is my ACL incorrectly defined?
Using build 24302 on Docker.
Thanks to @toggledbits for adding a custom CSS. I've started doing a darker Reactor style.
Here's the file: https://gist.github.com/dbochicchio/825098ac13b7f8cac22012eae37ff7ce
A couple of things are still too bright and I'll eventually catch-up. Just place it under your /config directory, naming the file as customstyles.css. Hard refresh your browser.
Hi!
In Home Assistant I sometimes uses the TTS, either to my Sonos or Google speakers. With reactor in Vera I also use TTS.
But in MSR I can't select the TTS-service. It's simply not there. Am I missing something, or is this the case, so far?
Thanks!
/Fanan
Hi
I have just connected a bunch of EzloPi controllers to MSR to import some ESP based devices etc.
They all seemed to have worked and imported in to MSR apart from I have one missing device. It is a Digital Gas Sensor device.
This is how that device looks in the Ezlo API.
Devices Info:
_id: "10696001" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "level_sensor" subcategory: "" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Digital" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"Items Info:
_id: "20696001" deviceId: "10696001" hasGetter: true hasSetter: false name: "smoke_density" show: true valueType: "substance_amount" scale: "parts_per_million" value: 2.7472610473632812 valueFormatted: "2.75" status: "idle"There is also an Analog Gas sensor that one did import in to MSR OK.
68d63dab-b871-4f44-912b-cf6e0b9eb4c6-image.png
Devices Info:
_id: "10696000" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "security_sensor" subcategory: "gas" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Analog" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"Items Info:
_id: "20696000" deviceId: "10696000" hasGetter: true hasSetter: false name: "gas_alarm" show: true valueType: "token" enum: 0: "no_gas" 1: "combustible_gas_detected" 2: "toxic_gas_detected" 3: "unknown" valueFormatted: "no_gas" value: "no_gas" status: "idle"And this is how this MQ2 Gas Sensor looks like on their dashboard:
Digital
cb77dfa3-4af5-4d06-9635-89207a716a89-image.png
Analog
4fb4da1b-e946-4b89-876c-bcd9f5699b6c-image.png
They have an EzloPi website here you can create your own sensor projects using ESP boards, which is very interesting stuff!
And I just wrote on the Ezlo forum here, how to connect an EzloPi controller to MSR.
THANKS.
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.A couple of things for you @toggledbits, since you mentioned that this release has new features and some tweaks are expected.
Local expressions cannot be deleted. Pushing the X button has no effect for me.
When cloning an entity action, the result is strange (first is cloned one, second is the original action):
a92ea094-9e2c-4aaa-bf47-2d07a6ffdbd0-image.png
When changing the action on the cloned element, the params are added to the original one. See screenshot:
92ac3011-83c8-466b-bd23-47d483ad7a52-image.png
Dark theme has a couple of strange contrasts. One is visible in the previous screenshots (white text on yellow background). Another one is in groups (blue text on blue background):
9b3c4988-53ef-44e6-9672-30e744cacb75-image.png
Overall, I found blue, yellow, red and green (in buttons and forms) to be too bright.
On the bright side:
I love the new script action: thank you! The dark theme is a great start to avoid getting blinded at night I promise I'll try very soon the new features around actions. Thanks!@toggledbits
I just upgraded to version MSR 24293, bare metal running on Fedora. Upon restart, I am getting a error banner:
I followed the new directions about npm
npm i --no-save --no-package-lock --omit dev
Any idea what the issue is?
Seems like switching the UI to the newly added dark mode (thank you for this) does nothing. The UI stays in light mode and only a few buttons turn into dark mode (see screenshot)
Things I have tried:
Hard refresh
Different browser
Different computer
Restarting Reactor
Failed troubleshooting attempts:
No errors in Chrome console
No relevant errors in Reactor log (can still PM the full log file)
Reactor version: latest-24293-ea42a81d
Hardware: Odroid N2+
Linux version: Ubuntu 24.04.1 LTS
3df2806f-9146-485b-9ec1-d056e91cefe5-image.png Dark mode enabled
ff823023-c079-4684-b01f-d6ac6527d31a-image.png Light mode enabled
Good morning,
I have a service MQTT service that needs a restart occasionally. The add-on (Smartbed MQTT) is for the smart bed base for my bed. It has a "safety light" that I can control from HAAS & MSR as a light entity, and also moves the head of the bed to a preset at bedtime, and then lies it back flat in the morning The problem is, from time to time, the light becomes "unavailable" Restarting from the Add-ons tab in HAAS always fixes it, but I should be able to detect when it happens when "light.tempur_pedic_safety_lights" is not true or false, i.e., unavailable.
What I don't know how to do is how to restart that service. Does anybody have experience in restarting add-ons from MSR?
Running:
Reactor (Multi-hub) latest-24212-3ce15e25 ZWaveJSController [0.1.24232]HAAS:
RPi5-64 (8GB) Core 2024.7.3 Supervisor 2024.08.0 Operating System 13.0 Frontend 20240710.0
Hi!
Is it possible to generate two additional log files, the first being the replica of what is displayed on screen by the Rule History widgets and the other with Recently Changed Entities?
And could I configure the generation of one file per day, and delete the older ones? For example, store the last 5 days?
And being more ambitious, does Windget have an icon to open these TXT files in the navigated?
Well, we're approaching Christmas, so here's my request to Santa Claus @toggledbits 🙂
Hi @toggledbits
I'm working on a controller to generate llm response from a prompt in reactor. I have http response coming thru an http request action at the moment, capturing the response inside a local variable. So, it's practically sync.
I want to create a controller, so I don't have to rely on a proxy (and have a simpler architecture), and duplicate absurd http actions, but AFAIK in the current implementation, actions are async only. But if I have multiple requests going on, I cannot be sure what it's really inside an attribute. I also thought that something like a correlation id when sending the request could be used to identity multiple responses, but I wanted to double check with you before starting with something too complicated. I also noticed that some actions in home assistant (ie forecast) are sync and I'm wondering if you have any plan or hint to address this situation. Thanks.
Thanks.
@togglebits I am curious as to why the tilt_sensor.state (primary) = NULL. I believe it should show true or false. I have to use binary_sensor.state instead in my rules.
Again, not sure if this is related to Reactor/ZwaveJSController implementation or the actual Z-Wave JS UI docker version. I have copied, below, the attributes of the tilt sensor in hopes it can help.
Thanks in advance.
Reactor version 23302
ZWaveJSController version 23254
Z-Wave JS UI version 9.3.0.724519f
zwave-js version 12.2.3
@toggledbits I have noticed after upgrading both Reactor and ZWaveJSController to version 24257 that two of my devices/entities, TILT-ZWAVE2.5-ECO and Zooz ZSE18, had their entity re-named in an unusual way and also appears to be duplicated.
Reactor version 24257
ZWaveJSController version 24257
Z-Wave JS UI version 9.18.1
zwave-js version 13.2.0
Vestibule Motion Sensor State attributes/partial screenshot of entities it created. All entities have the same attributes.
motion_sensor.state=true x_zwave_values.Notification_Home_Security_Motion_sensor_status=8 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=23 zwave_device.valueId=[113,"Notification","Home Security","Home Security","Motion sensor status","Motion sensor status"] zwave_device.version_info=nullTilt Sensor Door State and Tilt Sensor Door State Simple attributes/partial screenshot of entities it created. All entities have similar attributes with exception of x_zwave_values.Notification_Access_Control_Door_State = 22 or 23.
tilt_sensor.state=true x_zwave_values.Notification_Access_Control_Door_state=22 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"] zwave_device.version_info=null tilt_sensor.state=true x_zwave_values.Notification_Access_Control_Door_state_simple=22 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"] zwave_device.version_info=null tilt_sensor.state=false x_zwave_values.Notification_Access_Control_Door_state=23 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"] zwave_device.version_info=null tilt_sensor.state=false x_zwave_values.Notification_Access_Control_Door_state_simple=23 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"] zwave_device.version_info=nullI'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only).
Anyway, here's my reactor-mqtt-contrib package:
GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor
GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor
Contrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.
Simply download yaml files (everything or just the ones you need) and you're good to go.
I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them.
The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression.
Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests 🙂
Support for Ezlo Atom controllers?
-
The port number is right, it connects, it just never answers the usual login request, and doesn't issue any messages of any kind at all. I embellished details in my previous post there, and prompted Oleg in it. In any case, none of this is serviceable until this is documented.
Over a year ago on Skype, early on in perhaps March or April, I suggested that all of their PDF documents need to be in a single location/library where they can seen. This business of them posting single PDFs on demand in the forums is the worst possible way to get it done (maybe second worst: they were replying on Skype with them, which was actually worse). Did that ever happen? I know of no such repository. If there were, at least one could research, but as it is, their docs are a hodge-podge of "lucky if you have it" one-offs, a dated web reference site, and an incomplete/dated API tool. And no version control. Ugh. This entire situation is why I didn't want to do this eZLO interface, and I'm really regretting it this morning.
-
I feel your pain.
Forgot it for now then.
For me personally I don't need my Atom connected to MSR. But I just thought I'd try it and test it if it did connect.
As long as Ezlo Plus and Ezlo Secure works, I think most people will be happy with that.
That website you mentioned is all I know of and there's a bit of a library section they created on the forum here.
-
Yeah, nothing there either. Cart before the horse. API docs. No docs for how to log in to the API. And enough people have asked, including you, to produce various unofficial mechanisms; that should have been enough prompt/repetition to cause an official document to be produced (and really, together with/as part of the API docs is the perfect place for it).
-
Might be a bit OT, or not... I can't get my only Ezlo controller (a Plus) to work in MSR. I have the latest version of MSR (21203-9503e5d), and I have added all needed lines to my reactor.yaml. This is the message I get:
2021-07-29T13:13:57.524Z <Structure:ERR> [Structure:start] failed to start controller ezlo: Error: Cannot find module 'server/lib/Configuration' Require stack: - D:\msr\server\lib\EzloController.js 2021-07-29T13:13:57.525Z <Structure:CRIT> Error: Cannot find module 'server/lib/Configuration' Require stack: - D:\msr\server\lib\EzloController.js Error: Cannot find module 'server/lib/Configuration' Require stack: - D:\msr\server\lib\EzloController.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:924:15) at Function.Module._load (node:internal/modules/cjs/loader:769:27) 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\EzloController.js:527:157) 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 ModuleWrap.<anonymous> (node:internal/modules/esm/translators:201:29) Error: Cannot find module 'server/lib/Configuration' Require stack: - D:\msr\server\lib\EzloController.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:924:15) at Function.Module._load (node:internal/modules/cjs/loader:769:27) 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\EzloController.js:527:157) 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 ModuleWrap.<anonymous> (node:internal/modules/esm/translators:201:29) { code: 'MODULE_NOT_FOUND', requireStack: [ 'D:\\msr\\server\\lib\\EzloController.js' ] }And this is my reactor.yaml:
- id: ezlo enabled: true implementation: EzloController name: Ezlo Plus config: source: "wss://192.168.50.211:17000" # change the IP address serial: "90000453" # put your hub's serial # here username: "My_secret_name" # put your username here betw quotes password: "My_top_secret_password" # and passwordI have restarted MSR several times, with no luck. Any clues?
-
How is MSR installed, and how are you running/starting it?
-
@toggledbits
MSR is installed on Windows 10, bare metall.
I open up Windows Powershell and navigate to the MSR folder, and then type "node app.js".
Everything else is working. I have a Vera and a Home Assistant up and running since months back... It's just the Ezlo that's not working. -
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.
-
@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) -
@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.
-
@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?
-
@toggledbits
Yes. Everywhere. -
OK. That's probably it. Try creating an account with an all lower-case username. Password is fine.
