@toggledbits, not sure if this is a feature request or I'm using the search tool wrong. You have a "Search for rule" in the Rules Set tab in MSR. It works nicely to find a rule and bring up said rule, but can it/could it be used for as a "where used?" global search? For instance, I have a fairly large set of rules, divided up into 10 different rulesets. There's easily a hundred individual rules, and many of the rules have Rule State triggers, which of course refer to other rules. Amongst my troubleshooting today, I came across what may have been a duplicate or troubleshooting attempt, but I can't tell if it's actually used as a Rule State in another rule without opening each rule that I suspect it may be a part of.
Thanks.
I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI:
An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status
Last 11:20:37
My MQTT configuration (local_mqtt_devices.yaml) for the related entity is:
layzspa_message:
type: ValueSensor
capabilities: ["temperature_sensor", "value_sensor", "power_sensor"]
primary_attribute: power_sensor.value
events:
"layzspa/message":
"power_sensor.value":
json_payload: true
if_expr: '! isnull( payload?.PWR )'
expr: "float(payload.PWR)"
"value_sensor.air":
json_payload: true
if_expr: '! isnull( payload?.AIR )'
expr: "float(payload.AIR)"
"value_sensor.pump":
json_payload: true
if_expr: '! isnull( payload?.FLT )'
expr: "float(payload.FLT)"
"value_sensor.god":
json_payload: true
if_expr: '! isnull( payload?.GOD )'
expr: "float(payload.GOD)"
"value_sensor.lock":
json_payload: true
if_expr: '! isnull( payload?.LCK )'
expr: "float(payload.LCK)"
"value_sensor.unit":
json_payload: true
if_expr: '! isnull( payload?.UNT )'
expr: "float(payload.UNT)"
"value_sensor.error":
json_payload: true
if_expr: '! isnull( payload?.ERR )'
expr: "float(payload.ERR)"
"temperature_sensor.green":
json_payload: true
if_expr: '! isnull( payload?.GRN )'
expr: "float(payload.GRN)"
"temperature_sensor.red":
json_payload: true
if_expr: '! isnull( payload?.RED )'
expr: "float(payload.RED)"
"temperature_sensor.target":
json_payload: true
if_expr: '! isnull( payload?.TGT )'
expr: "float(payload.TGT)"
"temperature_sensor.value":
json_payload: true
if_expr: '! isnull( payload?.TMP )'
expr: "float(payload.TMP)"
"temperature_sensor.virtual":
json_payload: true
if_expr: '! isnull( payload?.VTM )'
expr: "round(float(payload.VTM), 1)"
"temperature_sensor.ambient":
json_payload: true
if_expr: '! isnull( payload?.AMB )'
expr: "float(payload.AMB)"
"layzspa/Status":
"value_sensor.status":
if_expr: '! isnull( payload )'
expr: "payload"
"layzspa/button":
"value_sensor.button":
if_expr: '! isnull( payload )'
expr: "payload"
and in reactor.yaml I have:
"layzspa_states":
name: "Lay-Z-Spa States"
friendly_name: 'Lay-Z-Spa States'
include: layzspa_message
I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded).
Get it at (install is similar to MQTTController and such):
https://github.com/dbochicchio/reactor-opensprinkler
Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty.
Since I've learnt a lot from this controller, I'll explore new controllers soon.
Good day all,
I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing.
I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container.
Has anyone done this? Any advice?
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.
Hi guys,
Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular.
Maybe there are better ways to organize my rule sets.
I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
I have the following yaml configuration in local_mqtt_devices file
x_mqtt_device:
set_speed:
arguments:
speed:
type: str
topic: "command/%friendly_name%"
payload:
type: json
expr: '{ "fan": parameters.speed }'
While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Hi!
I get this message when I'm on the status tab:
System Configuration Check
The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds.
I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6.
HA versions are:
Core 2025.3.4
Supervisor 2025.03.4
Operating System 15.1
I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version.
Do anyone know what I can try?
Thanks in advance!
Let's Be Careful Out There (Hill Street reference...)
/Fanan
Synology Docker installation
-
FYI, I can move them also.
-
No job too big or too small. If it needs to get done, I'm happy to do it.
-
Strictly FYI, I've gone ahead and installed NODE.JS v12 on my Synology NAS in anticipation of attempting the Reactor backup conversion to MSR Rulesets. In my Linux-challenged mind, that's a step in the right direction. Next, I'll need to (re-)learn how to SSH into the NAS for executing Terminal commands. Will let you know if this gets me further along that trajectory.
EDIT: Nope, I was clearly jumping the gun. Will have to take another tack.
-
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.
How To: Migrate Rules from the Reactor Vera Plugin - Reactor - Multi-Hub Automation
