(Last Updated: October 8, 2021)
For those who registered but didn't received the confirmation email, please send an email to support@smarthome.community with the email you used
-
Hass: 2022.11.4
Hardware: Container
MSR: stable-22310-3006e85cHi,
I have a number of rules where the reactions change the brightness of lights....that have been working for months. I upgraded MSR recently however I don't think that is issue as I spun up the old container and the the issue remains.
This image illustrates the problem.
bfe42fd7-e038-4aba-bd5a-9892946f7d33-image.png
This what is now available in the dropdown menu
8ec17afc-c23c-413d-956a-fc992881b0e7-image.png
I can turn the light on/off from MSR and Hass however in Hass I can also control the dimming (saturation, colours, effects and so on).
It seems MSR is no longer 'seeing' a number of 'attribute'. At a loss as to what has changed.
Any suggestions most welcome.
Thanks
-
Solution: An update to openLuups MQTT implementation on handling acknowledge packets for QoS > 0 solved this issue.
EDIT: Seems related to any restart without any configuration changes. If I revert to 22310 I can restart Reactor from UI and with systemd within seconds, but with 22328 it fails to restart., both from UI and systemd. I have to stop the service and then start again.
I tested to comment out my http (not https) baseurl in the config on my bare metal Ubuntu install latest-22328 and triggered a restart from the UI but Reactor would not start after that.
If I uncomment the key and restart the service, Reactor comes back to life.
Is my setup an exceptional circumstance or is this only applicable on new installs? -
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here.
Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed. -
I've noticed lately (at least with build 22328) that in some cases these yellow warning / alert icons in front of rules are missing, although errors are otherwise visible:
-
Hello @toggledbits I have a strange issue with the HTTP request that i send to Reactor.
I have two reactors one on a Unraid server and one on Ubuntu server installed as a docker, when i send http get request to the Unraid server to control home assistant entity everything is going ok, but when i send the same request to the ubuntu modified accordingly it says "Request failed" but when i try to run reaction via http request it works.When i go to entities and try to control the entity manually its working.
Any idea's?
Best regards
-
I probably messed things up trying to work around the shutdown timeout for Reactor 22328 when connected to openLuup MQTT server.
I got a Reaction from a rule stuck in Running Reactions.
"Stop this reaction" unfortunately does nothing and in my attempt to get rid of them I deleted the rule but they were still there. I downgraded to 22310 to do a clean restart of Reactor, no success. I even tried to rename/edit/delete reaction_queue.json but they are recreated after each restart and I can't get those orphan Reactions to disappear.
I need some advice from the guru, please.
-
Hey Patrick, noticed a bug running latest-22328-bb674d9c on my Rpi. When I go to the entities tab I can see the entity that is no longer available has a line through the text and a question mark, but say if I try adding the entity to a rule set it no longer shows as unavailable. See the screenshots for more clarity.
7d0593a9-c983-4a9f-abad-776a53b1dfe9-image.png
Entity is correctly shown that is unavailable in the entities tab.
1743d7e5-06d2-42b6-a774-2740f4eaee1a-image.png
When I go to choose an entity in a rule set it no longer has a line through and a question mark showing that it is unavailable.
PS: I am using the word unavailable in the context that it was deleted from my HA controller
-
Hello,
I am using MS-Reactor with a Home Assistant hub running on a Synoogy NAS as well as a VERA Plus hub. So far MS-R works AMAZING! However I have one rule I use when cleaning the house that essentially turns all the lights on to 100% (25+ lights) and it takes sometime for the action to take effect. I noticed it worked slighlty faster when I had the items in a scene on the vera controller Vs. a rule triggered by a virtual switch in MS-R.I suspect I could address the issue by increasing the action pace value per the documentation however, I do not know where to edit this setting? Do I just add a line in the MS-R reactor.yaml config file below the VERA controller info that states: "ActionPace: 00500"?
Please let me know where and how I can adjust he aforementioned setting.
All the best,
Phil
-
So it was time to update MSR (and then HA but I got stuck here)
Can't figure out what I have missed.My installed version of MSR was 22240.
Node.js is version 16.15.1First I tried to update, following online manual.
Spoiler
Download a Reactor distribution ZIP from https://reactor.toggledbits.com/download/ and place it in the folder above your existing reactor (runtime) directory.
Stop and remove any existing Reactor service:cd \path\to\reactor
node tools\install_reactor_windows_service.js -u .
Remove any existing package-lock.json file from your Reactor directory.Unzip the archive file and copy its contents over the contents of your existing Reactor install directory.
From the Reactor install directory, re-install/upgrade all package dependencies:npm install --no-save --omit dev
If you are running Reactor as a Windows service, repeat those steps above.Restart Reactor (restart the service).
Hard-refresh all browsers that are displaying Reactor content.I found several (maybe it was 3) package-lock.json and I deleted all I could search in reactor folder.
Unzip the new version and replaced old existing files.Install the reactor service again by instructions.
Spoiler
In a command prompt window, running as Administrator, change directory to your Reactor install directory.
Install the node-windows package as a global package (it must be global or the service will not work, and you must install the specific version provided by the command below):npm uninstall node-windows
npm uninstall -g node-windows
npm install -g node-windows@1.0.0-beta.6
npm link node-windows
Run the script to install:node tools\install_reactor_windows_service.js -i .
So this failed. Service wont start.
Tried again.
Then deleted everything exept my config folder and did a new install.
c:\reactor>node app.js Reactor latest-22310-a6da8097 app 22310 configuration from c:\reactor\config NODE_PATH C:\reactor [latest-22310]2022-11-23T22:18:43.030Z <app:null> Reactor build latest-22310-a6da8097 starting on v16.15.1 c:\reactor\app.js:277 log['always'](a0_0x3d42be(0x26a), BUILD_VERSION, process['version']), log['always']('Process\x20ID\x20%1\x20user/group\x20%2/%3;\x20%4;\x20platform\x20%5/%6\x20%7;\x20locale\x20%8', process['pid'], process[a0_0x3d42be(0x269)](), process[a0_0x3d42be(0x278)](), is_docker ? 'docker' : a0_0x3d42be(0x288), process[a0_0x3d42be(0x287)], process['arch'], os[a0_0x3d42be(0x263)](), sys_locale), log[a0_0x3d42be(0x28c)]('Basedir\x20%1;\x20data\x20in\x20%2', c[a0_0x3d42be(0x1f8)], c[a0_0x3d42be(0x27b)]), log[a0_0x3d42be(0x28c)](a0_0x3d42be(0x21b), process['env'][a0_0x3d42be(0x291)]); ^ TypeError: process[a0_0x3d42be(...)] is not a function at Object.<anonymous> (c:\reactor\app.js:277:226) at Module._compile (node:internal/modules/cjs/loader:1105:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10) at Module.load (node:internal/modules/cjs/loader:981:32) at Function.Module._load (node:internal/modules/cjs/loader:822:12) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12) at node:internal/main/run_main_module:17:47
Also downloaded 22310 again, but from "latest" build instead of "stable"
When running node app.js in command promt i get some kind of error message:But I can't figure out what TypeError means?
Also, before I tried a new install, there apperd an warning when installing reactor service.
c:\reactor>npm install -g node-windows@1.0.0-beta.6 npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead. npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead. added 5 packages, and audited 6 packages in 3s 2 vulnerabilities (1 moderate, 1 critical) To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details.Running npm audit fix --force seems to broke something, because I could not install service after that.
c:\reactor>npm audit fix --force npm WARN config global `--global`, `--local` are deprecated. Use `--location=global` instead. npm WARN using --force Recommended protections disabled. up to date, audited 89 packages in 826ms 12 packages are looking for funding run `npm fund` for details found 0 vulnerabilities c:\reactor>node tools\install_reactor_windows_service.js -i . node:internal/modules/cjs/loader:936 throw err; ^ Error: Cannot find module 'node-windows' Require stack: - c:\reactor\tools\install_reactor_windows_service.js ←[90m at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)←[39m ←[90m at Function.Module._load (node:internal/modules/cjs/loader:778:27)←[39m ←[90m at Module.require (node:internal/modules/cjs/loader:1005:19)←[39m ←[90m at require (node:internal/modules/cjs/helpers:102:18)←[39m at Object.<anonymous> (c:\reactor\tools\install_reactor_windows_service.js:102:15) ←[90m at Module._compile (node:internal/modules/cjs/loader:1105:14)←[39m ←[90m at Object.Module._extensions..js (node:internal/modules/cjs/loader:1159:10)←[39m ←[90m at Module.load (node:internal/modules/cjs/loader:981:32)←[39m ←[90m at Function.Module._load (node:internal/modules/cjs/loader:822:12)←[39m ←[90m at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)←[39m { code: ←[32m'MODULE_NOT_FOUND'←[39m, requireStack: [ ←[32m'c:\\reactor\\tools\\install_reactor_windows_service.js'←[39m ] } -
Hello All -
I'm still working on moving dozens of devices from Vera (internal Reactor) to HASS and (external - bare metal) Reactor.
One thing I've noticed is sometimes I move a few ZWave/Vera devices and find myself digging through rules finding where a device was used. Has anyone found a good way to do this?
I plan on digging in to this thread but thought I'd check to see if there's anything more recent.
https://smarthome.community/topic/483/entities-where-used-and-what-triggered-it?_=1669137134654
-
Hass: 2022.11.3
Hardware: Pi
MSR: latest-22310-a6da8097I'm trying to use MSR in automations to change the page displayed on a wall tablet (Windows and Edge in Kiosk mode)
Example use would be motion detected will change to the security dashboard, or heating turns on, shows the heating dashboard.Screenshot_20221122_193138.png I have Browser Mod installed and working and the entities are present in MSR. My only option for the entity which controls the page/dashboard displayed is "x_hass.call_service"
What I need to change is the state of the entity
state.png state2.pngIs this possible in MSR? Despite much searching i'm unsure what service to call to set the state?
I have tried using service: browser_mod.navigate but get an error
(this service detailed here https://smarthomescene.com/guides/how-to-setup-browser-mod-2-0-in-home-assistant/ )
error1.pngAlso trying to lay the data out like this with/out quotes and other variations has not helped
{ "/home-overview/heating" } -
Here's my second attempt at a Reactor Controller, this time to integrate LG TVs:
GitHub - dbochicchio/reactor-lgtv: Reactor controller for LG TV (webos) GitHub - dbochicchio/reactor-lgtv: Reactor controller for LG TV (webos)Reactor controller for LG TV (webos). Contribute to dbochicchio/reactor-lgtv development by creating an account on GitHub.
Standard capabilities are provided and TV volume, mute and switch status are controllable.
There's also an action to send toast notifications on your TV.webos 5+ is required.
-
I've moved many of my MQTT devices to Reactor, so I've coded a couple of templates and I'm publishing them for anyone in the same boat:
GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for ReactorContrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.
I'll add more in the future, since I still have a couple of things running in my own bridge that I'll eventually move to Reactor with dedicated templates.
Let me know if you need other templates, I'll probably add a couple more for Shellies (button as scene controller and i3/i4 as scene controller).
-
Before I'll open a feature request, I want a reality check, because this is maybe achievable in other ways.
Long story short: I want to react to a device in quasi-real time, but 15 or 30 secs are enough (and will prevent the rule from throttling). Right now, I've moved to 1 min, but it's obviously too late to catch all the variations. 15 secs or 30 are OK, so my first reaction to circumvent this limitation was to host the timer myself and send it via MQTT, but it's obviously a not welcome complication.
So, @toggledbits, is there any reason the minimum interval is 1 min and/or do you have any suggestion for my use case? Thanks Patrick!
-
I'm still trying to fully wrap my brain around Pulsing. Let's see if I have it:
2a1da895-5170-499f-a1ff-708d3ded1f5c-image.png
I believe this to indicate that this will wait five minutes, do the thing, wait five seconds and repeat.
Backstory: this is a reset ruleset for my HVAC. Sometimes Honeywell is finicky about taking the original commands so this should follow along and submit a retry after five minutes... continuing until the setting is accepted.
-
Hi @toggledbits !!
Would it be possible to improve the error messages, and instead of showing the "technical name", show the name we assigned to the rule?
a8298689-0c7b-43ef-a582-16baece4e4d1-image.png
In the above case, I have no idea what rule is causing the problem.
Thanks.
-
MSR latest-22310, Raspberry Pi 4 / Docker
While troubleshooting another issue, I deleted and recreated the hub information device on one of my Hubitat hubs. Reactor had been logging the old device information to InfluxDB, but it doesn't appear to have detected the new device. I made sure to enable the new device in Maker API, I've restarted reactor and done a 'docker-compose down' / 'docker-compose up - d'. Still no new data going to influxdb.
My recollection is that the Hubitat hub device is baken into MSR and is auto-detected, and that it isn't manually configured anywhere. I checked the docs and searched the forum without success.
Any advice on how I can get MSR to start logging the info from the new device?
-
Hi!
I can't find the original post where it's stated that it's possible to make a shortcut i HA to MSR, but I remember trying it out, and it failed, probably because I have duckdns, and a https address, and not a http address, which give us the wss: instead of ws:. Maybe not, but that was my understanding. I finally gave it up, but now I want to try it again. Anyway, is there anyone with duckdns and https that have been able to set this up? How?
Thanks in advance!
/Fanan -
MSR has a parameter called "http_request_action_maxresponse" that can be updated within the properties. There is a good section describing this in the manual. However, the installation config file doesn't include the parameter out of the box. I was able to add the parameter (see below) and eventually got it to work after searching for a while.
Suggestions:
Include the parameter in the initial config file (or) Update the manual to state that the parameter should be added to the fileAdditional suggestion:
engine: # # enabled - Whether or not the rules engine runs. Change only when directed. enabled: true http_request_action_maxresponse: 10000
I understand that it is potentially unsafe to have a large limit overall. However, some API calls unfortunately return large sizes which aren't necessarily problematic. The additional suggestion is to include a configurable max size within each HTTP Reaction in the UI. If it isn't populated then MSR could default to the config file like it does today. This way, we could have a reasonable default limit while allowing larger limit for certain HTTP calls. -
Hi,
@toggledbits do you have any plans to implement the missing endpoints of the REST API in near future? Especially the rule and ruleset functionality (list/enable/disable etc. as documented) would be really useful. I know there must tons of feature requests and the REST API isn't probably on the top of the backlog, so I'm not holding my breath. But if it's right around the corner on your roadmap, it would be nice to know.I'm asking this because I need a clean way to enable and disable certain rules from my custom home automation UI. I don't want to expose the MSR UI to the rest of my family to make sure they don't accidentally mess up with the rules and settings.
I could use a custom MQTT entity as a dynamic config object containing flags for different rules but it would be a lot cleaner to be toggle the rules thru the REST API.
br,
mgvraReactor (Multi-hub) latest-22310-a6da8097
MQTTController [0.1.22306]
EzloController error
-
@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: 1002Reactor latest-21270-48528ec, updated to latest-21270-46679ac just now.
-
When posting error messages from the logs it's really helpful to post several dozen lines from before the message, as well as the message itself. This gives the message more context and usually exposes what was going on at the time the error occurred. Can you post a bit of context for me? It would also be helpful to know what version of MSR you are running.
-
@crille said in EzloController error:
Reactor latest-21270-48528ec, updated to latest-21270-46679ac just now.
One of my rules executed at the time uses
set variableand I was running the version without the fix. I'm guessing the controller was unreachable for a short time but Reactor never caught the online status cause of the "Maximum call stack size exceeded".The hub responded but was offline in Reactor until I restarted Reactor.
2021-10-01T04:00:00.002Z <Rule:INFO> Schema - Vitrinskåp (Rule#rule-kmusx4kh) SET! 2021-10-01T04:00:00.003Z <Engine:5:Engine.js:1359> _process_reaction_queue() wake-up! 2021-10-01T04:00:00.003Z <Engine:INFO> Enqueueing "Schema - Vitrinskåp<SET>" (rule-kmusx4kh:S) 2021-10-01T04:00:00.007Z <Engine:5:Engine.js:1219> Engine#1 enqueued reaction rule-kmusx4kh:S as 428 2021-10-01T04:00:00.007Z <Engine:5:Engine.js:1359> _process_reaction_queue() ending with 1 in queue; waiting for 1633060800007<10/1/2021, 6:00:00 AM> (next delayed task) 2021-10-01T04:00:00.008Z <Rule:INFO> Schema - Larm: Nattläge (Rule#rule-ksvitzde) RESET! 2021-10-01T04:00:00.009Z <Engine:5:Engine.js:1359> _process_reaction_queue() wake-up! 2021-10-01T04:00:00.009Z <Engine:INFO> Enqueueing "Schema - Larm: Nattläge<RESET>" (rule-ksvitzde:R) 2021-10-01T04:00:00.009Z <Engine:5:Engine.js:1219> Engine#1 enqueued reaction rule-ksvitzde:R as 429 2021-10-01T04:00:00.010Z <Engine:5:Engine.js:1320> _process_reaction_queue() running task 428 { "tid": 428, "id": "rule-kmusx4kh:S", "rule": "rule-kmusx4kh", "__reaction": [RuleReaction#rule-kmusx4kh:S], "next_step": 0, "status": 0, "ts": 1633060800003, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise] } 2021-10-01T04:00:00.010Z <Engine:NOTICE> Starting reaction Schema - Vitrinskåp<SET> (rule-kmusx4kh:S) 2021-10-01T04:00:00.010Z <Engine:5:Engine.js:1421> Engine#1 reaction rule-kmusx4kh:S step 0 perform { "entity": "ezlo>device_603a0363129e0715cf4a75fe", "action": "power_switch.on" } 2021-10-01T04:00:00.011Z <Engine:5:Engine.js:1324> _process_reaction_queue() task returned, new status 3; task 428 2021-10-01T04:00:00.012Z <Engine:5:Engine.js:1320> _process_reaction_queue() running task 429 { "tid": 429, "id": "rule-ksvitzde:R", "rule": "rule-ksvitzde", "__reaction": [RuleReaction#rule-ksvitzde:R], "next_step": 0, "status": 0, "ts": 1633060800009, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise] } 2021-10-01T04:00:00.012Z <Engine:NOTICE> Starting reaction Schema - Larm: Nattläge<RESET> (rule-ksvitzde:R) 2021-10-01T04:00:00.012Z <Engine:5:Engine.js:1421> Engine#1 reaction rule-ksvitzde:R step 0 perform { "entity": "vera>device_10050", "action": "x_vera_plugin_housemodes.set_house_mode", "args": { "new_mode": "1" } } 2021-10-01T04:00:00.013Z <Engine:5:Engine.js:1324> _process_reaction_queue() task returned, new status 3; task 429 2021-10-01T04:00:00.013Z <VeraController:null> VeraController#vera enqueue task for Entity#vera>device_10050 action x_vera_plugin_housemodes.set_house_mode: task { "newHModeValue": 1, "DeviceNum": 10050, "id": "action", "serviceId": "urn:micasaverde-com:serviceId:HouseModes1", "action": "SetHMode" } 2021-10-01T04:00:00.014Z <Engine:5:Engine.js:1359> _process_reaction_queue ending with 2 in queue; none delayed/ready; waiting 2021-10-01T04:00:00.014Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [ ] }) took 0ms and returned 22 entities 2021-10-01T04:00:00.015Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [ ] }) took 0ms and returned 22 entities 2021-10-01T04:00:00.017Z <Engine:5:Engine.js:1359> _process_reaction_queue() wake-up! 2021-10-01T04:00:00.017Z <Engine:5:Engine.js:1320> _process_reaction_queue() running task 429 { "tid": 429, "id": "rule-ksvitzde:R", "rule": "rule-ksvitzde", "__reaction": [RuleReaction#rule-ksvitzde:R], "next_step": 1, "status": 1, "ts": 1633060800009, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise], "attempts": 1 } 2021-10-01T04:00:00.017Z <Engine:NOTICE> Resuming reaction Schema - Larm: Nattläge<RESET> (rule-ksvitzde:R) from step 1 2021-10-01T04:00:00.018Z <Engine:INFO> Schema - Larm: Nattläge<RESET> all actions completed. 2021-10-01T04:00:00.018Z <Engine:5:Engine.js:1324> _process_reaction_queue() task returned, new status -1; task 429 2021-10-01T04:00:00.019Z <Engine:5:Engine.js:1359> _process_reaction_queue ending with 1 in queue; none delayed/ready; waiting 2021-10-01T04:00:00.025Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [ ] }) took 0ms and returned 22 entities 2021-10-01T04:00:00.026Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [ ] }) took 0ms and returned 22 entities 2021-10-01T04:00:00.146Z <Engine:5:Engine.js:1083> Engine#1 var HouseMode dependency entity-changed Entity#vera>device_10050 2021-10-01T04:00:00.148Z <default:CRIT> Error: Object does not exist Error: Object does not exist at Function.getInstance (/home/username/reactor/server/lib/GlobalExpression.js:135:27) at Engine._expr_dependency (/home/username/reactor/server/lib/Engine.js:1084:59) at /home/username/reactor/server/lib/MessageBus.js:103:200 at Array.forEach (<anonymous>) at MessageBus._sendToBus (/home/username/reactor/server/lib/MessageBus.js:100:46) at Immediate._onImmediate (/home/username/reactor/server/lib/MessageBus.js:113:34) at processImmediate (internal/timers.js:461:21) 2021-10-01T04:00:00.149Z <Engine:5:Engine.js:1083> Engine#1 var hm dependency entity-changed Entity#vera>housemode 2021-10-01T04:00:00.151Z <default:CRIT> Error: Object does not exist Error: Object does not exist at Function.getInstance (/home/username/reactor/server/lib/GlobalExpression.js:135:27) at Engine._expr_dependency (/home/username/reactor/server/lib/Engine.js:1084:59) at /home/username/reactor/server/lib/MessageBus.js:103:200 at Array.forEach (<anonymous>) at MessageBus._sendToBus (/home/username/reactor/server/lib/MessageBus.js:100:46) at Immediate._onImmediate (/home/username/reactor/server/lib/MessageBus.js:113:34) at processImmediate (internal/timers.js:461:21) 2021-10-01T04:00:00.156Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>housemode) ctx=other 2021-10-01T04:00:00.156Z <Rule:INFO> Notifiering - House mode (Rule#rule-ksw26xod) SET! 2021-10-01T04:00:00.165Z <Engine:5:Engine.js:1359> _process_reaction_queue() wake-up! 2021-10-01T04:00:00.166Z <Engine:INFO> Enqueueing "Notifiering - House mode<SET>" (rule-ksw26xod:S) 2021-10-01T04:00:00.167Z <Engine:5:Engine.js:1219> Engine#1 enqueued reaction rule-ksw26xod:S as 430 2021-10-01T04:00:00.167Z <Engine:5:Engine.js:1359> _process_reaction_queue() ending with 2 in queue; waiting for 1633060800167<10/1/2021, 6:00:00 AM> (next delayed task) 2021-10-01T04:00:00.170Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>housemode) ctx=other 2021-10-01T04:00:00.178Z <Engine:5:Engine.js:1359> _process_reaction_queue() wake-up! 2021-10-01T04:00:00.179Z <Engine:5:Engine.js:1320> _process_reaction_queue() running task 430 { "tid": 430, "id": "rule-ksw26xod:S", "rule": "rule-ksw26xod", "__reaction": [RuleReaction#rule-ksw26xod:S], "next_step": 0, "status": 0, "ts": 1633060800166, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise] } 2021-10-01T04:00:00.179Z <Engine:NOTICE> Starting reaction Notifiering - House mode<SET> (rule-ksw26xod:S) 2021-10-01T04:00:00.179Z <Engine:5:Engine.js:1470> Engine#1 reaction rule-ksw26xod:S step 0 notify Pushover with { "message": "Larmet ändrades från night till home.", "profile": "MSR", "title": "Larmet ändrade status", "priority": "0" } 2021-10-01T04:00:00.180Z <NotifyPushover:5:NotifyPushover.js:228> NotifyPushover sending profile MSR notification request: Larmet ändrades från night till home. 2021-10-01T04:00:00.182Z <Engine:INFO> Notifiering - House mode<SET> all actions completed. 2021-10-01T04:00:00.182Z <Engine:5:Engine.js:1324> _process_reaction_queue() task returned, new status -1; task 430 2021-10-01T04:00:00.185Z <Engine:5:Engine.js:1359> _process_reaction_queue ending with 1 in queue; none delayed/ready; waiting 2021-10-01T04:00:01.171Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>housemode) ctx=other 2021-10-01T04:00:01.171Z <Rule:INFO> Notifiering - House mode (Rule#rule-ksw26xod) RESET! 2021-10-01T04:00:01.171Z <Engine:5:Engine.js:1359> _process_reaction_queue() wake-up! 2021-10-01T04:00:01.172Z <Engine:INFO> Enqueueing "Notifiering - House mode<RESET>" (rule-ksw26xod:R) 2021-10-01T04:00:01.173Z <Engine:5:Engine.js:1219> Engine#1 enqueued reaction rule-ksw26xod:R as 431 2021-10-01T04:00:01.173Z <Engine:5:Engine.js:1359> _process_reaction_queue() ending with 2 in queue; waiting for 1633060801173<10/1/2021, 6:00:01 AM> (next delayed task) 2021-10-01T04:00:01.184Z <Engine:5:Engine.js:1359> _process_reaction_queue() wake-up! 2021-10-01T04:00:01.184Z <Engine:5:Engine.js:1320> _process_reaction_queue() running task 431 { "tid": 431, "id": "rule-ksw26xod:R", "rule": "rule-ksw26xod", "__reaction": [RuleReaction#rule-ksw26xod:R], "next_step": 0, "status": 0, "ts": 1633060801172, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise] } 2021-10-01T04:00:01.185Z <Engine:NOTICE> Starting reaction Notifiering - House mode<RESET> (rule-ksw26xod:R) 2021-10-01T04:00:01.185Z <Engine:5:Engine.js:1597> Engine#1 reaction rule-ksw26xod:R step 0 set variable prevHouseMode=${{housemode}} (string home) 2021-10-01T04:00:01.185Z <Engine:5:Engine.js:1161> Engine#1 global set variable prevHouseMode = (string) home 2021-10-01T04:00:01.185Z <Engine:5:Engine.js:1167> Engine#1 var prevHouseMode set/changed to (string)home 2021-10-01T04:00:01.185Z <Engine:INFO> Notifiering - House mode<RESET> all actions completed. 2021-10-01T04:00:01.186Z <Engine:5:Engine.js:1324> _process_reaction_queue() task returned, new status -1; task 431 2021-10-01T04:00:01.186Z <Engine:5:Engine.js:1359> _process_reaction_queue ending with 1 in queue; none delayed/ready; waiting 2021-10-01T04:00:01.186Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>housemode) ctx=other 2021-10-01T04:00:01.187Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>housemode) ctx=other 2021-10-01T04:00:05.003Z <Engine:INFO> Engine#1 master timer tick, local time "10/1/2021, 6:00:05 AM" (TZ offset 120 mins from UTC) 2021-10-01T04:00:10.233Z <NotifyPushover:ERR> NotifyPushover failure response from endpoint: 520 (undefined) 2021-10-01T04:00:10.233Z <NotifyPushover:INFO> NotifyPushover request URL: https://api.pushover.net/1/messages.json 2021-10-01T04:00:10.234Z <NotifyPushover:INFO> NotifyPushover request body: token=xxxxxxxxxxxxxxxxxxxx&user=xxxxxxxxxxxxxxxxxxxxxxxxx&priority=0&title=Larmet%20%C3%A4ndrade%20status&message=Larmet%20%C3%A4ndrades%20fr%C3%A5n%20night%20till%20home. 2021-10-01T04:00:10.234Z <NotifyPushover:ERR> NotifyPushover request to https://api.pushover.net/1/messages.json failed: Error: NotifyPushover request failed 2021-10-01T04:00:10.234Z <Engine:ERR> Engine#1 reaction rule-ksw26xod:S step 0 notification (Pushover) failed: Error: NotifyPushover request failed 2021-10-01T04:00:13.164Z <Engine:5:Engine.js:1083> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005 2021-10-01T04:00:13.165Z <Engine:5:Engine.js:1083> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005 2021-10-01T04:00:13.167Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:00:13.168Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:00:13.169Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:00:13.170Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:00:13.171Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_52) ctx=global 2021-10-01T04:00:15.015Z <EzloController:ERR> EzloController#ezlo request "17c3a02460b" ({ "method": "hub.item.value.set", "api": "1.0" }) failed: TimedPromise timeout 2021-10-01T04:00:15.017Z <EzloController:WARN> EzloController#ezlo action power_switch.on on Entity#ezlo>device_603a0363129e0715cf4a75fe failed! 2021-10-01T04:00:15.018Z <Engine:ERR> Engine#1 reaction rule-kmusx4kh:S step 0 perform power_switch.on failed: TimedPromise timeout 2021-10-01T04:00:15.018Z <Engine:INFO> Engine#1 action args: { } 2021-10-01T04:00:15.018Z <Engine:5:Engine.js:1359> _process_reaction_queue() wake-up! 2021-10-01T04:00:15.020Z <Engine:5:Engine.js:1320> _process_reaction_queue() running task 428 { "tid": 428, "id": "rule-kmusx4kh:S", "rule": "rule-kmusx4kh", "__reaction": [RuleReaction#rule-kmusx4kh:S], "next_step": 1, "status": 1, "ts": 1633060800003, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise], "attempts": 1 } 2021-10-01T04:00:15.020Z <Engine:NOTICE> Resuming reaction Schema - Vitrinskåp<SET> (rule-kmusx4kh:S) from step 1 2021-10-01T04:00:15.021Z <Engine:INFO> Schema - Vitrinskåp<SET> all actions completed. 2021-10-01T04:00:15.021Z <Engine:5:Engine.js:1324> _process_reaction_queue() task returned, new status -1; task 428 2021-10-01T04:00:15.023Z <Engine:5:Engine.js:1359> _process_reaction_queue ending with 0 in queue; none delayed/ready; waiting 2021-10-01T04:00:57.033Z <Engine:5:Engine.js:1083> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005 2021-10-01T04:00:57.033Z <Engine:5:Engine.js:1083> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005 2021-10-01T04:00:57.035Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:00:57.035Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:00:57.036Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:00:57.037Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:00:57.038Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_52) ctx=global 2021-10-01T04:00:58.167Z <Engine:5:Engine.js:1083> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005 2021-10-01T04:00:58.168Z <Engine:5:Engine.js:1083> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005 2021-10-01T04:00:58.172Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:00:58.173Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:00:58.174Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:00:58.176Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:00:58.176Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_52) ctx=global 2021-10-01T04:01:00.004Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [ ] }) took 1ms and returned 22 entities 2021-10-01T04:01:00.009Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [ ] }) took 1ms and returned 22 entities 2021-10-01T04:01:00.018Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [ ] }) took 0ms and returned 22 entities 2021-10-01T04:01:00.023Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [ ] }) took 5ms and returned 22 entities 2021-10-01T04:01:12.961Z <Engine:5:Engine.js:1083> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005 2021-10-01T04:01:12.961Z <Engine:5:Engine.js:1083> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005 2021-10-01T04:01:12.961Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:01:12.962Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:01:12.962Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:01:12.963Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:01:12.963Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_52) ctx=global 2021-10-01T04:01:13.165Z <Engine:5:Engine.js:1083> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005 2021-10-01T04:01:13.165Z <Engine:5:Engine.js:1083> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005 2021-10-01T04:01:13.167Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:01:13.168Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:01:13.168Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:01:13.169Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:01:13.170Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_52) ctx=global 2021-10-01T04:01:56.999Z <Engine:5:Engine.js:1083> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005 2021-10-01T04:01:56.999Z <Engine:5:Engine.js:1083> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005 2021-10-01T04:01:57.000Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:01:57.000Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:01:57.000Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:01:57.001Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:01:57.001Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_52) ctx=global 2021-10-01T04:01:58.169Z <Engine:5:Engine.js:1083> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005 2021-10-01T04:01:58.170Z <Engine:5:Engine.js:1083> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005 2021-10-01T04:01:58.172Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:01:58.173Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:01:58.174Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:01:58.175Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:01:58.176Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_52) ctx=global 2021-10-01T04:02:00.004Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [ ] }) took 0ms and returned 22 entities 2021-10-01T04:02:00.005Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [ ] }) took 0ms and returned 22 entities 2021-10-01T04:02:00.015Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [ ] }) took 0ms and returned 22 entities 2021-10-01T04:02:00.016Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [ ] }) took 0ms and returned 22 entities 2021-10-01T04:02:13.427Z <Engine:5:Engine.js:1083> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005 2021-10-01T04:02:13.428Z <Engine:5:Engine.js:1083> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005 2021-10-01T04:02:13.430Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:02:13.431Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:02:13.431Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:02:13.433Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:02:13.433Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_52) ctx=global 2021-10-01T04:02:34.912Z <EzloController:NOTICE> EzloController#ezlo connection closed: 1006 2021-10-01T04:02:39.918Z <EzloController:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled) 2021-10-01T04:02:39.918Z <EzloController:INFO> EzloController#ezlo opening hub connection to "XXXXXXXX" at wss://192.168.1.100:17000 2021-10-01T04:02:39.920Z <EzloController:NOTICE> EzloController#ezlo connecting via WS to wss://192.168.1.100:17000 2021-10-01T04:02:40.007Z <EzloController:INFO> EzloController#ezlo hub websocket connected (wss://192.168.1.100:17000) 2021-10-01T04:02:40.007Z <EzloController:INFO> EzloController#ezlo hub websocket connected; inventory hub... 2021-10-01T04:02:55.016Z <EzloController:ERR> EzloController#ezlo request "17c3a04b708" (hub.info.get) failed: TimedPromise timeout 2021-10-01T04:02:55.017Z <EzloController:ERR> EzloController#ezlo failed to complete inventory: TimedPromise timeout 2021-10-01T04:02:55.018Z <EzloController:CRIT> !TimedPromise timeout 2021-10-01T04:02:55.025Z <EzloController:NOTICE> EzloController#ezlo connection closed: 1002 2021-10-01T04:02:56.933Z <Engine:5:Engine.js:1083> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005 2021-10-01T04:02:56.933Z <Engine:5:Engine.js:1083> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005 2021-10-01T04:02:56.933Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:02:56.934Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:02:56.934Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:02:56.934Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:02:56.934Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_52) ctx=global 2021-10-01T04:02:58.144Z <Engine:5:Engine.js:1083> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005 2021-10-01T04:02:58.144Z <Engine:5:Engine.js:1083> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005 2021-10-01T04:02:58.144Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:02:58.145Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:02:58.145Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:02:58.145Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:02:58.145Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_52) ctx=global 2021-10-01T04:03:00.003Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [ ] }) took 1ms and returned 22 entities 2021-10-01T04:03:00.005Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [ ] }) took 0ms and returned 22 entities 2021-10-01T04:03:00.015Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [ ] }) took 1ms and returned 22 entities 2021-10-01T04:03:00.016Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [ ] }) took 0ms and returned 22 entities 2021-10-01T04:03:00.025Z <EzloController:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled) 2021-10-01T04:03:00.025Z <EzloController:INFO> EzloController#ezlo opening hub connection to "XXXXXXXX" at wss://192.168.1.100:17000 2021-10-01T04:03:00.025Z <EzloController:NOTICE> EzloController#ezlo connecting via WS to wss://192.168.1.100:17000 2021-10-01T04:03:00.110Z <EzloController:INFO> EzloController#ezlo hub websocket connected (wss://192.168.1.100:17000) 2021-10-01T04:03:00.110Z <EzloController:INFO> EzloController#ezlo hub websocket connected; inventory hub... 2021-10-01T04:03:13.125Z <Engine:5:Engine.js:1083> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005 2021-10-01T04:03:13.125Z <Engine:5:Engine.js:1083> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005 2021-10-01T04:03:13.126Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:03:13.126Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:03:13.126Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:03:13.126Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_30005) ctx=global 2021-10-01T04:03:13.126Z <Engine:5:Engine.js:942> Engine#1 getEntity(vera>device_52) ctx=global 2021-10-01T04:03:15.112Z <EzloController:ERR> EzloController#ezlo request "17c3a05058e" (hub.info.get) failed: TimedPromise timeout 2021-10-01T04:03:15.113Z <EzloController:ERR> EzloController#ezlo failed to complete inventory: TimedPromise timeout 2021-10-01T04:03:15.113Z <EzloController:CRIT> !TimedPromise timeout 2021-10-01T04:03:15.117Z <EzloController:NOTICE> EzloController#ezlo connection closed: 1002 2021-10-01T04:03:15.119Z <EzloController:ERR> Controller EzloController#ezlo is off-line! 2021-10-01T04:03:15.129Z <Rule:INFO> Notifiering - Ezlo status (Rule#rule-ktsucjh1) SET! 2021-10-01T04:03:15.132Z <Engine:5:Engine.js:1359> _process_reaction_queue() wake-up! 2021-10-01T04:03:15.132Z <Engine:INFO> Enqueueing "Notifiering - Ezlo status<SET>" (rule-ktsucjh1:S) 2021-10-01T04:03:15.133Z <Engine:5:Engine.js:1219> Engine#1 enqueued reaction rule-ktsucjh1:S as 432 2021-10-01T04:03:15.133Z <Engine:5:Engine.js:1359> _process_reaction_queue() ending with 1 in queue; waiting for 1633060995133<10/1/2021, 6:03:15 AM> (next delayed task) 2021-10-01T04:03:15.144Z <Engine:5:Engine.js:1359> _process_reaction_queue() wake-up! 2021-10-01T04:03:15.145Z <Engine:5:Engine.js:1320> _process_reaction_queue() running task 432 { "tid": 432, "id": "rule-ktsucjh1:S", "rule": "rule-ktsucjh1", "__reaction": [RuleReaction#rule-ktsucjh1:S], "next_step": 0, "status": 0, "ts": 1633060995132, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise] } 2021-10-01T04:03:15.145Z <Engine:NOTICE> Starting reaction Notifiering - Ezlo status<SET> (rule-ktsucjh1:S) 2021-10-01T04:03:15.145Z <Engine:5:Engine.js:1470> Engine#1 reaction rule-ktsucjh1:S step 0 notify Pushover with { "message": "Ezlo Plus svarar inte, troligen nere.", "profile": "MSR", "title": "Ezlo Plus nere!", "priority": "0" } 2021-10-01T04:03:15.145Z <NotifyPushover:5:NotifyPushover.js:228> NotifyPushover sending profile MSR notification request: Ezlo Plus svarar inte, troligen nere. 2021-10-01T04:03:15.146Z <Engine:INFO> Notifiering - Ezlo status<SET> all actions completed. 2021-10-01T04:03:15.146Z <Engine:5:Engine.js:1324> _process_reaction_queue() task returned, new status -1; task 432 2021-10-01T04:03:15.147Z <Engine:5:Engine.js:1359> _process_reaction_queue ending with 0 in queue; none delayed/ready; waiting 2021-10-01T04:03:16.289Z <NotifyPushover:5:NotifyPushover.js:236> NotifyPushover successful endpoint exchange (message sent) 2021-10-01T04:03:20.122Z <EzloController:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled) 2021-10-01T04:03:20.123Z <EzloController:INFO> EzloController#ezlo opening hub connection to "XXXXXXXX" at wss://192.168.1.100:17000 2021-10-01T04:03:20.124Z <EzloController:NOTICE> EzloController#ezlo connecting via WS to wss://192.168.1.100:17000 2021-10-01T04:03:20.214Z <EzloController:INFO> EzloController#ezlo hub websocket connected (wss://192.168.1.100:17000) 2021-10-01T04:03:20.214Z <EzloController:INFO> EzloController#ezlo hub websocket connected; inventory hub... 2021-10-01T04:03:20.456Z <EzloController:INFO> EzloController#ezlo hub "XXXXXXXX" is h2.1 (undefined) firmware "2.0.19.1714.2" 2021-10-01T04:03:20.489Z <EzloController:ERR> EzloController#ezlo ws_message handler failed: RangeError: Maximum call stack size exceeded 2021-10-01T04:03:20.490Z <EzloController:CRIT> RangeError: Maximum call stack size exceeded RangeError: Maximum call stack size exceeded at EzloController._now.ws_message [as refreshTime] (/home/username/reactor/server/lib/EzloController.js:1136:43) at EzloController._now.ws_message [as refreshTime] (/home/username/reactor/server/lib/EzloController.js:1138:54) at EzloController._now.ws_message [as refreshTime] (/home/username/reactor/server/lib/EzloController.js:1138:54) at EzloController._now.ws_message [as refreshTime] (/home/username/reactor/server/lib/EzloController.js:1138:54) at EzloController._now.ws_message [as refreshTime] (/home/username/reactor/server/lib/EzloController.js:1138:54) at EzloController._now.ws_message [as refreshTime] (/home/username/reactor/server/lib/EzloController.js:1138:54) at EzloController._now.ws_message [as refreshTime] (/home/username/reactor/server/lib/EzloController.js:1138:54) at EzloController._now.ws_message [as refreshTime] (/home/username/reactor/server/lib/EzloController.js:1138:54) at EzloController._now.ws_message [as refreshTime] (/home/username/reactor/server/lib/EzloController.js:1138:54) at EzloController._now.ws_message [as refreshTime] (/home/username/reactor/server/lib/EzloController.js:1138:54) 2021-10-01T04:03:35.461Z <EzloController:ERR> EzloController#ezlo request "17c3a05550c" ({ "method": "hub.modes.get", "api": "2.0" }) failed: TimedPromise timeout 2021-10-01T04:03:35.462Z <EzloController:ERR> EzloController#ezlo failed to complete inventory: TimedPromise timeout 2021-10-01T04:03:35.462Z <EzloController:CRIT> !TimedPromise timeout 2021-10-01T04:03:35.468Z <EzloController:NOTICE> EzloController#ezlo connection closed: 1002 2021-10-01T04:03:40.474Z <EzloController:INFO> EzloController#ezlo performing hub login without cloud authentication (hub.offline.anonymous_access must be enabled) 2021-10-01T04:03:40.474Z <EzloController:INFO> EzloController#ezlo opening hub connection to "XXXXXXXX" at wss://192.168.1.100:17000 2021-10-01T04:03:40.475Z <EzloController:NOTICE> EzloController#ezlo connecting via WS to wss://192.168.1.100:17000 2021-10-01T04:03:40.563Z <EzloController:INFO> EzloController#ezlo hub websocket connected (wss://192.168.1.100:17000) 2021-10-01T04:03:40.563Z <EzloController:INFO> EzloController#ezlo hub websocket connected; inventory hub... 2021-10-01T04:03:40.596Z <EzloController:ERR> EzloController#ezlo ws_message handler failed: RangeError: Maximum call stack size exceeded 2021-10-01T04:03:40.597Z <EzloController:CRIT> RangeError: Maximum call stack size exceeded RangeError: Maximum call stack size exceeded... -
The Set Variable issue is specific to Vera controllers only and does not apply to eZLO or any other.
The variable
hmassociated with rule Notifiering - House mode (Rule#rule-ksw26xod): can you tell me if that's a rule variable, or a global variable?Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
@toggledbits Yes, in one of the rules I set the openLuup house mode via house mode plugin to push the mode to my Vera (That is otherwise primary for openLuup's house mode).
The variable
hmis an old test I did and does no longer exist and is not referenced anywhere visible to me? -
Variables
hmandHouseModeboth are referenced somewhere, but appear to not be global. If you don't seehmin the list of global variables, it's probably buried in a rule somewhere. What aboutHouseMode? Global or rule?Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
@toggledbits After going through every Rule Set I have, I deleted the global
HouseModehours before I got this error since it was not referenced anywhere.
hmwas a local in Notifiering - House mode (Rule#rule-ksw26xod) but was replaced weeks ago with a new local namedhousemode
This rule has been untouched for weaks and never failed, the thing I changed yesterday was the Trigger from housemode plugin to
vera>housemodesince it seems you fixed the housemode change issue from openLuup and native is snappier than the polling plugin. -
OK. Great detail. That helps, thank you. Let me see what I can do here...
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
@toggledbits I'm still having some problem with variables being referenced when deleted. Looks like the Engine is looking for an old global expression (undefined)? that I think I had a time ago with
matchEntities
and
@ 2021-10-04T14:11:00.003Z
This rule triggers: Rule:INFO Notifiering - Ezlo devices (Rule#rule-ku32xyj5) SET!
I've now put a sustianed for 3 secs on the first variable trigger to ignore flapping.
None of the other rules triggered in the log snippet has any local expression or referenced global expressions and the "Error: Object does not exist" is present from:
2021-10-04T10:31:08.900Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005 2021-10-04T10:31:08.901Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005 2021-10-04T10:31:08.905Z <Engine:5:Engine.js:948> Engine#1 set global Medeltemp; value=(number)22 2021-10-04T10:31:08.908Z <Engine:5:Engine.js:948> Engine#1 set global Luftfuktighet; value=(number)0.8148148148148148 2021-10-04T10:31:10.074Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005 2021-10-04T10:31:10.075Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005 2021-10-04T10:31:25.061Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005 2021-10-04T10:31:25.061Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005 2021-10-04T10:32:00.014Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [ ] }) took 0ms and returned 22 entities 2021-10-04T10:32:00.027Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [ ] }) took 0ms and returned 22 entities 2021-10-04T10:32:09.094Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005 2021-10-04T10:32:09.095Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005 2021-10-04T10:32:10.297Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005 2021-10-04T10:32:10.297Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005 2021-10-04T10:32:24.996Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005 2021-10-04T10:32:24.996Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005 2021-10-04T10:33:00.002Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [ ] }) took 0ms and returned 22 entities 2021-10-04T10:33:00.015Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [ ] }) took 0ms and returned 22 entities 2021-10-04T10:33:09.142Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005 2021-10-04T10:33:09.143Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005 2021-10-04T10:33:09.148Z <Engine:5:Engine.js:948> Engine#1 set global Luftfuktighet; value=(number)0.7901234567901234 2021-10-04T10:33:10.387Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005 2021-10-04T10:33:10.388Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005 2021-10-04T10:33:25.394Z <Engine:5:Engine.js:1108> Engine#1 var Medeltemp dependency entity-changed Entity#vera>device_30005 2021-10-04T10:33:25.394Z <Engine:5:Engine.js:1108> Engine#1 var Luftfuktighet dependency entity-changed Entity#vera>device_30005 2021-10-04T10:33:30.894Z <Engine:5:Engine.js:1108> Engine#1 var (undefined) dependency entity-changed Entity#ezlo>device_603a0373129e0715cf4a765f 2021-10-04T10:33:30.897Z <default:CRIT> Error: Object does not exist Error: Object does not exist at Function.getInstance (/home/homebridge/reactor/server/lib/GlobalExpression.js:130:27) at Engine._expr_dependency (/home/homebridge/reactor/server/lib/Engine.js:1109:59) at /home/homebridge/reactor/server/lib/MessageBus.js:99:208 at Array.forEach (<anonymous>) at MessageBus._sendToBus (/home/homebridge/reactor/server/lib/MessageBus.js:96:47) at /home/homebridge/reactor/server/lib/MessageBus.js:109:48 at new Promise (<anonymous>) at MessageBus.send (/home/homebridge/reactor/server/lib/MessageBus.js:106:16) at Entity.publish (/home/homebridge/reactor/server/lib/Observable.js:71:44) at Entity.deferNotifies (/home/homebridge/reactor/server/lib/Entity.js:248:207)Where everything above the error is just repeating.
Log from rule SET in next post...
-
First lines looks interesting
2021-10-04T14:10:33.692Z <EzloController:WARN> EzloController#ezlo warning: update parameter serviceNotification for Entity#ezlo>device_603a0367129e0715cf4a7604 not previously defined! (value now (boolean)false) 2021-10-04T14:10:33.693Z <EzloController:WARN> EzloController#ezlo warning: update parameter syncNotification for Entity#ezlo>device_603a0367129e0715cf4a7604 not previously defined! (value now (boolean)false) 2021-10-04T14:10:33.694Z <Engine:5:Engine.js:1108> Engine#1 var (undefined) dependency entity-changed Entity#ezlo>device_603a0367129e0715cf4a7604 2021-10-04T14:10:33.697Z <default:CRIT> Error: Object does not exist Error: Object does not exist at Function.getInstance (/home/username/reactor/server/lib/GlobalExpression.js:130:27) at Engine._expr_dependency (/home/username/reactor/server/lib/Engine.js:1109:59) at /home/username/reactor/server/lib/MessageBus.js:99:208 at Array.forEach (<anonymous>) at MessageBus._sendToBus (/home/username/reactor/server/lib/MessageBus.js:96:47) at /home/username/reactor/server/lib/MessageBus.js:109:48 at new Promise (<anonymous>) at MessageBus.send (/home/username/reactor/server/lib/MessageBus.js:106:16) at Entity.publish (/home/username/reactor/server/lib/Observable.js:71:44) at Entity.deferNotifies (/home/username/reactor/server/lib/Entity.js:248:207) 2021-10-04T14:10:35.317Z <EzloController:WARN> EzloController#ezlo warning: update parameter serviceNotification for Entity#ezlo>device_603a036a129e0715cf4a761d not previously defined! (value now (boolean)false) 2021-10-04T14:10:35.318Z <EzloController:WARN> EzloController#ezlo warning: update parameter syncNotification for Entity#ezlo>device_603a036a129e0715cf4a761d not previously defined! (value now (boolean)false) 2021-10-04T14:10:35.318Z <Engine:5:Engine.js:1108> Engine#1 var (undefined) dependency entity-changed Entity#ezlo>device_603a036a129e0715cf4a761d 2021-10-04T14:10:35.318Z <default:CRIT> Error: Object does not exist Error: Object does not exist at Function.getInstance (/home/username/reactor/server/lib/GlobalExpression.js:130:27) at Engine._expr_dependency (/home/username/reactor/server/lib/Engine.js:1109:59) at /home/username/reactor/server/lib/MessageBus.js:99:208 at Array.forEach (<anonymous>) at MessageBus._sendToBus (/home/username/reactor/server/lib/MessageBus.js:96:47) at /home/username/reactor/server/lib/MessageBus.js:109:48 at new Promise (<anonymous>) at MessageBus.send (/home/username/reactor/server/lib/MessageBus.js:106:16) at Entity.publish (/home/username/reactor/server/lib/Observable.js:71:44) at Entity.deferNotifies (/home/username/reactor/server/lib/Entity.js:248:207) 2021-10-04T14:10:35.439Z <EzloController:WARN> EzloController#ezlo warning: update parameter serviceNotification for Entity#ezlo>device_6107edd0129e071241a25469 not previously defined! (value now (boolean)false) 2021-10-04T14:10:35.439Z <EzloController:WARN> EzloController#ezlo warning: update parameter syncNotification for Entity#ezlo>device_6107edd0129e071241a25469 not previously defined! (value now (boolean)false) 2021-10-04T14:10:35.440Z <Engine:5:Engine.js:1108> Engine#1 var (undefined) dependency entity-changed Entity#ezlo>device_6107edd0129e071241a25469 2021-10-04T14:10:35.440Z <default:CRIT> Error: Object does not exist Error: Object does not exist at Function.getInstance (/home/username/reactor/server/lib/GlobalExpression.js:130:27) at Engine._expr_dependency (/home/username/reactor/server/lib/Engine.js:1109:59) at /home/username/reactor/server/lib/MessageBus.js:99:208 at Array.forEach (<anonymous>) at MessageBus._sendToBus (/home/username/reactor/server/lib/MessageBus.js:96:47) at /home/username/reactor/server/lib/MessageBus.js:109:48 at new Promise (<anonymous>) at MessageBus.send (/home/username/reactor/server/lib/MessageBus.js:106:16) at Entity.publish (/home/username/reactor/server/lib/Observable.js:71:44) at Entity.deferNotifies (/home/username/reactor/server/lib/Entity.js:248:207) 2021-10-04T14:10:39.201Z <EzloController:WARN> EzloController#ezlo warning: update parameter serviceNotification for Entity#ezlo>device_603a60dc129e071231a7f95e not previously defined! (value now (boolean)false) 2021-10-04T14:10:39.201Z <EzloController:WARN> EzloController#ezlo warning: update parameter syncNotification for Entity#ezlo>device_603a60dc129e071231a7f95e not previously defined! (value now (boolean)false) 2021-10-04T14:10:39.203Z <Engine:5:Engine.js:1108> Engine#1 var (undefined) dependency entity-changed Entity#ezlo>device_603a60dc129e071231a7f95e 2021-10-04T14:10:39.205Z <default:CRIT> Error: Object does not exist Error: Object does not exist at Function.getInstance (/home/username/reactor/server/lib/GlobalExpression.js:130:27) at Engine._expr_dependency (/home/username/reactor/server/lib/Engine.js:1109:59) at /home/username/reactor/server/lib/MessageBus.js:99:208 at Array.forEach (<anonymous>) at MessageBus._sendToBus (/home/username/reactor/server/lib/MessageBus.js:96:47) at /home/username/reactor/server/lib/MessageBus.js:109:48 at new Promise (<anonymous>) at MessageBus.send (/home/username/reactor/server/lib/MessageBus.js:106:16) at Entity.publish (/home/username/reactor/server/lib/Observable.js:71:44) at Entity.deferNotifies (/home/username/reactor/server/lib/Entity.js:248:207) 2021-10-04T14:11:00.002Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [ ] }) took 0ms and returned 22 entities 2021-10-04T14:11:00.003Z <Rule:INFO> Notifiering - Ezlo devices (Rule#rule-ku32xyj5) SET! 2021-10-04T14:11:00.005Z <Engine:5:Engine.js:1386> _process_reaction_queue() wake-up! 2021-10-04T14:11:00.005Z <Engine:INFO> Enqueueing "Notifiering - Ezlo devices<SET>" (rule-ku32xyj5:S) 2021-10-04T14:11:00.006Z <Engine:5:Engine.js:1246> Engine#1 enqueued reaction rule-ku32xyj5:S as 70 2021-10-04T14:11:00.006Z <Engine:5:Engine.js:1386> _process_reaction_queue() ending with 1 in queue; waiting for 1633356660006<10/4/2021, 4:11:00 PM> (next delayed task) 2021-10-04T14:11:00.013Z <Engine:INFO> Engine#1 matchEntities({ "controller": [ "ezlo" ], "capability": [ "x_ezlo_device" ], "group": [ ] }) took 0ms and returned 22 entities 2021-10-04T14:11:00.014Z <Rule:INFO> Notifiering - Ezlo devices (Rule#rule-ku32xyj5) RESET! 2021-10-04T14:11:00.015Z <Engine:5:Engine.js:1386> _process_reaction_queue() wake-up! 2021-10-04T14:11:00.015Z <Engine:5:Engine.js:1347> _process_reaction_queue() running task 70 { "tid": 70, "id": "rule-ku32xyj5:S", "rule": "rule-ku32xyj5", "__reaction": [RuleReaction#rule-ku32xyj5:S], "next_step": 0, "status": 0, "ts": 1633356660005, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise], "halt": true } 2021-10-04T14:11:00.015Z <Engine:INFO> Halting reaction Notifiering - Ezlo devices<SET> (rule-ku32xyj5:S) at step 0 2021-10-04T14:11:00.016Z <Engine:NOTICE> Handling reaction halt request for Notifiering - Ezlo devices<SET> at step 0 2021-10-04T14:11:00.016Z <Engine:5:Engine.js:1351> _process_reaction_queue() task returned, new status -1; task 70 2021-10-04T14:11:00.016Z <Engine:NOTICE> Engine#1 entry 70 reaction rule-ku32xyj5:S: terminated 2021-10-04T14:11:00.016Z <Engine:CRIT> !terminated 2021-10-04T14:11:00.017Z <Engine:5:Engine.js:1386> _process_reaction_queue ending with 0 in queue; none delayed/ready; waiting 2021-10-04T14:11:00.021Z <Engine:INFO> Enqueueing "Notifiering - Ezlo devices<RESET>" (rule-ku32xyj5:R) 2021-10-04T14:11:00.021Z <Engine:5:Engine.js:1246> Engine#1 enqueued reaction rule-ku32xyj5:R as 71 2021-10-04T14:11:00.021Z <Engine:5:Engine.js:1386> _process_reaction_queue() wake-up! 2021-10-04T14:11:00.022Z <Engine:5:Engine.js:1347> _process_reaction_queue() running task 71 { "tid": 71, "id": "rule-ku32xyj5:R", "rule": "rule-ku32xyj5", "__reaction": [RuleReaction#rule-ku32xyj5:R], "next_step": 0, "status": 0, "ts": 1633356660021, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise] } 2021-10-04T14:11:00.022Z <Engine:NOTICE> Starting reaction Notifiering - Ezlo devices<RESET> (rule-ku32xyj5:R) 2021-10-04T14:11:00.023Z <Engine:5:Engine.js:1496> Engine#1 reaction rule-ku32xyj5:R step 0 notify Pushover with { "message": "Alla enheter svarar igen.", "profile": "MSR", "title": "Ezlo-enheter svarar igen.", "priority": "0" } 2021-10-04T14:11:00.023Z <NotifyPushover:5:NotifyPushover.js:216> NotifyPushover sending profile MSR notification request: Alla enheter svarar igen. 2021-10-04T14:11:00.024Z <Engine:INFO> Notifiering - Ezlo devices<RESET> all actions completed. 2021-10-04T14:11:00.024Z <Engine:5:Engine.js:1351> _process_reaction_queue() task returned, new status -1; task 71 2021-10-04T14:11:00.025Z <Engine:5:Engine.js:1386> _process_reaction_queue ending with 0 in queue; none delayed/ready; waiting 2021-10-04T14:11:00.647Z <NotifyPushover:5:NotifyPushover.js:224> NotifyPushover successful endpoint exchange (message sent) 2021-10-04T14:11:03.822Z <Engine:5:Engine.js:1108> Engine#1 var (undefined) dependency entity-changed Entity#ezlo>device_603a036e129e0715cf4a763e 2021-10-04T14:11:03.825Z <default:CRIT> Error: Object does not exist Error: Object does not exist at Function.getInstance (/home/username/reactor/server/lib/GlobalExpression.js:130:27) at Engine._expr_dependency (/home/username/reactor/server/lib/Engine.js:1109:59) at /home/username/reactor/server/lib/MessageBus.js:99:208 at Array.forEach (<anonymous>) at MessageBus._sendToBus (/home/username/reactor/server/lib/MessageBus.js:96:47) at /home/username/reactor/server/lib/MessageBus.js:109:48 at new Promise (<anonymous>) at MessageBus.send (/home/username/reactor/server/lib/MessageBus.js:106:16) at Entity.publish (/home/username/reactor/server/lib/Observable.js:71:44) at Entity.deferNotifies (/home/username/reactor/server/lib/Entity.js:248:207) 2021-10-04T14:11:03.828Z <Rule:INFO> Tänd i Källaren beroende på Ljus (Rule#rule-kmuwu2tk) RESET! 2021-10-04T14:11:03.835Z <Engine:5:Engine.js:1386> _process_reaction_queue() wake-up! 2021-10-04T14:11:03.836Z <Engine:INFO> Enqueueing "Tänd i Källaren beroende på Ljus<RESET>" (rule-kmuwu2tk:R) 2021-10-04T14:11:03.837Z <Engine:5:Engine.js:1246> Engine#1 enqueued reaction rule-kmuwu2tk:R as 72 2021-10-04T14:11:03.838Z <Engine:5:Engine.js:1386> _process_reaction_queue() ending with 1 in queue; waiting for 1633356663837<10/4/2021, 4:11:03 PM> (next delayed task) 2021-10-04T14:11:03.840Z <Engine:5:Engine.js:1108> Engine#1 var (undefined) dependency entity-changed Entity#ezlo>device_603a036e129e0715cf4a763a 2021-10-04T14:11:03.842Z <default:CRIT> Error: Object does not exist Error: Object does not exist at Function.getInstance (/home/username/reactor/server/lib/GlobalExpression.js:130:27) at Engine._expr_dependency (/home/username/reactor/server/lib/Engine.js:1109:59) at /home/username/reactor/server/lib/MessageBus.js:99:208 at Array.forEach (<anonymous>) at MessageBus._sendToBus (/home/username/reactor/server/lib/MessageBus.js:96:47) at /home/username/reactor/server/lib/MessageBus.js:109:48 at new Promise (<anonymous>) at MessageBus.send (/home/username/reactor/server/lib/MessageBus.js:106:16) at Entity.publish (/home/username/reactor/server/lib/Observable.js:71:44) at Entity.deferNotifies (/home/username/reactor/server/lib/Entity.js:248:207) 2021-10-04T14:11:03.845Z <Engine:5:Engine.js:1108> Engine#1 var (undefined) dependency entity-changed Entity#ezlo>device_603a036e129e0715cf4a763a 2021-10-04T14:11:03.848Z <default:CRIT> Error: Object does not exist Error: Object does not exist at Function.getInstance (/home/username/reactor/server/lib/GlobalExpression.js:130:27) at Engine._expr_dependency (/home/username/reactor/server/lib/Engine.js:1109:59) at /home/username/reactor/server/lib/MessageBus.js:99:208 at Array.forEach (<anonymous>) at MessageBus._sendToBus (/home/username/reactor/server/lib/MessageBus.js:96:47) at /home/username/reactor/server/lib/MessageBus.js:109:48 at new Promise (<anonymous>) at MessageBus.send (/home/username/reactor/server/lib/MessageBus.js:106:16) at Entity.publish (/home/username/reactor/server/lib/Observable.js:71:44) at Entity.deferNotifies (/home/username/reactor/server/lib/Entity.js:248:207) 2021-10-04T14:11:03.850Z <Engine:5:Engine.js:1386> _process_reaction_queue() wake-up! 2021-10-04T14:11:03.851Z <Engine:5:Engine.js:1347> _process_reaction_queue() running task 72 { "tid": 72, "id": "rule-kmuwu2tk:R", "rule": "rule-kmuwu2tk", "__reaction": [RuleReaction#rule-kmuwu2tk:R], "next_step": 0, "status": 0, "ts": 1633356663836, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise] } 2021-10-04T14:11:03.852Z <Engine:NOTICE> Starting reaction Tänd i Källaren beroende på Ljus<RESET> (rule-kmuwu2tk:R) 2021-10-04T14:11:03.852Z <Engine:5:Engine.js:1416> Engine#1 reaction rule-kmuwu2tk:R handling group rule-kmuwu2tk:R-7pjfxee constraints state true 2021-10-04T14:11:03.852Z <Engine:5:Engine.js:1418> Engine#1 constraints OK for reaction rule-kmuwu2tk:R group rule-kmuwu2tk:R-7pjfxee, queueing 2021-10-04T14:11:03.853Z <Engine:5:Engine.js:1430> Engine#1 reaction rule-kmuwu2tk:R group rule-kmuwu2tk:R-7pjfxee enqueued, waiting for completion 2021-10-04T14:11:03.853Z <Engine:5:Engine.js:1351> _process_reaction_queue() task returned, new status 3; task 72 2021-10-04T14:11:03.855Z <Engine:5:Engine.js:1246> Engine#1 enqueued reaction rule-kmuwu2tk:R-7pjfxee as 73 2021-10-04T14:11:03.856Z <Engine:5:Engine.js:1386> _process_reaction_queue() ending with 2 in queue; waiting for 1633356663855<10/4/2021, 4:11:03 PM> (next delayed task) 2021-10-04T14:11:03.856Z <Engine:5:Engine.js:1108> Engine#1 var (undefined) dependency entity-changed Entity#ezlo>device_603a036e129e0715cf4a763a 2021-10-04T14:11:03.857Z <default:CRIT> Error: Object does not exist Error: Object does not exist at Function.getInstance (/home/username/reactor/server/lib/GlobalExpression.js:130:27) at Engine._expr_dependency (/home/username/reactor/server/lib/Engine.js:1109:59) at /home/username/reactor/server/lib/MessageBus.js:99:208 at Array.forEach (<anonymous>) at MessageBus._sendToBus (/home/username/reactor/server/lib/MessageBus.js:96:47) at /home/username/reactor/server/lib/MessageBus.js:109:48 at new Promise (<anonymous>) at MessageBus.send (/home/username/reactor/server/lib/MessageBus.js:106:16) at Entity.publish (/home/username/reactor/server/lib/Observable.js:71:44) at Entity.deferNotifies (/home/username/reactor/server/lib/Entity.js:248:207) 2021-10-04T14:11:03.858Z <Engine:5:Engine.js:1108> Engine#1 var (undefined) dependency entity-changed Entity#ezlo>device_603a036e129e0715cf4a763a 2021-10-04T14:11:03.859Z <default:CRIT> Error: Object does not exist Error: Object does not exist -
Is this on 21275?
Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
@toggledbits Sorry, yes. latest-21275-df3d784
-
OK. I think I see this. I was at least able to reproduce one case. It's not to do with deleting global variables, or global variables at all, really; it. It has to do with the subcontexts that are created by lexpjs in
eachstatements, and the MSR Engine looking for private data in the current context and not realizing that it was operating from a subcontext. And in this case, it was your rule expression that exposed the problem. Sounds messy, but not hard to fix. I think.Build coming later today.
FYI, just an observation on what you're doing in this rule expression:
join(each name in (each id in (matchEntities( { controller: 'ezlo', capability: 'x_ezlo_device' } )): getEntity( id ).attributes.x_ezlo_device.reachable == false ? id : null ): getEntity( name ).name, ', ' )If you use a compound statement (
do...done) as the body of a singleeachloop, and store thegetEntity()result in a temporary variable, you only need one loop, it looks a bit cleaner, and runs a lot faster (because you're only fetching the entity once):join( each id in matchEntities( { controller: 'ezlo', capability: 'x_ezlo_device' } ): do e=getEntity( id ), e.attributes.x_ezlo_device.reachable ? null : e.name done, ", " )This compound statement loop first stores the result of
getEntity()into a variablee. This variable, since it is being defined by the loop, can only be used within the loop. But, as you can see on the next line, it can be used both to make thereachabletest, and to returnnameas the loop body result foreach. Also note that since thereachableattribute is already a boolean, you can use it directly (without a comparison against another boolean), you just need to reverse the ternary operands (so whenreachableis true,nullis returned, and when not reachable, the entity name is returned).Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
@toggledbits Ok, great explanation!
I do like cleaner expressions and will absolutely switch todo...done, thank you for the example.
I knew it was doing double gets but each run took 0ms so I did not bother, but optimization is always welcomed.FYI: I have some devices paired that are not usable yet and they return x_ezlo_device.reachable=null so until they are integrated correctly I'll keep the boolean comparison for now.
-
Hi, updated MSR latest-21281-c4807c0
I have connection with ezloplus in set_anonymous_access: trueMSR 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`
-
[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 -
No changes to EzloController for several builds now. Mine is working great.
What's your install environment?
Log snippets need several dozen lines before the error in order to be useful. For controller connection issues, it's also good to capture the entire startup until a bit past the first connection failure.
-
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 -
Huh. Docker container also working just fine for me, with authenticated access, with anonymous access, and with anonymous insecure access. What version of firmware is your hub? Have you tried to reboot the hub?
-
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. -
Locked by toggledbits