• Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
Thanksgiving lighting took a holiday
G

18481340-4d9c-4d0c-8027-49adfa28f32a-image.png

e0e1c895-a830-48d5-8346-cbae551b441d-image.png

This has been working flawlessly each year incl this year until... Tonight... nada.

Is this due to the holiday being late this year ie because today is the 22nd, not after the 22nd?

Multi-System Reactor
MSR UI on a mobile browser
tunnusT

I've managed to use MSR UI on iOS devices to some degree*, so that although UI elements (e.g. rule sets) are not visible in portrait mode, you've seen them in landscape. Now with recents builds (24302) this does not work anymore, elements (rule sets, entities) are not anymore visible in landscape mode.

Does anyone have similar experiences? Using iOS 18 and Safari/Chrome browser.

( *Drag & drop of rule conditions have never worked on a mobile)

Multi-System Reactor
[Reactor] Assignment to alarm ignored -- expression-driven global cannot be set by assignment
therealdbT

Hi @toggledbits,

I have lots of logs with this:

<Engine:ERR> Assignment to alarm ignored -- expression-driven global cannot be set by assignment

Any hints to where look at to avoid this? Thanks.

Multi-System Reactor
[Reactor] [Dev] Clarifications/Docs for refreshCapabilities and Entity action implementations return types
therealdbT

Hi @toggledbits

I'd like to update my controllers with these new features, but I'm struggling to find any guidance in the docs - and in general to understand the context.

Could you please elaborate more? Thanks.

Multi-System Reactor
Access to log file viewer denied
tunnusT

I have the following ACL defined:

groups: admin: users: - admin applications: true api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: true

And I have authenticated to MSR as "admin" user. However, I'm getting "access denied" when trying to access http://*******:8111/api/v1/log

So what I'm missing, is my ACL incorrectly defined?

Using build 24302 on Docker.

Multi-System Reactor
Darker Reactor style
therealdbT

Thanks to @toggledbits for adding a custom CSS. I've started doing a darker Reactor style.

Here's the file: https://gist.github.com/dbochicchio/825098ac13b7f8cac22012eae37ff7ce

A couple of things are still too bright and I'll eventually catch-up. Just place it under your /config directory, naming the file as customstyles.css. Hard refresh your browser.

Multi-System Reactor
TTS in MSR?
F

Hi!

In Home Assistant I sometimes uses the TTS, either to my Sonos or Google speakers. With reactor in Vera I also use TTS.
But in MSR I can't select the TTS-service. It's simply not there. Am I missing something, or is this the case, so far?
Thanks!
/Fanan

Multi-System Reactor
Should MSR import this device type from an Ezlo controller?
cw-kidC

Hi

I have just connected a bunch of EzloPi controllers to MSR to import some ESP based devices etc.

They all seemed to have worked and imported in to MSR apart from I have one missing device. It is a Digital Gas Sensor device.

This is how that device looks in the Ezlo API.

Devices Info:

_id: "10696001" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "level_sensor" subcategory: "" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Digital" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"

Items Info:

_id: "20696001" deviceId: "10696001" hasGetter: true hasSetter: false name: "smoke_density" show: true valueType: "substance_amount" scale: "parts_per_million" value: 2.7472610473632812 valueFormatted: "2.75" status: "idle"

There is also an Analog Gas sensor that one did import in to MSR OK.

68d63dab-b871-4f44-912b-cf6e0b9eb4c6-image.png

Devices Info:

_id: "10696000" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "security_sensor" subcategory: "gas" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Analog" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"

Items Info:

_id: "20696000" deviceId: "10696000" hasGetter: true hasSetter: false name: "gas_alarm" show: true valueType: "token" enum: 0: "no_gas" 1: "combustible_gas_detected" 2: "toxic_gas_detected" 3: "unknown" valueFormatted: "no_gas" value: "no_gas" status: "idle"

And this is how this MQ2 Gas Sensor looks like on their dashboard:

Digital
cb77dfa3-4af5-4d06-9635-89207a716a89-image.png

Analog
4fb4da1b-e946-4b89-876c-bcd9f5699b6c-image.png

They have an EzloPi website here you can create your own sensor projects using ESP boards, which is very interesting stuff!

And I just wrote on the Ezlo forum here, how to connect an EzloPi controller to MSR.

THANKS.

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

Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here.

Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions; Fix an error in OWMWeatherController that could cause it to stop updating; Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later; Improve error detail in messages for EzloController during auth phase; Add isRuleSet() and isRuleEnabled() functions to expressions extensions; Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases); Fix a place in the UI where 24-hour time was not being displayed.
Multi-System Reactor
A couple of things about Reactor 24293
therealdbT

A couple of things for you @toggledbits, since you mentioned that this release has new features and some tweaks are expected.

Local expressions cannot be deleted. Pushing the X button has no effect for me.

When cloning an entity action, the result is strange (first is cloned one, second is the original action):
a92ea094-9e2c-4aaa-bf47-2d07a6ffdbd0-image.png

When changing the action on the cloned element, the params are added to the original one. See screenshot:
92ac3011-83c8-466b-bd23-47d483ad7a52-image.png

Dark theme has a couple of strange contrasts. One is visible in the previous screenshots (white text on yellow background). Another one is in groups (blue text on blue background):
9b3c4988-53ef-44e6-9672-30e744cacb75-image.png Overall, I found blue, yellow, red and green (in buttons and forms) to be too bright.

On the bright side:

I love the new script action: thank you! The dark theme is a great start to avoid getting blinded at night I promise I'll try very soon the new features around actions. Thanks!
Multi-System Reactor
Error on start for MSR after update to 24293
T

@toggledbits
I just upgraded to version MSR 24293, bare metal running on Fedora. Upon restart, I am getting a error banner:

TypeError: Cannot read properties of undefined (reading 'value') at Rulesets.getRulesets (https://*************************/client/Rulesets.js:111:38) at async StatusTab.updateSetRules (https://*************************/reactor/en-US/lib/js/reactor-ui-status.js:276:28) at async StatusTab.drawSetRules (https://*************************/reactor/en-US/lib/js/reactor-ui-status.js:270:13) You may report this error, but do not screen shot it. Copy-paste the text. Remember to include a description of the operation you were performing in as much detail as possible. Report using the Reactor Bug Tracker (in your left navigation) or at the SmartHome Community.

I followed the new directions about npm

npm i --no-save --no-package-lock --omit dev

Any idea what the issue is?

Multi-System Reactor
Dark Mode not Working - 24293
PablaP

Seems like switching the UI to the newly added dark mode (thank you for this) does nothing. The UI stays in light mode and only a few buttons turn into dark mode (see screenshot)

Things I have tried:

Hard refresh
Different browser
Different computer
Restarting Reactor

Failed troubleshooting attempts:

No errors in Chrome console
No relevant errors in Reactor log (can still PM the full log file)

Reactor version: latest-24293-ea42a81d
Hardware: Odroid N2+
Linux version: Ubuntu 24.04.1 LTS

3df2806f-9146-485b-9ec1-d056e91cefe5-image.png Dark mode enabled

ff823023-c079-4684-b01f-d6ac6527d31a-image.png Light mode enabled

Multi-System Reactor
Is there a way to restart an add-on in HAAS from MSR?
T

Good morning,
I have a service MQTT service that needs a restart occasionally. The add-on (Smartbed MQTT) is for the smart bed base for my bed. It has a "safety light" that I can control from HAAS & MSR as a light entity, and also moves the head of the bed to a preset at bedtime, and then lies it back flat in the morning The problem is, from time to time, the light becomes "unavailable" Restarting from the Add-ons tab in HAAS always fixes it, but I should be able to detect when it happens when "light.tempur_pedic_safety_lights" is not true or false, i.e., unavailable.

What I don't know how to do is how to restart that service. Does anybody have experience in restarting add-ons from MSR?

Running:

Reactor (Multi-hub) latest-24212-3ce15e25 ZWaveJSController [0.1.24232]

HAAS:

RPi5-64 (8GB) Core 2024.7.3 Supervisor 2024.08.0 Operating System 13.0 Frontend 20240710.0
Multi-System Reactor
Log files
wmarcolinW

Hi!

Is it possible to generate two additional log files, the first being the replica of what is displayed on screen by the Rule History widgets and the other with Recently Changed Entities?

And could I configure the generation of one file per day, and delete the older ones? For example, store the last 5 days?

And being more ambitious, does Windget have an icon to open these TXT files in the navigated?

Well, we're approaching Christmas, so here's my request to Santa Claus @toggledbits 🙂

Multi-System Reactor
[Reactor] Services with sync response
therealdbT

Hi @toggledbits

I'm working on a controller to generate llm response from a prompt in reactor. I have http response coming thru an http request action at the moment, capturing the response inside a local variable. So, it's practically sync.

I want to create a controller, so I don't have to rely on a proxy (and have a simpler architecture), and duplicate absurd http actions, but AFAIK in the current implementation, actions are async only. But if I have multiple requests going on, I cannot be sure what it's really inside an attribute. I also thought that something like a correlation id when sending the request could be used to identity multiple responses, but I wanted to double check with you before starting with something too complicated. I also noticed that some actions in home assistant (ie forecast) are sync and I'm wondering if you have any plan or hint to address this situation. Thanks.

Thanks.

Multi-System Reactor
TILT-ZWAVE2.5-ECO tilt_sensor.state (primary) = NULL
SnowmanS

@togglebits I am curious as to why the tilt_sensor.state (primary) = NULL. I believe it should show true or false. I have to use binary_sensor.state instead in my rules.

Again, not sure if this is related to Reactor/ZwaveJSController implementation or the actual Z-Wave JS UI docker version. I have copied, below, the attributes of the tilt sensor in hopes it can help.

Thanks in advance.

Reactor version 23302
ZWaveJSController version 23254
Z-Wave JS UI version 9.3.0.724519f
zwave-js version 12.2.3

battery_power.level=0.99 battery_power.since=1699401727360 binary_sensor.state=false tamper.state=true tilt_sensor.state=null x_debug.dt={"entity_class":"Binary Sensor","match":"deviceClass.generic.key=7","description":"Z-Wave Plus Tilt Sensor","default_name":"Tilt Sensor","model":"TILTZWAVE2.5-ECO","capabilities":["tilt_sensor"],"primary_attribute":"tilt_sensor.state","values":[{"valueId":"32:currentValue:","capabilities":{"tilt_sensor":{"attributes":{"state":{}}}}}],"manufacturerId":330,"productType":4,"productId":3} x_zwave_values.Battery_isLow=false x_zwave_values.Battery_level=99 x_zwave_values.Binary_Sensor_Any=false x_zwave_values.Configuration_Basic_Sets_for_Association_Group_2=0 x_zwave_values.Configuration_Send_Reports=0 x_zwave_values.Manufacturer_Specific_manufacturerId=330 x_zwave_values.Manufacturer_Specific_productId=3 x_zwave_values.Manufacturer_Specific_productType=4 x_zwave_values.Notification_Access_Control_Door_state=23 x_zwave_values.Notification_Access_Control_Door_state_simple=23 x_zwave_values.Notification_Home_Security_Cover_status=3 x_zwave_values.Notification_Power_Management_Battery_maintenance_status=0 x_zwave_values.Notification_UNKNOWN_0x46=23 x_zwave_values.Notification_alarmLevel=0 x_zwave_values.Notification_alarmType=0 x_zwave_values.Version_firmwareVersions=["10.1"] x_zwave_values.Version_hardwareVersion=2 x_zwave_values.Version_libraryType=6 x_zwave_values.Version_protocolVersion="4.5" x_zwave_values.Wake_Up_controllerNodeId=1 x_zwave_values.Wake_Up_wakeUpInterval=14400 zwave_device.capabilities=[48,112,113,114,128,132,134] zwave_device.endpoint=0 zwave_device.failed=false zwave_device.generic_class="Notification Sensor" zwave_device.impl_sig="23305:1:22057:1" zwave_device.is_beaming=false zwave_device.is_listening=false zwave_device.is_routing=true zwave_device.is_secure=false zwave_device.last_wakeup=1699563172708 zwave_device.manufacturer_info=[330,4,3] zwave_device.max_data_rate=null zwave_device.node_id=24 zwave_device.specific_class="Notification Sensor" zwave_device.status=1 zwave_device.status_text="asleep" zwave_device.version_info=[null,"10.1"] zwave_device.wakeup_interval=14400
Multi-System Reactor
Unusual zwavejs entity naming convention
SnowmanS

@toggledbits I have noticed after upgrading both Reactor and ZWaveJSController to version 24257 that two of my devices/entities, TILT-ZWAVE2.5-ECO and Zooz ZSE18, had their entity re-named in an unusual way and also appears to be duplicated.

Reactor version 24257
ZWaveJSController version 24257
Z-Wave JS UI version 9.18.1
zwave-js version 13.2.0

Vestibule Motion Sensor State attributes/partial screenshot of entities it created. All entities have the same attributes.

motion_sensor.state=true x_zwave_values.Notification_Home_Security_Motion_sensor_status=8 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=23 zwave_device.valueId=[113,"Notification","Home Security","Home Security","Motion sensor status","Motion sensor status"] zwave_device.version_info=null

Zooz ZSE18 Motion Sensor.jpg

Tilt Sensor Door State and Tilt Sensor Door State Simple attributes/partial screenshot of entities it created. All entities have similar attributes with exception of x_zwave_values.Notification_Access_Control_Door_State = 22 or 23.

tilt_sensor.state=true x_zwave_values.Notification_Access_Control_Door_state=22 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"] zwave_device.version_info=null tilt_sensor.state=true x_zwave_values.Notification_Access_Control_Door_state_simple=22 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"] zwave_device.version_info=null tilt_sensor.state=false x_zwave_values.Notification_Access_Control_Door_state=23 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"] zwave_device.version_info=null tilt_sensor.state=false x_zwave_values.Notification_Access_Control_Door_state_simple=23 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"] zwave_device.version_info=null

TILT-ZWAVE2.5-ECO.jpg

Multi-System Reactor

EzloController error

Scheduled Pinned Locked Moved Multi-System Reactor
20 Posts 3 Posters 667 Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • CrilleC Offline
    CrilleC Offline
    Crille
    replied to toggledbits on last edited by
    #5

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

    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #6

    Variables hm and HouseMode both are referenced somewhere, but appear to not be global. If you don't see hm in the list of global variables, it's probably buried in a rule somewhere. What about HouseMode? Global or rule?

    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

    CrilleC 1 Reply Last reply
    0
  • CrilleC Offline
    CrilleC Offline
    Crille
    replied to toggledbits on last edited by
    #7

    @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 named housemode

    rule_1.PNG rule_2.PNG

    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.

    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #8

    OK. Great detail. That helps, thank you. Let me see what I can do here...

    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

    CrilleC 1 Reply Last reply
    0
  • CrilleC Offline
    CrilleC Offline
    Crille
    replied to toggledbits on last edited by Crille
    #9

    @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!
    ezlo_triggers.PNG ezlo_expression.PNG

    I've now put a sustianed for 3 secs on the first variable trigger to ignore flapping.

    global_expressions.PNG

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

    CrilleC 1 Reply Last reply
    0
  • CrilleC Offline
    CrilleC Offline
    Crille
    replied to Crille on last edited by
    #10

    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
    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #11

    Is this on 21275?

    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

    CrilleC 1 Reply Last reply
    0
  • CrilleC Offline
    CrilleC Offline
    Crille
    replied to toggledbits on last edited by Crille
    #12

    @toggledbits Sorry, yes. latest-21275-df3d784

    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #13

    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 single each loop, and store the getEntity() 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 variable e. 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 the reachable test, and to return name as the loop body result for each. Also note that since the reachable 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 when reachable is true, null is returned, and when not reachable, the entity name is returned).

    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

    CrilleC 1 Reply Last reply
    0
  • CrilleC Offline
    CrilleC Offline
    Crille
    replied to toggledbits on last edited by Crille
    #14

    @toggledbits Ok, great explanation!
    I do like cleaner expressions and will absolutely switch to do...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.

    1 Reply Last reply
    1
  • N Offline
    N Offline
    noelab
    wrote on last edited by noelab
    #15

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

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

    `

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

    `

    -Reactor (Multi-hub) latest-24302-751a06b6
    -Docker on Synology NAS
    -Ezlo firmware version 2.0.59.2471.8
    -HASS Docker 2024.10.3

    • Update 02/11/2024
    N 1 Reply Last reply
    0
  • N Offline
    N Offline
    noelab
    replied to noelab on last edited by
    #16

    @noelab

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

    -Reactor (Multi-hub) latest-24302-751a06b6
    -Docker on Synology NAS
    -Ezlo firmware version 2.0.59.2471.8
    -HASS Docker 2024.10.3

    • Update 02/11/2024
    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by toggledbits
    #17

    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.

    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

    1 Reply Last reply
    0
  • N Offline
    N Offline
    noelab
    wrote on last edited by toggledbits
    #18

    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

    -Reactor (Multi-hub) latest-24302-751a06b6
    -Docker on Synology NAS
    -Ezlo firmware version 2.0.59.2471.8
    -HASS Docker 2024.10.3

    • Update 02/11/2024
    1 Reply Last reply
    0
  • toggledbitsT Offline
    toggledbitsT Offline
    toggledbits
    wrote on last edited by
    #19

    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?

    Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.

    1 Reply Last reply
    0
  • N Offline
    N Offline
    noelab
    wrote on last edited by
    #20

    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.

    -Reactor (Multi-hub) latest-24302-751a06b6
    -Docker on Synology NAS
    -Ezlo firmware version 2.0.59.2471.8
    -HASS Docker 2024.10.3

    • Update 02/11/2024
    1 Reply Last reply
    0
  • toggledbitsT toggledbits locked this topic on

Recent Topics

  • G
    Thanksgiving lighting took a holiday
  • G
    High temperature sensor for Zigbee
  • M
    MSR UI on a mobile browser
  • G
    New to Home Automation Looking for a Single app?
  • H
    UZB/RaZberry Firmwares - Update
  • therealdbT
    Sending data to a USB port to interface with a wireless switch
  • G
    Seeking Advice:
  • toggledbitsT
    [Reactor] Assignment to alarm ignored -- expression-driven global cannot be set by assignment
  • therealdbT
    [Reactor] [Dev] Clarifications/Docs for refreshCapabilities and Entity action implementations return types
  • akbooerA
    Looking for Remote Switch boxes that can also be used with a wireless Decora Style Switch.
  • parkercP
    Openluup - verabridge can not load devices.
Powered by NodeBB | Contributors
Hosted freely by 10RUPTiV - Solutions Technologiques | Contact us
  • Login
  • Don't have an account? Register
  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved