Having been messing around with some stuff I worked a way to self trigger some tests that I wanted to do on the HA <> MSR integration
This got me wondering if there's an entity that changes state / is exposed when a configured controller goes off line? I can't see one but thought it might be hidden or something?
Cheers
C
Using build 25328 and having the following users.yaml configuration:
users:
# This section defines your valid users.
admin: *******
groups:
# This section defines your user groups. Optionally, it defines application
# and API access restrictions (ACLs) for the group. Users may belong to
# more than one group. Again, no required or special groups here.
admin_group:
users:
- admin
applications: true # special form allows access to ALL applications
guests:
users: "*"
applications:
- dashboard
api_acls:
# This ACL allows users in the "admin" group to access the API
- url: "/api"
group: admin_group
allow: true
log: true
# This ACL allows anyone/thing to access the /api/v1/alive API endpoint
- url: "/api/v1/alive"
allow: true
session:
timeout: 7200 # (seconds)
rolling: true # activity extends timeout when true
# If log_acls is true, the selected ACL for every API access is logged.
log_acls: true
# If debug_acls is true, even more information about ACL selection is logged.
debug_acls: true
My goal is to allow anonymous user to dashboard, but MSR is still asking for a password when trying to access that. Nothing in the logs related to dashboard access. Probably an error in the configuration, but help needed to find that. Tried to put url: "/dashboard" under api_acls, but that was a long shot and didn't work.
I use Virtual Entity Controller virtual switches which I turn on via webhooks from other applications. Once a switch triggers and turns on, I can then activate associated rules.
I would like each virtual switch to automatically turn off after a configurable time (e.g., 5 seconds, 10 seconds).
Is there a better way to achieve this auto-off behavior instead of creating a separate rule for each switch that uses the 'Condition must be sustained for' option to turn it off?
With a large number of these switches (and the associated turn-off rules), I'm checking to see if there is a simpler approach.If not, could this be a feature request to add an auto-off timer directly to the virtual switches.
Thanks
Reactor (Multi-hub) latest-26011-c621bbc7
VirtualEntityController v25356
Synology Docker
TL;DR: Format of data in storage directory will soon change. Make sure you are backing up the contents of that directory in its entirety, and you preserve your backups for an extended period, particularly the backup you take right before upgrading to the build containing this change (date of that is still to be determined, but soon). The old data format will remain readable (so you'll be able to read your pre-change backups) for the foreseeable future.
In support of a number of other changes in the works, I have found it necessary to change the storage format for Reactor objects in storage at the physical level.
Until now, plain, standard JSON has been used to store the data (everything under the storage directory). This has served well, but has a few limitations, including no real support for native JavaScript objects like Date, Map, Set, and others. It also is unable to store data that contains "loops" — objects that reference themselves in some way.
I'm not sure exactly when, but in the not-too-distant future I will publish a build using the new data format. It will automatically convert existing JSON data to the new format. For the moment, it will save data in both the new format and the old JSON format, preferring the former when loading data from storage. I have been running my own home with this new format for several months, and have no issues with data loss or corruption.
A few other things to know:
If you are not already backing up your storage directory, you should be. At a minimum, back this directory up every time you make big changes to your Rules, Reactions, etc.
Your existing JSON-format backups will continue to be readable for the long-term (years). The code that loads data from these files looks for the new file format first (which will have a .dval suffix), and if not found, will happily read (and convert) a same-basenamed .json file (i.e. it looks for ruleid.dval first, and if it doesn't find it, it tries to load ruleid.json). I'll publish detailed instructions for restoring from old backups when the build is posted (it's easy).
The new .dval files are not directly human-readable or editable as easily as the old .json files. A new utility will be provided in the tools directory to convert .dval data to .json format, which you can then read or edit if you find that necessary. However, that may not work for all future data, as my intent is to make more native JavaScript objects directly storable, and many of those objects cannot be stored in JSON.
You may need to modify your backup tools/scripts to pick up the new files: if you explicitly name .json files (rather than just specifying the entire storage directory) in your backup configuration, you will need to add .dval files to get a complete, accurate backup. I don't think this will be an issue for any of you; I imagine that you're all just backing up the entire contents of storage regardless of format/name, that is the safest (and IMO most correct) way to go (if that's not what you're doing, consider changing your approach).
The current code stores the data in both the .dval form and the .json form to hedge against any real-world problems I don't encounter in my own use. Some future build will drop this redundancy (i.e. save only to .dval form). However, the read code for the .json form will remain in any case.
This applies only to persistent storage that Reactor creates and controls under the storage tree. All other JSON data files (e.g. device data for Controllers) are unaffected by this change and will remain in that form. YAML files are also unaffected by this change.
This thread is open for any questions or concerns.
Just another thought. Adding devices from my Home Assistant / Zigbee2MQTT integration. Works perfectly but they always add as their IEEE address. Some of these devices have up to 10 entities associated, and the moment they are renamed to something sensible, each of those entities 'ceases to exist' in MSR. I like things tidy, and deleting each defunct entity needs 3 clicks.
Any chance of a 'bulk delete' option?
No biggy as I've pretty much finished my Z-wave migration and I don't expect to be adding more than 2 new Zigbee devices
Cheers
C
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here.
Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions;
Fix an error in OWMWeatherController that could cause it to stop updating;
Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later;
Improve error detail in messages for EzloController during auth phase;
Add isRuleSet() and isRuleEnabled() functions to expressions extensions;
Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases);
Fix a place in the UI where 24-hour time was not being displayed.
I have 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.
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.
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
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
Synology Docker installation
-
I've also rolled 21062 (today's daily build) into a docker container for Synology. Link is in PR #58 on the bug tracker.
-
We can both thank @kfxo for those instructions!
-
Hi! this is for asking an help to correct time zone.
MSR is now installed (1.0.0-21200-16a604f) on my Synology NAS (DS 720+ with DSM 7) and Docker running on it. With my previous DS119j impossible to do anything with it.All entities from Vera Lite are imported ok .
Trying to import also entities from Ezlo Plus without success.
So looking in the "reactor.log" I notice TZ offset with something like this:
2021-08-03T20:46:16.212Z wsapi:NOTICE wsapi: starting version 21196
2021-08-03T20:46:16.286Z Engine:INFO Engine#1 master timer tick, local time "8/3/2021, 10:46:16 PM" (TZ offset 120 mins from UTC)
2021-08-03T20:46:16.560Z wsapi:INFO wsapi: connection from ::ffff:172.17.0.1In reactor container, going on LOG tab, I have something like this:
time = 23.00.05
and log
2021-08-03T23:00:05.001Z Engine:INFO Engine#1 master timer tick, local time "8/4/2021, 1:00:05 AM" (TZ offset 120 mins from UTC)TZ variable for reactor container is: Europe/Rome
On nas control Panel, server NTP is on time.google.com
in Docker LOG tab, time is correct
Browser time and host Time in MSR GUI are correctdoes anyone have any advice?
-
Seems like everything is correct. The log timestamps are always UTC. The master timer tick log entry looks correct for about the time of your posting and the time zone you show set below.
-
I was not able to import entities from Ezlo Plus and I was thinking about a problem between time zone and access token.
Now I have also ezlo entities imported ok but only after putting both “offlineAnonymousAccess” and “offlineInsecureAccess” set to true with API call.In all this ways nothing:
config:username: "somebody" # put your username here betw quotes password: "????????" # and passwordthen config
set_anonymous_access: true <--- add this line, same indent as previousthen with
“offlineInsecureAccess” enabled:truethe log was:
2021-08-04T00:08:25.648Z <EzloController:null> EzloController#ezlo created, config { "source": "wss://10.0.4.119:17000/" } 2021-08-04T00:08:25.648Z <EzloController:null> EzloController#ezlo instance log level (null) (4) 2021-08-04T00:08:25.667Z <Controller:INFO> EzloController#ezlo device data loaded; checking structure 2021-08-04T00:08:25.669Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication; hub.offline.insecure_access must be enabled! 2021-08-04T00:08:25.696Z <Controller:NOTICE> Controller SystemController#reactor_system is now online. 2021-08-04T00:08:25.743Z <Controller:INFO> EzloController#ezlo opening local hub connection to (undefined) at wss://10.0.4.119:17000/ 2021-08-04T00:08:25.743Z <Controller:NOTICE> EzloController#ezlo configured to ignore host ((undefined)) certificate 2021-08-04T00:08:25.744Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000/ 2021-08-04T00:08:25.750Z <app:INFO> Structure running; pausing for controllers' initial ready 2021-08-04T00:08:25.856Z <Controller:INFO> EzloController#ezlo hub websocket connected; inventory hub... 2021-08-04T00:08:25.905Z <Controller:ERR> EzloController#ezlo stopping; hub's offline insecure access is disabled, and cloud auth info is not configured 2021-08-04T00:08:25.906Z <Controller:ERR> EzloController#ezlo failed to complete inventory: Error: hub offline anonymous access is disabled, and cloud auth info is not configured 2021-08-04T00:08:25.907Z <Controller:CRIT> Error: hub offline anonymous access is disabled, and cloud auth info is not configured Error: hub offline anonymous access is disabled, and cloud auth info is not configured at /opt/reactor/server/lib/EzloController.js:895:27 at processTicksAndRejections (internal/process/task_queues.js:95:5) 2021-08-04T00:08:25.915Z <Controller:NOTICE> EzloController#ezlo websocket closing, 1002After putting both “offlineAnonymousAccess” and “offlineInsecureAccess” set to true with API call, all entities are imported OK. The problem was hub.offline.insecure_access . This is now the log:
2021-08-04T01:01:18.564Z <EzloController:null> EzloController#ezlo created, config { "source": "wss://10.0.4.119:17000/" } 2021-08-04T01:01:18.564Z <EzloController:null> EzloController#ezlo instance log level (null) (4) 2021-08-04T01:01:18.593Z <Controller:INFO> EzloController#ezlo device data loaded; checking structure 2021-08-04T01:01:18.596Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication; hub.offline.insecure_access must be enabled! 2021-08-04T01:01:18.626Z <Controller:NOTICE> Controller SystemController#reactor_system is now online. 2021-08-04T01:01:18.675Z <Controller:INFO> EzloController#ezlo opening local hub connection to (undefined) at wss://10.0.4.119:17000/ 2021-08-04T01:01:18.675Z <Controller:NOTICE> EzloController#ezlo configured to ignore host ((undefined)) certificate 2021-08-04T01:01:18.677Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000/ 2021-08-04T01:01:18.682Z <app:INFO> Structure running; pausing for controllers' initial ready 2021-08-04T01:01:18.790Z <Controller:INFO> EzloController#ezlo hub websocket connected; inventory hub... 2021-08-04T01:01:18.896Z <Controller:INFO> EzloController#ezlo data load complete; 2 devices received, 7 entities registered; 12 items. 2021-08-04T01:01:18.897Z <Controller:INFO> EzloController#ezlo hub inventory complete/successful; 105ms 2021-08-04T01:01:18.897Z <Controller:NOTICE> Controller EzloController#ezlo is now online. 2021-08-04T01:01:19.152Z <VeraController:WARN> VeraController#vera ignoring geotag ({ "iduser": 1520131, "geotags": [ { "PK_User": 0, "id": 1, "accuracy": 0, "ishome": 1, "notify": 1, "radius": 100, "address": "Via , fi", "color": "006e45", "latitude": "437930", "longitude": "11210", "name": "testi, fi", "status": --null-- } ] }) for user 1520131, user not in user list 2021-08-04T01:01:20.388Z <OWMWeatherController:NOTICE> Controller OWMWeatherController#weather is now online. 2021-08-04T01:01:22.993Z <VeraController:NOTICE> Controller VeraController#vera is now online. -
OK. So first, you need to learn to post code correctly on this site so I can actually see what you're posting. Any code that you post here (including config and log snippets) should have ``` on a line by itself both before and after.
Please repost your controller config, from the
- id:line to the end of the section, just XXX out your username and password. It looks like your config isn't (and wasn't to start) correctly set up. -
thanks for your advice.
Now seems I'm able to import entities from EzloPlus and to access token.
I put the ezlo plus again with previous API set and did some test againmodel: "h2.1" offlineAnonymousAccess: false offlineInsecureAccess: false serial: "90000XXX"in config
controllers: - id: vera enabled: true implementation: VeraController name: My Vera Lite Hub config: source: 'http://10.0.4.44:3480' - id: ezlo enabled: true implementation: EzloController name: My Ezlo Hub config: source: "wss://10.0.4.119:17000" # change the IP address serial: "90000xxx" # put your hub's serial # here username: "xxx" # put your username here betw quotes password: "xxx" # and passwordin the log:
2021-08-05T18:00:23.085Z <app:null> Reactor "1.0.0-21200-16a604f" starting on v14.17.3 2021-08-05T18:00:23.086Z <app:INFO> Process ID 1; platform linux/x64 #41890 SMP Thu Jul 15 03:37:40 CST 2021 2021-08-05T18:00:23.086Z <app:INFO> Basedir /opt/reactor; data in /var/reactor/storage 2021-08-05T18:00:23.131Z <Plugin:null> Module Plugin v21173 2021-08-05T18:00:23.138Z <default:INFO> Module Entity v21177 2021-08-05T18:00:23.141Z <Controller:null> Module Controller v21191 2021-08-05T18:00:23.141Z <default:null> Module Structure v21196 2021-08-05T18:00:23.148Z <default:null> Module Ruleset v21096 2021-08-05T18:00:23.148Z <default:null> Module Rulesets v21096 2021-08-05T18:00:23.166Z <default:null> Module Rule v21168 2021-08-05T18:00:23.173Z <default:null> Module Engine v21197 2021-08-05T18:00:23.173Z <default:null> Module httpapi v21197 2021-08-05T18:00:23.175Z <default:null> Module httpproxy v21054 2021-08-05T18:00:23.187Z <default:null> Module wsapi v21196 2021-08-05T18:00:23.212Z <app:NOTICE> Starting Structure... 2021-08-05T18:00:23.216Z <Structure:NOTICE> Structure#1 plugin ID influx disabled; skipping 2021-08-05T18:00:23.217Z <Structure:INFO> Structure#1 starting controller interface vera (VeraController) 2021-08-05T18:00:23.221Z <Structure:INFO> Structure#1 starting controller interface ezlo (EzloController) 2021-08-05T18:00:23.222Z <Structure:INFO> Structure#1 starting controller interface weather (OWMWeatherController) 2021-08-05T18:00:23.223Z <Structure:INFO> Structure#1 starting controller interface reactor_system (SystemController) 2021-08-05T18:00:23.265Z <default:null> Module VeraController v21195 2021-08-05T18:00:23.269Z <default:null> Module EzloController v21199 2021-08-05T18:00:23.272Z <default:null> Module OWMWeatherController v21140 2021-08-05T18:00:23.273Z <default:null> Module SystemController v21102 2021-08-05T18:00:23.277Z <VeraController:NOTICE> VeraController#vera starting 2021-08-05T18:00:23.326Z <VeraController:INFO> VeraController#vera loaded mapping ver 21177 rev 1 format 1 notice 2021-08-05T18:00:23.339Z <EzloController:null> EzloController#ezlo created, config { "source": "wss://10.0.4.119:17000", "serial": "90000xxx", "username": "xxx", "password": "xxx" } 2021-08-05T18:00:23.339Z <EzloController:null> EzloController#ezlo instance log level (null) (4) 2021-08-05T18:00:23.360Z <Controller:INFO> EzloController#ezlo device data loaded; checking structure 2021-08-05T18:00:23.362Z <Controller:INFO> EzloController#ezlo performing cloud auth to get local access token 2021-08-05T18:00:23.458Z <Controller:NOTICE> Controller SystemController#reactor_system is now online. 2021-08-05T18:00:23.505Z <app:INFO> Structure running; pausing for controllers' initial ready 2021-08-05T18:00:23.945Z <VeraController:WARN> VeraController#vera ignoring geotag ({ "iduser": 1520131, "geotags": [ { "PK_User": 0, "id": 1, "accuracy": 0, "ishome": 1, "notify": 1, "radius": 100, "address": "Via xxx, xxx", "color": "006e45", "latitude": "43xxx", "longitude": "11xxx", "name": "xxx, xxx", "status": --null-- } ] }) for user 1520131, user not in user list 2021-08-05T18:00:25.770Z <Controller:INFO> EzloController#ezlo cloud auth phase complete (local access token acquired) 2021-08-05T18:00:25.770Z <Controller:INFO> EzloController#ezlo opening local hub connection to "90000464" at wss://10.0.4.119:17000 2021-08-05T18:00:25.771Z <Controller:NOTICE> EzloController#ezlo configured to ignore host ("90000464") certificate 2021-08-05T18:00:25.772Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000 2021-08-05T18:00:25.886Z <Controller:NOTICE> EzloController#ezlo successful hub login; performing inventory 2021-08-05T18:00:25.969Z <Controller:INFO> EzloController#ezlo data load complete; 2 devices received, 7 entities registered; 12 items. 2021-08-05T18:00:25.970Z <Controller:INFO> EzloController#ezlo hub inventory complete/successful; 83ms 2021-08-05T18:00:25.972Z <Controller:NOTICE> Controller EzloController#ezlo is now online. 2021-08-05T18:00:27.923Z <VeraController:NOTICE> Controller VeraController#vera is now online. 2021-08-05T18:00:33.533Z <OWMWeatherController:NOTICE> Controller OWMWeatherController#weather is now online. 2021-08-05T18:00:33.534Z <app:NOTICE> Starting Reaction Engine... 2021-08-05T18:00:33.535Z <Engine:INFO> Reaction Engine starting 2021-08-05T18:00:33.535Z <Engine:INFO> Checking rule sets... 2021-08-05T18:00:33.537Z <Engine:INFO> Checking rules... 2021-08-05T18:00:33.537Z <Engine:INFO> Data check complete; no corrections. 2021-08-05T18:00:33.539Z <Engine:5:Engine.js:1081> _process_reaction_queue() entry 628 2021-08-05T18:00:33.540Z <Engine:NOTICE> Reaction Engine running! 2021-08-05T18:00:33.540Z <app:NOTICE> Starting HTTP server and API... 2021-08-05T18:00:33.545Z <app:NOTICE> Startup complete 2021-08-05T18:00:33.546Z <Engine:5:Engine.js:1144> _process_reaction_queue ending with 0 in queue; none delayed/ready; waiting 2021-08-05T18:00:33.548Z <httpapi:NOTICE> HTTP API v1 21197 base URL http://10.0.4.71:8111; listening 2021-08-05T18:00:33.568Z <app:NOTICE> HTTP server running; registering proxy endpoints. 2021-08-05T18:00:33.568Z <app:NOTICE> Starting WSAPI... 2021-08-05T18:00:33.569Z <wsapi:NOTICE> wsapi: starting version 21196 2021-08-05T18:00:33.639Z <Engine:INFO> Engine#1 master timer tick, local time "8/5/2021, 8:00:33 PM" (TZ offset 120 mins from UTC) 2021-08-05T18:00:35.984Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1 2021-08-05T18:00:36.874Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1 2021-08-05T18:08:33.852Z <wsapi:INFO> client "172.17.0.1#2" closed, code=1001, reason= 2021-08-05T18:08:34.228Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1 2021-08-05T18:35:24.207Z <wsapi:INFO> client "172.17.0.1#3" closed, code=1006, reason= 2021-08-05T18:35:24.208Z <wsapi:INFO> client "172.17.0.1#1" closed, code=1006, reason= 2021-08-05T18:49:28.209Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1 2021-08-05T18:49:38.215Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1 2021-08-05T19:00:05.004Z <Engine:INFO> Engine#1 master timer tick, local time "8/5/2021, 9:00:05 PM" (TZ offset 120 mins from UTC)and the dashboard is so fluid and immediate! I love it!
-
just to ask, Is there Importing ReactorSensors from Vera Reactor in synology docker method?
@noelab said in Synology Docker installation:
just to ask, Is there Importing ReactorSensors from Vera Reactor in synology docker method?
So far as I know, the answer is "Yes" - because that's a built-in feature of MSR, and not dependent on the platform on which it is installed.
Coincidentally, I never used the "Import" feature despite having dozens of rather involved Rules back on Reactor for Vera. My reasoning was, (a) I will likely build them better from scratch, (b) this is my chance to re-think a lot of my logic, and (c) with MSR being immensely more powerful, it was a good excuse to learn lexpjs and contribute (as I wound up doing far more than anticipated) to the bug/suggestion log along the way.
MSR 1.0.0 is a masterpiece. Hope you enjoy the transition.
-
@noelab said in Synology Docker installation:
just to ask, Is there Importing ReactorSensors from Vera Reactor in synology docker method?
So far as I know, the answer is "Yes" - because that's a built-in feature of MSR, and not dependent on the platform on which it is installed.
Coincidentally, I never used the "Import" feature despite having dozens of rather involved Rules back on Reactor for Vera. My reasoning was, (a) I will likely build them better from scratch, (b) this is my chance to re-think a lot of my logic, and (c) with MSR being immensely more powerful, it was a good excuse to learn lexpjs and contribute (as I wound up doing far more than anticipated) to the bug/suggestion log along the way.
MSR 1.0.0 is a masterpiece. Hope you enjoy the transition.
@librasun yes, of course I agree with you. In Vera I based my logic using a virtual dimmer (Switchboard Plugin) per room to interact with Alexa commands behind conditions/rules in a Reactorsensor per room and only some global reactor for the house. In this way it is possible to have until 100 voice commands per room associated to 100 preset rules per dimmer, controlling them in web gui, in mobile app or alexa. So at the moment trying to understand if there is a new approach in MSR to emulate virtual devices or to find another way.
-
thanks for your advice.
Now seems I'm able to import entities from EzloPlus and to access token.
I put the ezlo plus again with previous API set and did some test againmodel: "h2.1" offlineAnonymousAccess: false offlineInsecureAccess: false serial: "90000XXX"in config
controllers: - id: vera enabled: true implementation: VeraController name: My Vera Lite Hub config: source: 'http://10.0.4.44:3480' - id: ezlo enabled: true implementation: EzloController name: My Ezlo Hub config: source: "wss://10.0.4.119:17000" # change the IP address serial: "90000xxx" # put your hub's serial # here username: "xxx" # put your username here betw quotes password: "xxx" # and passwordin the log:
2021-08-05T18:00:23.085Z <app:null> Reactor "1.0.0-21200-16a604f" starting on v14.17.3 2021-08-05T18:00:23.086Z <app:INFO> Process ID 1; platform linux/x64 #41890 SMP Thu Jul 15 03:37:40 CST 2021 2021-08-05T18:00:23.086Z <app:INFO> Basedir /opt/reactor; data in /var/reactor/storage 2021-08-05T18:00:23.131Z <Plugin:null> Module Plugin v21173 2021-08-05T18:00:23.138Z <default:INFO> Module Entity v21177 2021-08-05T18:00:23.141Z <Controller:null> Module Controller v21191 2021-08-05T18:00:23.141Z <default:null> Module Structure v21196 2021-08-05T18:00:23.148Z <default:null> Module Ruleset v21096 2021-08-05T18:00:23.148Z <default:null> Module Rulesets v21096 2021-08-05T18:00:23.166Z <default:null> Module Rule v21168 2021-08-05T18:00:23.173Z <default:null> Module Engine v21197 2021-08-05T18:00:23.173Z <default:null> Module httpapi v21197 2021-08-05T18:00:23.175Z <default:null> Module httpproxy v21054 2021-08-05T18:00:23.187Z <default:null> Module wsapi v21196 2021-08-05T18:00:23.212Z <app:NOTICE> Starting Structure... 2021-08-05T18:00:23.216Z <Structure:NOTICE> Structure#1 plugin ID influx disabled; skipping 2021-08-05T18:00:23.217Z <Structure:INFO> Structure#1 starting controller interface vera (VeraController) 2021-08-05T18:00:23.221Z <Structure:INFO> Structure#1 starting controller interface ezlo (EzloController) 2021-08-05T18:00:23.222Z <Structure:INFO> Structure#1 starting controller interface weather (OWMWeatherController) 2021-08-05T18:00:23.223Z <Structure:INFO> Structure#1 starting controller interface reactor_system (SystemController) 2021-08-05T18:00:23.265Z <default:null> Module VeraController v21195 2021-08-05T18:00:23.269Z <default:null> Module EzloController v21199 2021-08-05T18:00:23.272Z <default:null> Module OWMWeatherController v21140 2021-08-05T18:00:23.273Z <default:null> Module SystemController v21102 2021-08-05T18:00:23.277Z <VeraController:NOTICE> VeraController#vera starting 2021-08-05T18:00:23.326Z <VeraController:INFO> VeraController#vera loaded mapping ver 21177 rev 1 format 1 notice 2021-08-05T18:00:23.339Z <EzloController:null> EzloController#ezlo created, config { "source": "wss://10.0.4.119:17000", "serial": "90000xxx", "username": "xxx", "password": "xxx" } 2021-08-05T18:00:23.339Z <EzloController:null> EzloController#ezlo instance log level (null) (4) 2021-08-05T18:00:23.360Z <Controller:INFO> EzloController#ezlo device data loaded; checking structure 2021-08-05T18:00:23.362Z <Controller:INFO> EzloController#ezlo performing cloud auth to get local access token 2021-08-05T18:00:23.458Z <Controller:NOTICE> Controller SystemController#reactor_system is now online. 2021-08-05T18:00:23.505Z <app:INFO> Structure running; pausing for controllers' initial ready 2021-08-05T18:00:23.945Z <VeraController:WARN> VeraController#vera ignoring geotag ({ "iduser": 1520131, "geotags": [ { "PK_User": 0, "id": 1, "accuracy": 0, "ishome": 1, "notify": 1, "radius": 100, "address": "Via xxx, xxx", "color": "006e45", "latitude": "43xxx", "longitude": "11xxx", "name": "xxx, xxx", "status": --null-- } ] }) for user 1520131, user not in user list 2021-08-05T18:00:25.770Z <Controller:INFO> EzloController#ezlo cloud auth phase complete (local access token acquired) 2021-08-05T18:00:25.770Z <Controller:INFO> EzloController#ezlo opening local hub connection to "90000464" at wss://10.0.4.119:17000 2021-08-05T18:00:25.771Z <Controller:NOTICE> EzloController#ezlo configured to ignore host ("90000464") certificate 2021-08-05T18:00:25.772Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000 2021-08-05T18:00:25.886Z <Controller:NOTICE> EzloController#ezlo successful hub login; performing inventory 2021-08-05T18:00:25.969Z <Controller:INFO> EzloController#ezlo data load complete; 2 devices received, 7 entities registered; 12 items. 2021-08-05T18:00:25.970Z <Controller:INFO> EzloController#ezlo hub inventory complete/successful; 83ms 2021-08-05T18:00:25.972Z <Controller:NOTICE> Controller EzloController#ezlo is now online. 2021-08-05T18:00:27.923Z <VeraController:NOTICE> Controller VeraController#vera is now online. 2021-08-05T18:00:33.533Z <OWMWeatherController:NOTICE> Controller OWMWeatherController#weather is now online. 2021-08-05T18:00:33.534Z <app:NOTICE> Starting Reaction Engine... 2021-08-05T18:00:33.535Z <Engine:INFO> Reaction Engine starting 2021-08-05T18:00:33.535Z <Engine:INFO> Checking rule sets... 2021-08-05T18:00:33.537Z <Engine:INFO> Checking rules... 2021-08-05T18:00:33.537Z <Engine:INFO> Data check complete; no corrections. 2021-08-05T18:00:33.539Z <Engine:5:Engine.js:1081> _process_reaction_queue() entry 628 2021-08-05T18:00:33.540Z <Engine:NOTICE> Reaction Engine running! 2021-08-05T18:00:33.540Z <app:NOTICE> Starting HTTP server and API... 2021-08-05T18:00:33.545Z <app:NOTICE> Startup complete 2021-08-05T18:00:33.546Z <Engine:5:Engine.js:1144> _process_reaction_queue ending with 0 in queue; none delayed/ready; waiting 2021-08-05T18:00:33.548Z <httpapi:NOTICE> HTTP API v1 21197 base URL http://10.0.4.71:8111; listening 2021-08-05T18:00:33.568Z <app:NOTICE> HTTP server running; registering proxy endpoints. 2021-08-05T18:00:33.568Z <app:NOTICE> Starting WSAPI... 2021-08-05T18:00:33.569Z <wsapi:NOTICE> wsapi: starting version 21196 2021-08-05T18:00:33.639Z <Engine:INFO> Engine#1 master timer tick, local time "8/5/2021, 8:00:33 PM" (TZ offset 120 mins from UTC) 2021-08-05T18:00:35.984Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1 2021-08-05T18:00:36.874Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1 2021-08-05T18:08:33.852Z <wsapi:INFO> client "172.17.0.1#2" closed, code=1001, reason= 2021-08-05T18:08:34.228Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1 2021-08-05T18:35:24.207Z <wsapi:INFO> client "172.17.0.1#3" closed, code=1006, reason= 2021-08-05T18:35:24.208Z <wsapi:INFO> client "172.17.0.1#1" closed, code=1006, reason= 2021-08-05T18:49:28.209Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1 2021-08-05T18:49:38.215Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1 2021-08-05T19:00:05.004Z <Engine:INFO> Engine#1 master timer tick, local time "8/5/2021, 9:00:05 PM" (TZ offset 120 mins from UTC)and the dashboard is so fluid and immediate! I love it!
@noelab said in Synology Docker installation:
I put the ezlo plus again with previous API set and did some test again
OK. Now that you have a successful cloud authentication, you can enable anonymous access if you wish on the hub using the procedure described here:
Getting Rid of the Ezlo Cloud Login Requirement
Follow the directions carefully -- they will guide you through telling MSR to set the hub flags for you, and then how to reconfigure MSR so that it stops using cloud authentication for access. Also read the warning about the risks of using anonymous access. The risks of not using it are also described; only you can judge which is the right path for you.
-
For the record, I'm using "Hyper Backup" - a native Synology NAS app - to backup my entire /REACTOR folder structure to a folder in my Google Drive cloud account. Suggest other MSR users consider doing something similar, in the event of a local NAS drive malfunction.
-
T toggledbits locked this topic on
How To: Migrate Rules from the Reactor Vera Plugin - Reactor - Multi-Hub Automation