Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.
N

noelab

@noelab
Disaster recovery and virtualisation
CatmanV2C

Following on from my last thread, some progress has been made over the weekend.

With 18G of spanky RAM in my Synology DS224+. I've jumped into the murky world of virtualisation and already eliminated the need for two Raspberry Pi's from my system.

Home Assistant: In theory they provide an OVA file which is supported by the Synology. I couldn't get it to work, however, so grabbed a copy of the .img file they supply, renamed it .iso and imported it as a VM. Restored from my full back up and that all seems fantastic.

Minidnla Music server: Trivial. Grabbed a Debian .iso for Bookworm and copied that onto the NAS. Created a new machine which mirrored the specs of the Raspberry Pi, booted from the ISO then did an expert install. Once that was all stable with a basic core of stuff and networking, I've made a copy of that as a good base system. Then fired up minidnla on it, mounted my media and that's also woking. Not bad for a short weekend's work.

Still not sure about the main NUC though. I'm thinking of buying a new USB stick so I can mess around getting it working on the Synology before I do anything drastic.

Once that hurdle is sorted I'm torn between:

Using a brand new install of Bookworm, re-installing Z-way server, OpenLuup, AltUI, MSR and HA bridge, then restoring across or Making an ISO of the current system, importing that and upgrading in place (which will be pretty risk free since I can snapshot everything before I make any changes.)

Decisions, decisions.

C

General Discussion
Local notification methods?
CatmanV2C

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

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

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

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

TIA

C

Multi-System Reactor
RFC: When disaster strikes (sorry it's a bit verbose)
CatmanV2C

Hi everyone. Thanks for all your input recently on the topic of local notifications. I think we got some really interesting solutions 🙂

Back to more prosaic matters. Most of you will know that I've been messing around with this stuff for some years. My last major change was when I migrated from Vera, which was something like 4-5 years ago.

While my system has grown, it's not really altered very regularly, although I try to keep most of it kind of up to date.

Current set up:
Intel NUC that runs:
Bare metal install of Debian
Z-way server with Z-wave.me USB stick
Openluup
Altui
Multi system reactor
HA Bridge
Mosquito

Raspberry Pi
Running Home Assistant

About 40 varied Z-wave and Wifi devices

I also have a Synology DS224+ which may inform some responses.

Home Assistant recovery is pretty simple. I get a full backup of the system every night dumped onto my SAN and I know from experience that it would simply be a case of booting up a new install and feeding it the backup.

The NUC on the other hand....
Coming from a commercial IT world, I am becoming more and more conscious that I don't really feel I have a suitable disaster recovery plan, and my core system is running on hardware heading for 10 years old.

My initial thought, which I've kept putting off as it's awkward would be to grab a nice SSD, reboot the NUC into Mint or something similar and simply do a dd copy onto a new drive. I can get a replacement NUC on ebay simply enough, and keep it in a cupboard if anything other than the hard drive fails on the existing one, but this feels rather like a stop gap. However one immediate question:

If I had to use the replacement NUC would all the Z-wave devices simply carry on talking to the stick, or would they all need to be re-paired?

How easy would it be to move everything the NUC does (as a start) onto the NAS? Create a VM and clone the disc onto it?

Should I move to Docker? Something else?

What are the hive mind's thoughts?

Apologies if we've done this before, but while it all just works...

Cheers!

C

General Discussion
AltUI sans internet connection
CatmanV2C

Morning world. Looking for some thoughts on recent experience 🙂

Yesterday my ISP had something of a catastrophic failure (in theory not yet fixed but seems OK for now)

While this is annoying for several reasons, one thing that I wasn't expecting was for AltUI to become pretty much un-usable.

Unless I have a tab already open and active, connecting to the Home page is pretty much random / impossible, just presenting with a white page and (sometimes) 'Waiting for initial data' on the bottom. Everything works (i.e. where I have controllers or Reactions I can trigger, they function flawlessly) it's just something of a pain since 99.9% of my control is via Alexa now, and not being able to access devices in AltUI makes things like turning some lights of a bit tricky 😉

I suspect that this is due to AltUI trying to pull licence info and Weather data, and failing. What I should do is probably access the OpelLuup console direct and see if that works better in future.

Does that make sense to anyone, or am I completely off track?

Cheers

C

Software
Eachen No Neutral smart wall switch to lights and Sonoff Mini R4 switch for LEDs
R

Hi all. First post so please be gentle.

I have an Eachen two-gang smart wall switch wired no neutral (with capacitor) connected to existing bathroom lights which works perfectly. It's also wired to a Sonoff Mini R4 Extreme connected to LED lights. I want the LED lights to switch on when the bathroom lights switch on (and vice versa). The Mini R4 works separately on my phone via Ewelink as well as on the Mini R4 itself (physical button). The switch is installed inside the wall and the rest of the components are in the ceiling / attic / roof cavity. The Mini R4 is set to Edge switch mode which works in my example I wired.

How I wired it:

cb919874-6933-460a-8cd0-f063bac88674-image.png

I have a video showcasing the example I wired today works. I could share it if required. Ignore the white cable. I only used it to power the example.

77ebbc23-83de-48ee-a4bf-247bfd24f121-image.png

3827ede6-cf5c-47aa-8fdb-c75470101c4a-image.png

The wiring diagram I used for the mini R4.

485de912-e656-4da3-b6f6-81cb076e0261-image.png

I wired it together with the existing lights of the bathroom so that L1 switches on both the Mini R4 and the bathroom lights:

a3ea5c93-a9ae-4aaf-8dce-24018bcdb4d1-image.png

This is the wiring diagram for the Eachen switch:
b867a3c7-c1ac-428c-a90f-7f0f4b62a609-image.png

The Eachen's first gang (L1) doesn't trigger the Mini R4 in any way.

Any help or advice will be much appreciated.

Thanks,
R

General Discussion
Custom capabilities in MQTT templates
M

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

So this is what I have in the local_mqtt_devices.yaml

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

And this is the template:

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

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

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

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

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

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

br,
mgvra

MSR latest-25016-d47fea38 / MQTTController [0.2.24293]

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

Hi, @toggledbits

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

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

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

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

Here is what I see from the log:

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

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

Questions:

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

Here is the log:

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

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

Not a big issue simply a request if easily doable.

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

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

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

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

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

Just a small anoyance

Thanks

Multi-System Reactor
Button.Since Revisited
SnowmanS

@toggledbits In the MSR documentation, under Standard Capabilities, I noticed that the
button.since attribute was deprecated as of version 22256 and the metadata is the preferred way to access the last-modified time of an attribute.

Am I reading this right? Should I stop using it in my rules?

Thanks

Multi-System Reactor
[SOLVED] reactor_inet_check script... and containers
G

When on my bare metal RPi with MSR I had a rule that ran every minute to check Internet status via a script in MSR called reactor_inet_check.sh

I've moved to containerized MSR and see in the instructions that this cannot be run from the container.

The script cannot run within the Reactor docker container. If you are using Reactor in a docker container, the script needs to be run by cron or an equivalent facility on the host system (e.g. some systems, like Synology NAS, have separate task managers that may be used to schedule the repeated execution of tasks such as this).

I've put a script on my container host that calls the reator_inet_check.sh script and it isn't erroring... but I still see the internet status within MSR as null.

Before I go diving down the rabbit hole... should this work?

My cronjob on the proxmox host:
909fe6f0-77fd-4734-80a4-c9e354c910b6-image.png

The contents of msr_internet_check_caller.sh
16337528-cf31-4968-bffe-af1149f7103e-image.png

Multi-System Reactor
Hello and first network question
D

Just bought a couple of generic smart plugs and set them up easily using SmartLife app in the house I then plugged one into a workshop over 100m away This workshop has a hardwired internet connection with a separate wireless access router (not mesh) after doing a reset on the device and pairing to the new router it actually works from the house when my phone is connected to a completely separate wifi network - how is that possible ?
I did read something about these devices connecting to a server somewhere in China similar to IP cameras but there is no lag

General Discussion
Lights switches for warehouse
S

I need to replace about 15 traditional wall light switches (no neutral wire) to turn on/off all lights with one operation inside the warehouse. And still maintain the ability to control each light individually.

The preference is not to set up a Wifi for each switch to reduce the number of devices connected to the network, and also, they change the Wifi password regularly, so they do not want to change all 15 switches.

I am looking for some solution that will achieve this with either Bluetooth/RF or any other technology.
The warehouse dimensions are about 100ftx100ft with sheetrock walls.

Please assist.

General Discussion
Catch-all lights rule
G

Background: this is a Windows MSR install I've done for our local pool/amenity center just to run some fans and lights (not my daily driver at home). Install went perfectly fine.

Scenario: I want the lights to go on when it's dark enough (even if during a storm, not just after sunset) so I'm using solarRadiation from my weather station to drive that Trigger. Easy stuff.

Issue: sometimes, someone goes in the office and just starts flipping switches and the result can be lights turned on in the daytime or off at night. I'm trying to create a "catch-all" wherein if it is daytime and the lights somehow find their way ON, they will turn themselves back OFF.

I have the following Reaction built:

b30eab5b-5a14-4a3a-8c9a-47e3e7e53dc3-image.png

I also have this Reaction for opposite, ie the lights find themselves turned off after dark and they will turn themselves back on:

5c6946b1-297c-4eb1-9618-74820979df29-image.png

Here are my two rules:

288cba86-f941-4157-86d9-d8e7487905f7-image.png *NOTE that in my manual testing, ie I turn on the light switch at the incorrect time, when the solarRadiation level changes the Lights ON rule flags and shows as SET. On the next change of solarRadiation it goes back to reset again.

My expectation is that Lights OFF rule should see the lights are on, the solarRadiation is above the set limit, and turn them off. Instead, every other run, the ON rule moves to SET and then reset again on the following run.

Logs appear angry:

[latest-25016]2025-01-26T22:03:31.696Z <Engine:INFO> Enqueueing "Lights ON<RESET>" (rule-m6e4ajh7:R) [latest-25016]2025-01-26T22:03:31.712Z <Engine:NOTICE> Starting reaction Lights ON<RESET> (rule-m6e4ajh7:R) [latest-25016]2025-01-26T22:03:31.713Z <Engine:INFO> Lights ON<RESET> all actions completed. [latest-25016]2025-01-26T22:03:42.565Z <wsapi:INFO> client "127.0.0.1#3" closed, code=1001, reason= [latest-25016]2025-01-26T22:03:42.753Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/lang [latest-25016]2025-01-26T22:03:42.754Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/lang from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/lang ACL (#7): [Object]{ "url": "/api/v1/lang", "allow": true, "index": 7 } [latest-25016]2025-01-26T22:03:42.790Z <wsapi:INFO> wsapi: connection from ::ffff:127.0.0.1 [latest-25016]2025-01-26T22:03:42.839Z <wsapi:INFO> [WSAPI]wsapi#1 client "127.0.0.1#6" authorized [latest-25016]2025-01-26T22:03:43.353Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/systime [latest-25016]2025-01-26T22:03:43.353Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/systime from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/systime ACL (#5): [Object]{ "url": "/api/v1/systime", "allow": true, "index": 5 } [latest-25016]2025-01-26T22:03:48.146Z <wsapi:INFO> client "127.0.0.1#6" closed, code=1001, reason= [latest-25016]2025-01-26T22:03:48.308Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/lang [latest-25016]2025-01-26T22:03:48.309Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/lang from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/lang ACL (#7): [Object]{ "url": "/api/v1/lang", "allow": true, "index": 7 } [latest-25016]2025-01-26T22:03:48.346Z <wsapi:INFO> wsapi: connection from ::ffff:127.0.0.1 [latest-25016]2025-01-26T22:03:48.390Z <wsapi:INFO> [WSAPI]wsapi#1 client "127.0.0.1#7" authorized [latest-25016]2025-01-26T22:03:49.412Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/systime [latest-25016]2025-01-26T22:03:49.413Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/systime from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/systime ACL (#5): [Object]{ "url": "/api/v1/systime", "allow": true, "index": 5 } [latest-25016]2025-01-26T22:03:52.734Z <wsapi:INFO> client "127.0.0.1#7" closed, code=1001, reason= [latest-25016]2025-01-26T22:03:52.891Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/lang [latest-25016]2025-01-26T22:03:52.892Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/lang from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/lang ACL (#7): [Object]{ "url": "/api/v1/lang", "allow": true, "index": 7 } [latest-25016]2025-01-26T22:03:52.925Z <wsapi:INFO> wsapi: connection from ::ffff:127.0.0.1 [latest-25016]2025-01-26T22:03:52.965Z <wsapi:INFO> [WSAPI]wsapi#1 client "127.0.0.1#8" authorized [latest-25016]2025-01-26T22:03:54.383Z <httpapi:INFO> [HTTPAPI]#1 API request from ::ffff:127.0.0.1: GET /api/v1/systime [latest-25016]2025-01-26T22:03:54.384Z <httpapi:INFO> [HTTPAPI]#1 request for /api/v1/systime from ::ffff:127.0.0.1 user anonymous auth none matches /api/v1/systime ACL (#5): [Object]{ "url": "/api/v1/systime", "allow": true, "index": 5 } [latest-25016]2025-01-26T22:04:01.590Z <wsapi:INFO> [WSAPI]wsapi#1 rpc_echo [Object]{ "comment": "UI activity" } [latest-25016]2025-01-26T22:04:39.646Z <Rule:INFO> Lights OFF (rule-m6e33ja3 in Atrium Lights) evaluated; rule state transition from RESET to SET! [latest-25016]2025-01-26T22:04:39.656Z <Rule:INFO> Lights ON (rule-m6e4ajh7 in Atrium Lights) evaluated; rule state transition from RESET to SET! [latest-25016]2025-01-26T22:04:39.663Z <Engine:INFO> Enqueueing "Lights OFF<SET>" (rule-m6e33ja3:S) [latest-25016]2025-01-26T22:04:39.665Z <Engine:INFO> Enqueueing "Lights ON<SET>" (rule-m6e4ajh7:S) [latest-25016]2025-01-26T22:04:39.668Z <Engine:NOTICE> Starting reaction Lights OFF<SET> (rule-m6e33ja3:S) [latest-25016]2025-01-26T22:04:39.669Z <Engine:NOTICE> Starting reaction Lights ON<SET> (rule-m6e4ajh7:S) [latest-25016]2025-01-26T22:04:39.669Z <Engine:INFO> Lights ON<SET> all actions completed. [latest-25016]2025-01-26T22:04:39.675Z <Rule:INFO> Lights OFF (rule-m6e33ja3 in Atrium Lights) evaluated; rule state transition from SET to RESET! [latest-25016]2025-01-26T22:04:39.680Z <Engine:NOTICE> ReactionHistory: no entry for [latest-25016]2025-01-26T22:04:39.683Z <Engine:NOTICE> [Engine]Engine#1 entry 256 reaction rule-m6e33ja3:S-1q2f1j0p: [Error] terminated [parent terminating] [latest-25016]2025-01-26T22:04:39.683Z <Engine:CRIT> Error: terminated [parent terminating] Error: terminated at Engine._process_reaction_queue (C:\Users\Jalan\msr\reactor\server\lib\Engine.js:1644:47) [latest-25016]2025-01-26T22:04:39.699Z <Engine:NOTICE> [Engine]Engine#1 entry 254 reaction rule-m6e33ja3:S: [Error] terminated [preempted by rule state change] [latest-25016]2025-01-26T22:04:39.699Z <Engine:CRIT> Error: terminated [preempted by rule state change] Error: terminated at Engine._process_reaction_queue (C:\Users\Jalan\msr\reactor\server\lib\Engine.js:1644:47) [latest-25016]2025-01-26T22:04:39.700Z <Engine:INFO> Enqueueing "Lights OFF<RESET>" (rule-m6e33ja3:R) [latest-25016]2025-01-26T22:04:39.704Z <Engine:NOTICE> Starting reaction Lights OFF<RESET> (rule-m6e33ja3:R) [latest-25016]2025-01-26T22:04:39.705Z <Engine:INFO> Lights OFF<RESET> all actions completed. [latest-25016]2025-01-26T22:05:48.822Z <Rule:INFO> Lights ON (rule-m6e4ajh7 in Atrium Lights) evaluated; rule state transition from SET to RESET! [latest-25016]2025-01-26T22:05:48.831Z <Engine:INFO> Enqueueing "Lights ON<RESET>" (rule-m6e4ajh7:R) [latest-25016]2025-01-26T22:05:48.847Z <Engine:NOTICE> Starting reaction Lights ON<RESET> (rule-m6e4ajh7:R) [latest-25016]2025-01-26T22:05:48.847Z <Engine:INFO> Lights ON<RESET> all actions completed.
Multi-System Reactor
Throttled problem
wmarcolinW

Hi @toggledbits

I found this very old post that talked about a way to limit device reading to avoid the throttled problem, because it's not a question of logic, it's that the device actually sends a lot of information, in my case the NUT ups installed in HE.

https://smarthome.community/topic/687/flapping-device?_=1737652139854

It mentions engine section of reactor.yaml by setting update_rate_limit, but I looked in the current MSR documentation and I can't find this information, so I don't know if it's still valid, its effect and parameters.

My situation is simple, when I have a UPS problem the NUT is sending dozens of reports per second and then I have the throttled problem. The same rule applies when the power is normal.

This is the rule, and the parameter that fails is the Tripp Lite UPS status.

cf9ddabf-3144-4e5a-80a4-0dc7664b9573-image.png

a813a077-974e-4737-897c-e383085b3d8f-image.png

All error is the same scenario.

[latest-25016]2025-01-23T12:01:32.753Z <Rule:WARN> (13) NUT Disconected (rule-l4djr0p7 in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttl> [latest-25016]2025-01-23T12:01:32.756Z <Rule:WARN> (27) Falta de Energia (rule-l4h9ceod in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Thrott> [latest-25016]2025-01-23T12:01:32.769Z <Rule:WARN> (73) UPS Battery Low (rule-l4hj850o in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttl> [latest-25016]2025-01-23T12:01:32.772Z <Rule:WARN> (74) UPS Comm Fail (rule-l4kbs5cp in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttlin> [latest-25016]2025-01-23T12:01:32.776Z <Rule:WARN> (76) UPS Utility Back (rule-l4hjhs6m in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Thrott> [latest-25016]2025-01-23T12:01:32.780Z <Rule:WARN> UPS On Battery (rule-l4hjuka5 in Datacenter) update rate 121/min exceeds limit (120/min)! Logic loop? Throttling> [latest-25016]2025-01-23T12:01:32.781Z <Rule:WARN> UPS Info (rule-l4gheo63 in Datacenter) update rate 121/min exceeds limit (120/min)! Logic loop? Throttling... [latest-25016]2025-01-23T12:01:40.757Z <Rule:WARN> (13) NUT Disconected (rule-l4djr0p7 in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttl> [latest-25016]2025-01-23T12:01:40.759Z <Rule:WARN> (27) Falta de Energia (rule-l4h9ceod in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Thrott> [latest-25016]2025-01-23T12:01:40.776Z <Rule:WARN> (73) UPS Battery Low (rule-l4hj850o in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttl> [latest-25016]2025-01-23T12:01:40.777Z <Rule:WARN> (74) UPS Comm Fail (rule-l4kbs5cp in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Throttlin> [latest-25016]2025-01-23T12:01:40.778Z <Rule:WARN> (76) UPS Utility Back (rule-l4hjhs6m in Warning) update rate 121/min exceeds limit (120/min)! Logic loop? Thrott>

Thanks.

Multi-System Reactor
Dynamic Alert Based on Tripped Expression
T

Hello -

Long time. Hope everyone is good.

I have a rule that looks at a number of temperature sensors around the house. It simply sends a general alert if any of them fall below their threshold. (A basic “House is too cold” alert for when we’re away)

Generally, this has worked well. But I was wondering if there’s a way to make the message somewhat dynamic without creating separate rules for each sensor.

E.g. “House is too cold due to Sump Temperature below 45 degrees.”

I thought I remember reading about someone doing this in the past but couldn’t find it.

Thanks for any ideas!

Multi-System Reactor
latest-25016 toggle.toggle on VeraController Lock entity not working
CrilleC

After upgrade from 24366 to 25016 toggle on Vera (openLuup) lock entity doesn't seem to work.

VeraController log level 5
24366:

[latest-24366]2025-01-20T20:26:49.724Z <VeraController:INFO> VeraController#vera perform action toggle.toggle on Lock#vera>device_10016 with [Object]{ } [latest-24366]2025-01-20T20:26:49.725Z <VeraController:5:VeraController.js:514> [VeraController:verarequest] requesting http://127.0.0.1:3480/data_request?id=action&serviceId=urn%3Amicasaverde-com%3AserviceId%3ADoorLock1&action=SetTarget&newTargetValue=0&DeviceNum=10016&output_format=json&_r=1737404809725 ([Object]{ })

25016:

[latest-25016]2025-01-20T20:30:25.457Z <VeraController:INFO> VeraController#vera perform action toggle.toggle on Lock#vera>device_10016 with [Object]{ } [latest-25016]2025-01-20T20:30:25.458Z <VeraController:5:VeraController.js:1210> VeraController#vera no configured implementation for toggle.toggle on Lock#vera>device_10016; calling super [latest-25016]2025-01-20T20:30:25.458Z <VeraController:INFO> VeraController#vera perform action lock.set on Lock#vera>device_10016 with [Object]{ "state": false } [latest-25016]2025-01-20T20:30:25.461Z <VeraController:5:VeraController.js:1255> VeraController#vera sending action request [Object]{ "newTargetValue": "0", "DeviceNum": 10016, "id": "action", "serviceId": "urn:upnp-org:serviceId:DoorLock1", "action": "SetTarget" } [latest-25016]2025-01-20T20:30:25.461Z <VeraController:5:VeraController.js:515> [VeraController:verarequest] requesting http://127.0.0.1:3480/data_request?newTargetValue=0&DeviceNum=10016&id=action&serviceId=urn%3Aupnp-org%3AserviceId%3ADoorLock1&action=SetTarget&output_format=json&_r=1737405025461 ([Object]{ }) [latest-25016]2025-01-20T20:30:25.463Z <VeraController:NOTICE> VeraController#vera action lock.set([Object]{ "state": false }) on Lock#vera>device_10016 succeeded

I tried to log an issue in Mantis Bug Tracker but I can't log in anymore?

Multi-System Reactor
[Solved] Local expression evaluation
V

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

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

Any help would be appreciated

I have the following test rule:

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

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

Here is the expressioncode:

vFrom1 = "09:25:00", vFrom2 = "09:30:00", vFrom3 = "09:41:00", vTo = "10:55:00", # Get current time (format HH:MM:SS) vToDay = strftime("%H:%M:%S"), #Get current house temperature CurrentHouseTemp = getEntity( "hass>Thermostat2 " ).attributes.temperature_sensor.value, case when CurrentHouseTemp <= 19 and vToDay >= vFrom1 && vToDay <= vTo: "true1" # From1 when CurrentHouseTemp <= 20 and vToDay >= vFrom2 && vToDay <= vTo: "true2" # From2 when CurrentHouseTemp < 26  and vToDay >= vFrom3 && vToDay <= vTo: "true3" # From3 else "false" end
Multi-System Reactor
Apple Home Automation Issue
J

I’ve set up an automation in Apple Home to turn on the lights when the first person arrives. However, the lights also turn on when I leave for work. It seems like the automation is triggered when I cross the geofence, whether arriving or leaving.

I’m using Matter-compatible Tapo smart plugs. Is there a way to fix this behavior?

How-To
Migration Vera to HA > how to send sensor data from Vera to HA?
M

Hi,

I started home automation in 2013 and using Vera controllers from the start. When Reactor plugin became available (super plugin of @toggledbits !!) I transferred all scenes to Reactor.
I must say everything here works still okay and I have a lot of devices, plugins and Reactors. But I fear at some point my Vera's will stop working.
I recognize many of your names here from the Vera forum. I also was banned a couple of years ago.
Recently I decided to switch to Home Assistant. I already transferred some of my zwave devices from Vera to HA and made some new automations.
I must say HA is great and with huge amount of integrations, add-ons, the HACS store and many examples (like blueprints) the opportunites to increase home automation are huge.
HA will be for sure my central system (incl UI)

But... the learning curve is quite steap (YAML is completely different from Lua/luup).
So for the time being I will keep my most complex Reactor automations.
I already found how I can connect/integrate Vera for binairy sensors via webhooks (as an example: changes in my home modes are directly send from Vera to HA).

Now I also want to use some data like sensors or Reactor variables automatically to HA via https requests (put those in Reactor).
I know I can create virtual sensors in HA via templates.

As an example: I have my own PWS with a rainmeter. In Reactor I compare the amount of rain (in mm) in the actual year with historical figures (past 15 years) and calculate the difference actual vs history in % Every day at 0.00h these figures are updated. I defined variables in Reactor and use Multistring plugin (Variable container) to show the data.

I know several specialists in coding with experience in both Vera and HA are active here on this forum.

Who can help me with this ?

Home Assistant
[Solved] Migrating MSR to Docker on Proxmox
G
Zero issues installing Proxmox on a new MiniPC. Zero issues migrating my HA instance over to the new hotness (I know, I was surprised, too!)

And then MSR...

My first issue: I'm logged into the msr CT as reactor (I used the suggested username just to keep things simple as this is new space for me and I was high off my success of migrating HA over).

When I run

docker pull toggledbits/reactor:latest-amd64

... it assigns the \reactor\ subdirectory where installed root ownership. I am absolutely logged in with the correct non-root user.
1c58aead-85ca-4b2c-8f48-c3d1f57d7fe3-image.png

Second issue: I copied over the following folders:
67e7e4a5-cee8-4de1-90c7-1df35f1070b9-image.png When MSR loads, all of my Global Expressions are missing.

Third issue:
All controllers connect wonderfully (Hubitat, etc)... except HA.
After changing ownership of the logs to reactor again I can see this when MSR calls HA:

[latest-24366]2025-01-12T00:03:43.128Z <HubitatController:INFO> HubitatController#hubitat successful connection to ws://192.168.1.214/eventsocket [latest-24366]2025-01-12T00:03:43.151Z <HubitatController:NOTICE> HubitatController#hubitat current mode is Evening (2) [latest-24366]2025-01-12T00:03:43.212Z <HubitatController:NOTICE> HubitatController#hubitat HSM status is disarmed [latest-24366]2025-01-12T00:03:43.214Z <Controller:NOTICE> Controller HubitatController#hubitat is now online. [latest-24366]2025-01-12T00:03:43.255Z <MQTTController:INFO> MQTTController#mqtt2 connected; opening subscriptions [latest-24366]2025-01-12T00:03:43.371Z <MQTTController:INFO> MQTTController#mqtt2 sending inits and going online! [latest-24366]2025-01-12T00:03:43.373Z <Controller:NOTICE> Controller MQTTController#mqtt2 is now online. [latest-24366]2025-01-12T00:03:47.179Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.1.123:8123/api/websocket [latest-24366]2025-01-12T00:03:47.180Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error] connect ECONNREFUSED 192.168.1.123:8123 [-] [latest-24366]2025-01-12T00:03:47.180Z <HassController:WARN> HassController#hass ws error code ECONNREFUSED [latest-24366]2025-01-12T00:03:47.180Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.1.123:8123/api/websocket closed during open/negotiation [latest-24366]2025-01-12T00:03:47.180Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error] connect ECONNREFUSED 192.168.1.123:8123 [-] [latest-24366]2025-01-12T00:03:52.181Z <HassController:NOTICE> HassController#hass connecting to ws://192.168.1.123:8123/api/websocket [latest-24366]2025-01-12T00:03:52.183Z <HassController:WARN> HassController#hass websocket error during open/negotation: [Error] connect ECONNREFUSED 192.168.1.123:8123 [-] [latest-24366]2025-01-12T00:03:52.183Z <HassController:WARN> HassController#hass ws error code ECONNREFUSED [latest-24366]2025-01-12T00:03:52.183Z <HassController:NOTICE> HassController#hass websocket to ws://192.168.1.123:8123/api/websocket closed during open/negotiation [latest-24366]2025-01-12T00:03:52.183Z <HassController:WARN> HassController#hass failed to connect/initialize communication: [Error] connect ECONNREFUSED 192.168.1.123:8123 [-]

Yes, I created a fresh new long-lived access token for the MSR containerized install and updated the reactor.yaml config file correctly.

Honestly, all-in-all, for my total lack of expertise here I'm very pleased that I only have these three issues. But they are def blockers atm.

My RPi bare metal install of MSR hooked right up to the new HA and is humming along just fine (I used hostnames were possible and shuffled some IPs in other places so I wouldn't run into things later that were mapped incorrectly that I'd forgotten about.)

Proxmox 8.3.2 MSR lives in an Ubuntu 24.04 Proxmox container MSR is latest docker version

What else can I provide to those smarter than me here?

Multi-System Reactor
About
Posts
50
Topics
8
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial
  • TTS in MSR?
    N noelab

    @therealdb said in TTS in MSR?:

    [
    "Bentornato a casa",
    "Casa, dolce casa!",
    "Ciao!",
    ]

    Grazie! and thanks to @toggledbits for the new dark theme, also my eyes are happy!

  • TTS in MSR?
    N noelab

    Hi, just playing around this topic with Alexa and I share it:
    Example that works:

    image.png

    image.png

    Still no lucky to play with "random" announce.
    This example not work:

    image.png

    image.png

  • Need Testers
    N noelab

    @toggledbits
    some devices are created for test purpose so maybe there are errors

    code_text

    • id: virtual
      name: VEC
      implementation: VirtualEntityController
      enabled: true
      config:
      entities:

      HomeMode

       -
   id: v00_Automation
   template: Binary Sensor
   name: v00 Automation Mode

      Indici Temperatura Umidità

       -
   id: v00_InsideHOT
   template: Binary Sensor
   name: v00 Temp Inside HOT                
 -
   id: v00_OutsideHOT
   template: Value Sensor
   name: v00 Temp Outside HOT
 -
   id: v00_TempOutsideInside
   template: Binary Sensor
   name: v00 Temp Outside>Inside
 -
   id: v00_umidita_assoluta_interna
   name: v00 Umidita Assoluta Interna      
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xWeather_Umidita_Assoluta_Interna
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: v00_umidita_assoluta_esterna
   name: v00 Umidita Assoluta Esterna
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xWeather_Umidita_Assoluta_Esterna
   primary_attribute: value_sensor.value
   type: ValueSensor

      IndiceThom

       -
   id: vB1_IndiceThom
   template: Value Sensor
   name: vB1 IndiceThom    
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xB1_IndiceThom_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vB2_IndiceThom
   name: vB2 IndiceThom
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xB2_IndiceThom_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vCS_IndiceThom
   name: vCS IndiceThom
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xCS_IndiceThom_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vH_IndiceThom
   name: vH IndiceThom    
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xH_IndiceThom_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vK_IndiceThom
   name: vK IndiceThom
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xK_IndiceThom_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vL_IndiceThom
   name: vL IndiceThom
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xL_IndiceThom_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vR1_IndiceThom
   name: vR1 IndiceThom
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xR1_IndiceThom_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vR2_IndiceThom
   name: vR2 IndiceThom
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xR2_IndiceThom_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vR3_IndiceThom
   name: vR3 IndiceThom    
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xR3_IndiceThom_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vR4_IndiceThom
   name: vR4 IndiceThom
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xR4_IndiceThom_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vT_IndiceThom
   name: vT IndiceThom
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xT_IndiceThom_ID
   primary_attribute: value_sensor.value
   type: ValueSensor

      LUX Funzionale

       -
   id: vB1_LuxFunzionale
   name: vB1 LuxFunzionale  
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xB1_Lux_Funzionale_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vB2_LuxFunzionale
   name: vB2 LuxFunzionale
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xB2_Lux_Funzionale_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vCS_LuxFunzionale
   name: vCS LuxFunzionale
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xCS_Lux_Funzionale_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vH_LuxFunzionale
   name: vH LuxFunzionale    
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xH_Lux_Funzionale_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vK_LuxFunzionale
   name: vK LuxFunzionale
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xK_Lux_Funzionale_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vL_LuxFunzionale
   name: vL LuxFunzionale
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xL_Lux_Funzionale_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vR1_LuxFunzionale
   name: vR1 LuxFunzionale
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xR1_Lux_Funzionale_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vR2_LuxFunzionale
   name: vR2 LuxFunzionale
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xR2_Lux_Funzionale_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vR3_LuxFunzionale
   name: vR3 LuxFunzionale  
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xR3_Lux_Funzionale_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vR4_LuxFunzionale
   name: vR4 LuxFunzionale
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xR4_Lux_Funzionale_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vT_LuxFunzionale
   name: vT LuxFunzionale
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xT_Lux_Funzionale_ID
   primary_attribute: value_sensor.value
   type: ValueSensor

      LUX AMBIENTALE

       -
   id: vB1_LuxAmbientale
   name: vB1 LuxAmbientale  
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xB1_Lux_Ambientale_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vB2_LuxAmbientale
   name: vB2 LuxAmbientale
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xB2_Lux_Ambientale_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vCS_LuxAmbientale
   name: vCS LuxAmbientale
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xCS_Lux_Ambientale_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vH_LuxAmbientale
   name: vH LuxAmbientale    
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xH_Lux_Ambientale_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vK_LuxAmbientale
   name: vK LuxAmbientale
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xK_Lux_Ambientale_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vL_LuxAmbientale
   name: vL LuxAmbientale
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xL_Lux_Ambientale_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vR1_LuxAmbientale
   name: vR1 LuxAmbientale
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xR1_Lux_Ambientale_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vR2_LuxAmbientale
   name: vR2 LuxAmbientale
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xR2_Lux_Ambientale_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vR3_LuxAmbientale
   name: vR3 LuxAmbientale
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xR3_Lux_Ambientale_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vR4_LuxAmbientale
   name: vR4 LuxAmbientale
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xR4_Lux_Ambientale_ID
   primary_attribute: value_sensor.value
   type: ValueSensor
 -
   id: vT_LuxAmbientale
   name: vT LuxAmbientale
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: xT_Lux_Ambientale_ID
   primary_attribute: value_sensor.value
   type: ValueSensor

      State

      EnergyMode10

       -
   id: v00_EnergyMode_Biorario
   template: Binary Sensor
   name: v00 EnergyMode Biorario
 -
   id: v00_EnergyMode_Sovraccarico_Locale
   template: Binary Sensor
   name: v00 EnergyMode Sovraccarico Locale
 -
   id: v00_EnergyMode_Lavatrice_State
   name: v00 EnergyMode Lavatrice State
   template: String Sensor
   capabilities:
     string_sensor:
       attributes:
         value: 
           expr: xB1_Lavatrice_State
 -
   id: v00_EnergyMode_Oven_State
   name: v00 EnergyMode Oven State
   template: String Sensor
   capabilities:
     string_sensor:
       attributes:
         value: 
           expr: xK_Oven_State
 -
   id: v00_EnergyMode_Fridge_State
   name: v00 EnergyMode Fridge State
   template: String Sensor
   capabilities:
     string_sensor:
       attributes:
         value: 
           expr: xK_Fridge_State
 -
   id: v00_EnergyMode_Dishwasher_State
   name: v00 EnergyMode Dishwasher State
   template: String Sensor
   capabilities:
     string_sensor:
       attributes:
         value: 
           expr: xK_Dishwasher_State

      HVACMode20

      TEST100

       -
   id: testA
   template: Binary Switch
   name: TestA Binary         
 -
   id: testB
   template: Binary Switch
   name: TestB Binary        
 -
   id: testC
   template: Binary Switch
   name: TestC Binary
 -
   id: testD
   template: Binary Switch
   name: TestD Binary        
 -
   id: testE
   template: Binary Switch
   name: TestE Binary
 -
   id: testF
   template: Value Sensor
   name: TestF ValueSensor       
 -
   id: testG
   template: Value Sensor
   name: TestG ValueSensor
 -
   id: testH
   template: String Sensor
   name: TestH StringSensor
 -
   id: testI
   template: String Sensor
   name: TestI StringSensor   
 -
   id: testJ
   template: String Sensor
   name: TestJ StringSensor
 -
   id: virtual_therm
   name: Test Virtual Heating Thermostat
   capabilities:
     - hvac_control
     - hvac_heating_unit
     - temperature_sensor
   primary_attribute: hvac_control.state
 -
   id: color_dimmerA
   template: Dimmer
   name: Test Virtual Color DimmerA
   capabilities:
     - color_temperature
 -
   id: color_dimmerB
   template: Dimmer
   name: Test Virtual Color DimmerB
 -
   id: testK
   template: Binary Sensor
   name: TestK Binary
 -
   id: mode
   name: Test ModeHouse StringSensor
   template: String Sensor
   capabilities:
     string_sensor:
       attributes:
         value: 
           expr: x00_HouseMode_StartState
 -
   id: testA_dynamic_vec
   name: TestA Dynamic Vec Binary
   capabilities:
     value_sensor:
       attributes:
         value:
           expr: x00_HouseMode_StartState
   primary_attribute: string_sensor.value
   type: StringSensor
   
 -
   id: testB_dynamic_vec
   name: TestB Dynamic Vec Binary
   capabilities:
     binary_sensor:
       attributes:
         state:
           expr: 
   primary_attribute: state_sensor.value
   type: BinarySensor
 -
   id: testC_dynamic_vec
   name: TestC Dynamic Vec Binary
   capabilities:
     value_sensor:
       attributes:
         value:
           if_expr: test
 -
   id: testD_dynamic_vec
   name: TEST D Dynamic VEC
   capabilities:
     binary_sensor:
       attributes:
         state:
           expr:

      END VIRTUAL DEVICE

  • Need Testers
    N noelab

    @tunnus yes, some problem here too from the reactor log in container manager. Hope this may help too:

    2024/05/08 21:20:46	stdout	stream /var/reactor/logs/reactor.log not open boolean false
2024/05/08 21:20:46	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:20:46	stdout	[Reactor Log Panic] FileLogStream("/var/reactor/logs/reactor.log") error: Error [ERR_STREAM_WRITE_AFTER_END]: write after end
2024/05/08 21:20:46	stdout	/var/reactor/logs/reactor.log size hit rotation limit, rotating
2024/05/08 21:20:46	stdout	[userauth-24120]2024-05-08T19:20:46.401Z <Timer:null> Timer#rule-lq5rhax4 just a note: I'm setting a delay of only 7ms (from 1715196046401<5/8/2024, 9:20:46 PM> to 1715196046408<5/8/2024, 9:20:46 PM>)
2024/05/08 21:20:45	stdout	[userauth-24120]2024-05-08T19:20:45.347Z <Timer:null> Timer#rule-lq1iq5i3 just a note: I'm setting a delay of only 8ms (from 1715196045347<5/8/2024, 9:20:45 PM> to 1715196045355<5/8/2024, 9:20:45 PM>)
2024/05/08 21:20:42	stdout	[userauth-24120]2024-05-08T19:20:42.093Z <Timer:null> Timer#rule-lq5ri09p just a note: I'm setting a delay of only 8ms (from 1715196042093<5/8/2024, 9:20:42 PM> to 1715196042101<5/8/2024, 9:20:42 PM>)
2024/05/08 21:19:04	stdout	[userauth-24120]2024-05-08T19:19:04.547Z <Timer:null> Timer#rule-lq5rgx5t just a note: I'm setting a delay of only 8ms (from 1715195944547<5/8/2024, 9:19:04 PM> to 1715195944555<5/8/2024, 9:19:04 PM>)
2024/05/08 21:19:02	stdout	[userauth-24120]2024-05-08T19:19:02.765Z <Timer:null> Timer#rule-lq5rhvua just a note: I'm setting a delay of only 8ms (from 1715195942765<5/8/2024, 9:19:02 PM> to 1715195942773<5/8/2024, 9:19:02 PM>)
2024/05/08 21:19:02	stdout	[userauth-24120]2024-05-08T19:19:02.153Z <EzloController:null> remapped item action to [Object]{ "item": "switch", "value": true, "method": "hub.item.value.set", "parameters": { "value": { "value": true } } }
2024/05/08 21:19:01	stdout	[userauth-24120]2024-05-08T19:19:01.110Z <Timer:null> Timer#rule-lq5qgdau just a note: I'm setting a delay of only 8ms (from 1715195941110<5/8/2024, 9:19:01 PM> to 1715195941118<5/8/2024, 9:19:01 PM>)
2024/05/08 21:18:59	stdout	[userauth-24120]2024-05-08T19:18:59.226Z <Timer:null> Timer#rule-lq5rh750 just a note: I'm setting a delay of only 8ms (from 1715195939226<5/8/2024, 9:18:59 PM> to 1715195939234<5/8/2024, 9:18:59 PM>)
2024/05/08 21:17:10	stdout	[userauth-24120]2024-05-08T19:17:10.678Z <Timer:null> Timer#rule-lq5rhax4 just a note: I'm setting a delay of only 8ms (from 1715195830678<5/8/2024, 9:17:10 PM> to 1715195830686<5/8/2024, 9:17:10 PM>)
2024/05/08 21:14:44	stdout	[userauth-24120]2024-05-08T19:14:44.540Z <Timer:null> Timer#rule-lq5rh750 just a note: I'm setting a delay of only 8ms (from 1715195684540<5/8/2024, 9:14:44 PM> to 1715195684548<5/8/2024, 9:14:44 PM>)
2024/05/08 21:09:18	stdout	[userauth-24120]2024-05-08T19:09:18.150Z <Timer:null> Timer#rule-lq5rhax4 just a note: I'm setting a delay of only 8ms (from 1715195358150<5/8/2024, 9:09:18 PM> to 1715195358158<5/8/2024, 9:09:18 PM>)
2024/05/08 21:05:44	stdout	[userauth-24120]2024-05-08T19:05:44.738Z <Timer:null> Timer#rule-ks56ms0b just a note: I'm setting a delay of only 8ms (from 1715195144738<5/8/2024, 9:05:44 PM> to 1715195144746<5/8/2024, 9:05:44 PM>)
2024/05/08 21:05:44	stdout	[userauth-24120]2024-05-08T19:05:44.719Z <Timer:null> Timer#rule-lq5rh750 just a note: I'm setting a delay of only 8ms (from 1715195144719<5/8/2024, 9:05:44 PM> to 1715195144727<5/8/2024, 9:05:44 PM>)
2024/05/08 21:00:16	stdout	stream /var/reactor/logs/reactor.log not open boolean false
2024/05/08 21:00:14	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	[Reactor Log Panic] FileLogStream("/var/reactor/logs/reactor.log") error: Error [ERR_STREAM_WRITE_AFTER_END]: write after end
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 21:00:12	stdout	/var/reactor/logs/reactor.log size hit rotation limit, rotating
2024/05/08 20:59:52	stdout	[userauth-24120]2024-05-08T18:59:52.886Z <Timer:null> Timer#rule-lq5rhax4 just a note: I'm setting a delay of only 8ms (from 1715194792886<5/8/2024, 8:59:52 PM> to 1715194792894<5/8/2024, 8:59:52 PM>)
2024/05/08 20:58:22	stdout	[userauth-24120]2024-05-08T18:58:22.585Z <Timer:null> Timer#rule-lq5rh750 just a note: I'm setting a delay of only 8ms (from 1715194702585<5/8/2024, 8:58:22 PM> to 1715194702593<5/8/2024, 8:58:22 PM>)
2024/05/08 20:56:26	stdout	[userauth-24120]2024-05-08T18:56:26.917Z <Timer:null> Timer#rule-lq5rh1ns just a note: I'm setting a delay of only 8ms (from 1715194586917<5/8/2024, 8:56:26 PM> to 1715194586925<5/8/2024, 8:56:26 PM>)
2024/05/08 20:56:06	stdout	[userauth-24120]2024-05-08T18:56:06.581Z <Timer:null> Timer#rule-lq1iq5i3 just a note: I'm setting a delay of only 8ms (from 1715194566581<5/8/2024, 8:56:06 PM> to 1715194566589<5/8/2024, 8:56:06 PM>)
2024/05/08 20:54:49	stdout	[userauth-24120]2024-05-08T18:54:49.514Z <Timer:null> Timer#rule-lq5rgx5t just a note: I'm setting a delay of only 8ms (from 1715194489514<5/8/2024, 8:54:49 PM> to 1715194489522<5/8/2024, 8:54:49 PM>)
2024/05/08 20:54:49	stdout	[userauth-24120]2024-05-08T18:54:49.058Z <Timer:null> Timer#rule-lq5qgdau just a note: I'm setting a delay of only 8ms (from 1715194489058<5/8/2024, 8:54:49 PM> to 1715194489066<5/8/2024, 8:54:49 PM>)
2024/05/08 20:54:43	stdout	[userauth-24120]2024-05-08T18:54:43.027Z <Timer:null> Timer#rule-lq5qgdau just a note: I'm setting a delay of only 8ms (from 1715194483027<5/8/2024, 8:54:43 PM> to 1715194483035<5/8/2024, 8:54:43 PM>)
2024/05/08 20:50:44	stdout	[userauth-24120]2024-05-08T18:50:44.225Z <Timer:null> Timer#rule-lq5rh750 just a note: I'm setting a delay of only 8ms (from 1715194244225<5/8/2024, 8:50:44 PM> to 1715194244233<5/8/2024, 8:50:44 PM>)
2024/05/08 20:50:43	stdout	[userauth-24120]2024-05-08T18:50:43.256Z <EzloController:null> remapped item action to [Object]{ "item": "dimmer", "value_expr": "min(100,max(0,floor(parameters.level*100+0.5)))", "method": "hub.item.value.set", "parameters": { "value": { "value_expr": "min(100,max(0,floor(parameters.level*100+0.5)))" } } }
2024/05/08 20:47:23	stdout	[userauth-24120]2024-05-08T18:47:23.713Z <Timer:null> Timer#rule-ks56ms0b just a note: I'm setting a delay of only 8ms (from 1715194043713<5/8/2024, 8:47:23 PM> to 1715194043721<5/8/2024, 8:47:23 PM>)
2024/05/08 20:47:23	stdout	[userauth-24120]2024-05-08T18:47:23.693Z <Timer:null> Timer#rule-lq5rhax4 just a note: I'm setting a delay of only 8ms (from 1715194043693<5/8/2024, 8:47:23 PM> to 1715194043701<5/8/2024, 8:47:23 PM>)
2024/05/08 20:47:22	stdout	[userauth-24120]2024-05-08T18:47:22.392Z <EzloController:null> remapped item action to [Object]{ "item": "switch", "value": false, "method": "hub.item.value.set", "parameters": { "value": { "value": false } } }
2024/05/08 20:46:10	stdout	[userauth-24120]2024-05-08T18:46:09.716Z <default:null> Module NotifyAlert v21092
2024/05/08 20:46:10	stdout	stream /var/reactor/logs/reactor.log not open boolean false
2024/05/08 20:46:10	stdout	[userauth-24120]2024-05-08T18:46:09.704Z <default:null> Module NotifyPushover v21195
2024/05/08 20:46:10	stdout	[Reactor Log Panic] FileLogStream("/var/reactor/logs/reactor.log") error: Error [ERR_STREAM_WRITE_AFTER_END]: write after end
2024/05/08 20:46:10	stdout	[Reactor Log Panic] FileLogStream("/var/reactor/logs/reactor.log") error: Error [ERR_STREAM_WRITE_AFTER_END]: write after end
2024/05/08 20:46:10	stdout	stream /var/reactor/logs/reactor.log not open boolean false
2024/05/08 20:46:10	stdout	stream /var/reactor/logs/reactor.log not open boolean false
2024/05/08 20:46:10	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 20:46:10	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 20:46:10	stdout	/var/reactor/logs/reactor.log not found; reopening stream
2024/05/08 20:46:10	stdout	/var/reactor/logs/reactor.log size hit rotation limit, rotating
2024/05/08 20:46:09	stdout	[userauth-24120]2024-05-08T18:46:09.014Z <Notifier:null> Module Notifier v22283
2024/05/08 20:46:06	stdout	    at /opt/reactor/server/lib/VirtualEntityController.js:357:319
2024/05/08 20:46:06	stdout	    at VirtualEntityController._load_devices (/opt/reactor/server/lib/VirtualEntityController.js:644:114)
2024/05/08 20:46:06	stdout	    at Entity.setPrimaryAttribute (/opt/reactor/server/lib/Entity.js:563:19)
2024/05/08 20:46:06	stdout	Error: Invalid primary attribute assignment; capability not assigned (state_sensor.value)
2024/05/08 20:46:06	stdout	[userauth-24120]2024-05-08T18:46:06.542Z <VirtualEntityController:CRIT> Error: Invalid primary attribute assignment; capability not assigned (state_sensor.value) [-]
2024/05/08 20:46:06	stdout	    at /opt/reactor/server/lib/VirtualEntityController.js:357:319
2024/05/08 20:46:06	stdout	    at VirtualEntityController._load_devices (/opt/reactor/server/lib/VirtualEntityController.js:644:114)
2024/05/08 20:46:06	stdout	    at Entity.setPrimaryAttribute (/opt/reactor/server/lib/Entity.js:563:19)
2024/05/08 20:46:06	stdout	Error: Invalid primary attribute assignment; capability not assigned (string_sensor.value)
2024/05/08 20:46:06	stdout	[userauth-24120]2024-05-08T18:46:06.541Z <VirtualEntityController:CRIT> Error: Invalid primary attribute assignment; capability not assigned (string_sensor.value) [-]
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:05.410Z <VirtualEntityController:null> Module VirtualEntityController v24117
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:05.391Z <SystemController:null> Module SystemController v24076
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:05.382Z <OWMWeatherController:null> Module OWMWeatherController v22294
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:05.161Z <EzloController:null> Module EzloController v23345
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:05.090Z <VeraController:null> Module VeraController v24050
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:05.089Z <TaskQueue:null> Module TaskQueue 24113
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:04.993Z <HassController:null> Module HassController v24115
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:04.726Z <InfluxFeed:null> Module InfluxFeed v23341
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:04.682Z <wsapi:null> Module wsapi v24115
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:04.439Z <httpapi:null> Module httpapi v24119
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:04.231Z <Engine:null> Module Engine v24113
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:04.229Z <GlobalReaction:null> Module GlobalReaction v24099
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:04.197Z <Rule:null> Module Rule v24115
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:04.176Z <AlertManager:null> Module AlertManager v24099
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:04.107Z <Predicate:null> Module Predicate v23093
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:04.045Z <GlobalExpression:null> Module GlobalExpression v24099
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:04.023Z <default:null> Module Rulesets v24099
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:04.022Z <default:null> Module Ruleset v24099
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:03.952Z <Controller:null> Module Controller v24099
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:03.929Z <Entity:null> Module Entity v24108
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:03.925Z <TimerBroker:null> Module TimerBroker v22283
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:03.460Z <Plugin:null> Module Plugin v22300
2024/05/08 20:46:05	stdout	[userauth-24120]2024-05-08T18:46:03.311Z <Capabilities:null> Module Capabilities v23331
2024/05/08 20:46:03	stdout	[userauth-24120]2024-05-08T18:46:03.269Z <Structure:null> Module Structure v24110
2024/05/08 20:46:03	stdout	[userauth-24120]2024-05-08T18:46:03.059Z <app:null> Local date/time using configured timezone and locale formatting is "5/8/2024, 8:46:03 PM"
2024/05/08 20:46:03	stdout	[userauth-24120]2024-05-08T18:46:03.058Z <app:null> Loaded locale en-US for en-US
2024/05/08 20:46:02	stdout	[userauth-24120]2024-05-08T18:46:02.890Z <app:null> Configured locale (undefined); selected locale(s) en-US.UTF-8
2024/05/08 20:46:02	stdout	[userauth-24120]2024-05-08T18:46:02.750Z <app:null> Resolved timezone=Europe/Rome, environment TZ=Europe/Rome; offset minutes from UTC=120
2024/05/08 20:46:02	stdout	[userauth-24120]2024-05-08T18:46:02.656Z <app:null> NODE_PATH=/opt/reactor:/opt/reactor/node_modules
2024/05/08 20:46:02	stdout	[userauth-24120]2024-05-08T18:46:02.656Z <app:null> Basedir /opt/reactor; data in /var/reactor/storage
2024/05/08 20:46:02	stdout	[userauth-24120]2024-05-08T18:46:02.656Z <app:null> Process ID 1 user/group 0/0; docker; platform linux/x64 #69057 SMP Fri Jan 12 17:02:28 CST 2024; locale (undefined)
2024/05/08 20:46:02	stdout	[userauth-24120]2024-05-08T18:46:02.584Z <app:null> Reactor build userauth-24120-7745fb8d starting on v20.10.0 /usr/local/bin/node
2024/05/08 20:46:02	stdout	NODE_PATH /opt/reactor:/opt/reactor/node_modules
2024/05/08 20:46:02	stdout	Reactor userauth-24120-7745fb8d app 24120 configuration from /var/reactor/config
  • Need Testers
    N noelab

    Hi, I used Portainer to change the image from latest to userauth and it was easy and thanks for this update!

    current configuration:
    Synology NAS/Docker/Reactor (Multi-hub) userauth-24120-7745fb8d

    unexpected:
    when I try to log in on http://10.0.0.1:8111/dashboard/ as admin:admin, I'm redirect to reactor http://10.0.0.1:8111/reactor/en-US/ and not to dashboard
    This happens on Chrome and Edge

    Features/suggestion that I image:

    Guest user has access to:
    all dashboard set to public (homescreen - all public group tile - all public single tile)

    where group tile are rooms/hubs/virtual/weather on homescreen dashboard
    and single tile are all the entities: devices/virtual devices/etc

    Admin can use option on tile VISIBLE/HIDDEN icon by clicking on it.

    If a tile is set to HIDDEN, all entities associated with it will also be hidden. Setting VISIBLE on specific entities will not be respected. Setting hidden on specific entities it will be not visible to guests.
    So Public means VISIBLE.

    imaging it:

    image.png

  • Need Testers
    N noelab

    @toggledbits happy to help!

    I'm running Reactor>Docker>Synology NAS

  • Virtual Entities (value or string) can auto update based on a Global variables?
    N noelab

    ops, soorry! now it is in signature too.

    Reactor (Multi-hub) latest-23338-170ea0c7
    Docker - Synology NAS

  • Virtual Entities (value or string) can auto update based on a Global variables?
    N noelab

    Thanks to you!!!
    Lines are added

    c0aebaa0-658c-441e-a120-ca769cb5a5af-image.png

    another idea for the future:
    a gauge range applied to ValueSensor or Weather in simple text color:
    RED text for value out of range min/max

  • Virtual Entities (value or string) can auto update based on a Global variables?
    N noelab

    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)

    f5870887-9ee3-4687-8261-e09ed14ecb26-image.png

    reactor.yaml

            -
          id: testA_dynamic_vec
          name: TestA Dynamic Vec Value
          capabilities:
            value_sensor:
              attributes:
                value:
                  expr: xB1_IndiceThom_ID

    dashboard
    c677f4b8-727f-42a0-9c4d-60020783fb43-image.png

  • Virtual Entities (value or string) can auto update based on a Global variables?
    N noelab

    @toggledbits

    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

    388644a6-2698-4fae-b28f-58abd4aff25c-image.png

    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

    cfb59b79-4156-4cf4-91f5-8afe949c1471-image.png

  • Virtual Entities (value or string) can auto update based on a Global variables?
    N noelab

    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

  • Dashboard extended to guests with visible/hidden icons - an idea?
    N noelab

    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

  • Ezlo Controller - Error Incompatible serialization data - api cloud Timeout
    N 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!

  • Ezlo Controller - Error Incompatible serialization data - api cloud Timeout
    N 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"
  • Ezlo Controller - Error Incompatible serialization data - api cloud Timeout
    N 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)
  • Plugin - InfluxDB 2- RequestTimedOutError: Request timed out
    N noelab

    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

  • Power_switch.state - no change state - EzloPlus - Msr v. 21351-a3aef - Synology Docker
    N noelab

    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
  • Power_switch.state - no change state - EzloPlus - Msr v. 21351-a3aef - Synology Docker
    N noelab

    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
  • Power_switch.state - no change state - EzloPlus - Msr v. 21351-a3aef - Synology Docker
    N noelab

    eheh, I was hoping to go happy to sleep 🙂 Yes, they diverge:

    ![alt text](c32f3243-5ef7-48d4-a5e9-ef1b5d72df08-image.png image url)

  • Power_switch.state - no change state - EzloPlus - Msr v. 21351-a3aef - Synology Docker
    N noelab

    Now seems ok, no error in the log. It was related to Google Chrome. Thanks!

    ![alt text](28e558ac-598b-4063-b0f7-eb96de2f993c-image.png image url)

  • Login
  • Don't have an account? Register
  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved