Navigation

    Discussion Forum to share and further the development of home control and automation, independent of platforms.

    SmartHome Community
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Unsolved
    1. Home
    2. noelab

    • Fun Stuff

      toggledbits

      In the background of other work, I've been putting together a build system for the OpenWrt version that Ezlo is using on the Plus. Job done. I can build pretty much any package, which may come in handy some day.

      As a test of that, I thought, why not build nodejs... and you know where that leads, right?

      It took some doing. There are a lot of dependencies, and the errors you get when the dependencies aren't met correctly can be cryptic and took quite a bit of research and experimentation to resolve... weeks, in fact, over a couple of hours here, a couple there.

      But it's done and I now have Reactor running on an Ezlo Plus.

      I'm not sure what the long term utility of this might be. Since the new Ezlo philosophy is to upgrade your system automatically on reboots, and so far the upgrades have wiped substantial parts of the file system in my experience, this could be a non-starter as a platform — you wouldn't want your automations to get blown off the machine every time Ezlo upgrades firmware (because you don't know when that's going to be, and Murphy says it will be while you are on vacation with no remote access). But, if there is some place it can be tucked away safely, or if, as probably should be demanded by the user community, updates become elective and user-driven, it actually makes a nice Pi-ish platform to run on.

      On to the next skunkworks project...

      Multi-System Reactor

    • Reactor log timestamps

      B

      Timestamps do not match the UI time or the system time:

      [latest-21286]2021-10-16T03:10:43.922Z <Engine:INFO> Engine#1 master timer tick, local time "10/15/2021, 8:10:43 PM" (TZ offset -420 mins from UTC)

      I tried adding TZ to the docker container with "docker exec reactor apk add tzdata" but there was no change in log timestamps. I have the TZ in the compose file as:

      environment: REACTOR_DATA_PREFIX: /var/reactor TZ: America/Los_Angeles

      This does set the UI time correctly. The Reactor config is also set correctly:

      location: city: "Los Angeles"
      Multi-System Reactor

    • Sending a service request to Home Assistant

      B

      I'd like to invoke in Reactor a Home Assistant service through the HA API. I use the following code in a vera plugin I wrote to send an HTTP request to Home Assistant to trigger an announcement on Alexa--using a Home Assistant Alexa integration that you can install through HACS.

      myEchoDevice = "alexa_media_".. myEchoDevice myEchoMessage = table.concat(myEchoMessage) local request_body = json.encode {message = myEchoMessage, data = {["type"] = "announce",method = "all"}} local response_body = {} local theURL = 'http://'..HomeAssistantIP..':'..HomeAssistantPort..'/api/services/notify/'..myEchoDevice r, c, h = http.request { url = theURL, method = "POST", headers = { ["Content-Type"] = "application/json", ["Authorization"] = "Bearer ".. HomeAssistantToken, ["Content-Length"] = request_body:len() }, source = ltn12.source.string(request_body), sink = ltn12.sink.table(response_body) }

      I don't see the "notify" service in the HA attributes revealed by reactor. Is there a way to access the Home Assistant API through reactor, or do I need to use HTTP requests to initiate services.

      Multi-System Reactor

    • How to? Rule for Vera "Can't Detect Device" errors and reset

      cw-kid

      Hi

      I have some devices on my Vera Plus controller that sometimes change to say "Can't detect device".

      I can clear those red banners that show up in the Vera UI7 web GUI, for a device by running some LUA code like this:

      luup.set_failure(0, 331)

      Maybe I can use the new MSR matchEntities to find and detect any devices on Vera that have developed the "Can't detect device" error and then reset them. ?

      I can currently manually specify a particular problem device in a ruleset trigger like this:

      6f789006-ce19-4776-b3dd-290e28e84c8b-image.png

      But if I could have a rule that automatically detects any device that develops this problem that would be better.

      Thanks

      Multi-System Reactor

    • Logic loop? Throttling...

      W

      Hi Patrick! @toggledbits

      I don't remember before version 21277 receiving this kind of message.

      dbea16f0-39f8-475a-bee8-8899069f2db3-image.png

      This is in the log, this warning appears hundreds of times, every 1 second it repeats.

      [latest-21281]2021-10-10T16:13:46.107Z Rule:WARN Rule#rule-ku32lfti (Warning (93) Devices) update rate 61/min exceeds limit (60/min)! Logic loop? Throttling...
      [latest-21281]2021-10-10T16:13:46.482Z Rule:WARN Rule#rule-ku32lfti (Warning (93) Devices) update rate 61/min exceeds limit (60/min)! Logic loop? Throttling...
      [latest-21281]2021-10-10T16:13:46.835Z Rule:WARN Rule#rule-ku32lfti (Warning (93) Devices) update rate 61/min exceeds limit (60/min)! Logic loop? Throttling...

      As you can see, the rule that has generated this warning is run on demand at 10am, where the information is loaded into local variables, and then I use it to send the information by Telegram, only once a day.

      5d55901a-bcbe-4cd6-8989-01d7a0ff9c67-image.png

      I started using this matchEntities() instruction recently when it was made available, and I see you have been making recent adjustments. Wouldn't this situation of continuing to evaluate be related?

      I will turn the rule off, so as not to generate this situation that surely damages the functioning of the MSR, and I look forward to your comments please.

      Thanks

      Multi-System Reactor

    • "kinda smart" switch to put behind a normal light switch

      H

      Hello!

      I want to trigger an event (like switching on a smart Zigbee power plug) when a regular light switch (that switches regular non-smart LED light bulbs) is flipped. Is there something I can put behind a light switch to achieve this? Or something to splice in between the switch and the light bulbs? A good option would also be Hue compatible.

      Thank you!

      General Discussion

    • The syntax of locale

      F

      Hi!
      I would like to try out the swedish translation (thanks @Crille ). I have tried to edit my reactor.yaml file in many ways, but the translation don't show up. I have done a browser hard refresh every time. Where do I go wrong? Here's my latest try:

      - id: reactor_system enable: true implementation: SystemController name: Reactor System config: # # The update_interval can be set lower for more frequent updates. The default is 60 # seconds, which is probably fine for most cases, but causes the 15-second load av- # erage to be inaccurate (the first value in reactor_system.system_load). If you # don't care about the 15-second load average, then the default 60 seconds is fine. # This value is expressed in milliseconds. update_interval: 60000 locale: sv-SE #

      What's the correct syntax, placement and intendention?
      Thanks!
      /Fanan

      Multi-System Reactor

    • Reactor (Multi-System/Multi-Hub) Announcements

      toggledbits

      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

    • Flapping device

      tunnus

      Got a warning that "Rule is being throttled because its update rate exceeds 60 updates per minute. Check for logic errors that may be causing an evaluation loop, or devices that are "flapping".

      Device in question here is Aeotec Smart Switch 6 connected to Vera Plus, and its configuration is below:

      Screenshot 2021-08-31 at 13.13.22.png

      Shouldn't be an evaluation loop as the rule is very simple (two AND'ed conditions where the first checks whether alarm state is "disarmed" and the second if smart switch power switch state is false).

      Noticed though at the time of warning that wattage measured/reported was changing quite rapidly, so even though wattage was not used in the rule, could that be the reason for throttling? If so, is there anything else that could be done other than raising minimum change values in device configuration? Would like to retain sensitivity for other purposes.

      Multi-System Reactor

    • Ordering of global expressions

      tunnus

      Just noticed that when trying to reorder some expressions, e.g. move the most recent one from the bottom of the list to the first, this new order didn't "stick".

      At first yes, but when visiting some other menus (obviously saving before that) and then coming back, the moved item was in its original position (in the end of the list).

      I currently have 29 global expressions (which may or may not have some relevance to this problem). Using build 21281 on linux.

      Can log a PR with logs, if this seems hard to reproduce.

      Multi-System Reactor

    • Trouble connecting Vera to MSR

      A

      Hey crew, I followed the tutorial to get MSR installed on Rasbperry Pi (bare metal). Just having a little trouble getting Vera to connect to it.

      I'm getting error messages-- I searched in the forum and didn't see other people running into these messages. Here are the two main errors I've been getting...

      2021-09-21T01:30:36.477Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632187836460 failed, reason: socket hang up

      and

      2021-09-21T01:26:08.296Z <VeraController:ERR> VeraController#vera update request failed: FetchError: request to http://10.0.0.141:3480/data_request?id=user_data&ns=1&Timeout=15&output_format=json&_r=1632187568275 failed, reason: connect ECONNREFUSED 10.0.0.141:3480

      I'm sure it'll be an easy fix, but truthfully I'm stumped here and would love any advice. Thank you!

      Multi-System Reactor

    • Localization

      Crille

      @toggledbits I've done a (test) Swedish translation for MSR, I don't want/need a translated version, but I had the time and perhaps some future users would find it useful 🙂
      I noticed it's a bit early in the process to go live with systemwide localizations so no github in place yet, do you want input on this now or should we wait a few releases? considering it may be low priority issues.
      If so, do you want feedback here or in mantis?

      Multi-System Reactor

    • Array manipulation

      tunnus

      Let's say I have an array like the one below:

      ["vera>device_216","vera>device_235","vera>device_241"]

      How do I remove "vera>device_235" out of it?

      Alternatively, when filtering entities:

      each id in dynamic_array: getEntity( id ).attributes.x_vera_svc_micasaverde_com_HaDevice1?.CommFailure == 1 ? id : null

      How could I exclude certain id from the array that is produced?

      Multi-System Reactor

    • Bluetooth Control - Vera / Openluup

      parkerc

      Hi,

      Is anyone aware of any way in which Bluetooth devices can be connected and controlled via a home automation controller, such as Vera / openluup (even NodeRed, HASS) etc ?

      I recall Bluetooth was an original ‘feature’ on the Veraplus but that soon died a death, and was never heard of again.

      What, if anything are people doing with Bluetooth ?

      General Discussion

    • How to monitor sensors that stop working?

      A

      I have some battery powered sensors that doesn't report battery level and thought it would be nice if can make MSR to send me a notification if a sensor value doesn't change for 24h.

      I tried to make a rule that monitored if a temperature value NOT changes, but in this setup I couldn't choose Sustained For as I expected.
      Any way around this?
      Any reason that Sustained For can't be used when monitoring a value Change?

      Multi-System Reactor

    • EzloController error

      Crille

      @toggledbits Today I got a false positive from Reactor saying my Ezlo Plus was offline, a restart of Reactor solved it.
      This was found in the log before the restart:

      2021-10-01T06:32:29.441Z <EzloController:ERR> EzloController#ezlo ws_message handler failed: RangeError: Maximum call stack size exceeded 2021-10-01T06:32:29.441Z <EzloController:CRIT> RangeError: Maximum call stack size exceeded RangeError: Maximum call stack size exceeded at EzloController._now.ws_message [as refreshTime] (/home/user/reactor/server/lib/EzloController.js:1134:127) at EzloController._now.ws_message [as refreshTime] (/home/user/reactor/server/lib/EzloController.js:1138:54) at EzloController._now.ws_message [as refreshTime] (/home/user/reactor/server/lib/EzloController.js:1138:54) at EzloController._now.ws_message [as refreshTime] (/home/user/reactor/server/lib/EzloController.js:1138:54) at EzloController._now.ws_message [as refreshTime] (/home/user/reactor/server/lib/EzloController.js:1138:54) at EzloController._now.ws_message [as refreshTime] (/home/user/reactor/server/lib/EzloController.js:1138:54) at EzloController._now.ws_message [as refreshTime] (/home/user/reactor/server/lib/EzloController.js:1138:54) at EzloController._now.ws_message [as refreshTime] (/home/user/reactor/server/lib/EzloController.js:1138:54) at EzloController._now.ws_message [as refreshTime] (/home/user/reactor/server/lib/EzloController.js:1138:54) at EzloController._now.ws_message [as refreshTime] (/home/user/reactor/server/lib/EzloController.js:1138:54) 2021-10-01T06:32:38.985Z <EzloController:ERR> EzloController#ezlo request "17c3a8dccaf" (hub.info.get) failed: TimedPromise timeout 2021-10-01T06:32:38.985Z <EzloController:ERR> EzloController#ezlo failed to complete inventory: TimedPromise timeout 2021-10-01T06:32:38.985Z <EzloController:CRIT> !TimedPromise timeout 2021-10-01T06:32:38.988Z <EzloController:NOTICE> EzloController#ezlo connection closed: 1002

      Reactor latest-21270-48528ec, updated to latest-21270-46679ac just now.

      Multi-System Reactor

    • Synology Docker installation

      LibraSun

      @toggledbits I followed to the letter your excellent step-by-step guide on launching a Docker container from the image I fetched from PR #58 this morning.

      All proceeded swimmingly – folder creation, image upload, settings & parameters, etc. – until the moment of actual Launch.

      Whereupon, Docker threw up the following on-screen "Stopped Unexpectedly" warning (which repeated every 30 seconds or so until I Stop'ped the container from running/restarting):
      docker_msr_stopped.png

      Concurrently, every attempt to access http://<mySynNAS_IP>:8111/ resulted in a "This site can't be reached" error page in Chrome (under Windows, mind you).

      Immediately, I took the liberty of inspecting and Export'ing the logfile (Container ► Details ► Log) as an HTML file, which I attach below (oops, no attachment feature in this forum, so here is the direct link) for your inspection.

      Hope you find some clues, because I'm not at all sure where things went wrong. (The only facet of setup where I expressly deviated from your typed notes involved creating a "Shared" (i.e. top-level, rather than under /home) folder called "Reactor" with r/w access, under which I created a subfolder named "Data", to which I pointed /var/reactor during container creation.)

      Excellent write-up and thanks for the chance to test this out!!

      Libra

      FOLLOW-UP NOTES
      I do see where Container ► Edit ► Environment ► variable PATH has a value of "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" which strikes me as odd, but maybe that's normal nomenclature? (By contract, Windows and DOS always use semicolons, not colons, to separate PATH variable entries.)

      RESOLVED
      Noting that the Log displayed an error message related to /var/reactor/config, I went and created a folder named 'config' (all lowercase) under the NAS's top-level Reactor\Data folder, then restarted the container. It's running fine now, and I'm able to access the :8111 interface for the first time.
      Log ► "Configuration path: /var/reactor/config resolved /var/reactor/config"

      SUGGEST
      Please add explicit declaration in your How-To regarding the need for a /config underneath the data folder.

      Multi-System Reactor

    • Plugin Influxdb 2.0

      N

      Hi, I was trying to setup influxdb for MSR and on my Synology Nas, docker installation, I started with Influxdb 2.0.
      Now seems it is very different from 1.x.
      Databases don't exist anymore, they are named "buckets" now and there are token values.
      Looking around, I found something on HA like this in "configuration.yaml" file.

      influxdb: api_version: 2 ssl: false host: 10.0.0.11 port: 8086 token: Your HomeAssistant - Write token organization: Home bucket: HomeAssistant

      I don't use HA, just starting to bring devices on ezlo plus. Does MSR support this version Influxdb 2.0? or better to re-install 1.x?

      Thanks in advance

      Multi-System Reactor

    • Docker Compose

      B

      I did a fresh install of MSR yesterday and noticed that the latest docker image was not pulling down. I had to use the CLI command "docker-compose pull MSR" where "MSR" is the service name I gave to the container in docker compose. After pulling the image, most everything worked as expected and the localization bug I saw was resolved. I've seen this type of update behavior before in other containers-- usually when the docker tags are not updated, but it could be something wacky on my end as well.

      I also saw a small bug in the config file that I tried to post on Mantis, but I could not log in. Are you using the bug tracker, or do you prefer forum posts?

      Multi-System Reactor

    • What notification system is best?

      A

      Hi everyone

      I'm about to set up notifications from MSR and would like input on what works best.
      Quick and reliable delivery to Android devices is the goal.

      (Tried to set up pushover last night, but probably missed something because it doesn't work. Succeed thru homeassistant, but not with MSR.)

      Is pushover worth its money?
      what do you use and why?

      Greatly appreciate your thoughts 🙂

      Multi-System Reactor
    For those who registered but didn't received the confirmation email, please send an email to support@smarthome.community with the email you used
    N
    • Profile
    • Following 0
    • Followers 0
    • Topics 1
    • Posts 12
    • Best 2
    • Groups 0

    noelab

    @noelab

    10
    Reputation
    5
    Profile views
    12
    Posts
    0
    Followers
    0
    Following
    Joined Last Online
    noelab Unfollow Follow

    Best posts made by noelab

    • RE: Release 1.0.0

      Hi everybody!
      I was following this web site as non-member. Finally I have a new Synology Nas to try the new @toggledbits 's reactor project and this post is first of all to thank @toggledbits for his effort and passion to share his projects and to make them accessible even for those who are not a programmer. I know many of you reading the posts from the vera community and would like to express my gratitude for the advice you give to understand things. So a big Thanks and congratulations to Patrick for this new project !!!
      I just installed MSR and I am excited to try it out!

      posted in Multi-System Reactor
      N
      noelab
    • RE: Synology Docker installation

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

      posted in Multi-System Reactor
      N
      noelab

    Latest posts made by noelab

    • RE: EzloController error

      Now it's working again after I powered off/on ezlo controller and restarted Reactor. The log is too long, no privileges to upload it. It's not the first time it happens upgrating the container.
      ezloplus Firmware: 2.0.19.1714.2
      Thanks anyway.

      [latest-21281]2021-10-08T21:55:33.176Z <Controller:INFO> EzloController#ezlo hub inventory complete/successful; 837ms
[latest-21281]2021-10-08T21:55:33.179Z <Controller:NOTICE> Controller EzloController#ezlo is now online.
      posted in Multi-System Reactor
      N
      noelab
    • RE: EzloController error

      It's Docker on Synology

      [latest-21281]2021-10-08T21:17:51.677Z <app:null> Reactor latest-21281-c4807c0 starting on v14.17.3
[latest-21281]2021-10-08T21:17:51.678Z <app:INFO> Process ID 1; platform linux/x64 #41890 SMP Thu Jul 15 03:37:40 CST 2021; locale (undefined)
[latest-21281]2021-10-08T21:17:51.678Z <app:INFO> Basedir /opt/reactor; data in /var/reactor/storage
[latest-21281]2021-10-08T21:17:51.679Z <app:INFO> NODE_PATH /opt/reactor
[latest-21281]2021-10-08T21:17:51.691Z <app:INFO> Configured locale (undefined); selected locale(s) en-US.UTF-8
[latest-21281]2021-10-08T21:17:51.746Z <app:INFO> Loaded locale en-US
[latest-21281]2021-10-08T21:17:51.880Z <Plugin:null> Module Plugin v21173
[latest-21281]2021-10-08T21:17:51.888Z <default:INFO> Module Entity v21260
[latest-21281]2021-10-08T21:17:51.891Z <Controller:null> Module Controller v21278
[latest-21281]2021-10-08T21:17:51.891Z <default:null> Module Structure v21270
[latest-21281]2021-10-08T21:17:51.900Z <default:null> Module Ruleset v21096
[latest-21281]2021-10-08T21:17:51.900Z <default:null> Module Rulesets v21096
[latest-21281]2021-10-08T21:17:51.922Z <default:null> Module Rule v21278
[latest-21281]2021-10-08T21:17:51.978Z <default:null> Module Engine v21277
[latest-21281]2021-10-08T21:17:51.978Z <default:null> Module httpapi v21278
[latest-21281]2021-10-08T21:17:51.987Z <default:null> Module httpproxy v21054
[latest-21281]2021-10-08T21:17:52.004Z <default:null> Module wsapi v21274
[latest-21281]2021-10-08T21:17:52.075Z <app:NOTICE> Starting Structure...
[latest-21281]2021-10-08T21:17:52.079Z <Structure:NOTICE> Structure#1 plugin ID influx disabled; skipping
[latest-21281]2021-10-08T21:17:52.081Z <Structure:INFO> Structure#1 starting controller interface vera (VeraController)
[latest-21281]2021-10-08T21:17:52.085Z <Structure:INFO> Structure#1 starting controller interface ezlo (EzloController)
[latest-21281]2021-10-08T21:17:52.086Z <Structure:INFO> Structure#1 starting controller interface weather (OWMWeatherController)
[latest-21281]2021-10-08T21:17:52.087Z <Structure:INFO> Structure#1 starting controller interface reactor_system (SystemController)
[latest-21281]2021-10-08T21:17:52.173Z <default:null> Module VeraController v21271
[latest-21281]2021-10-08T21:17:52.180Z <default:null> Module EzloController v21274
[latest-21281]2021-10-08T21:17:52.183Z <default:null> Module OWMWeatherController v21278
[latest-21281]2021-10-08T21:17:52.184Z <default:null> Module SystemController v21102
[latest-21281]2021-10-08T21:17:52.192Z <VeraController:NOTICE> VeraController#vera starting
[latest-21281]2021-10-08T21:17:52.246Z <VeraController:INFO> VeraController#vera loaded mapping ver 21274 rev 1 format 1 notice 
[latest-21281]2021-10-08T21:17:52.247Z <VeraController:INFO> VeraController: deviceclass vera_system_object capability sys_system does not provide attribute state
[latest-21281]2021-10-08T21:17:52.295Z <EzloController:null> EzloController#ezlo created, config { "source": "wss://10.0.4.119:17000", "serial": "XXXXXXXXXX" }
[latest-21281]2021-10-08T21:17:52.295Z <EzloController:null> EzloController#ezlo instance log level (null) (4)
[latest-21281]2021-10-08T21:17:52.314Z <Controller:INFO> EzloController#ezlo device mapping data loaded; checking...
[latest-21281]2021-10-08T21:17:52.316Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
[latest-21281]2021-10-08T21:17:52.346Z <Controller:NOTICE> Controller SystemController#reactor_system is now online.
[latest-21281]2021-10-08T21:17:52.374Z <Controller:INFO> EzloController#ezlo opening hub connection to "XXXXXXXXXX" at wss://10.0.4.119:17000
[latest-21281]2021-10-08T21:17:52.376Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
[latest-21281]2021-10-08T21:17:52.381Z <app:INFO> Structure running; pausing for controllers' initial ready
[latest-21281]2021-10-08T21:17:52.632Z <OWMWeatherController:INFO> OWMWeatherController#weather done; 1 locations, 0 failed
[latest-21281]2021-10-08T21:17:52.634Z <OWMWeatherController:NOTICE> Controller OWMWeatherController#weather is now online.
[latest-21281]2021-10-08T21:17:53.307Z <VeraController:NOTICE> Controller VeraController#vera is now online.
[latest-21281]2021-10-08T21:18:22.427Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
[latest-21281]2021-10-08T21:18:22.428Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
[latest-21281]2021-10-08T21:18:22.429Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
[latest-21281]2021-10-08T21:18:27.433Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
[latest-21281]2021-10-08T21:18:27.433Z <Controller:INFO> EzloController#ezlo opening hub connection to "XXXXXXXXXX" at wss://10.0.4.119:17000
[latest-21281]2021-10-08T21:18:27.434Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
[latest-21281]2021-10-08T21:18:52.386Z <app:NOTICE> Starting HTTP server and API...
[latest-21281]2021-10-08T21:18:52.392Z <app:NOTICE> Starting Reaction Engine...
[latest-21281]2021-10-08T21:18:52.393Z <Engine:INFO> Reaction Engine starting
[latest-21281]2021-10-08T21:18:52.393Z <Engine:INFO> Checking rule sets...
[latest-21281]2021-10-08T21:18:52.445Z <Engine:INFO> Checking rules...
[latest-21281]2021-10-08T21:18:52.446Z <Engine:INFO> Data check complete; no corrections.
[latest-21281]2021-10-08T21:18:52.485Z <Engine:5:Engine.js:1350> _process_reaction_queue() entry 630
[latest-21281]2021-10-08T21:18:52.500Z <Rule:5:Rule.js:623> Rule#rule-kuhickgs cleaning loaded condition states
[latest-21281]2021-10-08T21:18:52.501Z <Engine:5:Engine.js:886> Engine: new rule rule-kuhickgs ((undefined)), creating!
[latest-21281]2021-10-08T21:18:52.522Z <Rule:5:Rule.js:623> Rule#rule-ku1myjlz cleaning loaded condition states
[latest-21281]2021-10-08T21:18:52.522Z <Engine:5:Engine.js:886> Engine: new rule rule-ku1myjlz ((undefined)), creating!
[latest-21281]2021-10-08T21:18:52.534Z <Rule:5:Rule.js:623> Rule#rule-ks5pci0k cleaning loaded condition states
[latest-21281]2021-10-08T21:18:52.534Z <Engine:5:Engine.js:886> Engine: new rule rule-ks5pci0k ((undefined)), creating!
[latest-21281]2021-10-08T21:18:52.536Z <Rule:5:Rule.js:623> Rule#rule-ks5pdqcs cleaning loaded condition states
[latest-21281]2021-10-08T21:18:52.536Z <Engine:5:Engine.js:886> Engine: new rule rule-ks5pdqcs ((undefined)), creating!
[latest-21281]2021-10-08T21:18:52.537Z <Rule:5:Rule.js:623> Rule#rule-ks5pbeg9 cleaning loaded condition states
[latest-21281]2021-10-08T21:18:52.538Z <Engine:5:Engine.js:886> Engine: new rule rule-ks5pbeg9 ((undefined)), creating!
[latest-21281]2021-10-08T21:18:52.539Z <Rule:5:Rule.js:623> Rule#rule-ks5p8t6m cleaning loaded condition states
[latest-21281]2021-10-08T21:18:52.539Z <Engine:5:Engine.js:886> Engine: new rule rule-ks5p8t6m ((undefined)), creating!
[latest-21281]2021-10-08T21:18:52.540Z <Rule:5:Rule.js:623> Rule#rule-ks3j24qn cleaning loaded condition states
[latest-21281]2021-10-08T21:18:52.541Z <Engine:5:Engine.js:886> Engine: new rule rule-ks3j24qn ((undefined)), creating!
[latest-21281]2021-10-08T21:18:52.549Z <Rule:5:Rule.js:623> Rule#rule-ktrlog1t cleaning loaded condition states
[latest-21281]2021-10-08T21:18:52.549Z <Engine:5:Engine.js:886> Engine: new rule rule-ktrlog1t ((undefined)), creating!
[latest-21281]2021-10-08T21:18:52.550Z <Rule:5:Rule.js:623> Rule#rule-ktrlox2g cleaning loaded condition states
[latest-21281]2021-10-08T21:18:52.550Z <Engine:5:Engine.js:886> Engine: new rule rule-ktrlox2g ((undefined)), creating!
[latest-21281]2021-10-08T21:18:52.551Z <Rule:5:Rule.js:623> Rule#rule-ktrlp04x cleaning loaded condition states
[latest-21281]2021-10-08T21:18:52.552Z <Engine:5:Engine.js:886> Engine: new rule rule-ktrlp04x ((undefined)), creating!
[latest-21281]2021-10-08T21:18:52.553Z <Rule:5:Rule.js:623> Rule#rule-ktrlp2cn cleaning loaded condition states
[latest-21281]2021-10-08T21:18:52.553Z <Engine:5:Engine.js:886> Engine: new rule rule-ktrlp2cn ((undefined)), creating!
[latest-21281]2021-10-08T21:18:52.554Z <Rule:5:Rule.js:623> Rule#rule-ktrlp4il cleaning loaded condition states
[latest-21281]2021-10-08T21:18:52.555Z <Engine:5:Engine.js:886> Engine: new rule rule-ktrlp4il ((undefined)), creating!
[latest-21281]2021-10-08T21:18:52.556Z <Rule:5:Rule.js:623> Rule#rule-ktrlp6j9 cleaning loaded condition states
[latest-21281]2021-10-08T21:18:52.556Z <Engine:5:Engine.js:886> Engine: new rule rule-ktrlp6j9 ((undefined)), creating!
[latest-21281]2021-10-08T21:18:52.557Z <Rule:5:Rule.js:623> Rule#rule-ktrlp8v2 cleaning loaded condition states
[latest-21281]2021-10-08T21:18:52.557Z <Engine:5:Engine.js:886> Engine: new rule rule-ktrlp8v2 ((undefined)), creating!
[latest-21281]2021-10-08T21:18:52.558Z <Rule:5:Rule.js:623> Rule#rule-ktrlpbmt cleaning loaded condition states
[latest-21281]2021-10-08T21:18:52.558Z <Engine:5:Engine.js:886> Engine: new rule rule-ktrlpbmt ((undefined)), creating!
[latest-21281]2021-10-08T21:18:52.559Z <Rule:5:Rule.js:623> Rule#rule-ktrlpdzf cleaning loaded condition states
      posted in Multi-System Reactor
      N
      noelab
    • RE: EzloController error

      @noelab

      [latest-21281]2021-10-08T20:37:59.635Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
[latest-21281]2021-10-08T20:38:06.565Z <Rule:5:Rule.js:763> Rule#rule-ks56pa4y dependency notification timer-trigger Timer#rule-ks56pa4y from Timer#rule-ks56pa4y
[latest-21281]2021-10-08T20:38:06.566Z <Rule:5:Rule.js:769> Rule#rule-ks56pa4y requesting eval; timer-trigger Timer#rule-ks56pa4y
[latest-21281]2021-10-08T20:38:06.566Z <Rule:5:Rule.js:982> Rule#rule-ks56pa4y (vK DLT 8 Delay OFF ) evaluate() acquiring mutex
[latest-21281]2021-10-08T20:38:06.569Z <Rule:5:Rule.js:986> Rule#rule-ks56pa4y._evaluate() mutex acquired, evaluating
[latest-21281]2021-10-08T20:38:06.570Z <Rule:5:Rule.js:990> Rule#rule-ks56pa4y update rate is 0/min limit 60/min
[latest-21281]2021-10-08T20:38:06.570Z <Rule:5:Rule.js:914> Rule#rule-ks56pa4y evaluateExpressions() with 0 expressions
[latest-21281]2021-10-08T20:38:06.571Z <Rule:5:Rule.js:1650> cond condcxc7czr evaluation state false->true
[latest-21281]2021-10-08T20:38:06.576Z <Rule:5:Rule.js:1002> Rule#rule-ks56pa4y._evaluate() trigger state now false (was false)
[latest-21281]2021-10-08T20:38:06.576Z <Rule:5:Rule.js:1004> Rule#rule-ks56pa4y._evaluate() constraints state true
[latest-21281]2021-10-08T20:38:06.576Z <Rule:5:Rule.js:1013> Rule#rule-ks56pa4y rule state now false, changed no
[latest-21281]2021-10-08T20:38:07.815Z <Rule:5:Rule.js:763> Rule#rule-ktrefqfy dependency notification timer-trigger Timer#rule-ktrefqfy from Timer#rule-ktrefqfy
[latest-21281]2021-10-08T20:38:07.815Z <Rule:5:Rule.js:769> Rule#rule-ktrefqfy requesting eval; timer-trigger Timer#rule-ktrefqfy
[latest-21281]2021-10-08T20:38:07.816Z <Rule:5:Rule.js:982> Rule#rule-ktrefqfy (vH DLT 8 Delay OFF  ) evaluate() acquiring mutex
[latest-21281]2021-10-08T20:38:07.816Z <Rule:5:Rule.js:986> Rule#rule-ktrefqfy._evaluate() mutex acquired, evaluating
[latest-21281]2021-10-08T20:38:07.816Z <Rule:5:Rule.js:990> Rule#rule-ktrefqfy update rate is 0/min limit 60/min
[latest-21281]2021-10-08T20:38:07.816Z <Rule:5:Rule.js:914> Rule#rule-ktrefqfy evaluateExpressions() with 0 expressions
[latest-21281]2021-10-08T20:38:07.817Z <Rule:5:Rule.js:1650> cond condcxc7czr evaluation state false->true
[latest-21281]2021-10-08T20:38:07.818Z <Rule:5:Rule.js:1002> Rule#rule-ktrefqfy._evaluate() trigger state now false (was false)
[latest-21281]2021-10-08T20:38:07.818Z <Rule:5:Rule.js:1004> Rule#rule-ktrefqfy._evaluate() constraints state true
[latest-21281]2021-10-08T20:38:07.818Z <Rule:5:Rule.js:1013> Rule#rule-ktrefqfy rule state now false, changed no
[latest-21281]2021-10-08T20:38:19.635Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
[latest-21281]2021-10-08T20:38:19.636Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:38:19.636Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:38:28.614Z <wsapi:WARN> wsapi: timed out waiting for ping reply (pong) from client "172.17.0.1#4"
[latest-21281]2021-10-08T20:38:28.615Z <wsapi:INFO> client "172.17.0.1#4" closed, code=1006, reason=
[latest-21281]2021-10-08T20:38:49.688Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
[latest-21281]2021-10-08T20:38:49.688Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
[latest-21281]2021-10-08T20:38:49.688Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
[latest-21281]2021-10-08T20:38:54.226Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1
[latest-21281]2021-10-08T20:39:14.695Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
[latest-21281]2021-10-08T20:39:14.695Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:39:14.696Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:39:44.747Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
[latest-21281]2021-10-08T20:39:44.747Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
[latest-21281]2021-10-08T20:39:44.748Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
[latest-21281]2021-10-08T20:40:14.758Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
[latest-21281]2021-10-08T20:40:14.758Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:40:14.759Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:40:44.809Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
[latest-21281]2021-10-08T20:40:44.810Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
[latest-21281]2021-10-08T20:40:44.810Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
[latest-21281]2021-10-08T20:41:19.824Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
[latest-21281]2021-10-08T20:41:19.824Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:41:19.825Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:41:39.101Z <wsapi:WARN> wsapi: timed out waiting for ping reply (pong) from client "172.17.0.1#5"
[latest-21281]2021-10-08T20:41:39.102Z <wsapi:INFO> client "172.17.0.1#5" closed, code=1006, reason=
[latest-21281]2021-10-08T20:41:49.876Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
[latest-21281]2021-10-08T20:41:49.876Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
[latest-21281]2021-10-08T20:41:49.876Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
[latest-21281]2021-10-08T20:42:29.878Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
[latest-21281]2021-10-08T20:42:29.879Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:42:29.879Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:42:59.931Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
[latest-21281]2021-10-08T20:42:59.931Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
[latest-21281]2021-10-08T20:42:59.931Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
[latest-21281]2021-10-08T20:43:44.942Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
[latest-21281]2021-10-08T20:43:44.942Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:43:44.943Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:44:14.994Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
[latest-21281]2021-10-08T20:44:14.994Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
[latest-21281]2021-10-08T20:44:14.994Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
[latest-21281]2021-10-08T20:44:33.693Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1
[latest-21281]2021-10-08T20:44:35.025Z <wsapi:INFO> client "172.17.0.1#6" closed, code=1001, reason=
[latest-21281]2021-10-08T20:44:54.281Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1
[latest-21281]2021-10-08T20:45:04.999Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
[latest-21281]2021-10-08T20:45:04.999Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:45:05.000Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:45:35.050Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
[latest-21281]2021-10-08T20:45:35.051Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
[latest-21281]2021-10-08T20:45:35.051Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
[latest-21281]2021-10-08T20:46:30.052Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
[latest-21281]2021-10-08T20:46:30.052Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:46:30.053Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:46:34.315Z <wsapi:WARN> wsapi: timed out waiting for ping reply (pong) from client "172.17.0.1#7"
[latest-21281]2021-10-08T20:46:34.316Z <wsapi:INFO> client "172.17.0.1#7" closed, code=1006, reason=
[latest-21281]2021-10-08T20:46:46.206Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1
[latest-21281]2021-10-08T20:47:00.103Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
[latest-21281]2021-10-08T20:47:00.103Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
[latest-21281]2021-10-08T20:47:00.104Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
[latest-21281]2021-10-08T20:47:11.581Z <wsapi:INFO> client "172.17.0.1#8" closed, code=1005, reason=
[latest-21281]2021-10-08T20:47:14.206Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1
[latest-21281]2021-10-08T20:48:00.114Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
[latest-21281]2021-10-08T20:48:00.115Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:48:00.115Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:48:30.167Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
[latest-21281]2021-10-08T20:48:30.167Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
[latest-21281]2021-10-08T20:48:30.168Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
[latest-21281]2021-10-08T20:49:30.169Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
[latest-21281]2021-10-08T20:49:30.169Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:49:30.170Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:50:00.221Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
[latest-21281]2021-10-08T20:50:00.221Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
[latest-21281]2021-10-08T20:50:00.221Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
[latest-21281]2021-10-08T20:50:24.385Z <wsapi:WARN> wsapi: timed out waiting for ping reply (pong) from client "172.17.0.1#9"
[latest-21281]2021-10-08T20:50:24.386Z <wsapi:INFO> client "172.17.0.1#9" closed, code=1006, reason=
[latest-21281]2021-10-08T20:50:27.211Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1
[latest-21281]2021-10-08T20:51:00.225Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
[latest-21281]2021-10-08T20:51:00.225Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:51:00.226Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:51:22.359Z <wsapi:INFO> client "172.17.0.1#10" closed, code=1001, reason=
[latest-21281]2021-10-08T20:51:22.848Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1
[latest-21281]2021-10-08T20:51:30.276Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
[latest-21281]2021-10-08T20:51:30.277Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
[latest-21281]2021-10-08T20:51:30.277Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
[latest-21281]2021-10-08T20:52:30.279Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
[latest-21281]2021-10-08T20:52:30.279Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:52:30.280Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:53:00.331Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
[latest-21281]2021-10-08T20:53:00.331Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
[latest-21281]2021-10-08T20:53:00.331Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
[latest-21281]2021-10-08T20:54:00.338Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
[latest-21281]2021-10-08T20:54:00.338Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:54:00.339Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:54:30.006Z <Rule:5:Rule.js:763> Rule#rule-ktggia4q dependency notification entity-changed Entity#vera>device_719 from Entity#vera>device_719
[latest-21281]2021-10-08T20:54:30.007Z <Rule:5:Rule.js:769> Rule#rule-ktggia4q requesting eval; entity-changed Entity#vera>device_719
[latest-21281]2021-10-08T20:54:30.007Z <Rule:5:Rule.js:982> Rule#rule-ktggia4q (vB2 DLT 2 Motion ID) evaluate() acquiring mutex
[latest-21281]2021-10-08T20:54:30.008Z <Rule:5:Rule.js:986> Rule#rule-ktggia4q._evaluate() mutex acquired, evaluating
[latest-21281]2021-10-08T20:54:30.008Z <Rule:5:Rule.js:990> Rule#rule-ktggia4q update rate is 0/min limit 60/min
[latest-21281]2021-10-08T20:54:30.008Z <Rule:5:Rule.js:914> Rule#rule-ktggia4q evaluateExpressions() with 0 expressions
[latest-21281]2021-10-08T20:54:30.009Z <Rule:5:Rule.js:1002> Rule#rule-ktggia4q._evaluate() trigger state now false (was false)
[latest-21281]2021-10-08T20:54:30.009Z <Rule:5:Rule.js:1004> Rule#rule-ktggia4q._evaluate() constraints state true
[latest-21281]2021-10-08T20:54:30.009Z <Rule:5:Rule.js:1013> Rule#rule-ktggia4q rule state now false, changed no
[latest-21281]2021-10-08T20:54:30.389Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
[latest-21281]2021-10-08T20:54:30.390Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
[latest-21281]2021-10-08T20:54:30.390Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
      posted in Multi-System Reactor
      N
      noelab
    • RE: EzloController error

      Hi, updated MSR latest-21281-c4807c0
      I have connection with ezloplus in set_anonymous_access: true

      MSR starts to be connected and disconnected.
      Ezlo is not connected
      sys_system.state=false

      `

      [latest-21281]2021-10-08T20:29:30.398Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1
[latest-21281]2021-10-08T20:29:33.849Z <Controller:WARN> EzloController#ezlo websocket error during open/negotation: Error: WebSocket was closed before the connection was established
[latest-21281]2021-10-08T20:29:33.850Z <Controller:ERR> EzloController#ezlo failed to connect websocket to wss://10.0.4.119:17000: TimedPromise timeout
[latest-21281]2021-10-08T20:29:33.850Z <Controller:NOTICE> EzloController#ezlo websocket to wss://10.0.4.119:17000 closed during open/negotiation
[latest-21281]2021-10-08T20:29:38.850Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled)
[latest-21281]2021-10-08T20:29:38.851Z <Controller:INFO> EzloController#ezlo opening hub connection to "90000464" at wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:29:38.851Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000
[latest-21281]2021-10-08T20:29:59.226Z <Structure:WARN> Structure#1 promiseEntity(ezlo>housemode,30000) timeout!
[latest-21281]2021-10-08T20:29:59.227Z <Rule:CRIT> Rule#rule-ks210svp failed subscription to ezlo>housemode
[latest-21281]2021-10-08T20:29:59.227Z <Rule:CRIT> !timeout
[latest-21281]2021-10-08T20:29:59.251Z <Structure:WARN> Structure#1 promiseEntity(ezlo>housemode,30000) timeout!
[latest-21281]2021-10-08T20:29:59.251Z <Rule:CRIT> Rule#rule-ks210svp failed subscription to ezlo>housemode
[latest-21281]2021-10-08T20:29:59.252Z <Rule:CRIT> !timeout
[latest-21281]2021-10-08T20:29:59.252Z <Rule:5:Rule.js:704> Rule#rule-ks210svp start() dependencies resolved, performing initial evaluation
[latest-21281]2021-10-08T20:29:59.252Z <Rule:5:Rule.js:982> Rule#rule-ks210svp (v0 Function DayMode OverNight) evaluate() acquiring mutex
[latest-21281]2021-10-08T20:29:59.252Z <Rule:5:Rule.js:986> Rule#rule-ks210svp._evaluate() mutex acquired, evaluating
[latest-21281]2021-10-08T20:29:59.253Z <Rule:5:Rule.js:990> Rule#rule-ks210svp update rate is 0/min limit 60/min
[latest-21281]2021-10-08T20:29:59.253Z <Rule:5:Rule.js:914> Rule#rule-ks210svp evaluateExpressions() with 0 expressions
[latest-21281]2021-10-08T20:29:59.254Z <Rule:5:Rule.js:1002> Rule#rule-ks210svp._evaluate() trigger state now false (was false)
[latest-21281]2021-10-08T20:29:59.259Z <Rule:CRIT> ReferenceError: Can't find entity ezlo>housemode
ReferenceError: Can't find entity ezlo>housemode
    at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1294:27)
    at Rule._evaluateGroup (/opt/reactor/server/lib/Rule.js:1658:99)
    at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1283:47)
    at Rule._evaluateConstraints (/opt/reactor/server/lib/Rule.js:1689:42)
    at Rule._evaluate (/opt/reactor/server/lib/Rule.js:1003:55)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async /opt/reactor/server/lib/Rule.js:969:17
[latest-21281]2021-10-08T20:29:59.261Z <Structure:WARN> Structure#1 promiseEntity(ezlo>device_613e233f129e2912114c0941,30000) timeout!
[latest-21281]2021-10-08T20:29:59.262Z <Rule:CRIT> Rule#rule-ktmit785 failed subscription to ezlo>device_613e233f129e2912114c0941
[latest-21281]2021-10-08T20:29:59.262Z <Rule:CRIT> !timeout
[latest-21281]2021-10-08T20:29:59.262Z <Rule:5:Rule.js:704> Rule#rule-ktmit785 start() dependencies resolved, performing initial evaluation
[latest-21281]2021-10-08T20:29:59.262Z <Rule:5:Rule.js:982> Rule#rule-ktmit785 (vT DLT 1 Bulb ID ) evaluate() acquiring mutex
[latest-21281]2021-10-08T20:29:59.263Z <Rule:5:Rule.js:986> Rule#rule-ktmit785._evaluate() mutex acquired, evaluating
[latest-21281]2021-10-08T20:29:59.263Z <Rule:5:Rule.js:990> Rule#rule-ktmit785 update rate is 0/min limit 60/min
[latest-21281]2021-10-08T20:29:59.263Z <Rule:5:Rule.js:914> Rule#rule-ktmit785 evaluateExpressions() with 0 expressions
[latest-21281]2021-10-08T20:29:59.279Z <Rule:CRIT> ReferenceError: Can't find entity ezlo>device_613e233f129e2912114c0941
ReferenceError: Can't find entity ezlo>device_613e233f129e2912114c0941
    at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1294:27)
    at Rule._evaluateGroup (/opt/reactor/server/lib/Rule.js:1658:99)
    at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1283:47)
    at Rule._evaluateTriggers (/opt/reactor/server/lib/Rule.js:1675:38)
    at Rule._evaluate (/opt/reactor/server/lib/Rule.js:1001:55)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async /opt/reactor/server/lib/Rule.js:969:17
[latest-21281]2021-10-08T20:29:59.280Z <Structure:WARN> Structure#1 promiseEntity(ezlo>device_613e2b02129e2912114c0993,30000) timeout!
[latest-21281]2021-10-08T20:29:59.280Z <Rule:CRIT> Rule#rule-kthqmgb6 failed subscription to ezlo>device_613e2b02129e2912114c0993
[latest-21281]2021-10-08T20:29:59.280Z <Rule:CRIT> !timeout
[latest-21281]2021-10-08T20:29:59.280Z <Rule:5:Rule.js:704> Rule#rule-kthqmgb6 start() dependencies resolved, performing initial evaluation
[latest-21281]2021-10-08T20:29:59.281Z <Rule:5:Rule.js:982> Rule#rule-kthqmgb6 (vR4 DLT 1 Bulb ID ) evaluate() acquiring mutex
[latest-21281]2021-10-08T20:29:59.281Z <Rule:5:Rule.js:986> Rule#rule-kthqmgb6._evaluate() mutex acquired, evaluating
[latest-21281]2021-10-08T20:29:59.281Z <Rule:5:Rule.js:990> Rule#rule-kthqmgb6 update rate is 0/min limit 60/min
[latest-21281]2021-10-08T20:29:59.282Z <Rule:5:Rule.js:914> Rule#rule-kthqmgb6 evaluateExpressions() with 0 expressions
[latest-21281]2021-10-08T20:29:59.284Z <Rule:CRIT> ReferenceError: Can't find entity ezlo>device_613e2b02129e2912114c0993
ReferenceError: Can't find entity ezlo>device_613e2b02129e2912114c0993
    at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1294:27)
    at Rule._evaluateGroup (/opt/reactor/server/lib/Rule.js:1658:99)
    at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1283:47)
    at Rule._evaluateTriggers (/opt/reactor/server/lib/Rule.js:1675:38)
    at Rule._evaluate (/opt/reactor/server/lib/Rule.js:1001:55)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at runNextTicks (internal/process/task_queues.js:64:3)
    at listOnTimeout (internal/timers.js:526:9)
    at processTimers (internal/timers.js:500:7)
    at async /opt/reactor/server/lib/Rule.js:969:17
[latest-21281]2021-10-08T20:29:59.285Z <Structure:WARN> Structure#1 promiseEntity(ezlo>device_613e2959129e2912114c098f,30000) timeout!
[latest-21281]2021-10-08T20:29:59.285Z <Rule:CRIT> Rule#rule-kthqpda8 failed subscription to ezlo>device_613e2959129e2912114c098f
[latest-21281]2021-10-08T20:29:59.286Z <Rule:CRIT> !timeout
[latest-21281]2021-10-08T20:29:59.286Z <Rule:5:Rule.js:704> Rule#rule-kthqpda8 start() dependencies resolved, performing initial evaluation
[latest-21281]2021-10-08T20:29:59.286Z <Rule:5:Rule.js:982> Rule#rule-kthqpda8 (vR4 DLT 3 Lux ID  ) evaluate() acquiring mutex
[latest-21281]2021-10-08T20:29:59.287Z <Rule:5:Rule.js:986> Rule#rule-kthqpda8._evaluate() mutex acquired, evaluating
[latest-21281]2021-10-08T20:29:59.287Z <Rule:5:Rule.js:990> Rule#rule-kthqpda8 update rate is 0/min limit 60/min
[latest-21281]2021-10-08T20:29:59.287Z <Rule:5:Rule.js:914> Rule#rule-kthqpda8 evaluateExpressions() with 1 expressions
[latest-21281]2021-10-08T20:29:59.290Z <Rule:ERR> Rule#rule-kthqpda8: error evaluating expression test: TypeError: Cannot read property 'log' of null
[latest-21281]2021-10-08T20:29:59.290Z <Rule:ERR> Rule#rule-kthqpda8: expression: round((abs(int( getEntity( "ezlo>device_613e2959129e2912114c098f" ).attributes.light_sensor.value ) * (100/300) -100) - int((  getEntity( "ezlo>device_613e2959129e2912114c098f" ).attributes.light_sensor.value  * (100/300) ) - 100))/2)
[latest-21281]2021-10-08T20:29:59.291Z <Rule:CRIT> TypeError: Cannot read property 'log' of null
TypeError: Cannot read property 'log' of null
    at _0x2f8d77 (/opt/reactor/server/lib/Engine.js:984:21)
    at _run (/opt/reactor/common/lexp.js:1383:34)
    at _run (/opt/reactor/common/lexp.js:1338:33)
    at _run (/opt/reactor/common/lexp.js:1338:33)
    at _run (/opt/reactor/common/lexp.js:1338:33)
    at /opt/reactor/common/lexp.js:1381:33
    at Array.forEach (<anonymous>)
    at _run (/opt/reactor/common/lexp.js:1380:28)
    at _run (/opt/reactor/common/lexp.js:1208:34)
    at _run (/opt/reactor/common/lexp.js:1208:34)
[latest-21281]2021-10-08T20:29:59.295Z <Rule:CRIT> ReferenceError: Can't find entity ezlo>device_613e2959129e2912114c098f
ReferenceError: Can't find entity ezlo>device_613e2959129e2912114c098f
    at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1294:27)
    at Rule._evaluateGroup (/opt/reactor/server/lib/Rule.js:1658:99)
    at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1283:47)
    at Rule._evaluateTriggers (/opt/reactor/server/lib/Rule.js:1675:38)
    at Rule._evaluate (/opt/reactor/server/lib/Rule.js:1001:55)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at runNextTicks (internal/process/task_queues.js:64:3)
    at listOnTimeout (internal/timers.js:526:9)
    at processTimers (internal/timers.js:500:7)
    at async /opt/reactor/server/lib/Rule.js:969:17
[latest-21281]2021-10-08T20:29:59.296Z <Structure:WARN> Structure#1 promiseEntity(ezlo>device_613e2959129e2912114c0982,30000) timeout!
[latest-21281]2021-10-08T20:29:59.296Z <Rule:CRIT> Rule#rule-kthqljcu failed subscription to ezlo>device_613e2959129e2912114c0982
[latest-21281]2021-10-08T20:29:59.296Z <Rule:CRIT> !timeout
[latest-21281]2021-10-08T20:29:59.296Z <Rule:5:Rule.js:704> Rule#rule-kthqljcu start() dependencies resolved, performing initial evaluation
[latest-21281]2021-10-08T20:29:59.297Z <Rule:5:Rule.js:982> Rule#rule-kthqljcu (vR4 DLT 2 Motion ID ) evaluate() acquiring mutex
[latest-21281]2021-10-08T20:29:59.297Z <Rule:5:Rule.js:986> Rule#rule-kthqljcu._evaluate() mutex acquired, evaluating
[latest-21281]2021-10-08T20:29:59.297Z <Rule:5:Rule.js:990> Rule#rule-kthqljcu update rate is 0/min limit 60/min
[latest-21281]2021-10-08T20:29:59.297Z <Rule:5:Rule.js:914> Rule#rule-kthqljcu evaluateExpressions() with 0 expressions
[latest-21281]2021-10-08T20:29:59.299Z <Rule:CRIT> ReferenceError: Can't find entity ezlo>device_613e2959129e2912114c0982
ReferenceError: Can't find entity ezlo>device_613e2959129e2912114c0982
    at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1294:27)
    at Rule._evaluateGroup (/opt/reactor/server/lib/Rule.js:1658:99)
    at Rule._evaluateCondition (/opt/reactor/server/lib/Rule.js:1283:47)
    at Rule._evaluateTriggers (/opt/reactor/server/lib/Rule.js:1675:38)
    at Rule._evaluate (/opt/reactor/server/lib/Rule.js:1001:55)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at runNextTicks (internal/process/task_queues.js:64:3)
    at listOnTimeout (internal/timers.js:526:9)
    at processTimers (internal/timers.js:500:7)
    at async /opt/reactor/server/lib/Rule.js:969:17
[latest-21281]2021-10-08T20:29:59.300Z <Structure:WARN> Structure#1 promiseEntity(ezlo>device_614e0c2f129e29124dfcd825,30000) timeout!
[latest-21281]2021-10-08T20:29:59.300Z <Rule:CRIT> Rule#rule-ktpv9g18 failed subscription to ezlo>device_614e0c2f129e29124dfcd825
[latest-21281]2021-10-08T20:29:59.300Z <Rule:CRIT> !timeout
[latest-21281]2021-10-08T20:29:59.301Z <Rule:5:Rule.js:704> Rule#rule-ktpv9g18 start() dependencies resolved, performing initial evaluation
[latest-21281]2021-10-08T20:29:59.301Z <Rule:5:Rule.js:982> Rule#rule-ktpv9g18 (vR3 DLT 1 Bulb ID) evaluate() acquiring mutex
[latest-21281]2021-10-08T20:29:59.301Z <Rule:5:Rule.js:986> Rule#rule-ktpv9g18._evaluate() mutex acquired, evaluating
[latest-21281]2021-10-08T20:29:59.301Z <Rule:5:Rule.js:990> Rule#rule-ktpv9g18 update rate is 0/min limit 60/min
[latest-21281]2021-10-08T20:29:59.301Z <Rule:5:Rule.js:914> Rule#rule-ktpv9g18 evaluateExpressions() with 0 expressions
[latest-21281]2021-10-08T20:29:59.304Z <Rule:CRIT> ReferenceError: Can't find entity ezlo>device_614e0c2f129e29124dfcd825

      `

      posted in Multi-System Reactor
      N
      noelab
    • Plugin Influxdb 2.0

      Hi, I was trying to setup influxdb for MSR and on my Synology Nas, docker installation, I started with Influxdb 2.0.
      Now seems it is very different from 1.x.
      Databases don't exist anymore, they are named "buckets" now and there are token values.
      Looking around, I found something on HA like this in "configuration.yaml" file.

      influxdb:

api_version: 2

ssl: false

host: 10.0.0.11

port: 8086

token: Your HomeAssistant - Write token

organization: Home

bucket: HomeAssistant

      I don't use HA, just starting to bring devices on ezlo plus. Does MSR support this version Influxdb 2.0? or better to re-install 1.x?

      Thanks in advance

      posted in Multi-System Reactor
      N
      noelab
    • RE: Synology Docker installation

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

      posted in Multi-System Reactor
      N
      noelab
    • RE: Synology Docker installation

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

      Importing ReactorSensors from Vera Reactor - Reactor - Multi-Hub Automation
      posted in Multi-System Reactor
      N
      noelab
    • RE: Synology Docker installation

      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!

      posted in Multi-System Reactor
      N
      noelab
    • RE: Synology Docker installation

      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.
      posted in Multi-System Reactor
      N
      noelab
    • RE: Synology Docker installation

      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?

      posted in Multi-System Reactor
      N
      noelab