Synology Docker installation

LibraSun

Beneath your pay grade sir.

toggledbits

No job too big or too small. If it needs to get done, I'm happy to do it.

LibraSun

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.

toggledbits

I've also rolled 21062 (today's daily build) into a docker container for Synology. Link is in PR #58 on the bug tracker.

LibraSun

Installed. Works like a charm. Your instructions were spot on, as per usual.

toggledbits

We can both thank @kfxo for those instructions!

noelab

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

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

does anyone have any advice?

toggledbits

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.

noelab

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 password

then config

set_anonymous_access: true   <--- add this line, same indent as previous

then with

“offlineInsecureAccess” enabled:true

the 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, 1002

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

toggledbits

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.

noelab

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 again

model: "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 password

in 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

just to ask, Is there Importing ReactorSensors from Vera Reactor in synology docker method?

How To: Migrate Rules from the Reactor Vera Plugin - Reactor - Multi-Hub Automation

LibraSun

@noelab said in Synology Docker installation:

just to ask, Is there Importing ReactorSensors from Vera Reactor in synology docker method?

How To: Migrate Rules from the Reactor Vera Plugin - Reactor - Multi-Hub Automation

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

This post is deleted!

noelab

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

toggledbits

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

LibraSun

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.

Gradually turn on lights.

Stop the MSR by an external switch on Hubitat.

Error After Upgrade

Reset attribute value of entity in event handler

Need help figuring out how to delay a reset on reaction

Way to search for rules (rule state) in other rules

Links to MSR from HA

Set Reaction > Script Action

Errors after updating to MQTTController build 25139

🎉 My very first MSR controller: OpenSprinkler

Advice reqeusted to migrate MSR from Bare Metal to Container

Reactor (Multi-System/Multi-Hub) Announcements

Can´t restart or upgrade/deploy MSR

[Solved] Limit HA Entity in MSR

Organizing/ structuring rule sets and rules

Moving MSR from a QNAP container to RP 5 - some issues

Widget deletion does not work and landing page (status) is empy

Need help reducing false positive notifications

Deleting widgets

MQTT configuration question

Synology Docker installation

Recent Topics