Copying a global reaction

[noelab]

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)

[toggledbits]

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.

[toggledbits]

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.

[noelab]

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"

[toggledbits]

@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

[noelab]

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!