ops, soorry! now it is in signature too.
Reactor (Multi-hub) latest-23338-170ea0c7
Docker - Synology NAS
I need a handful of victims volunteers to help test previews of the next build of Reactor. A long-standing request was for "a simple login mechanism," but in practice, adding user authentication and competent access control turned out to be a pretty big project with a lot of big changes on both server and client sides. It's a bit more than I'm comfortable testing myself and springing out to everyone at once, so I'd like to work with a small group to put it through "sea trials."
Major changes/features include:
User authentication with hashed password storage; User group configuration with application restriction (admin, dashboard, API); Detailed control over API access, with user- and token-based authentication/authorization; Improvements to the HTTPS service; Improvements to UI coordination with the core for Rules and Reactions.If this sounds like something you'd like to help with, drop me a reply here in this thread or privately.
Good morning,
So Home Assistant decided to change the default weather home format that I've been using for the past year and a half. I had two Global Expressions set up to pull the high and low temp forecast for the day. Now it's pulling null values.
094c9205-cc9e-4fcc-ac4f-1bf54acea299-image.png
In the dev tools, it now uses a new service (Weather. get forecasts), plural, where the old Weather.get forecast is depreciated and now longer functions.
8c7a1fcc-dd3f-4268-a0b7-29d542f86adc-image.png
It shows a templow field, and a temperature field, which I presume is the forecast high.
When I head back over to MSR, I'm having a hard time finding those values in the Entities tab.
c5ea1048-a72e-4647-9c50-9d0c5fd20767-image.png
wx.asoftime=null wx.ceiling=null wx.ceiling_unit=null wx.cloud_cover=null wx.condition_code=null wx.description="partlycloudy" wx.feels_like=null wx.humidity=57 wx.humidity_unit="%" wx.icon=null wx.location=null wx.precipitation_1hr=null wx.precipitation_24hr=null wx.precipitation_other=null wx.precipitation_type=null wx.precipitation_unit="in" wx.pressure=30 wx.pressure_unit="inHg" wx.temperature=55 wx.temperature_unit="°F" wx.visibility=null wx.visibility_unit="mi" wx.wind_compass=210.3 wx.wind_conditions=null wx.wind_direction="SSW" wx.wind_gust=null wx.wind_speed=6.28 wx.wind_speed_unit="mph" x_hass.domain="weather" x_hass.entity_id="weather.forecast_home" x_hass.services=["weather"] x_hass.state="partlycloudy" x_hass_attr.attribution="Weather forecast from met.no, delivered by the Norwegian Meteorological Institute." x_hass_attr.cloud_coverage=85.9 x_hass_attr.dew_point=40 x_hass_attr.friendly_name="New Windsor Weather" x_hass_attr.humidity=57 x_hass_attr.precipitation_unit="in" x_hass_attr.pressure=30 x_hass_attr.pressure_unit="inHg" x_hass_attr.supported_features=3 x_hass_attr.temperature=55 x_hass_attr.temperature_unit="°F" x_hass_attr.visibility_unit="mi" x_hass_attr.wind_bearing=210.3 x_hass_attr.wind_speed=6.28 x_hass_attr.wind_speed_unit="mph"There is a x_hass_attr.temperature, but that appears to be the current temperature, not the high that I found on the dev tools screenshot.
Any ideas?
Running:
Core
2024.4.3
Supervisor
2024.04.0
Operating System
12.2
Frontend
20240404.2
MSR: latest-24057-e9add9f5
@DesT I think I mentioned this some time ago, but Chat in this software seems broken. I normally use Brave browser, but it's same for Chrome. Haven't tried others.
Someone is trying to contact me via chat. I can see that here:
4a8a5332-2f25-476b-a9c9-decffb6a9c01-image.png
When I click on that message, or any message in this list, the header and navigation left/right of the side go away, and I get a page that looks like this:
f69b117b-8ac9-446b-8487-6d586b24ea29-image.png
It has no messages in it, not even the message that I can see the preview for in the previous image. Nothing I do from here seems to bring up any conversations. The user who messaged me isn't listed on the left. And if I click on any of the messages in the list on the left, nothing major happens: the tab title changes and the message in the left list I click on is highlighted gray, but no conversation is displayed and the middle of page stays blank except for the input area, it doesn't even display the full text of the message I clicked on. Since there's no navigation on the page, the only way I can leave this page is to use the back button or re-enter the URL in the location bar to start over.
Maybe I'm committing some kind of ID 10T error, but it's not obvious to me what it is. Just seems... not working.
Hey Patrick, I recently have been noticing that MSR has been acting up ie. it's been needing restarts and has been slow. I began trouble shooting by looking at the logs and have noticed the following errors for a lot of entities. I thought maybe a simple reboot of RPi was needed and I kept seeing the same errors in the system logs. I am oddly enough not seeing these same errors in the MSR logs. Where things started getting weird is whenever I rebooted MSR it wouldn't come back online .I would have to restart the RPi then it would come back online. I just restarted MSR again to capture logs and it restarted fine, so I guess its good for now? I think this is more or so a corrupted SD card issue rather a MSR issue but well being troubleshooting from here. The SD card is about 1-2 years old.
Apologies if this post is everywhere, I cannot consistently recreate any oddities that are happening, that's what is leading me to believe my SD is going bad.
PS: If anyone knows how to diagnose a corrupt SD card please chime in.
MSR latest-24057-e9add9f5
Home Assistant 2024.4.3
Raspberry Pi 3b+
Feedback / solutions with openLuup's built-in Shelly bridge.
Been using zigbee2mqtt and openLuup for sometime now and it is working well.
I attempted to add another Hue switch to-day. It's a newer version of the other ones I have been using so far. They are pretty much identical.
The older ones installed no problem (which is weird), but the new one won't. Looking at the code, it looks this function in L_Zigbee2MQTTBridge.lua:
configure_scene_controller(dno)is not being passed the parameter "dno" when the function is called. The device is created but is incomplete.
Just out of interest how do you pretty print to the log from within say L_Zigbee2MQTTBridge.lua? I tried a few incarnations such a:
local pretty = openLuup.loader.shared_environment.prettybut they all failed.
A list of openLuup releases including the latest developments…
master – stable, and infrequently updated, development – latest updates and bug fixes, testing – use only when advised!A long while ago (May, 2015) I wrote my 2000-th post on another forum: openLuup - running unmodified plugins on any machine.
Now rehosted at https://community.ezlo.com/t/openluup-running-unmodified-plugins-on-any-machine/187412
Here’s the gist of it:
...I want to work in a more open and stable [Vera] environment...
...All would be solved if Luup was open source and could be run on the plethora of cheap and reliable hardware available today. But it’s not. But we could get something like that effect if we engineered a sufficient subset of Luup to run on such a platform. Could it be done? What would we need?
1. UI
2. scheduler
3. web server
4. Luup compatible API
5. Device and Implementation xml file reader
6. Zwave bridge to Vera
7. runs most plugins without modification
What we wouldn’t need is UPnP.
What have we (nearly) got already?
We have, courtesy of @amg0, the most excellent AltUI: Alternate UI to UI7, and that, I think, is probably the hardest one to do in the above list. Items 2 - 5, and 7, I’ve prototyped, in pure Lua, and posted elsewhere: DataYours on Raspberry Pi, running selected plugins unmodified, including: DataYours, EventWatcher, Netatmo, RBLuaTest, altUI. See screenshot attached.Is it worth the effort? Probably not. Will I pursue this quest? Yes.
openLuup was the result.
This system has been running flawlessly year after year for the time changes twice a year literally since MSR came out so I was caught off-guard when this happened this morning.
Time in MSR browser is EST, time on RPi is local time (DST).
76ed5313-b9b9-46d4-b0f9-462c40e99750-image.png
195e61c5-58a7-4453-b96a-18cebae75550-image.png
I've rebooted the RPi I've restarted MSR after double-checking the time on the RPi. Used a completely different browser to eliminate any caching concerns. Double-checked MSR reactor.yamla5f23151-d691-4343-8499-8e77a55528e5-image.png
What am I missing here @toggledbits ?
Hello,
I had an iCOMEN boiler switch that worked for many years. And I used iCOMEN app on my phone to manage it. Short time ago app started to have an error message that it cannot connect to the server, and after some time the device also stopped working.
With their awesome new X10 switch!
dbe7408f-dc86-4932-bf71-f0528f5384c1-image.png
I'm hopping in my 1980s time machine to go see whether this is exactly what I think it is. 🙂
(Srsly, tho, I love(d) X10 and did everything humanly possible to keep that old equipment perking along with Vera, and almost succeeded.)
LibraP.S. Just got banned for the 9th time from Hubitat Forum, so had a little extra time to throw shade.
P.P.S. The boilerplate 5-star reviews for this brand-new product come from bots with names like Avery, Phoenix and Owen (two from Mateo!). Sheesh.
Hi,
For the standard capabilities MSR sends both a value record and a units record to InfluxDB. The latter I would like not to send as they are not really any use for me and it will reduce the number of records send to my InfluxDB.
Is there a quick way to do this with a filter_entities line like: *>units?
Or do I have to update all capabilities to read like this:
power_sensor:
attributes:
value: true
Cheers Rene
I'm trying to replicate this
wallbox_set_number.PNG
into a MQTT entity where I could set a number with a min and max value.
I can't find a standard capability that fits or any documentation on local MQTT capabilities and the only post on the forum mentioning local MQTT capabilities is this post, is it even possible in current release?
My trial and error work in local_mqtt_capabilities.yaml isn't much to show as it's just a copy of mqtt_capabilities.yaml with changed names and then I got stuck.
Any guidance, examples, documentation, future feature request or denial would be much appreciated, thanks!
Reactor 24057-e9add9f5 bare metal
MQTTController 24050
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.Hoping you could tell us a bit about your experiences with ZWaveJS and MQTT.
Hi guys,
I've recently bought a new Govee outdoor permanent lights set, and I love it. WAF is pretty high, and the product is good quality. I hope to never run lights in the front of the house.
This new addition has found me searching for something to control these lights, locally. Govee has officials remote and LAN APIs and Home Assistant has it supported, but some undocumented stuff that's integrated into an Homebridge plugin that seems very promising. Without this plugin, my playlist is orchestrated via the cloud and that makes zero sense.
In the past I got some inspiration from plugins running on other platforms and Homebridge seems one of the most active. I could map its devices via HomeKit-local on HA, but I've decommissioned Homebridge years ago when we settled to Alexa (and I want to stay simple), so I had an idea: why get inspiration and rewrite things, when you could write an Homebridge adapter that could load any Homebridge plugin and run them natively under Reactor (MSR)?
I'm not sure if that's viable or made any sense, so I'm posting here to get feedback, encouragement and your thoughts. Anyone could be potentially interested in such a thing?
Hi- looking for a hint in where to start. My goal is to set a PIN code in a zwave kwikset lock triggered in a rule.
The device isn’t exposing methods to help. The x-hass.call-service looks promising, but what would the service name be?
Plan b would be send the zwave controller a config command- I don’t see any way to explicitly send a command through JS Zwave in my environment.
Running reactor bare metal. JS Zwave is running as an add on inside HASS OS.
Any tips are appreciated.
Originally I was using Futzle's UPnP event proxy plugin on Vera with the Sonos plugin. Worked very well.
On making the move to openLuup, one finds that the proxy can't be used because the proxy daemon start and stop, etc uses a script installed by the plugin that only works on openWRT, as used by Vera.
The Sonos plugin still works without the proxy but it reverts to polling. It becomes a bit on the sluggish side and sometimes doesn't function quite as intended.
I've modified the proxy plugin to install a script that runs as a systemd service. systemd can be found on a lot of contemporary Linux installs, including Raspberry Pis. To make use of; just install the plugin from the AltUI app store and restart the Luup engine a couple of times. The dashboard should indicate "Status: Proxy running".
Note that the service file expects "L_UPnPProxyDaemon.lua" to be located at the typical plugin files location:
/etc/cmh-ludl/After the plugin is installed, the service file should be found in:
/etc/systemd/system/as UPnPProxy.service.
If you use the Sonos plugin, you need to change the variable "UseProxy" to "1" and restart the LuupEngine. In the Sonos parent device, you should see: "Running x zones; proxy detected".
Updated doco here.
Hope it works - YMMV.
Hey crew, I'm trying to use MSR to control the RGB values of a Z-Wave bulb in Home Assistant.
Problem I'm running into - I would like to use 'rgb_color.set' to control this, but it doesn't work, instead it always passes the values '255,255,255' to HA no matter what values I enter within MSR.
More notes and examples below - I'm wondering if this is a formatting issue that I'm missing? Thanks for any help!
NOTES FROM TROUBLESHOOTING:
'rgb_color.set_rgb' works successfully, which seems strange. You'd think they would both be affected I've tried a couple different formats, like adding quotes, adding/removing spaces between the RGB values, nothing has fixed it.EXAMPLES:
When I use 'rgb_color.set_rgb', the values successfully carry over to Home Assistant:
f0f4befc-a642-428e-8923-e5f856ca7e2b-image.png
0af0a4f8-50b9-4100-b1e8-52a0de4cbcbb-image.png
But when I use 'rgb_color.set', the values DO NOT successfully carry over to Home Assistant:
9e2d7004-8085-4b70-bb3e-45614b7260a0-image.png 0d630228-c74b-4db8-89bd-2572a08608a3-image.png
DETAILS:
Bulb is LZW42 by Inovelli MSR version: stable-23242-5ee8e1d4HA DETAILS
Core 2024.2.5 Supervisor 2024.02.1 Operating System 12.0Some of you may know that I took at shot at building an alternate geofencing solution for Vera. The core of it was system agnostic, using the OwnTracks application and AWS lambdas to track devices and keep a central data, then disseminate that to the Vera via a websocket-based plugin. It worked with other apps as well, including Tasker and GPSLogger, but of the dozen people that were testing it, most used OwnTracks.
A lot was learned in the process, not the least of which is that the success of any such solution is highly dependent on the phone and its settings. Phone manufacturers love to set things up for the longest battery life, of course, but that's usually very anti-geofencing behavior. In the case of at least one brand, it was unusable and the settings could not be modified. It was also cost-prohibitive to maintain on Amazon, as AWS grabs a dime here and a dollar there and before you know it, it added $100/month to my AWS bill, which my wife deducted from my Scotch budget. Unacceptable.
But it's quite reasonable to use OwnTracks to a local endpoint, and I could pretty easily replicate the functionality as a local application, or maybe even as an additional endpoint built into MSR's API (still separate port and process, but in the package).
So the question really is... would you do it, or would you be too concerned about the security risks associated (e.g., dynamic DNS and NAT mapping in the firewall necessary for the phone to contact the service when not on LAN)?
ops, soorry! now it is in signature too.
Reactor (Multi-hub) latest-23338-170ea0c7
Docker - Synology NAS
or
glabal expression
xB1_IndiceThom_ID = round( float( xB1_Temp_01_ID ) - (0.55-0.0055 * float( xB1_Humidity_01_ID )) * ( float( xB1_Temp_01_ID ) - 14.5) , 1)
reactor.yaml
-
id: testA_dynamic_vec
name: TestA Dynamic Vec Value
capabilities:
value_sensor:
attributes:
value:
expr: xB1_IndiceThom_ID
Reactor (Multi-hub) latest-23338-170ea0c7
Docker - Synology NAS
Global expression
xB1_Temp_01_ID = getEntity( "ezlo>device_626d5f9f129e2912444634a4" ).attributes.temperature_sensor.value
xB1_Humidity_01_ID = getEntity( "ezlo>device_626d5f9f129e2912444634a0" ).attributes.humidity_sensor.value
in reactor.yaml
-
id: testA_dynamic_vec
name: TestA Dynamic Vec Value
capabilities:
value_sensor:
attributes:
value:
expr: round( float( xB1_Temp_01_ID ) - (0.55-0.0055 * float( xB1_Humidity_01_ID )) * ( float( xB1_Temp_01_ID ) - 14.5) , 1)
in dashboard
Hi, I tried with my skills and no luck, so I want understand if it is possible.
if I create a Global variable, for example to have a Thom Index value
xB1_Thom_Index_ID = round( float( xB1_Temp_01_ID ) - (0.55-0.0055 * float( xB1_Humidity_01_ID )) * ( float( xB1_Temp_01_ID ) - 14.5) , 1)
and then I create a Virtual Entity that show the updated value also on the dashboard every time xB1_Thom_Index_ID changes
seems that this is not the right way
id: testA_dynamic_vec
name: TestA Dynamic Vec Value
capabilities:
value_sensor:
attributes:
value:
expr: xB1_Thom_Index_ID
nothing
id: testA_dynamic_vec
name: TestA Dynamic Vec Value
capabilities:
value_sensor:
attributes:
value:
expr: round( float( xB1_Temp_01_ID ) - (0.55-0.0055 * float( xB1_Humidity_01_ID )) * ( float( xB1_Temp_01_ID ) - 14.5) , 1)
I get the value updated only when MSR restart. Is this way totally wrong?
Thanks in advance
Hi, I like a lot the MSR Dashboard: it's quick and easy without an authentication system and this is great.
Not really a good idea if I give this possibility to my wife to power off all switches included the nas with MSR or to a guest to power off the light in my room.
Is it scheduled to have a main dashboard and a guest dashboard? as a sub-dashboard
Maybe from the main dashboard, using a built-in GUI editors that can set icons as visible or hidden and automatically reflect on a guest dashboard with a different ip
Just an idea for MSR
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!
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"
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)
Hi, I don't know from which MSR version I have this error in the log:
[latest-22080]2022-03-27T14:24:44.195Z <wsapi:INFO> wsapi: connection from ::ffff:172.18.0.1
[latest-22080]2022-03-27T14:24:44.569Z <NotifyPushover:5:NotifyPushover.js:239> [NotifyPushover]NotifyPushover successful endpoint exchange (message sent)
[latest-22080]2022-03-27T14:24:48.793Z <InfluxFeed:ERR> [InfluxFeed]InfluxFeed#influx write failed (data lost): [b]RequestTimedOutError: Request timed out
[latest-22080]2022-03-27T14:24:48.832Z <InfluxFeed:ERR> [InfluxFeed]InfluxFeed#influx write failed (data lost): [b]RequestTimedOutError: Request timed out
[latest-22080]2022-03-27T14:24:48.863Z <InfluxFeed:ERR> [InfluxFeed]InfluxFeed#influx write failed (data lost): [b]RequestTimedOutError: Request timed out
[latest-22080]2022-03-27T14:24:48.893Z <InfluxFeed:ERR> [InfluxFeed]InfluxFeed#influx write failed (data lost): [b]RequestTimedOutError: Request timed out
[latest-22080]2022-03-27T14:24:48.924Z <InfluxFeed:ERR> [InfluxFeed]InfluxFeed#influx write failed (data lost): [b]RequestTimedOutError: Request timed out
[latest-22080]2022-03-27T14:24:48.967Z <InfluxFeed:ERR> [InfluxFeed]InfluxFeed#influx write failed (data lost): [b]RequestTimedOutError: Request timed out
[latest-22080]2022-03-27T14:24:49.000Z <InfluxFeed:ERR> [InfluxFeed]InfluxFeed#influx write failed (data lost): [b]RequestTimedOutError: Request timed out
[latest-22080]2022-03-27T14:24:49.027Z <InfluxFeed:ERR> [InfluxFeed]InfluxFeed#influx write failed (data lost): [b]RequestTimedOutError: Request timed out
[latest-22080]2022-03-27T14:24:49.060Z <InfluxFeed:ERR> [InfluxFeed]InfluxFeed#influx write failed (data lost): [b]RequestTimedOutError: Request timed out
[latest-22080]2022-03-27T14:24:49.093Z <InfluxFeed:ERR> [InfluxFeed]InfluxFeed#influx write failed (data lost): [b]RequestTimedOutError: Request timed out
[latest-22080]2022-03-27T14:24:49.271Z <InfluxFeed:ERR> [InfluxFeed]InfluxFeed#influx write failed (data lost): [b]RequestTimedOutError: Request timed out
[latest-22080]2022-03-27T14:24:49.727Z <InfluxFeed:ERR> [InfluxFeed]InfluxFeed#influx write failed (data lost): [b]RequestTimedOutError: Request timed out
MSR is running in synology docker with the latest-22080-ae7212f
I can access to influxdb 2 like before with no changes on bucket and token.
my setup in yaml is:
plugins:
- id: influx
name: InfluxDB 2.0 Feed
enabled: true
implementation: InfluxFeed
config:
influx_url: "http://10.0.4.71:8086"
influx_token: XKKoCcQHVDF8p7-RkNQXLkJhe6neB48V7sNAG39HX4bOTcDA0Bv4B2SVtaUfHb_rdvVvUpbDDbaNEBeS1ISacQ==
influx_org: myhome
influx_bucket: test
I use influx_url and before it worked.
from portainer log, I see:
WARN: Write to InfluxDB failed (attempt: 1). b [RequestTimedOutError]: Request timed out
at ClientRequest.<anonymous> (/opt/reactor/node_modules/@influxdata/influxdb-client/dist/index.js:16:4115)
at ClientRequest.emit (node:events:520:28)
at ClientRequest.emit (node:domain:475:12)
at Socket.emitRequestTimeout (node:_http_client:758:9)
at Object.onceWrapper (node:events:639:28)
at Socket.emit (node:events:532:35)
at Socket.emit (node:domain:475:12)
at Socket._onTimeout (node:net:501:8)
at listOnTimeout (node:internal/timers:559:17)
at processTimers (node:internal/timers:502:7)
any advice to resolve this error?
Thanks in advance
Hi, it seems working ok. Thanks! If you need more infos to test, just tell me how I can produce them.
L Bulb FibaroDimmer2
ezlo>device_61425874129e29124dfcd75e
0.65
7:30:07 PM
dimming.level=0.65
dimming.step=0.1
energy_sensor.units="KWh"
energy_sensor.value=11.3400001525879
power_sensor.units="W"
power_sensor.value=6.90000009536743
power_switch.state=true
x_ezlo_device.battery_powered=false
x_ezlo_device.category="dimmable_light"
x_ezlo_device.manufacturer="Fibaro"
x_ezlo_device.model="FGD-212"
x_ezlo_device.parent=""
x_ezlo_device.reachable=true
x_ezlo_device.ready=true
x_ezlo_device.room="613e2024129e2912114c093b"
x_ezlo_device.status="idle"
x_ezlo_device.subcategory="dimmable_in_wall"
x_ezlo_device.type_id="271_258_4096"
x_ezlo_item.dimmer=65
x_ezlo_item.dimmer_down=0
x_ezlo_item.dimmer_stop=0
x_ezlo_item.dimmer_up=0
x_ezlo_item.electric_meter_kwh=11.3400001525879
x_ezlo_item.electric_meter_watt=6.90000009536743
x_ezlo_item.hw_state="hardware_failure"
x_ezlo_item.load_error_state="unknown"
x_ezlo_item.meter_reset=0
x_ezlo_item.over_current_state="unknown"
x_ezlo_item.over_load_state="unknown"
x_ezlo_item.power_surge_state="no_surge"
x_ezlo_item.switch=true
x_ezlo_item.voltage_drop_drift_state="unknown"
x_ezlo_object.id="61425874129e29124dfcd75e"
zwave_device.capabilities=null
zwave_device.failed=false
zwave_device.manufacturer_info=["Fibaro","FGD-212",null]
zwave_device.node_id=27
zwave_device.version_info=null
Capabilities: dimming, energy_sensor, power_sensor, power_switch, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device
Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighbors
another
K Bulb Domitech
ezlo>device_61423589129e29124dfcd756
0.65
7:35:42 PM
dimming.level=0.65
dimming.step=0.1
power_switch.state=true
x_ezlo_device.battery_powered=false
x_ezlo_device.category="dimmable_light"
x_ezlo_device.manufacturer="Domitech"
x_ezlo_device.model="ZE27EU"
x_ezlo_device.parent=""
x_ezlo_device.reachable=true
x_ezlo_device.ready=true
x_ezlo_device.room="613e2020129e2912114c093a"
x_ezlo_device.status="idle"
x_ezlo_device.subcategory="dimmable_bulb"
x_ezlo_device.type_id="526_19522_12596"
x_ezlo_item.dimmer=65
x_ezlo_item.dimmer_down=0
x_ezlo_item.dimmer_stop=0
x_ezlo_item.dimmer_up=0
x_ezlo_item.switch=true
x_ezlo_object.id="61423589129e29124dfcd756"
zwave_device.capabilities=null
zwave_device.failed=false
zwave_device.manufacturer_info=["Domitech","ZE27EU",null]
zwave_device.node_id=26
zwave_device.version_info=null
Capabilities: dimming, power_switch, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device
Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighbors
another
H Bulb Widom dimmer
ezlo>device_6147578c129e29124dfcd814
1
7:36:56 PM
dimming.level=1
dimming.step=0.1
energy_sensor.units="KWh"
energy_sensor.value=0.651000022888184
power_sensor.units="W"
power_sensor.value=2.47000002861023
power_switch.state=true
x_ezlo_device.battery_powered=false
x_ezlo_device.category="dimmable_light"
x_ezlo_device.manufacturer="Unknown"
x_ezlo_device.model="Unknown"
x_ezlo_device.parent=""
x_ezlo_device.reachable=true
x_ezlo_device.ready=true
x_ezlo_device.room="613e2012129e2912114c0938"
x_ezlo_device.status="idle"
x_ezlo_device.subcategory="dimmable_in_wall"
x_ezlo_device.type_id="329_4628_2560"
x_ezlo_item.dimmer=100
x_ezlo_item.dimmer_down=0
x_ezlo_item.dimmer_stop=0
x_ezlo_item.dimmer_up=0
x_ezlo_item.electric_meter_kwh=0.651000022888184
x_ezlo_item.electric_meter_watt=2.47000002861023
x_ezlo_item.meter_reset=0
x_ezlo_item.switch=true
x_ezlo_object.id="6147578c129e29124dfcd814"
zwave_device.capabilities=null
zwave_device.failed=false
zwave_device.manufacturer_info=["Unknown","Unknown",null]
zwave_device.node_id=41
zwave_device.version_info=null
Capabilities: dimming, energy_sensor, power_sensor, power_switch, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device
Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighbors
what I can notice in "Entities" is that at the moment this device is OFF, but dimmer_level is =1
L Bulb Spot Widom Dimmer
ezlo>device_61475325129e29124dfcd7e6
1
2:16:40 AM
dimming.level=1
dimming.step=0.1
dimming.undefined=0
energy_sensor.undefined="KWh"
energy_sensor.units="KWh"
energy_sensor.value=0.994000017642975
power_sensor.undefined="W"
power_sensor.units="W"
power_sensor.value=7.96000003814697
power_switch.state=true
power_switch.undefined=false
x_ezlo_device.battery_powered=false
x_ezlo_device.category="dimmable_light"
x_ezlo_device.manufacturer="Unknown"
x_ezlo_device.model="Unknown"
x_ezlo_device.parent=""
x_ezlo_device.reachable=true
x_ezlo_device.ready=true
x_ezlo_device.room="613e2024129e2912114c093b"
x_ezlo_device.status="idle"
x_ezlo_device.subcategory="dimmable_in_wall"
x_ezlo_device.type_id="329_4628_2560"
x_ezlo_item.dimmer=0
x_ezlo_item.dimmer_down=0
x_ezlo_item.dimmer_stop=0
x_ezlo_item.dimmer_up=0
x_ezlo_item.electric_meter_kwh=0.996999979019165
x_ezlo_item.electric_meter_watt=0
x_ezlo_item.meter_reset=0
x_ezlo_item.switch=false
x_ezlo_object.id="61475325129e29124dfcd7e6"
zwave_device.capabilities=null
zwave_device.failed=false
zwave_device.manufacturer_info=["Unknown","Unknown",null]
zwave_device.node_id=38
zwave_device.version_info=null
Capabilities: dimming, energy_sensor, power_sensor, power_switch, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device
Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighbors
or this other one, dimmer level diverge from msr to ezlo
K Bulb Domitech
ezlo>device_61423589129e29124dfcd756
0
2:30:41 AM
dimming.level=0
dimming.step=0.1
dimming.undefined=0.25
power_switch.state=false
power_switch.undefined=true
x_ezlo_device.battery_powered=false
x_ezlo_device.category="dimmable_light"
x_ezlo_device.manufacturer="Domitech"
x_ezlo_device.model="ZE27EU"
x_ezlo_device.parent=""
x_ezlo_device.reachable=true
x_ezlo_device.ready=true
x_ezlo_device.room="613e2020129e2912114c093a"
x_ezlo_device.status="idle"
x_ezlo_device.subcategory="dimmable_bulb"
x_ezlo_device.type_id="526_19522_12596"
x_ezlo_item.dimmer=25
x_ezlo_item.dimmer_down=0
x_ezlo_item.dimmer_stop=0
x_ezlo_item.dimmer_up=0
x_ezlo_item.switch=true
x_ezlo_object.id="61423589129e29124dfcd756"
zwave_device.capabilities=null
zwave_device.failed=false
zwave_device.manufacturer_info=["Domitech","ZE27EU",null]
zwave_device.node_id=26
zwave_device.version_info=null
Capabilities: dimming, power_switch, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device
Actions: dimming.down, dimming.set, dimming.up, power_switch.off, power_switch.on, power_switch.set, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighbors
Happy Holidays and very best wishes for a wonderfull and reactor New Year!
Hi, checking Ezlo app and the device is also in OFF state on Dashboard. So the problem is not Reactor but Ezlo.
Thanks!
If can help, today I added another zwave device "Widom Smart Plug" https://www.widom.it/wp-content/uploads/2019/08/Widom-Smart-Plug_EN_20190404_0.pdf
At the moment it is ON and in Entities power.switch_state is FALSE
energy_sensor.units="kilo_watt_hour"
energy_sensor.value=0.0230000000447035
power_sensor.units="watt"
power_sensor.value=36.7000007629395
power_switch.state=false
x_ezlo_device.battery_powered=false
x_ezlo_device.category="switch"
x_ezlo_device.manufacturer="Unknown"
x_ezlo_device.model="Unknown"
x_ezlo_device.parent=""
x_ezlo_device.reachable=true
x_ezlo_device.ready=true
x_ezlo_device.room="613e2037129e2912114c093e"
x_ezlo_device.status="idle"
x_ezlo_device.subcategory="interior_plugin"
x_ezlo_device.type_id="329_4628_1792"
x_ezlo_item.electric_meter_kwh=0.0230000000447035
x_ezlo_item.electric_meter_volt=230.399993896484
x_ezlo_item.electric_meter_watt=36.7000007629395
x_ezlo_item.meter_reset=0
x_ezlo_item.switch=false
x_ezlo_object.id="61c18f96129e291255528096"
zwave_device.capabilities=null
zwave_device.failed=false
zwave_device.manufacturer_info=["Unknown","Unknown",null]
zwave_device.node_id=60
zwave_device.version_info=null
Capabilities: energy_sensor, power_sensor, power_switch, toggle, x_ezlo_device, x_ezlo_item, x_ezlo_object, zwave_device
Actions: power_switch.off, power_switch.on, power_switch.set, toggle.toggle, x_ezlo_device.device_check, x_ezlo_device.set_item_value, x_ezlo_device.set_name, x_ezlo_device.set_room, x_ezlo_device.status_check, zwave_device.poll, zwave_device.reconfigure, zwave_device.refresh, zwave_device.reset_meters, zwave_device.set_config, zwave_device.update_neighbors
```
Hi, the file it is uploaded.
Thanks