Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
  1. Home
  2. Software
  3. Multi-System Reactor
  4. Ezlo Controller - Error Incompatible serialization data - api cloud Timeout
Organizing/ structuring rule sets and rules
R

Hi guys,

Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular.

Maybe there are better ways to organize my rule sets.

I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.

Multi-System Reactor
Moving MSR from a QNAP container to RP 5 - some issues
Tom_DT

I have installed MSR on a RP5 bare metal and then copied the config and store files. Everything seems to be on the RP5 but I am missing all global expression and I don't see the controller time.

Screenshot 2025-04-06 201446.png

My browser is Microsoft Edge Version 135.0.3179.54 (Official build) (64-bit)

I have probably done something stupid or missed a step but I am stuck.

Thanks for any help.

Multi-System Reactor
Widget deletion does not work and landing page (status) is empy
M

Hi,
It seems that the widget deletion does not work. I tried to drag the widget to the left (as explained in here https://smarthome.community/topic/1071/deleting-widgets?_=1744037333660)
but it does not delete it. Anyone else experiencing the same problem?

Also the landing page after login is empty and seems be have some JS issues on the dev console:

Screenshot from 2025-04-07 18-06-19.png

fd7f0424-debb-49d3-86d8-9a3b09ad3868-image.png

Using dockerized version of Reactor (Multi-hub) latest-25082-3c348de6 on Chromium 135.0.7049.52 (Official Build) snap (64-bit)

br,
mgvra

Multi-System Reactor
Need help reducing false positive notifications
T

Good day all,
I have an notification set up for my washing machine to let me know when it's complete. I have a templete sensor set up in HAAS to let me know if it's Washing, in Standby, or off, based upon the power consumption (Shelly 1PM on outlets)

- name: "Washing Machine" state: > {% if states("sensor.washer_switch_0_power")|float == 0 %} Off {% elif states("sensor.washer_switch_0_power")|float <= 2.9 %} Standby {% else %} Washing {% endif %} icon: > {% if states("sensor.washer_switch_0_power") == "off" %} mdi:washing-machine-alert {% elif states("sensor.washer_switch_0_power")|float <= 2.9 %} mdi:washing-machine-off {% else %} mdi:washing-machine {% endif %} minutes: 2

The MSR code is relatively simple. I have a built in false positive attribute for if MSR gets rebooted, because I would suddenly get tons of notifications when I upgraded MSR.

6774565a-06cc-443f-99c1-e71301b33d83-image.png

What I'm trying to introduce, is a way to verify that I just didn't bump the knob on the washing machine when transferring loads from the washer to the dryer, which turns on the display and brings the power above the Standby threshold.

The power goes up to 3.7W for about 4 minutes if the selector knob is bumped/turned.

What would the best way to do this be? I have most of my MSR code set up for a couple of years now, and my coding logic is struggling a bit.

I think I need a power threshold to be substained for a minimum time period (say 2 or 3 minutes, above 10W), before the other triggers can act. What would the best way to do that be?

Running: latest-25082-3c348de6
Fedora 41 Server
HAAS:
Core
2025.3.4
Supervisor
2025.03.4
Operating System
15.1
Frontend
20250306.0

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
Deleting widgets
tunnusT

Hopefully a trivial question, but how do you delete widgets in a status page? Using build 22266

Multi-System Reactor
MQTT configuration question
tunnusT

I have the following yaml configuration in local_mqtt_devices file

x_mqtt_device: set_speed: arguments: speed: type: str topic: "command/%friendly_name%" payload: type: json expr: '{ "fan": parameters.speed }'

While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?

Multi-System Reactor
System Configuration Check - time is offset
F

Hi!

I get this message when I'm on the status tab:

System Configuration Check
The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds.

I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6.
HA versions are:
Core 2025.3.4
Supervisor 2025.03.4
Operating System 15.1

I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version.
Do anyone know what I can try?
Thanks in advance!
Let's Be Careful Out There (Hill Street reference...) 🙂
/Fanan

Multi-System Reactor
Programmatically capture HTTP Request action status code or error
therealdbT

I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB.

While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed.

So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response.

While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits

Thanks!

Multi-System Reactor
ZwaveJSUI - RGBWW BULB - Warm/Cold White interfered with RGB settings - Bulb doesn't change color if in WarmWhite state.
N

Hi ,
I'm on
-Reactor (Multi-hub) latest-25067-62e21a2d
-Docker on Synology NAS
-ZWaveJSUI 9.31.0.6c80945

Problem with ZwaveJSUI:
When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white.
I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui.

I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb".
After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color.

This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite.

x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33}

The "cold white" and "warm white" settings interfer with the rgb color settings.

Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white
are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white.

So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have

x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33} 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: targetColor └─endpoint: 0 └─newValue └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──red: 235 └──green: 33 └──blue: 33 └─propertyName: targetColor 14/03/2025, 16:43:57 - value updated Arg 0: └─commandClassName: Color Switch └─commandClass: 51 └─property: currentColor └─endpoint: 0 └─newValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─prevValue └──warmWhite: 204 └──coldWhite: 0 └──red: 235 └──green: 33 └──blue: 33 └─propertyName: currentColor

In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set.

x_zwave_values.Color_Switch_currentColor_0=204 x_zwave_values.Color_Switch_currentColor_1=0 x_zwave_values.Color_Switch_currentColor_2=235 x_zwave_values.Color_Switch_currentColor_3=33 x_zwave_values.Color_Switch_currentColor_4=33

Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this?

x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33}

Thanks in advance.

Multi-System Reactor
Problem with simultaneous notifications.
T

Good day all,
I have a reaction set up, that I use for both troubleshooting and changing home modes when one of my family members either arrive or are leaving. I use the companion app for HAAS on our iPhones, and HAAS reports if the person associated with the iPhone enters or leaves the geofenced area around my home. I'm sure most MSR and HAAS users are familiar with this.

I use this rule set mainly as a condition for other rules, however, as part of troubleshooting, a notification is sent through HAAS to the companion app when the rule becomes true. The problem is that I'm getting notifications now for both arriving and departing simultaneously.

96b3f7db-ba09-499e-a78c-86903b603857-image.png

36903cdd-a87f-473b-82ef-af9ef96d3c44-image.png It used to work fine as intended. I'm not sure exactly when it changed, but now I'm getting two notifications when either of these conditions change.

Any idea what could be happening?

Edit:
Running: latest-25082-3c348de6, bare-metal Linux
ZWaveJSControllerr [0.1.25082]

Multi-System Reactor
Problem after upgrading to 25067
R

MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem?
I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.

Multi-System Reactor
Global expressions not always evaluated
tunnusT

Similarly as for local expressions, global expressions evaluate and update fine when getEntity(...) structure is used. However, at least when certain functions are in use, expressions do not update.

Consider the following test case:

Screenshot 2025-03-13 at 16.29.42.png

Even though auto-evaluation is active, value does not change (it changes only if that expression is manually run). MSR restarts do not help.

Screenshot 2025-03-13 at 16.31.43.png

Note: Tested using build 25067 on Docker. I have also a PR open (but couldn't now get details or PR number as my Mantis account was somehow expired?).

Multi-System Reactor
[Solved] Local expression evaluation
V

Trying to understand what cause a local expresssion to be evaluated. I have read the manual but I am still not clear about it. Using the test rule below, I can see in the log that the rule is being automatically evaluated every time the temperature entity is changing. That is great...

What I am trying to understand is why the expression is not evaluated based on time as well since the "case" statement has time dependencies.

Any help would be appreciated

I have the following test rule:

eba6a3ea-ff61-4610-88c9-9b9864f11ff8-Screenshot 2025-01-21 095244.png

2d9c1ff5-7b73-4005-b324-9029c2709db9-Screenshot 2025-01-21 095302.png

Here is the expressioncode:

vFrom1 = "09:25:00", vFrom2 = "09:30:00", vFrom3 = "09:41:00", vTo = "10:55:00", # Get current time (format HH:MM:SS) vToDay = strftime("%H:%M:%S"), #Get current house temperature CurrentHouseTemp = getEntity( "hass>Thermostat2 " ).attributes.temperature_sensor.value, case when CurrentHouseTemp <= 19 and vToDay >= vFrom1 && vToDay <= vTo: "true1" # From1 when CurrentHouseTemp <= 20 and vToDay >= vFrom2 && vToDay <= vTo: "true2" # From2 when CurrentHouseTemp < 26  and vToDay >= vFrom3 && vToDay <= vTo: "true3" # From3 else "false" end
Multi-System Reactor
[Solved] Runtime error when exiting global reaction that contains a group
S

I am getting a Runtime error on different browsers when I click exit when editing an existing or creating a new global reaction containing a group. If the global reaction does not have a group I don't get an error. I see a similar post on the forum about a Runtime Error when creating reactions but started a new thread as that appears to be solved.

The Runtime Error is different in the two browsers
Safari v18.3

@http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:44 You may report this error, but do not screen shot it. Copy-paste the complete 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.

Google Chrome 133.0.6943.142

TypeError: self.editor.isModified is not a function at HTMLButtonElement.<anonymous> (http://192.168.10.21:8111/reactor/en-US/lib/js/reaction-list.js:171:34) You may report this error, but do not screen shot it. Copy-paste the complete 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.

Steps to reproduce:
Click the pencil to edit a global reaction with a group.
Click the Exit button.
Runtime error appears.
or
Click Create Reaction
Click Add Action
Select Group
Add Condition such as Entity Attribute.
Add an Action.
Click Save
Click Exit
Runtime error appears.

I don’t know how long the error has been there as I haven’t edited the global reaction in a long time.

Reactor (Multi-hub) latest-25060-f32eaa46
Docker
Mac OS: 15.3.1
Thanks

Multi-System Reactor
Cannot delete Global Expressions
SnowmanS

I am trying to delete a global expression (gLightDelay) but for some strange reason, it comes back despite clicking the Delete this expression and Save Changes buttons.

I have not created a global expression for some times and just noticed this while doing some clean-up.

I have upgraded Reactor to 25067 from 25060 and the behaviour is still there. I have restarted Reactor (as well as restarting its container) and cleared the browser's cache several times without success.

Here's what the log shows.

[latest-25067]2025-03-08T23:50:22.690Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25067]2025-03-08T23:50:26.254Z <GlobalExpression:NOTICE> Deleting global expression gLightDelay [latest-25067]2025-03-08T23:50:27.887Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" }

Reactor latest-25067-62e21a2d
Docker on Synology NAS

Multi-System Reactor
Local notification methods?
CatmanV2C

Morning, experts. Hard on learning about the internet check script in MSR tools, I was wondering what suggestions anyone has about a local (i.e. non-internet dependent) notification method.

This was prompted by yesterday's fun and games with my ISP.

I've got the script Cronned and working properly but short of flashing a light on and off, I'm struggling to think of a way of alerting me (ideally to my phone)

I guess I could set up a Discord server at home, but that feels like overkill for a rare occasion. Any other suggestions?

TIA

C

Multi-System Reactor
Custom capabilities in MQTT templates
M

Hi,
I'm trying to integrate the sonos-mqtt (https://sonos2mqtt.svrooij.io/) with the MSR and it's coming along nicely so far.
But cannot wrap my head around how to define custom capabilities in MQTT templates. I need this for the TTS announcements and similarly for the notification sounds where I would pass the sound file as parameter.

So this is what I have in the local_mqtt_devices.yaml

capabilities: x_sonos_announcement: attributes: actions: speak: arguments: text: type: string volume: type: int delay: type: int

And this is the template:

templates: sonos-announcement: capabilities: - x_sonos_announcement actions: x_sonos_announcement: speak: topic: "sonos/cmd/speak" payload: expr: > { "text": parameters.text, "volume": parameters.volume, "delayMs": parameters.delay, "onlyWhenPlaying": false, "engine": "neural" } type: json

So the speak action should send something like this to topic sonos/cmd/speak

{ "text": "message goes here", "volume": 50, "delayMs": 100, "onlyWhenPlaying": false, "engine": "neural" }

At startup the MSR seems to be quite unhappy with my configuration:

reactor | [latest-25016]2025-02-09T08:19:59.029Z <MQTTController:WARN> MQTTController#mqtt entity Entity#mqtt>sonos-announcement unable to configure capabilities [Array][ "x_sonos_announcement" ] reactor | i18n: missing fi-FI language string: Configuration for {0:q} is incomplete because the following requested capabilities are undefined: {1} reactor | i18n: missing fi-FI language string: Configuration for {0:q} has unrecognized capability {1:q} in actions reactor | Trace: Configuration for {0:q} is incomplete because the following requested capabilities are undefined: {1} reactor | at _T (/opt/reactor/server/lib/i18n.js:611:28) reactor | at AlertManager.addAlert (/opt/reactor/server/lib/AlertManager.js:125:25) reactor | at MQTTController.sendWarning (/opt/reactor/server/lib/Controller.js:627:30) reactor | at MQTTController.start (/var/reactor/ext/MQTTController/MQTTController.js:268:26) reactor | at async Promise.allSettled (index 0) Configuration for "sonos-announcement" has unrecognized capability "x_sonos_announcement" in actions Controller: MQTTController#mqtt Last 10:21:37 AM Configuration for "sonos-announcement" is incomplete because the following requested capabilities are undefined: x_sonos_announcement Controller: MQTTController#mqtt Last 10:21:37 AM

This is probably a pretty stupid question and the approach may not even work at all, but maybe someone or @toggledbits for sure, could point me to the right direction.
Basically the idea is to be able to send TTS messages from reactions using entity actions. I've previously used HTTP requests to Sonos HTTP API (https://hub.docker.com/r/chrisns/docker-node-sonos-http-api/) for the same functionality, but since moving to sonos-mqtt, I need a way to send the TTS notifications using MQTTController. Along with the actual message, volume and delay must also be parameterizable.

br,
mgvra

MSR latest-25016-d47fea38 / MQTTController [0.2.24293]

Multi-System Reactor
[SOLVED]Hass websocket falsely reporting ready on boot??
V

Hi, @toggledbits

I just noticed that following a reboot of my raspberry pi, some of the rules, that I was expecting to recover, are not catching up following a reboot. I have made a simple test rule (rule-m6rz6ol1) with only "after Date/time" as trigger and "turn on a lamp" as a set reaction. All my infrastructure is on the same board so Reactor, Hass, Zwavejs, ... are all rebooting.

Here is the sequence of the test case (All time converted to Zulu to match logs):

Rule "after Date/Time" set to 14:05:00z Shutdown on Raspberry Pi at 14:04:00z Power back up at 14:08:00z Rule overview shows true as of 14:08:14z waiting for 00:00:00 in GUI

From the log I can see that MSR is picking up the rule and knows that the state of the rule has changed from false to true and tries to send the update to HASS but failed with websocket error.

Here is what I see from the log:

14:04:04z shutdown complete 14:08:08z Power up 14:08:13.111z websocket connection 14:08:15:323z Reaction to the light failed, Websocket not opened After there is a series of websocket connection attempt until 14:08:51z where it seemed to be really ready.

Back in 2021 we had a discussion (https://smarthome.community/topic/700/solved-start-up?_=1738766986566) and you proposed to add a startup_delay:xxxx and startup_wait:xxxx parameter in the engine section of "reactor.yaml". When I try the startup_delay (this used to be a hard delay), the engine failed to start (I think). I then try the startup_wait:xxxx without any success. Since it wait for the connection status to be up to cancel the delay, it does not do anyting since Hass is reporting the socket up without really being up ( I think...).

Questions:

Did I figured it all wrong? should the startup_delay:xxxxx have worked? Any ideas?

Here is the log:

OK now I am stuck. I did add the log but when I submit the editor complained saying that I am limited to 32767 characters. The log from the shutdown to the time the websocket is stable is about 300000 character long. What are my options?

Multi-System Reactor
[SOLVED]Logs permissions for Docker Install
V

Not a big issue simply a request if easily doable.

The MSR logs files inside the container are owned by root witch is fine however, the permissions are very restrictive. I do not know if there is something wrong with my installation but the logs permission are set to 222 (write only). Even if the docker volume is set for Read/Write the log files are retaining these values.

I go around the problem by doing a chmod 777 on all reactor logs but every time there is an MSR log rotation the permissions are set back to 222. So unless the permission are implemented in the container there is no permanent solution to this (that I know of).

I do not know much about Docker container so I do not know what is involved here.

Can the logfiles permission be simply chaged in the container to at least allow "other" read permission?

Could the MSR log rotation routine implement a chmod to set the permission?

Just a small anoyance

Thanks

Multi-System Reactor

Ezlo Controller - Error Incompatible serialization data - api cloud Timeout

Scheduled Pinned Locked Moved Multi-System Reactor
6 Posts 2 Posters 276 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • N Offline
    N Offline
    noelab
    wrote on last edited by noelab
    #1

    Hi,
    Connection to Ezlo is going in timeout with api-cloud.ezlo. This happens in anonymous_access set to false or in true.
    A lot of Error Incompatible serialization data (in the log I cut many more).
    In MSR controller status, Ezlo is in green icon but after sometime devices start to not respond.
    Can I have some help?

    Synology Nas - INTEL - DSM 7.1.1-42962 Update 3
    Ezlo Hub Model: h2.1 - v.2.0.35.2156.5
    Docker Container
    Reactor latest-23010-7dd2c9e9

    Thanks in advance

    
[latest-23010]2023-01-20T18:11:08.069Z <app:null> Reactor build latest-23010-7dd2c9e9 starting on v16.15.1
[latest-23010]2023-01-20T18:11:08.071Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #42962 SMP Tue Oct 18 15:07:03 CST 2022; locale (undefined)
[latest-23010]2023-01-20T18:11:08.071Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage
[latest-23010]2023-01-20T18:11:08.071Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules
[latest-23010]2023-01-20T18:11:08.085Z <app:INFO> Configured locale (undefined); selected locale(s) en-US.UTF-8
[latest-23010]2023-01-20T18:11:08.122Z <app:INFO> Loaded locale en-US
[latest-23010]2023-01-20T18:11:08.128Z <Structure:null> Module Structure v22323
[latest-23010]2023-01-20T18:11:08.131Z <Capabilities:null> Module Capabilities v22356
[latest-23010]2023-01-20T18:11:08.166Z <Capabilities:NOTICE> System capabilities loaded from core distribution, data version 22356 revision 1
[latest-23010]2023-01-20T18:11:08.211Z <Plugin:null> Module Plugin v22300
[latest-23010]2023-01-20T18:11:08.238Z <TimerBroker:null> Module TimerBroker v22283
[latest-23010]2023-01-20T18:11:08.241Z <Entity:null> Module Entity v22353
[latest-23010]2023-01-20T18:11:08.247Z <Controller:null> Module Controller v22323
[latest-23010]2023-01-20T18:11:08.261Z <default:null> Module Ruleset v22293
[latest-23010]2023-01-20T18:11:08.262Z <default:null> Module Rulesets v22146
[latest-23010]2023-01-20T18:11:08.271Z <GlobalExpression:null> Module GlobalExpression v22146
[latest-23010]2023-01-20T18:11:08.296Z <Predicate:null> Module Predicate v22345
[latest-23010]2023-01-20T18:11:08.317Z <AlertManager:null> Module AlertManager v22283
[latest-23010]2023-01-20T18:11:08.322Z <Rule:null> Module Rule v22345
[latest-23010]2023-01-20T18:11:08.327Z <GlobalReaction:null> Module GlobalReaction v22324
[latest-23010]2023-01-20T18:11:08.329Z <Engine:null> Module Engine v23001
[latest-23010]2023-01-20T18:11:08.335Z <httpapi:null> Module httpapi v22347
[latest-23010]2023-01-20T18:11:08.400Z <wsapi:null> Module wsapi v22320
[latest-23010]2023-01-20T18:11:08.400Z <app:NOTICE> Starting Structure...
[latest-23010]2023-01-20T18:11:08.460Z <InfluxFeed:null> Module InfluxFeed v22286
[latest-23010]2023-01-20T18:11:08.462Z <Structure:INFO> Structure#1 starting plugin influx (InfluxFeed)
[latest-23010]2023-01-20T18:11:08.463Z <Structure:INFO> Structure#1 loading controller interface vera (VeraController)
[latest-23010]2023-01-20T18:11:08.517Z <TaskQueue:null> Module TaskQueue 21351
[latest-23010]2023-01-20T18:11:08.518Z <VeraController:null> Module VeraController v22325
[latest-23010]2023-01-20T18:11:08.548Z <Structure:INFO> Structure#1 loading controller interface ezlo (EzloController)
[latest-23010]2023-01-20T18:11:08.635Z <EzloController:null> Module EzloController v22344
[latest-23010]2023-01-20T18:11:08.867Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_613c8f94129e291209006add: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:08.868Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
Error: Incompatible serialization data; can't unserialize
    at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19)
    at /opt/reactor/server/lib/Controller.js:794:70
    at Array.forEach (<anonymous>)
    at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36)
    at new Controller (/opt/reactor/server/lib/Controller.js:395:43)
    at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9)
    at /opt/reactor/server/lib/Controller.js:451:37
[latest-23010]2023-01-20T18:11:08.869Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_613c9094129e291209006ae4: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:08.869Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
Error: Incompatible serialization data; can't unserialize
    at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19)
    at /opt/reactor/server/lib/Controller.js:794:70
    at Array.forEach (<anonymous>)
    at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36)
    at new Controller (/opt/reactor/server/lib/Controller.js:395:43)
    at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9)
    at /opt/reactor/server/lib/Controller.js:451:37
[latest-23010]2023-01-20T18:11:08.902Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_61437a57129e29124dfcd791: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:08.902Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
Error: Incompatible serialization data; can't unserialize
    at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19)
    at /opt/reactor/server/lib/Controller.js:794:70
    at Array.forEach (<anonymous>)
    at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36)
    at new Controller (/opt/reactor/server/lib/Controller.js:395:43)
    at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9)
    at /opt/reactor/server/lib/Controller.js:451:37
[latest-23010]2023-01-20T18:11:08.925Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_61437a58129e29124dfcd7a0: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:08.925Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
Error: Incompatible serialization data; can't unserialize
    at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19)
    at /opt/reactor/server/lib/Controller.js:794:70
    at Array.forEach (<anonymous>)
    at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36)
    at new Controller (/opt/reactor/server/lib/Controller.js:395:43)
    at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9)
    at /opt/reactor/server/lib/Controller.js:451:37
[latest-23010]2023-01-20T18:11:08.942Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_6198168b129e2918c5ce97bc: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:08.943Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
    at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19)
    at /opt/reactor/server/lib/Controller.js:794:70
    at Array.forEach (<anonymous>)
    at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36)
    at new Controller (/opt/reactor/server/lib/Controller.js:395:43)
    at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9)
    at /opt/reactor/server/lib/Controller.js:451:37
[latest-23010]2023-01-20T18:11:08.945Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_61981760129e2918c5ce97cb: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:08.945Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
Error: Incompatible serialization data; can't unserialize
    at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19)
    at /opt/reactor/server/lib/Controller.js:794:70
    at Array.forEach (<anonymous>)
    at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36)
    at new Controller (/opt/reactor/server/lib/Controller.js:395:43)
    at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9)
    at /opt/reactor/server/lib/Controller.js:451:37
[latest-23010]2023-01-20T18:11:08.945Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_61981770129e2918c5ce97d0: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:08.945Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
Error: Incompatible serialization data; can't unserialize
    at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19)
    at /opt/reactor/server/lib/Controller.js:794:70
    at Array.forEach (<anonymous>)
    at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36)
    at new Controller (/opt/reactor/server/lib/Controller.js:395:43)
    at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9)
    at /opt/reactor/server/lib/Controller.js:451:37
[latest-23010]2023-01-20T18:11:08.946Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_6198177e129e2918c5ce97d5: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:08.946Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
Error: Incompatible serialization data; can't unserialize
    at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19)
    at /opt/reactor/server/lib/Controller.js:794:70
    at Array.forEach (<anonymous>)
    at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36)
    at new Controller (/opt/reactor/server/lib/Controller.js:395:43)
    at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9)
    at /opt/reactor/server/lib/Controller.js:451:37
[latest-23010]2023-01-20T18:11:08.947Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_6198178b129e2918c5ce97da: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:08.947Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
Error: Incompatible serialization data; can't unserialize
    at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19)
    at /opt/reactor/server/lib/Controller.js:794:70
    at Array.forEach (<anonymous>)
    at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36)
    at new Controller (/opt/reactor/server/lib/Controller.js:395:43)
    at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9)
    at /opt/reactor/server/lib/Controller.js:451:37
[latest-23010]2023-01-20T18:11:08.947Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_6198179b129e2918c5ce97df: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:08.947Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
Error: Incompatible serialization data; can't unserialize
    at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19)
    at /opt/reactor/server/lib/Controller.js:794:70
    at Array.forEach (<anonymous>)
    at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36)
    at new Controller (/opt/reactor/server/lib/Controller.js:395:43)
    at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9)
    at /opt/reactor/server/lib/Controller.js:451:37
[latest-23010]2023-01-20T18:11:08.948Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_619817a6129e2918c5ce97e4: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:08.948Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
Error: Incompatible serialization data; can't unserialize
    at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19)
    at /opt/reactor/server/lib/Controller.js:794:70
    at Array.forEach (<anonymous>)
    at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36)
    at new Controller (/opt/reactor/server/lib/Controller.js:395:43)
    at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9)
    at /opt/reactor/server/lib/Controller.js:451:37
[latest-23010]2023-01-20T18:11:08.948Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_619817b2129e2918c5ce97e9: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:08.949Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]

[latest-23010]2023-01-20T18:11:09.012Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_626d5d16129e291244463492: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:09.012Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
Error: Incompatible serialization data; can't unserialize
    at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19)
    at /opt/reactor/server/lib/Controller.js:794:70
    at Array.forEach (<anonymous>)
    at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36)
    at new Controller (/opt/reactor/server/lib/Controller.js:395:43)
    at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9)
    at /opt/reactor/server/lib/Controller.js:451:37
[latest-23010]2023-01-20T18:11:09.013Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_626d5d16129e291244463494: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:09.013Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
Error: Incompatible serialization data; can't unserialize
    at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19)
    at /opt/reactor/server/lib/Controller.js:794:70
    at Array.forEach (<anonymous>)
    at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36)
    at new Controller (/opt/reactor/server/lib/Controller.js:395:43)
    at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9)
    at /opt/reactor/server/lib/Controller.js:451:37
[latest-23010]2023-01-20T18:11:09.013Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_626d64d4129e2912444634a8: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:09.014Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
Error: Incompatible serialization data; can't unserialize
    at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19)
    at /opt/reactor/server/lib/Controller.js:794:70
    at Array.forEach (<anonymous>)
    at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36)
    at new Controller (/opt/reactor/server/lib/Controller.js:395:43)
    at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9)
    at /opt/reactor/server/lib/Controller.js:451:37
[latest-23010]2023-01-20T18:11:09.014Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_626d64d5129e2912444634af: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:09.014Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
Error: Incompatible serialization data; can't unserialize
    at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19)
    at /opt/reactor/server/lib/Controller.js:794:70
    at Array.forEach (<anonymous>)
    at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36)
    at new Controller (/opt/reactor/server/lib/Controller.js:395:43)
    at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9)
    at /opt/reactor/server/lib/Controller.js:451:37
[latest-23010]2023-01-20T18:11:09.015Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_626d64d5129e2912444634b2: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:09.015Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
Error: Incompatible serialization data; can't unserialize
    at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19)
    at /opt/reactor/server/lib/Controller.js:794:70
    at Array.forEach (<anonymous>)
    at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36)
    at new Controller (/opt/reactor/server/lib/Controller.js:395:43)
    at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9)
    at /opt/reactor/server/lib/Controller.js:451:37
[latest-23010]2023-01-20T18:11:09.039Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_629e6ec1129e2912b034351f: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:09.040Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
Error: Incompatible serialization data; can't unserialize
    at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19)
    at /opt/reactor/server/lib/Controller.js:794:70
    at Array.forEach (<anonymous>)
    at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36)
    at new Controller (/opt/reactor/server/lib/Controller.js:395:43)
    at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9)
    at /opt/reactor/server/lib/Controller.js:451:37
[latest-23010]2023-01-20T18:11:09.040Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_629e6ec2129e2912b0343529: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:09.040Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
Error: Incompatible serialization data; can't unserialize
    at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19)
    at /opt/reactor/server/lib/Controller.js:794:70
    at Array.forEach (<anonymous>)
    at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36)
    at new Controller (/opt/reactor/server/lib/Controller.js:395:43)
    at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9)
    at /opt/reactor/server/lib/Controller.js:451:37
[latest-23010]2023-01-20T18:11:09.041Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_629e6ec3129e2912b034352b: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:09.041Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
Error: Incompatible serialization data; can't unserialize
    at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19)
    at /opt/reactor/server/lib/Controller.js:794:70
    at Array.forEach (<anonymous>)
    at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36)
    at new Controller (/opt/reactor/server/lib/Controller.js:395:43)
    at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9)
    at /opt/reactor/server/lib/Controller.js:451:37
[latest-23010]2023-01-20T18:11:09.042Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_629e6ec3129e2912b034352d: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:09.042Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
Error: Incompatible serialization data; can't unserialize
    at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19)
    at /opt/reactor/server/lib/Controller.js:794:70
    at Array.forEach (<anonymous>)
    at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36)
    at new Controller (/opt/reactor/server/lib/Controller.js:395:43)
    at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9)
    at /opt/reactor/server/lib/Controller.js:451:37
[latest-23010]2023-01-20T18:11:09.043Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_629e6ec3129e2912b034352f: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:09.043Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
Error: Incompatible serialization data; can't unserialize
    at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19)
    at /opt/reactor/server/lib/Controller.js:794:70
    at Array.forEach (<anonymous>)
    at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36)
    at new Controller (/opt/reactor/server/lib/Controller.js:395:43)
    at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9)
    at /opt/reactor/server/lib/Controller.js:451:37
[latest-23010]2023-01-20T18:11:09.043Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_62a6d99a129e29123e7b0a8f: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:09.043Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
Error: Incompatible serialization data; can't unserialize
    at Entity.unserialize (/opt/reactor/server/lib/Entity.js:452:19)
    at /opt/reactor/server/lib/Controller.js:794:70
    at Array.forEach (<anonymous>)
    at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36)
    at new Controller (/opt/reactor/server/lib/Controller.js:395:43)
    at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9)
    at /opt/reactor/server/lib/Controller.js:451:37
[latest-23010]2023-01-20T18:11:09.044Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity device_62a6d99b129e29123e7b0a9d: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:09.044Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:09.060Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity room_629687b6129e2912430f2de2: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:09.060Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
Error: Incompatible serialization data; can't unserialize
    at Group.unserialize (/opt/reactor/server/lib/Entity.js:452:19)
    at /opt/reactor/server/lib/Controller.js:794:70
    at Array.forEach (<anonymous>)
    at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36)
    at new Controller (/opt/reactor/server/lib/Controller.js:395:43)
    at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9)
    at /opt/reactor/server/lib/Controller.js:451:37
[latest-23010]2023-01-20T18:11:09.061Z <Controller:WARN> EzloController#ezlo failed (1) to restore entity room_62a66189129e29124345f791: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:09.061Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
Error: Incompatible serialization data; can't unserialize
    at Group.unserialize (/opt/reactor/server/lib/Entity.js:452:19)
    at /opt/reactor/server/lib/Controller.js:794:70
    at Array.forEach (<anonymous>)
    at EzloController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36)
    at new Controller (/opt/reactor/server/lib/Controller.js:395:43)
    at new EzloController (/opt/reactor/server/lib/EzloController.js:707:9)
    at /opt/reactor/server/lib/Controller.js:451:37
[latest-23010]2023-01-20T18:11:09.128Z <Structure:INFO> Structure#1 loading controller interface groups (DynamicGroupController)
[latest-23010]2023-01-20T18:11:09.146Z <DynamicGroupController:null> Module DynamicGroupController v22313
[latest-23010]2023-01-20T18:11:09.178Z <Controller:WARN> DynamicGroupController#groups failed (1) to restore entity earthquake_entities: [Error] Incompatible serialization data; can't unserialize [-]
[latest-23010]2023-01-20T18:11:09.178Z <Controller:CRIT> Error: Incompatible serialization data; can't unserialize [-]
Error: Incompatible serialization data; can't unserialize
    at Group.unserialize (/opt/reactor/server/lib/Entity.js:452:19)
    at /opt/reactor/server/lib/Controller.js:794:70
    at Array.forEach (<anonymous>)
    at DynamicGroupController._restoreEntities (/opt/reactor/server/lib/Controller.js:782:36)
    at new Controller (/opt/reactor/server/lib/Controller.js:395:43)
    at new DynamicGroupController (/opt/reactor/server/lib/DynamicGroupController.js:207:9)
    at /opt/reactor/server/lib/Controller.js:451:37
[latest-23010]2023-01-20T18:11:09.186Z <Structure:INFO> Structure#1 loading controller interface weather (OWMWeatherController)
[latest-23010]2023-01-20T18:11:09.219Z <OWMWeatherController:null> Module OWMWeatherController v22294
[latest-23010]2023-01-20T18:11:09.222Z <Structure:INFO> Structure#1 loading controller interface reactor_system (SystemController)
[latest-23010]2023-01-20T18:11:09.227Z <SystemController:null> Module SystemController v22306
[latest-23010]2023-01-20T18:11:09.231Z <Structure:INFO> Structure#1 loading controller interface virtual (VirtualEntityController)
[latest-23010]2023-01-20T18:11:09.238Z <VirtualEntityController:null> Module VirtualEntityController v22325
[latest-23010]2023-01-20T18:11:09.348Z <Structure:INFO> Starting controller VeraController#vera
[latest-23010]2023-01-20T18:11:09.348Z <VeraController:NOTICE> VeraController#vera starting...
[latest-23010]2023-01-20T18:11:09.357Z <Controller:INFO> VeraController#vera loaded vera capabilities ver 22253 rev 1 format 1 
[latest-23010]2023-01-20T18:11:09.394Z <Controller:INFO> VeraController#vera loaded implementation data ver 22345 rev 1 format 1 
[latest-23010]2023-01-20T18:11:09.394Z <Structure:INFO> Starting controller EzloController#ezlo
[latest-23010]2023-01-20T18:11:09.397Z <Controller:INFO> EzloController#ezlo loaded ezlo capabilities ver 22266 rev 1 format 1 
[latest-23010]2023-01-20T18:11:09.408Z <Controller:INFO> EzloController#ezlo loaded implementation data ver 22344 rev 1 format 1 
[latest-23010]2023-01-20T18:11:09.408Z <Structure:INFO> Starting controller DynamicGroupController#groups
[latest-23010]2023-01-20T18:11:09.413Z <Controller:NOTICE> Controller DynamicGroupController#groups is now online.
[latest-23010]2023-01-20T18:11:09.413Z <Structure:INFO> Starting controller OWMWeatherController#weather
[latest-23010]2023-01-20T18:11:09.503Z <Structure:INFO> Starting controller SystemController#reactor_system
[latest-23010]2023-01-20T18:11:09.506Z <Controller:NOTICE> Controller SystemController#reactor_system is now online.
[latest-23010]2023-01-20T18:11:09.537Z <Structure:INFO> Starting controller VirtualEntityController#virtual
[latest-23010]2023-01-20T18:11:09.549Z <Controller:INFO> VirtualEntityController#virtual loaded virtualentity capabilities ver 22263 rev 2 format 1 
[latest-23010]2023-01-20T18:11:09.550Z <Controller:INFO> VirtualEntityController#virtual loaded implementation data ver 22280 rev 1 format 1 
[latest-23010]2023-01-20T18:11:09.556Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute members
[latest-23010]2023-01-20T18:11:09.556Z <VeraController:INFO> VeraController: deviceclass room capability sys_group does not provide attribute empty
[latest-23010]2023-01-20T18:11:09.557Z <EzloController:INFO> EzloController#ezlo device mapping data loaded; checking...
[latest-23010]2023-01-20T18:11:09.566Z <EzloController:INFO> EzloController#ezlo: connecting to hub "90000464"
[latest-23010]2023-01-20T18:11:09.570Z <VirtualEntityController:INFO> VirtualEntityController#virtual configuring virtual .DefaultMode (vec01)
[latest-23010]2023-01-20T18:11:09.571Z <VirtualEntityController:INFO> VirtualEntityController#virtual configuring virtual .GuestMode (vec02)
[latest-23010]2023-01-20T18:11:09.571Z <VirtualEntityController:INFO> VirtualEntityController#virtual configuring virtual .PartyMode (vec03)

    -Reactor (Multi-hub) 25082-3c348de6
    -Docker on Synology NAS
    -Ezlo firmware version 2.0.59.2471.8
    -HASS Docker 2025.2.5
    -ZWaveJSUI 10.1.3
    -Update 30/03/2025

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

      Have you had a recent disk full condition, or is it full now? Quotas in effect? Check all that. That's usually the cause of such things.

      To clear the serialization error, stop Reactor, remove the storage/entities directory entirely. Then restart Reactor.

      Edit:

      Connection to Ezlo is going in timeout with api-cloud.ezlo. This happens in anonymous_access set to false or in true.

      There's no evidence of this in the log you posted.

      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
      • toggledbitsT Offline
        toggledbitsT Offline
        toggledbits
        wrote on last edited by toggledbits
        #3

        Some additional information...

        I hadn't plugged in my Ezlo Plus in some time. It was running firmware 2.0.32.2097. It connected immediately, and I had no trouble with login credentials or getting access tokens from Ezlo's infrastructure; it accessed the hub API instantly and configured the entities/devices.

        Then my hub updated itself to 2.0.33.2116.2 and things came a gutser. I had several 500 errors trying to authenticate with Ezlo's cloud. I've been down this road before; they sometimes have outages and transient errors (one server in a cluster down and their HA/load balancing isn't configured well, things like that). I waited. Before too long, those errors went away, authentications were fine, but EzloController could not connect to the local API on the hub's port 17000. Again, I waited. The hub was doing a light show, so clearly things were happening, perhaps post-upgrade work and what not. It took about 15 minutes, but then everything was connected again.

        Just to make sure it was all clean, I restarted Reactor and at the same time, rebooted the hub. Again, the cloud auths and token requests went fine, but as before, the local API on the hub did not immediately accept a connection. It was, in fact, exactly 10 minutes into hub uptime that the API became available on the hub. I did the whole thing again, with the same result. I have since left the hub alone, and EzloController and the hub are playing nicely as they previously have.

        So, I think this is related to the 2.0.33 firmware. They either screwed something up, or left some debug delay in their code for some reason, or maybe they are just screwing with us. Don't know, don't care. Not my circus, not my monkeys. Nothing is wrong with EzloController that I can see; the hub just doesn't start the API immediately in 2.0.33.2116.2 firmware, and their cloud is performing about average for them (which is to say, below my expectations of industry standard). Just wait out the delay and the hub connects.

        If you want to bypass their delay, you can configure EzloController to use their remote access (cloud) API instead of the hub's local API. This makes you entirely dependent on their cloud, so that's the trade-off. You can be the judge of which is the lesser of the two evils. To enable remote access, make sure username, password and serial are configured, and comment-out any source config you have; restart Reactor.

        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
          #4

          Hi, thanks for tips!
          About disk full condition and Quotas in effect ----> No, there are no limits.

          Error Incompatible serialization data is now SOLVED after removing the storage/entities directory entirely.

          Then I restarted MSR many times. At startup EzloController and MSR are working good with no problem and authentications were fine.
          But at same point, about one hour later, something always went wrong.

          from the log I saw different kind of error:

          [latest-23010]2023-01-21T13:38:01.098Z <wsapi:WARN> wsapi: timed out waiting for ping reply (pong) from client "172.17.0.1#5"
[latest-23010]2023-01-21T13:38:01.099Z <wsapi:INFO> client "172.17.0.1#5" closed, code=1006, reason=
[latest-23010]2023-01-21T13:38:10.109Z <wsapi:WARN> wsapi: timed out waiting for ping reply (pong) from client "172.17.0.1#6"
[latest-23010]2023-01-21T13:38:10.110Z <wsapi:INFO> client "172.17.0.1#6" closed, code=1006, reason=

          or

          [latest-23010]2023-01-20T22:36:15.141Z <EzloController:null> remapped item action to [Object]{ "item": "switch", "value_expr": "! entity.attributes.power_switch.state", "method": "hub.item.value.set", "parameters": { "value": { "value_expr": "! entity.attributes.power_switch.state" } } }
[latest-23010]2023-01-20T22:36:23.586Z <wsapi:INFO> client "172.17.0.1#6" closed, code=1001, reason=
[latest-23010]2023-01-20T22:36:23.907Z <wsapi:INFO> wsapi: connection from ::ffff:172.17.0.1
[latest-23010]2023-01-20T22:36:26.080Z <httpapi:INFO> httpapi: API request from ::ffff:172.17.0.1: GET /api/v1/systime
[latest-23010]2023-01-20T22:36:30.145Z <EzloController:ERR> EzloController#ezlo request "185d1534ba7" ([Object]{ "method": "hub.item.value.set", "api": "1.0" }) failed: TimedPromise timeout
[latest-23010]2023-01-20T22:36:30.145Z <EzloController:WARN> EzloController#ezlo action toggle.toggle on Switch#ezlo>device_6145cbb1129e29124dfcd7c8 failed!
[latest-23010]2023-01-20T22:36:30.146Z <wsapi:CRIT> !TimedPromise timeout
[latest-23010]2023-01-20T22:36:33.239Z <EzloController:ERR> EzloController#ezlo request "185d15357bd" ([Object]{ "method": "hub.item.value.set", "api": "1.0" }) failed: TimedPromise timeout
[latest-23010]2023-01-20T22:36:33.240Z <EzloController:WARN> EzloController#ezlo action toggle.toggle on Switch#ezlo>device_6145cbb1129e29124dfcd7c8 failed!
[latest-23010]2023-01-20T22:36:33.240Z <wsapi:CRIT> !TimedPromise timeout
[latest-23010]2023-01-20T22:36:35.788Z <EzloController:ERR> EzloController#ezlo request "185d15361b4" ([Object]{ "method": "hub.item.value.set", "api": "1.0" }) failed: TimedPromise timeout
[latest-23010]2023-01-20T22:36:35.789Z <EzloController:WARN> EzloController#ezlo action toggle.toggle on Light#ezlo>device_6150872e129e29124787e2f6 failed!
[latest-23010]2023-01-20T22:36:35.789Z <wsapi:CRIT> !TimedPromise timeout

          then I notice this one

          [latest-23010]2023-01-21T18:33:02.387Z <Engine:5:Engine.js:1613> _process_reaction_queue() wake-up!
[latest-23010]2023-01-21T18:33:02.387Z <Engine:5:Engine.js:1550> _process_reaction_queue() running task 170: [Object]{ "tid": 170, "id": "re-ktn80xbr", "rule": false, "__reaction": GlobalReaction#re-ktn80xbr, "next_step": 0, "status": 0, "ts": 1674325982366, "parent": --null--, "__resolve": --function--, "__reject": --function--, "__promise": [object Promise] }
[latest-23010]2023-01-21T18:33:02.388Z <Engine:NOTICE> Starting reaction rL_Bulbs_01_ON&RESET (re-ktn80xbr)
[latest-23010]2023-01-21T18:33:02.388Z <Engine:5:Engine.js:1690> [Engine]Engine#1 reaction re-ktn80xbr step 1 perform [Object]{ "entity": "ezlo>device_614efa37129e29124dfcd853", "action": "color_temperature.set", "args": { "value": 4800 } }
[latest-23010]2023-01-21T18:33:02.388Z <EzloController:null> remapped item action to [Object]{ "item": "rgbcolor", "value_expr": "parameters.value > 5500 ?\n  { wwhite: 0, cwhite: floor( ( parameters.value - 5500 ) / 3500 * 255 ) } :\n  { cwhite: 0, wwhite: floor( ( parameters.value - 2000 ) / 3500 * 255 ) }\n", "method": "hub.item.value.set", "parameters": { "value": { "value_expr": "parameters.value > 5500 ?\n  { wwhite: 0, cwhite: floor( ( parameters.value - 5500 ) / 3500 * 255 ) } :\n  { cwhite: 0, wwhite: floor( ( parameters.value - 2000 ) / 3500 * 255 ) }\n" } } }
[latest-23010]2023-01-21T18:33:02.390Z <Engine:5:Engine.js:1566> _process_reaction_queue() task returned, new status 3; task 170, history 565875
[latest-23010]2023-01-21T18:33:02.390Z <Engine:5:Engine.js:1613> _process_reaction_queue() ending with 2 in queue; waiting for 1674325987357<1/21/2023, 7:33:07 PM> (next delayed task)
[latest-23010]2023-01-21T18:33:05.922Z <EzloController:ERR> EzloController#ezlo request "185d59acfe8" ([Object]{ "method": "hub.item.value.set", "api": "1.0" }) failed: TimedPromise timeout
[latest-23010]2023-01-21T18:33:05.923Z <EzloController:WARN> EzloController#ezlo action toggle.toggle on Light#ezlo>device_61475325129e29124dfcd7e6 failed!
[latest-23010]2023-01-21T18:33:05.923Z <wsapi:CRIT> !TimedPromise timeout

          there is no item "rgbcolor" in that rule, only: temperature color, dimming set and switch off. I saved again the rule.

          At the moment api.cloud is working and I wait to see again if the problem is gone.

          [latest-23010]2023-01-21T20:59:21.886Z <EzloController:NOTICE> EzloController#ezlo: successful connection to "90000464" via cloud relay
[latest-23010]2023-01-21T20:59:21.887Z <EzloController:INFO> EzloController#ezlo starting hub inventory
[latest-23010]2023-01-21T20:59:22.296Z <EzloController:INFO> EzloController#ezlo hub "90000464" is h2.1 (undefined) firmware "2.0.35.2156.5"

          -Reactor (Multi-hub) 25082-3c348de6
          -Docker on Synology NAS
          -Ezlo firmware version 2.0.59.2471.8
          -HASS Docker 2025.2.5
          -ZWaveJSUI 10.1.3
          -Update 30/03/2025

          toggledbitsT 1 Reply Last reply
          0
          • toggledbitsT Offline
            toggledbitsT Offline
            toggledbits
            replied to noelab on last edited by toggledbits
            #5

            @noelab The wsapi ping timeouts are not related to EzloController. A browser using the Reactor UI is timing out; the browser is at the IP address mentioned. This can happen when the tab or browser go to sleep, the tab is closed, the browser crashes, the device leaves the network (i.e. mobile device leaves the home's WiFi), etc. The connection between the browser and Reactor is a websocket, and the WS protocol requires that periodically, a ping be sent between the client and server so that each know the other is still alive. Usually, you can ignore these messages, but they also can point to network stability problems (see below).

            there is no item "rgbcolor" in that rule

            The rgbcolor item is the item (an Ezlo term) on the Ezlo device that needs to be modified in response to the command. It is not a Reactor entity attribute, but rather what Reactor's entity attributes maps to on Ezlo's device. In order to change color temperature via the Reactor color_temperature.set action, Reactor has to tell the Ezlo device to change its rgbcolor item.

            from the log I saw different kind of error:
            [latest-23010]2023-01-20T22:36:30.145Z <EzloController:ERR> EzloController#ezlo request "185d1534ba7" ([Object]{ "method": "hub.item.value.set", "api": "1.0" }) failed: TimedPromise timeout

            The time-outs on Ezlo commands are the Ezlo hub's API not acknowledging the command given by Reactor within 15 seconds. There can be several causes for this:

            1. Your local network connection to the Ezlo hub is poor and it's dropping packets. If your Ezlo hub is connected to your local network via WiFi, move it to a hard-wired connection. WiFi is often not reliable enough for hub connectivity in home automation. Hubs should always be on hard network connections. If you are already on a hard connection, check your internal network for cabling problems/faults, broadcast storms, or faulty switches/hubs/routers. The fact that you also have wsapi timeouts makes me suspicious that you may have a local network quality problem.
            2. Your Ezlo hub is too busy doing something to answer in time. It may be that the Z-Wave mesh is poor and the hub is having problems communicating reliably with the target device, and is thus slow to answer, causing the timeout. Other causes could be a completely different device that is offline/unreachable (out of mesh, battery dead, etc.) causing the hub to be over-busy trying to talk to it, a firmware problem, or a plugin that is overwhelming the system. In any case, EzloController didn't get an answer from the hub within 15 seconds, and that's a hub issue, not something I can address in EzloController.
            3. Ezlo firmware bugs. At this point, they've spent about 4-1/2 years since the acquisition of Vera trying to produce firmware and still haven't produced anything that has full functional parity with Vera's last version of firmware. A recent post on their forums by another user observed that "Ezlo is NOT ready for prime time... All these bells and whistles are fine and all, but I STILL - AFTER A YEAR OF WORKING WITH THEM - cannot get a stable system with even a fraction of the devices I have." Another user followed up saying "Their development direction... is confusing and doesn’t show user-centric development." I agree. In my view, their product has not (for too long) and still is not making sufficient, timely progress toward meeting the needs of real users and the quality standard for home automation today. There are better choices with mature, stable products and active, enthusiastic user communities.

            Ref: archived post archived post

            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
            1
            • N Offline
              N Offline
              noelab
              wrote on last edited by
              #6

              Thanks a lot! I will start to check better these kind of problems!
              EzloController is hard-wired connection, so I will start with battery devices and zwave-mesh.

              Thanks!

              -Reactor (Multi-hub) 25082-3c348de6
              -Docker on Synology NAS
              -Ezlo firmware version 2.0.59.2471.8
              -HASS Docker 2025.2.5
              -ZWaveJSUI 10.1.3
              -Update 30/03/2025

              1 Reply Last reply
              0
              • toggledbitsT toggledbits locked this topic on

              Recent Topics

              • Disaster recovery and virtualisation
                CatmanV2C
                CatmanV2
                0
                5
                567
              • Remote access of Zwave stick from Z-wave server
                CatmanV2C
                CatmanV2
                0
                3
                285
              • Organizing/ structuring rule sets and rules
                G
                gwp1
                0
                5
                345
              • Moving MSR from a QNAP container to RP 5 - some issues
                G
                gwp1
                0
                5
                290
              • Widget deletion does not work and landing page (status) is empy
                G
                gwp1
                0
                4
                262
              • Need help reducing false positive notifications
                T
                tamorgen
                0
                7
                454
              • Reactor (Multi-System/Multi-Hub) Announcements
                toggledbitsT
                toggledbits
                5
                120
                35.1k
              • Deleting widgets
                toggledbitsT
                toggledbits
                0
                4
                437
              • MQTT configuration question
                tunnusT
                tunnus
                0
                11
                590
              • System Configuration Check - time is offset
                G
                gwp1
                0
                8
                581
              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