-
Some background
I have MQTTController based entities that I want to use in time calculations in my rules. These entities represent two separate time ranges, one for the weekdays and the other for the weekends. In this particular example they are used to control my doorbell activity (whether it's enabled or disabled).
MQTT message which is used to update the entities. NOTE: time is in 24h format
{ "data": { "weekdays": { "enable": "09:28", "disable": "20:00" }, "weekends": { "enable": "09:00", "disable": "21:00" } } }Entity definitions (here's only the definition for the weekdays for brevity)
doorbell-weekdays-enable: name: 'Ovikello päälle (arkisin)' topic: 'doorbell/settings' capabilities: - string_sensor primary_attribute: string_sensor.value events: "%topic%": "string_sensor.value": json_payload: true expr: "payload.data.weekdays.enable" doorbell-weekdays-disable: name: 'Ovikello pois päältä (arkisin)' topic: 'doorbell/settings' capabilities: - string_sensor primary_attribute: string_sensor.value events: "%topic%": "string_sensor.value": json_payload: true expr: "payload.data.weekdays.disable"I have verified that the entities are populated correctly and the values are working in local expressions.
The entity (only the range start for brevity):
Screenshot from 2023-03-22 09-27-54.pngThe rule:
Screenshot from 2023-03-22 09-28-28.pngAnd the local expression within the rule:
weekdays_enabled = (time() >= time(getEntity( "mqtt>doorbell-weekdays-enable" ).attributes.string_sensor.value )) && (time() <= time(getEntity( "mqtt>doorbell-weekdays-disable" ).attributes.string_sensor.value ))The problem
Local expression doesn't seem to evaluate to true even if the current time gets within the range. But if the related entities are updated, then the expression is evaluated and the rule is triggered.As seen from the screenshots, the current time is 09:28:12 and the start time in corresponding entity is set to 09:28. But still the rule is not triggered. However, if I update the entity e.g. to 09:27, the local expression will get evaluated and the rule is triggered.
My understanding is that the local expression is working correctly but since it's not evaluated, it will not trigger the rule.
Is this a bug or have I misunderstood something? If so, how should I implement this kind of functionality?
br,
mgvraReactor (Multi-hub) latest-23078-d592d400 + MQTTController [0.1.23010]
-
Converting from Vera Plus to Hubitat at two different locations. The two sites are interconnected via a router-to-router VPN. I currently have a Hubitat C7 running at Site One and a Vera Plus at Site Two. The MSR Raspberry Pi is co-located with the Vera Plus at Site Two. I "activated" a Hubitat C8 (ethernet connected) at Site Two including the installation of Hub Information Driver and its associated device. I also installed a single zwave outlet module (GE ZW4202). I restarted MSR. The C8 and its associated devices appear on both the Entities page and the MSR Dashboard, but the C8 reports as down on the MSR Status page and the GE outlet does not respond when "clicked". I am not sure where to look to try to find the source of the problem and will greatly appreciate any suggestions.
-
I have a use case where I need to have a boolean variable that will be set to true/false by reactions.
I see that i can define a local variable by giving it a name and leaving the definition empty. This leaves it at state "null" until a reaction tells it that its a boolean.
Is there a way to tell it that it should start out as "false" (i.e when reactor has restarted), and not null?
Am i going about this the wrong way?
-- The use case is that I have a sensor on my fireplace, and the following logic is for notifying when its time to get up en refill with firewood.. I also want to reset the MaxInInterval to CurrentTemp when notification is sent..
1fd2951f-cb6b-4a2f-b957-1e0698171f4d-image.png dd99634e-f0ad-4878-bb87-0284c2df5535-image.png
Edit: better screenhots. Reactor version 23010-7dd2c9e9
-
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here.
Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed. -
Hi guys,
I want to import my reactor sensors in the MSR addon for Home Assistant, but I can't find the app.js file anywhere. So now I don't know where to put the backup file.
I have not tried to put it in the main directory (config/reactor) yet. Wanted to know if I'm the only one with the problem.
Reactor addon: v0.0.8
MSR: 23063-c464b685
Home Assistant 2023.3.3
Supervisor 2023.03.1
Operating System 9.5
Frontend 20230202.0 - latestI started with v0.0.7, have just updated everything. Still no file.
-
I'm a little bit confused how to configure extended capabilities for the entities in the MQTTController.
mqtt_cababilities.yaml states that: "...You can add your own capabilities by adding a "capabilities" section to your own local_mqtt_capabilities.yaml file in your config directory."
So I did this in my local_mqtt_capabilities.yaml in the config directory:
version: 22353 revision: 1 format: 1 capabilities: x_my_config: attributes: partyMode: type: bool actions: some_action: topic: '%topic/write' payload: "some value"And in my reactor.yaml I have following configuration entry:
my-config: name: 'My custom configuration' topic: 'my-config' query: "%topic%/read" init: "%topic%/read" capabilities: - x_my_config primary_attribute: x_my_config.partyMode events: "%topic%/status": "x_my_config.partyMode": json_payload: true expr: "payload.partyMode"This sort of works but not quite. The partyMode attribute gets updated when messages arrive for that specific topic, so that's fine. But I don't see x_my_config capability in the Capabilities list in the UI and also the some_action is missing.
Screenshot from 2023-03-09 19-42-49.png
Addition to that the primary value is not set and I'm getting the following error:
Screenshot from 2023-03-09 19-30-42.pngHave I completely misunderstood the idea behind the capability extension and the attributes? If so, could someone point me to the right direction with few explanatory example configs.
What I'm trying to achieve is a set of configuration options that could be updated thru the MQTT, and also provide some actions that the rules could invoke.
Reactor (Multi-hub) latest-23063-c464b685 + MQTTController [0.1.23010]
br,
mgvra -
-
Installing MQTTController on Home Assistant Core when Reactor is installed as an Add-In (VirtualBox)
Running Home Assistant Core under VirtualBox (on Windows) and Reactor is installed and working fine as an add-in. What I can't figure out is how to install MQTTController in this situation. I can upload the files and unzip them, but I can't run install.sh in a terminal window because npm is not a part of the Core installation.
It does appear that somewhere in the stack there is a version of docker there between VirtualBox and HA, (I see some references go by in the VirtualBox startup log) but it appears minimal and will not execute the install via the docker technique in your documentation from the VB console.
Is there a way to do this?
Thanks.
-
I've done a bit of repackaging of MSR to make it work as an add-on under Home Assistant mostly for my own purposes but hopefully it makes it a bit easier to install and get going.
GitHub - mrw298/hassio-reactor-addon GitHub - mrw298/hassio-reactor-addon
Contribute to mrw298/hassio-reactor-addon development by creating an account on GitHub.
-
@toggledbits somewhere I thought I read that MSR goes thru the items in set reaction and reset reaction in stack order, ie from top to bottom/first to last.
Am I mistaken?
-
Reactor 23063 running on Windows Bare Metal.
Home assistant 2023.3.1
ESPHome 2023.2.4I've been trying a few ways using some results from search to call a Hass service as a reaction in a Reactor rule.
Specifically, when the PIR in the room senses motion, wake the NsPanel screen.
My Reactions otherwise so far are basic If this then that so I'm way behind what others are doing.
What I want to call as a Reaction:
Capture1.PNGWhat I've tried (a few variations on):
Capture2.PNGWhat happens:
[latest-23063]2023-03-07T07:45:21.688Z <wsapi:ERR> wsapi: error thrown handling client message [Object]{ "command": "perform", "entity": "WOKHASS1>system", "action": "x_hass_system.call_service", "parameters": { "service": "ESPHome: nspensuite_send_command_printf", "data": "page home" }, "qid": 75 } [latest-23063]2023-03-07T07:45:21.688Z <wsapi:CRIT> TypeError: Cannot read properties of null (reading '1') [-] TypeError: Cannot read properties of null (reading '1') at HassController.performOnEntity (C:\reactor\reactor\server\lib\HassController.js:584:108) at System.perform (C:\reactor\reactor\server\lib\Entity.js:707:56) at WSAPI.clientMessage (C:\reactor\reactor\server\wsapi\wsapi.js:499:48) at WebSocket.<anonymous> (C:\reactor\reactor\server\wsapi\wsapi.js:290:158) at WebSocket.emit (node:events:520:28) at WebSocket.emit (node:domain:475:12) at Receiver.receiverOnMessage (C:\reactor\reactor\node_modules\ws\lib\websocket.js:1059:20) at Receiver.emit (node:events:520:28) at Receiver.emit (node:domain:475:12) at Receiver.dataMessage (C:\reactor\reactor\node_modules\ws\lib\receiver.js:517:14)If someone can convert the 'call service' to a 'reaction' for me, or share their own similar thing I think that's what I need to achieve this goal.
I suspect if I'm even close to being on the right track, my problems are probably formatting like curly braces etc and lack thereof.
Thanks in advance.
-
@toggledbits was looking thru rule sets and updating which (new) lights I wanted REMII to impact and saw that this...
4711b0df-5e98-4992-bb25-d0e53203f0e8-image.png
...is showing as (missing) in the rule Deactivatedand looking in the dropdown of Variables it appears I cannot select that local expression (only Global) as I did when originally building this out back in 2021.
27f7025c-057e-441a-88ea-dc4bdf39614d-image.png
In looking at the rule Active Period I'm seeing:
487074ef-3bfa-4a84-b03d-ed6d920c118c-image.png which appears to be pointing to setting a variable in a rule?It's admittedly been a couple years since this was built and it's def not fresh in my memory.
-
New installation of Reactor version 23063-c464b685 on a Raspberry PI4 with Portainer/Docker.
Report :
No drop-down list on Entity Attribute in "Creation Rule Sets" interface
I can however visualize the entities.
I have configured HomeAssistant and all entities are coming up fine.
I have an unsupported Hass version 2023.3.0b5.
I'm new to Docker and can someone guide me to a solution?
Christian FABREAlert:
[latest-23063]2023-03-05T09:51:49.575Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/arm64 #1595 SMP PREEMPT Wed Oct 26 11:07:24 BST 2022; locale (undefined) [latest-23063]2023-03-05T09:51:49.576Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-23063]2023-03-05T09:51:49.577Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-23063]2023-03-05T09:51:49.584Z <app:INFO> Configured locale (undefined); selected locale(s) en-US.UTF-8 [latest-23063]2023-03-05T09:51:49.708Z <app:INFO> Loaded locale en-US for en-US [latest-23063]2023-03-05T09:51:49.725Z <Structure:null> Module Structure v22323 [latest-23063]2023-03-05T09:51:49.729Z <Capabilities:null> Module Capabilities v22356 [latest-23063]2023-03-05T09:51:49.806Z <Capabilities:NOTICE> System capabilities loaded from core distribution, data version 23058 revision 1 [latest-23063]2023-03-05T09:51:49.849Z <Plugin:null> Module Plugin v22300 [latest-23063]2023-03-05T09:51:49.869Z <TimerBroker:null> Module TimerBroker v22283 [latest-23063]2023-03-05T09:51:49.878Z <Entity:null> Module Entity v22353 [latest-23063]2023-03-05T09:51:49.889Z <Controller:null> Module Controller v23044 [latest-23063]2023-03-05T09:51:49.926Z <default:null> Module Ruleset v22293 [latest-23063]2023-03-05T09:51:49.928Z <default:null> Module Rulesets v22146 [latest-23063]2023-03-05T09:51:49.943Z <GlobalExpression:null> Module GlobalExpression v22146 [latest-23063]2023-03-05T09:51:49.977Z <Predicate:null> Module Predicate v22345 [latest-23063]2023-03-05T09:51:49.987Z <AlertManager:null> Module AlertManager v22283 [latest-23063]2023-03-05T09:51:49.995Z <Rule:null> Module Rule v22345 [latest-23063]2023-03-05T09:51:50.004Z <GlobalReaction:null> Module GlobalReaction v22324 [latest-23063]2023-03-05T09:51:50.008Z <Engine:null> Module Engine v23001 [latest-23063]2023-03-05T09:51:50.019Z <httpapi:null> Module httpapi v23058 [latest-23063]2023-03-05T09:51:50.078Z <wsapi:null> Module wsapi v23053 [latest-23063]2023-03-05T09:51:50.080Z <app:NOTICE> Starting Structure... [latest-23063]2023-03-05T09:51:50.100Z <Structure:NOTICE> Structure#1 plugin ID influx disabled; skipping [latest-23063]2023-03-05T09:51:50.106Z <Structure:INFO> Structure#1 loading controller interface hass (HassController) [latest-23063]2023-03-05T09:51:50.210Z <HassController:null> Module HassController v23060 [latest-23063]2023-03-05T09:51:50.639Z <Structure:INFO> Structure#1 loading controller interface groups (DynamicGroupController) [latest-23063]2023-03-05T09:51:50.649Z <DynamicGroupController:null> Module DynamicGroupController v22313 [latest-23063]2023-03-05T09:51:50.659Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController) [latest-23063]2023-03-05T09:51:50.672Z <SystemController:null> Module SystemController v22306 [latest-23063]2023-03-05T09:51:50.680Z <Structure:INFO> Starting controller HassController#hass [latest-23063]2023-03-05T09:51:50.682Z <HassController:NOTICE> HassController#hass starting... [latest-23063]2023-03-05T09:51:50.691Z <Controller:INFO> HassController#hass loaded hass capabilities ver 22312 rev 2 format 1 [latest-23063]2023-03-05T09:51:50.715Z <Controller:INFO> HassController#hass loaded implementation data ver 23058 rev 1 format 1 [latest-23063]2023-03-05T09:51:50.715Z <Structure:INFO> Starting controller DynamicGroupController#groups [latest-23063]2023-03-05T09:51:50.728Z <Controller:NOTICE> Controller DynamicGroupController#groups is now online. [latest-23063]2023-03-05T09:51:50.728Z <Structure:INFO> Starting controller SystemController#reactor_system [latest-23063]2023-03-05T09:51:50.733Z <Controller:NOTICE> Controller SystemController#reactor_system is now online. [latest-23063]2023-03-05T09:51:50.877Z <HassController:INFO> HassController#hass device mapping data loaded; checking... [latest-23063]2023-03-05T09:51:50.881Z <HassController:WARN> HassController: implementation of capability input_select.selector does not provide attribute values [latest-23063]2023-03-05T09:51:50.884Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.1.31:8123/api/websocket [latest-23063]2023-03-05T09:51:50.894Z <app:NOTICE> Starting HTTP server and API... [latest-23063]2023-03-05T09:51:50.901Z <httpapi:NOTICE> httpapi: starting HTTP service on port "8111" [latest-23063]2023-03-05T09:51:50.909Z <app:NOTICE> Starting Reaction Engine... [latest-23063]2023-03-05T09:51:50.910Z <Engine:INFO> Reaction Engine starting [latest-23063]2023-03-05T09:51:50.911Z <Engine:INFO> Checking rule sets... [latest-23063]2023-03-05T09:51:50.916Z <Engine:INFO> Checking rules... [latest-23063]2023-03-05T09:51:50.923Z <Engine:INFO> Data check complete; no corrections. [latest-23063]2023-03-05T09:51:50.938Z <Rule:NOTICE> rule-leu8xfe4 (rule-leu8xfe4 in First Rule Set) starting [latest-23063]2023-03-05T09:51:50.939Z <Engine:NOTICE> Reaction Engine running! [latest-23063]2023-03-05T09:51:50.939Z <Rule:NOTICE> rule-leu8xfe4 (rule-leu8xfe4 in First Rule Set) can't start -- rule is disabled [latest-23063]2023-03-05T09:51:50.952Z <httpapi:NOTICE> httpapi: listening [latest-23063]2023-03-05T09:51:50.981Z <app:NOTICE> Starting WSAPI... [latest-23063]2023-03-05T09:51:50.983Z <wsapi:NOTICE> wsapi: starting version 23053 [latest-23063]2023-03-05T09:51:51.080Z <Engine:INFO> [Engine]Engine#1 master timer tick, local time "3/5/2023 10:51:51 AM" (TZ offset 60 mins from UTC) [latest-23063]2023-03-05T09:51:51.119Z <HassController:NOTICE> HassController#hass connected, starting protocol [latest-23063]2023-03-05T09:51:51.127Z <httpapi:INFO> httpapi: API request from ::ffff:192.168.1.42: GET /api/v1/systime [latest-23063]2023-03-05T09:51:51.145Z <HassController:INFO> HassController#hass successful authentication with ws://192.168.1.31:8123; fetching initial data... [latest-23063]2023-03-05T09:51:51.155Z <HassController:INFO> HassController#hass Hass reports version "2023.3.0b5" location Maison timezone Europe/Paris state RUNNING safe_mode false [latest-23063]2023-03-05T09:51:51.245Z <HassController:NOTICE> HassController#hass no signature match for update.home_assistant_supervisor_update [latest-23063]2023-03-05T09:51:51.248Z <HassController:NOTICE> HassController#hass no signature match for update.home_assistant_core_update [latest-23063]2023-03-05T09:51:51.249Z <HassController:NOTICE> HassController#hass no signature match for update.terminal_ssh_update [latest-23063]2023-03-05T09:51:51.250Z <HassController:NOTICE> HassController#hass no signature match for update.file_editor_update [latest-23063]2023-03-05T09:51:51.251Z <HassController:NOTICE> HassController#hass no signature match for update.samba_backup_update [latest-23063]2023-03-05T09:51:51.252Z <HassController:NOTICE> HassController#hass no signature match for update.home_assistant_operating_system_update [latest-23063]2023-03-05T09:51:51.253Z <HassController:NOTICE> HassController#hass no signature match for sun.sun [latest-23063]2023-03-05T09:51:51.285Z <HassController:NOTICE> HassController#hass no signature match for calendar.calendrier [latest-23063]2023-03-05T09:51:51.413Z <HassController:NOTICE> HassController#hass no signature match for siren.piscine_siren [latest-23063]2023-03-05T09:51:51.419Z <HassController:NOTICE> HassController#hass no signature match for camera.portillon [latest-23063]2023-03-05T09:51:51.607Z <Controller:INFO> HassController#hass 0 dead entities older than 86400000s purged [latest-23063]2023-03-05T09:51:51.633Z <Controller:NOTICE> Controller HassController#hass is now online. [latest-23063]2023-03-05T09:51:51.634Z <DynamicGroupController:INFO> All controllers ready, setting up dynamic groups [latest-23063]2023-03-05T09:51:51.726Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.1.42 [latest-23063]2023-03-05T09:51:55.510Z <wsapi:INFO> client "192.168.1.42#1" closed, code=1001, reason= [latest-23063]2023-03-05T09:51:55.815Z <httpapi:INFO> httpapi: API request from ::ffff:192.168.1.42: GET /api/v1/lang [latest-23063]2023-03-05T09:51:55.843Z <wsapi:INFO> wsapi: connection from ::ffff:192.168.1.42 [latest-23063]2023-03-05T09:51:56.849Z <httpapi:INFO> httpapi: API request from ::ffff:192.168.1.42: GET /api/v1/systime [latest-23063]2023-03-05T09:52:07.392Z <httpapi:INFO> httpapi: API request from ::ffff:192.168.1.42: GET /api/v1/systime---
reactor_20230305_01.png Rule :
reactor_20230305_02.png Entities:
reactor_20230305_03.png log Reactor :Log Portainer:
NODE_PATH /opt/reactor:/opt/reactor/node_modules [latest-23063]2023-03-05T08:55:17.734Z <app:null> Reactor build latest-23063-c464b685 starting on v16.15.1 [latest-23063]2023-03-05T08:55:17.736Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/arm64 #1595 SMP PREEMPT Wed Oct 26 11:07:24 BST 2022; locale (undefined) [latest-23063]2023-03-05T08:55:17.737Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage [latest-23063]2023-03-05T08:55:17.738Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules [latest-23063]2023-03-05T08:55:17.875Z <Structure:null> Module Structure v22323 [latest-23063]2023-03-05T08:55:17.879Z <Capabilities:null> Module Capabilities v22356 [latest-23063]2023-03-05T08:55:18.004Z <Plugin:null> Module Plugin v22300 [latest-23063]2023-03-05T08:55:18.023Z <TimerBroker:null> Module TimerBroker v22283 [latest-23063]2023-03-05T08:55:18.032Z <Entity:null> Module Entity v22353 [latest-23063]2023-03-05T08:55:18.042Z <Controller:null> Module Controller v23044 [latest-23063]2023-03-05T08:55:18.079Z <default:null> Module Ruleset v22293 [latest-23063]2023-03-05T08:55:18.080Z <default:null> Module Rulesets v22146 [latest-23063]2023-03-05T08:55:18.096Z <GlobalExpression:null> Module GlobalExpression v22146 [latest-23063]2023-03-05T08:55:18.129Z <Predicate:null> Module Predicate v22345 [latest-23063]2023-03-05T08:55:18.139Z <AlertManager:null> Module AlertManager v22283 [latest-23063]2023-03-05T08:55:18.146Z <Rule:null> Module Rule v22345 [latest-23063]2023-03-05T08:55:18.156Z <GlobalReaction:null> Module GlobalReaction v22324 [latest-23063]2023-03-05T08:55:18.159Z <Engine:null> Module Engine v23001 [latest-23063]2023-03-05T08:55:18.171Z <httpapi:null> Module httpapi v23058 [latest-23063]2023-03-05T08:55:18.232Z <wsapi:null> Module wsapi v23053 [latest-23063]2023-03-05T08:55:18.358Z <HassController:null> Module HassController v23060 [latest-23063]2023-03-05T08:55:18.780Z <DynamicGroupController:null> Module DynamicGroupController v22313 [latest-23063]2023-03-05T08:55:18.803Z <SystemController:null> Module SystemController v22306``` -
Sorry for another dumb question. Migrating from Vera Alexa to HASS Vera TTS. MSR is on bare metal, Debian Bullseye version 23049
I can get TTS from MSR and basic TTS from MSR which is great!
Trying to get some of the variables I used to use though is stumping me.
In the original MSR, I'd use:
It is now ${{OutingDays}} days until we go to ${{OutingName}}. , Sleep well!for example, and that worked fine (I've not bothered to list the variables as I know the worked)
If I use
{ "message":"It is now${{OutingDays}} days until we go to ${{OutingName}}. , Sleep well!", "data":{"type":"announce", "method":"speak"}, "target":["media_player.everywhere"] }In the data field of the hass service system call it doesn't evaluate the variables (Not really surprised)
So might someone take mercy on me and give me a clue?
TIA
C
-
I'm back from a vacation and it was the first winter one with MSR.
I have a special vacation mode that's auto-setting after the house is in away mode for at least 18 hours - and that's mostly OK. In this mode, lights are turned on/off automatically, some things are off to preverse powers, etc. Thermostats are automatically set at 17C unless there's solar power. That's mostly OK, except when you have to deal with winters and clouds on the day back home.
Long story short: back from vacation, we found the house at 17C - wife wasn't impressed.
Back in the luup days I had a special override, that I forgot to port to MSR, that was basically like this in MSR (coded on the fly):
32298706-86f7-451e-9700-2baf5d5a23b6-image.png
So, I could tell my system when I'm on vacation and have a last day flag to re-set the house to normal behavior before I'm back. It was just two strings variable in a virtual binary sensor.
I don't want to code this in global expressions, so I'm wondering if it's possible to accomplish this with a Virtual Device, but I'm failing to visualize the correct answer and I'm here for inspiration for what others are doing to tackle this.
I don't want to create 4 separate devices (start date, end date, status, last day) in order to keep it easy and I want to be able to change the start/end date from the UI, to simplify things. Any hint is appreciated 🙂
-
I updated to the latest version of Reactor this morning. I run reactor (successfully) on a Raspberry PI 4 4GB with SSD 64GB. I also run Home Assistant in Docker. After updating I noticed a disk space critical error warning!
9f4e1ea1-977a-481b-9806-d3d43a4eff04-image.png
I have tried purging the docker install (docker image prune -a)
I have rebooted the Raspberry PI also, and the error messages keep coming.
I have the following disk space:
58742ed7-e10d-4572-b380-0abda64f90b4-image.png
How do I free up space?
Any help would be appreciated.
-
Good morning,
I'm trying to recreate some notifications I received on my old Vera system based upon House mode. I migrated from Vera to Home Assistant about 6 months ago, and all the automation I have set up are working great, however, I'm noticing that there were things that were once simple in Vera that are more involved in Home Assistant.In House Modes in Vera, there was a screen where I could select all the devices I wanted to be armed in various house modes. I recreated those house modes in Home Assistant very early on, but what I'm not getting now is notifications for various sensors. For instance, if the system is in Away mode, and interior motion is detected, I would get a Vera push notification on my phone. I've been setting these up one by one using haas>system --> x_haas_system.call_service, then setting the notify device and the message, one by one, but it's repetitious and tedious. For a few devices, like motion sensors on my ground floor, it's not a big deal, but now I'm looking at all the windows in my home, which have sensors on them.
So, enough of the background thesis. Simply put, is there a way to have a group of devices ( like 16 different window sensors ) as an entity, and when they are tripped, send out a notification and state which of those sensors was tripped, all in a single rule?
If I have to copy and edit 16 different rules, I'll do that, but I'd prefer a more elegant way where there is one rule to send out the notifications that tells me what was opened.
Thanks for all your advice/help in advance.
I'm running MSR latest-23049-1fd87c91 and Home Assistant 2023.2.5, Supervisor 2023.01.1, Operating System 9.5,
BTW, @toggledbits, I noticed on the About screen for MSR it still shows copyright from 2022. I know you've released versions this year.
Reactor (Multi-hub) latest-23049-1fd87c91 © 2020-2022 Kedron Holdings LLC, All Rights Reserved; Patrick Rigney (toggledbits), Principal Engineer.
-
I'd like the "None deferred" Reset Reaction group to have multiple Conditions. Is this not possible?
Running latest version of MSR, 23049-1fd87c91
-
I have upgraded my Hubitat Hub Information Driver to v3 and after the latest MSR update latest-23028 MSR is working ok. The problem is when MSR probes the device it appears to affect the polling in the new Hub Information Device and its data does not update the data fields in Hubitat. If I remove the Hub Information Device from Maker API so MSR can't see it, The Hub information driver updates the data as expected in Hubitat. I added the device back into Maker API the same problem returns in Hubitat. I have tried to have MSR probe a different device by adding a different probe device and probe action in the reactor.yaml per the documentation but it appears then it still uses the Hub Information Device as the probe device instead of the one specified in the reactor.yaml. See Logs below. Is this the intended behavior to always use the Hub Information Driver if found and not use the device in the reactor.yaml file? Any recommendations on how to get MSR and the v3 of the driver to work correctly or can you see what I am doing wrong?
[latest-23028]2023-02-11T23:27:50.471Z <Controller:NOTICE> Controller HassController#hass is now online. [latest-23028]2023-02-11T23:27:50.471Z <Rule:INFO> Internet Check (rule-l44qss4f in Home) starting evaluation; because entity-changed System#reactor_system>system [latest-23028]2023-02-11T23:27:50.471Z <Rule:INFO> MSR Update Version Available (rule-labweim2 in Notify) starting evaluation; because entity-changed System#reactor_system>system [latest-23028]2023-02-11T23:27:50.472Z <Rule:INFO> Internet Check (rule-l44qss4f in Home) trigger evaluation result is false (previously false) [latest-23028]2023-02-11T23:27:50.472Z <Rule:INFO> Internet Check (rule-l44qss4f in Home) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23028]2023-02-11T23:27:50.472Z <Rule:INFO> MSR Update Version Available (rule-labweim2 in Notify) trigger evaluation result is false (previously false) [latest-23028]2023-02-11T23:27:50.472Z <Rule:INFO> MSR Update Version Available (rule-labweim2 in Notify) evaluated; trigger state unchanged (false); rule state remains RESET [latest-23028]2023-02-11T23:27:50.472Z <Rule:INFO> Internet Check (rule-l44qss4f in Home) evaluation complete [latest-23028]2023-02-11T23:27:50.472Z <Rule:INFO> MSR Update Version Available (rule-labweim2 in Notify) evaluation complete [latest-23028]2023-02-11T23:27:50.673Z <HubitatController:INFO> HubitatController#hubitat Maker API responded with 91 devices [latest-23028]2023-02-11T23:27:50.766Z <HubitatController:INFO> HubitatController#hubitat found 'Hub Information Driver v3' device #"481"; using for probe/health checks. [latest-23028]2023-02-11T23:27:50.780Z <Controller:INFO> HubitatController#hubitat 0 dead entities older than 86400000s purged [latest-23028]2023-02-11T23:27:50.780Z <Rule:INFO> Roku Pause (rule-l3nlrzu9 in Home) starting evaluation; because entity-changed BinarySensor#hubitat>519 [latest-23028]2023-02-11T23:27:50.780Z <Rule:INFO> Stairs Light Low Light (rule-kulslls9 in Living Room) starting evaluation; because entity-changed BinarySensor#hubitat>519 [latest-23028]2023-02-11T23:27:50.780Z <Rule:INFO> Porch Motion Extended check (rule-l3kr45m8 in Porch) starting evaluation; because entity-changed BinarySensor#hubitat>519 [latest-23028]2023-02-11T23:27:50.780Z <Rule:INFO> Porch Light Manual On (rule-kmtxw155 in Porch) starting evaluation; because entity-changed BinarySensor#hubitat>519Snippet from the reactor.yaml:
# action_pace: 100 # warn_unresponsive: true # probe_device: hubitat>132 (not needed if Hub Information app installed) probe_device: hubitat>2 # probe_action: x_hubitat_Configuration.configure (not needed if Hub Information app installed) probe_action: x_hubitat_Configuration.configure # probe_action: x_hubitat_Refresh.refreshSynology Docker latest-23028
Hubitat v2.3.4.139
Hub Information Driver v3 -
Hey Patrick,
I’m trying to figure out how to run Home Assistant native push notifications from MSR. I have MSR set up to arm my home alarm every night, and when all users are out of the home. I’ve used it for years through Reactor, and it works fine, but when I ran Vera and Reactor for Vera, I would get notifications from Vera when Vera went into different home modes. (Home, Away, Night, etc). I’ve set up Home Modes in HA as well, so I’m looking to get the native push notifications from the HA companion app (i.e., System in Home Mode, System Armed Away, or Good Night, etc) Can I set up notifications from MSR to use those native push notifications, or does that need to be done from HA exclusively?I’m running latest-23028-ddc3fb14 and Home Assistant 2023.1.7.
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: 1002
Reactor 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 variable
and 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
hm
associated with rule Notifiering - House mode (Rule#rule-ksw26xod): can you tell me if that's a rule variable, or a global variable? -
@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
hm
is an old test I did and does no longer exist and is not referenced anywhere visible to me? -
Variables
hm
andHouseMode
both are referenced somewhere, but appear to not be global. If you don't seehm
in the list of global variables, it's probably buried in a rule somewhere. What aboutHouseMode
? Global or rule? -
@toggledbits After going through every Rule Set I have, I deleted the global
HouseMode
hours before I got this error since it was not referenced anywhere.
hm
was 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>housemode
since 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...
-
@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?
-
@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
each
statements, 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 singleeach
loop, 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 thereachable
test, and to returnname
as the loop body result foreach
. Also note that since thereachable
attribute is already a boolean, you can use it directly (without a comparison against another boolean), you just need to reverse the ternary operands (so whenreachable
is true,null
is returned, and when not reachable, the entity name is returned). -
@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.
-
toggledbits