Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. Support for Ezlo Atom controllers?
Copying a global reaction
tunnusT
With build 25328, if you copy a global reaction, a new reaction does not appear in the UI unless you do a refresh. I recall this used to work without needing this page refresh? Anyway, only a minor nuisance.
Multi-System Reactor
[Reactor] Bug when sending MQTT boolean payloads
therealdbT
Topic thumbnail image
Multi-System Reactor
Difficulty defining repeating annual period
R
I have tried numerous ways to define a recurring annual period, for example from December 15 to January 15. No matter which method I try - after and before, between, after and/not after, Reactor reports "waiting for invalid date, invalid date. Some constructs also seem to cause Reactor to hang, timeout and restart. For example "before January 15 is evaluated as true, but reports "waiting for invalid date, invalid date". Does anyone have a tried and true method to define a recurring annual period? I think the "between" that I used successfully in the past may have broken with one of the updates.
Multi-System Reactor
Need help with sequence
T
Good evening all, For about the past week or so, I've been having problems with a specific rule in my home automation that controls when my home goes from an Away mode to Home mode. One of the conditions it checked for was my alarm panel, when it changed from Armed Away to Disarmed. There seems to have been a firmware update on the panel that added an intermittent step of "pending", and I can't say for certain it happens 100% of the time. Is there a way to write a condition that so it changes from one condition, to the next, and then another condition? As in, Home alarm changes from armed_away to pending to disarmed. Thanks.
Multi-System Reactor
Possible feature request?
CatmanV2C
No idea how easy this would be. During my migration away from Z-wave I've been replacing the Z-wave devices with Sonoff which has broken some of my automations. Any chance of a 'Test Reaction' function to call out which ones are broken because an entity no longer exists? Without actually running the reaction? Or does this exist already and I'm just not aware of how to do it? Obviously I can see entities that are no longer available, but not quite what I'm looking for. I guess it's something of an edge case so no huge issue. TIA! C
Multi-System Reactor
Logic Assistance: Exterior Lights on when Illuminance Below Threshold
PablaP
Topic thumbnail image
Multi-System Reactor
Time series documentation
tunnusT
Is the current manual (incl. examples) up to date with how retention value is handled in time series configuration? Referring to this post
Multi-System Reactor
MQTT templates for ZIgbee scene controller, or a better way?
CatmanV2C
Topic thumbnail image
Multi-System Reactor
Reset a delay
CatmanV2C
I'm sure this has been asked, and answered, but damned if I can figure it out Use case: I have a rear garden with lights. A door from the kitchen into the garden and a door from the garage. Currently if I open the kitchen door the lights come on (yay) and a 3 minute delay starts. After 3 minutes, no matter what else happens, the lights go off (Boo! But also yay!) What I would like is for the 3 minute delay until the lights go off to start from the latest door open event. That is, if I'm going from kitchen to garage, and back again, the lights stay on until there's three minutes of no activity. I've tried 'hacking' with a virtual switch, but can't seem to stop the delay. Any pointers? TIA C
Multi-System Reactor
Reactor Loading Screen Safari
S
Topic thumbnail image
Multi-System Reactor
Constraints states visually do not match actual
S
Topic thumbnail image
Multi-System Reactor
[MSR] Feature request: For Each action on arrays/groups
therealdbT
Topic thumbnail image
Multi-System Reactor
[Solved] Error: Command timeout
G
at _ClientAPI._commandTimeout (http://192.168.1.100:8111/client/ClientAPI.js:807:179 Seeing this randomly when returning to open browser tab after being away awhile. Once, maybe twice a day. "What did you do to trigger it?" Literally nothing, just walked away and returned and there it was. Actions taken in reasonably close proximity to this particular instance of it popping up: I'd restarted the MSR container in Portainer. I'll try to grab some logs here shortly.
Multi-System Reactor
Issue with MSR UI becoming unresponsive
S
I'm having an issue with MSR's UI being very unresponsive. It started happening a couple days ago and I didn't make any changes that would have caused this except adding some meross lan devices in HA. When I go into an entity action and use the search functionality, it usually will start filtering and then get to a place after a few letters are entered where it will take 30 seconds or more (sometimes minutes) for the UI to show what I am typing. During this time MSR ui is completely unresponsive. I've tried multiple browsers and multiple computers. HA and MSR are both deployed in docker. I have run HTOP on the host and when the problem happens there are no CPU/Memory spikes at all. From a functionality standpoint MSR is working perfectly. This seems to be an UI issue only. Do i need to ditch Docker and run MSR on a Proxmox VM? I have both stand alone Docker and Proxmox environments. I dont mind doing that I just want to be able to use the UI again... Installation method Home Assistant Container Core 2025.7.3 Frontend 20250702.3 nothing crazy in the logs except some openweather map stuff that doesn't make any sense as it is working fine in MSR Any help would be greatly appreciated Reactor latest-25328-b2ed1365 app 25328 configuration from /var/reactor/config NODE_PATH /opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.843Z <app:null> Reactor build latest-25328-b2ed1365 starting on v24.11.1 /usr/local/bin/node [latest-25328]2025-11-30T20:01:53.844Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #161-Ubuntu SMP Tue Jul 22 14:25:40 UTC 2025; locale (undefined) [latest-25328]2025-11-30T20:01:53.844Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-25328]2025-11-30T20:01:53.844Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-25328]2025-11-30T20:01:53.865Z <app:null> Resolved timezone=America/New_York, environment TZ=America/New_York; offset minutes from UTC=-300 [latest-25328]2025-11-30T20:01:53.867Z <default:null> Module i18n v25141 [latest-25328]2025-11-30T20:01:53.867Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8 [latest-25328]2025-11-30T20:01:53.879Z <app:null> Loaded locale en-US for en-US [latest-25328]2025-11-30T20:01:53.879Z <app:null> Local date/time using configured timezone and locale formatting is "11/30/2025, 3:01:53 PM" [latest-25328]2025-11-30T20:01:53.889Z <Structure:null> Module Structure v25326 [latest-25328]2025-11-30T20:01:53.890Z <Capabilities:null> Module Capabilities v24312 [latest-25328]2025-11-30T20:01:53.904Z <Plugin:null> Module Plugin v25141 [latest-25328]2025-11-30T20:01:53.923Z <Timer:null> Module Timer v25279 [latest-25328]2025-11-30T20:01:53.924Z <TimerBroker:null> Module TimerBroker v25314 [latest-25328]2025-11-30T20:01:53.927Z <Entity:null> Module Entity v25251 [latest-25328]2025-11-30T20:01:53.929Z <Controller:null> Module Controller v25253 [latest-25328]2025-11-30T20:01:53.930Z <AlertManager:null> Module AlertManager v25318 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Ruleset v25283 [latest-25328]2025-11-30T20:01:53.937Z <default:null> Module Rulesets v25141 [latest-25328]2025-11-30T20:01:53.942Z <GlobalExpression:null> Module GlobalExpression v25258 [latest-25328]2025-11-30T20:01:53.953Z <Predicate:null> Module Predicate v25328 [latest-25328]2025-11-30T20:01:53.956Z <Rule:null> Module Rule v25323 [latest-25328]2025-11-30T20:01:53.958Z <GlobalReaction:null> Module GlobalReaction v25292 [latest-25328]2025-11-30T20:01:53.959Z <Engine:null> Module Engine v25325 [latest-25328]2025-11-30T20:01:53.964Z <httpapi:null> Module httpapi v25328 [latest-25328]2025-11-30T20:01:53.972Z <wsapi:null> Module wsapi v25328 [latest-25328]2025-11-30T20:01:53.994Z <TaskQueue:null> Module TaskQueue 24138 [latest-25328]2025-11-30T20:01:53.994Z <VeraController:null> Module VeraController v25141 [latest-25328]2025-11-30T20:01:54.179Z <HassController:null> Module HassController v25325 [latest-25328]2025-11-30T20:02:13.797Z <OWMWeatherController:null> Module OWMWeatherController v25268 [latest-25328]2025-11-30T20:02:13.800Z <SystemController:null> Module SystemController v25323 [latest-25328]2025-11-30T20:02:13.807Z <MQTTController:null> Module MQTTController v22092 [latest-25328]2025-11-30T20:02:20.630Z <OWMWeatherController:CRIT> FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxx&lon=-xxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxxxxxxxxx&units=standard&_r=1xxxxxxxxxxxxxxfailed, reason: [-] FetchError: request to https://api.openweathermap.org/data/2.5/weather?lat=xxxxxxxxxxx&lon=-xxxxxxxxxxxxxxxxxx&appid=xxxxxxxxxxxxxxxxxxx&units=standard&_r=xxxxxxxxxxxxxxxfailed, reason: at ClientRequest.<anonymous> (/opt/reactor/node_modules/node-fetch/lib/index.js:1501:11) at ClientRequest.emit (node:events:508:28) at ClientRequest.emit (node:domain:489:12) at emitErrorEvent (node:_http_client:108:11) at TLSSocket.socketErrorListener (node:_http_client:575:5) at TLSSocket.emit (node:events:508:28) at TLSSocket.emit (node:domain:489:12) at emitErrorNT (node:internal/streams/destroy:170:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at processTicksAndRejections (node:internal/process/task_queues:89:21
Multi-System Reactor
Date/time condition
tunnusT
Topic thumbnail image
Multi-System Reactor
Device log?
G
@toggledbits is there a log that will show me what rule is turning on a specific device? I've got a switch that has been kicking on at 2200 ET for several nights now and the reactor.log doesn't have a thing in it that I can see on a device level (it being more rules-based).
Multi-System Reactor
Midnight crossing not working in date/time condition (build 25325)
tunnusT
Topic thumbnail image
Multi-System Reactor
Reactor (Multi-System/Multi-Hub) Announcements
toggledbitsT
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.
Multi-System Reactor
[Solved] Local expression in Rule does not evaluate as they used to do
CrilleC
Topic thumbnail image
Multi-System Reactor
Home Assistant 2025.11.2 and latest-25315
CrilleC
Topic thumbnail image
Multi-System Reactor

Support for Ezlo Atom controllers?

Scheduled Pinned Locked Moved Multi-System Reactor
51 Posts 3 Posters 8.6k Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #19

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

    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

    F 1 Reply Last reply
    0
    • toggledbitsT toggledbits

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

      F Offline
      F Offline
      Fanan
      wrote on last edited by
      #20

      @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)
      
      1 Reply Last reply
      0
      • toggledbitsT Offline
        toggledbitsT Offline
        toggledbits
        wrote on last edited by
        #21

        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.

        Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

        F 1 Reply Last reply
        1
        • toggledbitsT toggledbits

          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.

          F Offline
          F Offline
          Fanan
          wrote on last edited by Fanan
          #22

          @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:\reactor
          

          All 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

          1 Reply Last reply
          0
          • toggledbitsT Offline
            toggledbitsT Offline
            toggledbits
            wrote on last edited by
            #23

            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)
            

            Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

            F 1 Reply Last reply
            0
            • toggledbitsT toggledbits

              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)
              
              F Offline
              F Offline
              Fanan
              wrote on last edited by Fanan
              #24

              @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?

              91b3ef69-f368-4a32-92d6-c6cec0a3dcf8-image.png

              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
              
              1 Reply Last reply
              0
              • toggledbitsT Offline
                toggledbitsT Offline
                toggledbits
                wrote on last edited by toggledbits
                #25

                Username or password is incorrect. The "NOT FOUND" it is referring to is you.

                Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                F 1 Reply Last reply
                0
                • toggledbitsT toggledbits

                  Username or password is incorrect. The "NOT FOUND" it is referring to is you.

                  F Offline
                  F Offline
                  Fanan
                  wrote on last edited by
                  #26

                  @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?
                  55c82243-9760-40a4-8cb6-2990ff4dc134-image.png

                  1 Reply Last reply
                  0
                  • toggledbitsT Offline
                    toggledbitsT Offline
                    toggledbits
                    wrote on last edited by toggledbits
                    #27

                    Are there any special characters in the password, like international characters? Also what region are you in?

                    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                    1 Reply Last reply
                    0
                    • F Offline
                      F Offline
                      Fanan
                      wrote on last edited by Fanan
                      #28

                      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.
                      1 Reply Last reply
                      0
                      • toggledbitsT Offline
                        toggledbitsT Offline
                        toggledbits
                        wrote on last edited by
                        #29

                        Is your username capitalized?

                        Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                        F 1 Reply Last reply
                        0
                        • toggledbitsT toggledbits

                          Is your username capitalized?

                          F Offline
                          F Offline
                          Fanan
                          wrote on last edited by
                          #30

                          @toggledbits
                          Yes. Everywhere.

                          1 Reply Last reply
                          0
                          • toggledbitsT Offline
                            toggledbitsT Offline
                            toggledbits
                            wrote on last edited by
                            #31

                            OK. That's probably it. Try creating an account with an all lower-case username. Password is fine.

                            Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

                            1 Reply Last reply
                            0
                            • F Offline
                              F Offline
                              Fanan
                              wrote on last edited by
                              #32

                              Thanks! It worked! Finally after so many hours.... 😊 It was the low-case username that did the trick!
                              Have a great weekend Patrick!
                              /Fanan

                              1 Reply Last reply
                              0
                              • toggledbitsT Offline
                                toggledbitsT Offline
                                toggledbits
                                wrote on last edited by
                                #33

                                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.

                                cw-kidC 1 Reply Last reply
                                1
                                • toggledbitsT toggledbits

                                  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.

                                  cw-kidC Offline
                                  cw-kidC Offline
                                  cw-kid
                                  wrote on last edited by cw-kid
                                  #34

                                  @toggledbits

                                  "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

                                  1 Reply Last reply
                                  0
                                  • toggledbitsT Offline
                                    toggledbitsT Offline
                                    toggledbits
                                    wrote on last edited by
                                    #35

                                    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 source field. If the source field is not present, then the EzloController uses 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_access field 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.

                                    cw-kidC 1 Reply Last reply
                                    0
                                    • toggledbitsT toggledbits

                                      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 source field. If the source field is not present, then the EzloController uses 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_access field is not available for Atom and PlugHub; it is not supported on these platforms.

                                      cw-kidC Offline
                                      cw-kidC Offline
                                      cw-kid
                                      wrote on last edited by cw-kid
                                      #36

                                      @toggledbits

                                      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: true
                                      

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

                                      1 Reply Last reply
                                      0
                                      • cw-kidC Offline
                                        cw-kidC Offline
                                        cw-kid
                                        wrote on last edited by cw-kid
                                        #37

                                        OK its listed now in Entities

                                        133a7a4f-2eb2-47f6-96f3-c1315e3ea58e-image.png

                                        Still not sure if this is gen 1 or 2 ? It was sent to me by Ezlo as part of their beta program.

                                        Also not seeing the one Z-Wave device that is currently paired to that Atom a TKB Home RGBW module.

                                        1 Reply Last reply
                                        0
                                        • cw-kidC Offline
                                          cw-kidC Offline
                                          cw-kid
                                          wrote on last edited by cw-kid
                                          #38

                                          It says:

                                          sys_system.state=false

                                          Which I assume means its a gen 1 Atom ?

                                          1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          Recent Topics

                                          • Copying a global reaction
                                            toggledbitsT
                                            toggledbits
                                            0
                                            3
                                            78

                                          • [HowTo] Using HABridge with Reactor
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            9
                                            374

                                          • [Reactor] Bug when sending MQTT boolean payloads
                                            toggledbitsT
                                            toggledbits
                                            0
                                            4
                                            128

                                          • Genuinely impressed with Zigbee and HA / Reactor
                                            therealdbT
                                            therealdb
                                            1
                                            8
                                            292

                                          • Difficulty defining repeating annual period
                                            G
                                            gwp1
                                            0
                                            5
                                            97

                                          • Need help with sequence
                                            therealdbT
                                            therealdb
                                            0
                                            3
                                            60

                                          • Possible feature request?
                                            therealdbT
                                            therealdb
                                            0
                                            5
                                            161

                                          • Logic Assistance: Exterior Lights on when Illuminance Below Threshold
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            11
                                            337

                                          • Time series documentation
                                            tunnusT
                                            tunnus
                                            0
                                            11
                                            387

                                          • MQTT templates for ZIgbee scene controller, or a better way?
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            3
                                            155

                                          • Reset a delay
                                            CatmanV2C
                                            CatmanV2
                                            0
                                            8
                                            215
                                          Powered by NodeBB | Contributors
                                          Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
                                          • Login

                                          • Don't have an account? Register

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