I'm running MSR build 25139 on Docker, using MQTT controller 24293, and everything working as expected. But if I try to upgrade to MQTTController build 25139, I'm getting the following errors on MSR UI:
An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.god
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa auto heating off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.green
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa filter pump auto off" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute temperature_sensor.red
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa filter pump auto run" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.pump
Last 11:20:37
An Entity Attribute condition in "Lay-Z-Spa watchdog" (Terrace) failed because the referenced entity "Lay-Z-Spa States" (mqtt>layzspa_states) does not have attribute value_sensor.status
Last 11:20:37
My MQTT configuration (local_mqtt_devices.yaml) for the related entity is:
layzspa_message:
type: ValueSensor
capabilities: ["temperature_sensor", "value_sensor", "power_sensor"]
primary_attribute: power_sensor.value
events:
"layzspa/message":
"power_sensor.value":
json_payload: true
if_expr: '! isnull( payload?.PWR )'
expr: "float(payload.PWR)"
"value_sensor.air":
json_payload: true
if_expr: '! isnull( payload?.AIR )'
expr: "float(payload.AIR)"
"value_sensor.pump":
json_payload: true
if_expr: '! isnull( payload?.FLT )'
expr: "float(payload.FLT)"
"value_sensor.god":
json_payload: true
if_expr: '! isnull( payload?.GOD )'
expr: "float(payload.GOD)"
"value_sensor.lock":
json_payload: true
if_expr: '! isnull( payload?.LCK )'
expr: "float(payload.LCK)"
"value_sensor.unit":
json_payload: true
if_expr: '! isnull( payload?.UNT )'
expr: "float(payload.UNT)"
"value_sensor.error":
json_payload: true
if_expr: '! isnull( payload?.ERR )'
expr: "float(payload.ERR)"
"temperature_sensor.green":
json_payload: true
if_expr: '! isnull( payload?.GRN )'
expr: "float(payload.GRN)"
"temperature_sensor.red":
json_payload: true
if_expr: '! isnull( payload?.RED )'
expr: "float(payload.RED)"
"temperature_sensor.target":
json_payload: true
if_expr: '! isnull( payload?.TGT )'
expr: "float(payload.TGT)"
"temperature_sensor.value":
json_payload: true
if_expr: '! isnull( payload?.TMP )'
expr: "float(payload.TMP)"
"temperature_sensor.virtual":
json_payload: true
if_expr: '! isnull( payload?.VTM )'
expr: "round(float(payload.VTM), 1)"
"temperature_sensor.ambient":
json_payload: true
if_expr: '! isnull( payload?.AMB )'
expr: "float(payload.AMB)"
"layzspa/Status":
"value_sensor.status":
if_expr: '! isnull( payload )'
expr: "payload"
"layzspa/button":
"value_sensor.button":
if_expr: '! isnull( payload )'
expr: "payload"
and in reactor.yaml I have:
"layzspa_states":
name: "Lay-Z-Spa States"
friendly_name: 'Lay-Z-Spa States'
include: layzspa_message
I realize my MQTT configuration might be a bit unorthodox, but could there still be something unintentional in the latest MQTTController build? If needed, I can provide detailed logs.
Since today is my birthday - and I still pretend to be unconventional - I'm giving away a present to this wonderful community and I'm releasing my first OpenSprinkler controller for MSR. It was real fun to code it - and while it's still WIP, it seems to work OK for me. It's polling-based at the moment, but I'll add support for updates via MQTT very soon (it's already partially coded).
Get it at (install is similar to MQTTController and such):
https://github.com/dbochicchio/reactor-opensprinkler
Feel free to try it. It's beta software, but it's stable. I'll update it weekly until all the tasks from my todo list are empty.
Since I've learnt a lot from this controller, I'll explore new controllers soon.
Good day all,
I'm in the process of trying to shut down my 10 year old Linux home server that served many purposes, but primarily it's what I used for my NAS/Plex Media server. I migrated the NAS aspect of the server in November of last year to a true NAS solution (Ubiquti UNAS Pro), which is rack mount and much more efficient than my old tower, which it's only side benefit was heating my home office during the winter. Unfortunately it also means heating my home office during the summer, which were about to be in full swing.
I have two things running on this 10 year old server at this point. MSR and pi-hole. I'm running Plex Media Server on Fedora Workstation in Podman on mini PC, which is much more energy efficient than my old tower. My next step is to migrate MSR. I know there are images of MSR out there, and creating it is well documented. I'm going to be using Podman instead of Docker for various reasons, but they work very similar. What I don't know, is what I need to do to migrate my existing Bare Metal installation over to a container.
Has anyone done this? Any advice?
Build 21228 has been released. Docker images available from DockerHub as usual, and bare-metal packages here.
Home Assistant up to version 2021.8.6 supported; the online version of the manual will now state the current supported versions;
Fix an error in OWMWeatherController that could cause it to stop updating;
Unify the approach to entity filtering on all hub interface classes (controllers); this works for device entities only; it may be extended to other entities later;
Improve error detail in messages for EzloController during auth phase;
Add isRuleSet() and isRuleEnabled() functions to expressions extensions;
Implement set action for lock and passage capabilities (makes them more easily scriptable in some cases);
Fix a place in the UI where 24-hour time was not being displayed.
Hi guys,
Just wondering how you guys organize your rule sets and rules. I wish I had an extra layer to have some more granularity, but my feature request was not popular.
Maybe there are better ways to organize my rule sets.
I use the rule sets now primarily for rooms. So a rule set per room. But maybe grouping by functionality works better. Any examples/ suggestions would be appreciated.
I have the following yaml configuration in local_mqtt_devices file
x_mqtt_device:
set_speed:
arguments:
speed:
type: str
topic: "command/%friendly_name%"
payload:
type: json
expr: '{ "fan": parameters.speed }'
While this works fine, I'm wondering how this could be changed to "fixed" parameters, as in this case "fan" only accepts "A", "Q" or a numeric value of 1-5?
Hi!
I get this message when I'm on the status tab:
System Configuration Check
The time on this system and on the Reactor host are significantly different. This may be due to incorrect system configuration on either or both. Please check the configuration of both systems. The host reports 2025-04-01T15:29:29.252Z; browser reports 2025-04-01T15:29:40.528Z; difference 11.276 seconds.
I have MSR installed as a docker on my Home Assistant Blue / Hardkernel ODROID-N2/N2+. MSR version is latest-25082-3c348de6.
HA versions are:
Core 2025.3.4
Supervisor 2025.03.4
Operating System 15.1
I have restarted HA as well as MSR multiple times. This message didn´t show two weeks ago. Don´t know if it have anything to do with the latest MSR version.
Do anyone know what I can try?
Thanks in advance!
Let's Be Careful Out There (Hill Street reference...)
/Fanan
I have a very strange situation, where if InfluxDB restarts, other containers may fail when restarting at the same time (under not easy to understand circumstances), and InfluxDB remains unreachable (and these containers crashes). I need to reboot these containers in an exact order, after rebooting InfluxDB.
While I understand what's going on, I need a way to reliable determine that InfluxDB is not reachable and these containers are not reachable, in order to identify this situation and manually check what's going on - and, maybe, in the future, automatically restart them if needed.
So, I was looking at HTTP Request action, but I need to capture the HTTP response code, instead of the response (becase if ping is OK, InfluxDB will reply with a 204), and, potentially, a way to programmatically detect that it's failing to get the response.
While I could write a custom HTTP controller for this or a custom HTTP virtual device, I was wondering if this is somewhat on you roadmap @toggledbits
Thanks!
Hi ,
I'm on
-Reactor (Multi-hub) latest-25067-62e21a2d
-Docker on Synology NAS
-ZWaveJSUI 9.31.0.6c80945
Problem with ZwaveJSUI:
When I try to change color to a bulb RGBWW, it doesn't change to the RGB color and the bulb remains warm or cold white.
I tryed with Zipato RGBW Bulb V2 RGBWE2, Hank Bulb HKZW-RGB01, Aentec 6 A-ZWA002, so seems that it happens with all RGBWW bulb with reactor/zwavejsui.
I'm using from reator the entity action: "rgb_color.set" and "rgb_color.set_rgb".
After I send the reactor command, It changes in zwavejsui the rgb settings but doesn't put the white channel to "0", so the prevalent channel remains warm/cold White and the bulb doesn't change into the rgb color.
This is the status of the bulb in zwavejsui after "rgb_color.set" (235,33,33,) and the bulb is still warmWhite.
x_zwave_values.Color_Switch_currentColor={"warmWhite":204,"coldWhite":0,"red":235,"green":33,"blue":33}
The "cold white" and "warm white" settings interfer with the rgb color settings.
Reactor can change bulb colors with rgb_color set — (value, ui8, 0x000000 to 0xffffff) or rgb_color set_rgb — (red, green, blue, all ui1, 0 to 255) but if warm or cold white
are not to "0", zwavejsui doesn't change them and I can't find a way to change into rgb or from rgb back to warm white.
So if I use from reactor: rgb_color set_rgb — (235,33,33) in zwavejsui I have
x_zwave_values.Color_Switch_targetColor={"red":235,"green":33,"blue":33}
14/03/2025, 16:43:57 - value updated
Arg 0:
└─commandClassName: Color Switch
└─commandClass: 51
└─property: targetColor
└─endpoint: 0
└─newValue
└──red: 235
└──green: 33
└──blue: 33
└─prevValue
└──red: 235
└──green: 33
└──blue: 33
└─propertyName: targetColor
14/03/2025, 16:43:57 - value updated
Arg 0:
└─commandClassName: Color Switch
└─commandClass: 51
└─property: currentColor
└─endpoint: 0
└─newValue
└──warmWhite: 204
└──coldWhite: 0
└──red: 235
└──green: 33
└──blue: 33
└─prevValue
└──warmWhite: 204
└──coldWhite: 0
└──red: 235
└──green: 33
└──blue: 33
└─propertyName: currentColor
In zwavejsui, the bulb changes rgb set but warm White remains to "204" and the bulb remais on warm White channel bacause is prevalent on rgb set.
x_zwave_values.Color_Switch_currentColor_0=204
x_zwave_values.Color_Switch_currentColor_1=0
x_zwave_values.Color_Switch_currentColor_2=235
x_zwave_values.Color_Switch_currentColor_3=33
x_zwave_values.Color_Switch_currentColor_4=33
Is it possible to targetColor also for "warmWhite" and "coldWhite" and have something similar to this?
x_zwave_values.Color_Switch_targetColor={"warmWhite":0,"coldWhite":0,"red":235,"green":33,"blue":33}
Thanks in advance.
MSR had been running fine, but I decided to follow the message to upgrade to 25067. Since the upgrade, I have received the message "Controller "<name>" (HubitatController hubitat2) could not be loaded at startup. Its ID is not unique." MSR throws the message on every restart. Has anyone else encountered this problem?
I am running MSR on a Raspberry Pi4 connecting to two Hubitat units over an OpenVPN tunnel. One C8 and a C8 Pro. Both are up-to-date. It appears that despite the error message that MSR may be operating properly.
Need Testers
-
@gwp1 said in Need Testers:
Logged in as the default admin
When you reload the page, do you get any similar errors, specifically for /api/v1/systime? Is the time display in the page header correct (showing both host and browser times)?
@toggledbits no errors for /api/v1/systime and the browser time and system time are identical, perhaps a split second apart as they tick by.
-
@therealdb the fixed build I just put up (to include the missing HTML file) also includes a potential fix for VirtualEntityController to preserve attributes across upgrades. Let's see how it works out.
@toggledbits yep, it's working beautifully
time to delete some junky code I wrote for the occasion 
I'll play with AuthN&AuthZ on May 1st, since it's a public holiday here in Italy and rain is forecast.
--
On a mission to automate everything. -
@toggledbits yep, it's working beautifully
time to delete some junky code I wrote for the occasion I'll play with AuthN&AuthZ on May 1st, since it's a public holiday here in Italy and rain is forecast.
@therealdb said in Need Testers:
yep, it's working beautifully
Outstanding. I can apply the same type of fix to MQTTController, so I'll do that.
-
@toggledbits I have not done that yet. One step at a time
The Not found issue has been resolved with your latest build and Access Control is WAE. The Reactionsissue I noted has also not reappeared.I have noticed that the
TOOLS>Restart Reactorbutton does not work and I see nothing in the logs whatsoever even after "elevator button-ing" it (press press press press press press press).@toggledbits I have finally finished up the SSL and am getting this from my local browser:
Going to spin this off into it's own thread.
-
Build 24120
- Mostly code cleanup and tightening around application restriction.
- Should fix Tools > Restart Reactor issue
-
Not hearing a lot of grumbling, which is a Good Thing so far. Any and all feedback welcome. Please comment on the docs, too, if you have anything. On my end, I'm out of things to do on this feature, nothing to add, so I'm just waiting for fixing/tweaking.
-
@toggledbits thanks for this feature! I sort of had to volunteer as a tester as I originally did a feature request for authentication support...
Anyway, seems to work nicely, although only about an hour of testing behind. Will keep you posted if anything unexpected comes up. You could update docs though:
"1. Copy the template users.yaml-dist from the dist-config distribution directory to your config directory."
--> "1. Copy the template users.yaml-dist from the /opt/reactor/dist-config distribution directory to your config directory. Rename it as users.yaml file."
(at least for me as a Docker user it wasn't immediately clear where to find this template)
Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT
-
@toggledbits thanks for this feature! I sort of had to volunteer as a tester as I originally did a feature request for authentication support...
Anyway, seems to work nicely, although only about an hour of testing behind. Will keep you posted if anything unexpected comes up. You could update docs though:
"1. Copy the template users.yaml-dist from the dist-config distribution directory to your config directory."
--> "1. Copy the template users.yaml-dist from the /opt/reactor/dist-config distribution directory to your config directory. Rename it as users.yaml file."
(at least for me as a Docker user it wasn't immediately clear where to find this template)
-
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-7745fb8dunexpected:
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 EdgeFeatures/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/etcAdmin 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:
-
Not sure if others are experiencing the same, but with this build (userauth-24120-7745fb8d) if I go to Manual (i.e. http://reactor-ip:8111/docs/), it takes a very long time before search can be used as it stays in "initializing search" state. At least I haven't noticed the same with earlier releases. Browser is Chrome.
-
@toggledbits another thing noticed with this build is that deleting global reactions does not work.
How to reproduce:
- create reaction
- delete it
- refresh browser
- reaction is back...
Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT
-
@toggledbits another thing noticed with this build is that deleting global reactions does not work.
How to reproduce:
- create reaction
- delete it
- refresh browser
- reaction is back...
@tunnus said in Need Testers:
noticed with this build is that deleting global reactions does not work.
I see it. It's also happening to latest-24115. I've got it fixed on my end and will roll a build on Sunday.
@noelab said in Need Testers:
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
I think I've got that nailed down as well. Look for Sunday's build.
@Pabla said in Need Testers:
Yes this would be a good improvement to the docs
I think better still, have Reactor docker containers copy
dist-configto your data directory (asdist-config, not overwriting any existing real config), so no special steps are needed to find those files, they are just there. Sunday's build.Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
-
Not sure if others are experiencing the same, but with this build (userauth-24120-7745fb8d) if I go to Manual (i.e. http://reactor-ip:8111/docs/), it takes a very long time before search can be used as it stays in "initializing search" state. At least I haven't noticed the same with earlier releases. Browser is Chrome.
@tunnus said in Need Testers:
Not sure if others are experiencing the same, but with this build (userauth-24120-7745fb8d) if I go to Manual (i.e. http://reactor-ip:8111/docs/), it takes a very long time before search can be used as it stays in "initializing search" state. At least I haven't noticed the same with earlier releases. Browser is Chrome.
Anyone else noticed this? @noelab, @Pabla? Other thing I found out today was that there's some kind of a log problem going on, Docker logs claim that reactor.log file cannot be found:
2024/05/11 21:48:36 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/11 21:48:32 stdout [Reactor Log Panic] FileLogStream("/var/reactor/logs/reactor.log") error: Error [ERR_STREAM_WRITE_AFTER_END]: write after end 2024/05/11 21:48:32 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/11 21:48:32 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:48:32 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:48:32 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:48:32 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:48:32 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:48:32 stdout /var/reactor/logs/reactor.log size hit rotation limit, rotating 2024/05/11 21:48:09 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/11 21:48:08 stdout [Reactor Log Panic] FileLogStream("/var/reactor/logs/reactor.log") error: Error [ERR_STREAM_WRITE_AFTER_END]: write after end 2024/05/11 21:48:08 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/11 21:48:08 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:48:08 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:48:08 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:48:08 stdout /var/reactor/logs/reactor.log size hit rotation limit, rotating 2024/05/11 21:46:50 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/11 21:46:45 stdout [Reactor Log Panic] FileLogStream("/var/reactor/logs/reactor.log") error: Error [ERR_STREAM_WRITE_AFTER_END]: write after end 2024/05/11 21:46:45 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening streamBut reactor.log file seems to in place when checked via terminal:
Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8, Zigbee2MQTT
-
@tunnus said in Need Testers:
Not sure if others are experiencing the same, but with this build (userauth-24120-7745fb8d) if I go to Manual (i.e. http://reactor-ip:8111/docs/), it takes a very long time before search can be used as it stays in "initializing search" state. At least I haven't noticed the same with earlier releases. Browser is Chrome.
Anyone else noticed this? @noelab, @Pabla? Other thing I found out today was that there's some kind of a log problem going on, Docker logs claim that reactor.log file cannot be found:
2024/05/11 21:48:36 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/11 21:48:32 stdout [Reactor Log Panic] FileLogStream("/var/reactor/logs/reactor.log") error: Error [ERR_STREAM_WRITE_AFTER_END]: write after end 2024/05/11 21:48:32 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/11 21:48:32 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:48:32 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:48:32 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:48:32 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:48:32 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:48:32 stdout /var/reactor/logs/reactor.log size hit rotation limit, rotating 2024/05/11 21:48:09 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/11 21:48:08 stdout [Reactor Log Panic] FileLogStream("/var/reactor/logs/reactor.log") error: Error [ERR_STREAM_WRITE_AFTER_END]: write after end 2024/05/11 21:48:08 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/11 21:48:08 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:48:08 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:48:08 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:48:08 stdout /var/reactor/logs/reactor.log size hit rotation limit, rotating 2024/05/11 21:46:50 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/11 21:46:45 stdout [Reactor Log Panic] FileLogStream("/var/reactor/logs/reactor.log") error: Error [ERR_STREAM_WRITE_AFTER_END]: write after end 2024/05/11 21:46:45 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening stream 2024/05/11 21:46:45 stdout /var/reactor/logs/reactor.log not found; reopening streamBut reactor.log file seems to in place when checked via terminal:
@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 [33mfalse[39m 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 [33mfalse[39m 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 [33mfalse[39m 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 [33mfalse[39m 2024/05/08 20:46:10 stdout stream /var/reactor/logs/reactor.log not open boolean [33mfalse[39m 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 [33m24120[39m configuration from /var/reactor/config -
It looks like you may have a misconfiguration in your VirtualEntityController config. Can you post the config section for that?
-
It looks like you may have a misconfiguration in your VirtualEntityController config. Can you post the config section for that?
@toggledbits
some devices are created for test purpose so maybe there are errorscode_text-
id: virtual
name: VEC
implementation: VirtualEntityController
enabled: true
config:
entities:HomeMode
- id: v00_Automation template: Binary Sensor name: v00 Automation ModeIndici 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: ValueSensorIndiceThom
- 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: ValueSensorLUX 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: ValueSensorLUX 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: ValueSensorState
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_StateHVACMode20
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
-Reactor (Multi-hub) 25082-3c348de6
-Docker on Synology NAS
-Ezlo firmware version 2.0.59.2471.8
-HASS Docker 2025.2.5
-ZWaveJSUI 10.1.3
-Update 30/03/2025 -
-
@toggledbits
some devices are created for test purpose so maybe there are errorscode_text-
id: virtual
name: VEC
implementation: VirtualEntityController
enabled: true
config:
entities:HomeMode
- id: v00_Automation template: Binary Sensor name: v00 Automation ModeIndici 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: ValueSensorIndiceThom
- 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: ValueSensorLUX 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: ValueSensorLUX 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: ValueSensorState
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_StateHVACMode20
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
@noelab said in Need Testers:
- id: testB_dynamic_vec
name: TestB Dynamic Vec Binary
capabilities:
binary_sensor:
attributes:
state:
expr:
primary_attribute: state_sensor.value
type: BinarySensor
In this config, you are declaring
binary_sensoras a capability, but then trying to set the primary attribute tostate_sensor.value-- the capabilitystate_sensoris not a Reactor-defined capability. That should be corrected.I have other changes coming today to help examine the timer complaints. The logging issue seems like it should be more rare -- it's a race condition in the asynchronous writing of streams. I expect to see this messages occasionally, rarely (as I said), but in runs like you are getting is not cool, but I think it's induced by the timer complaint. Stay tuned.
Also, @noelab and @tunnus the log snippets you posted look heavily filtered. That removes important context, so please don't do that. I'd rather see one error message with full context than 20 with none.
-
-
Build 24133 userauth
- Force logging to be synchronous, to work around many long-standing issues with the naturally asynchronous nature of nodejs streams.
- Enhance diagnostic reporting for short timers (temporarily, in this branch only).
- Fix some issues with post-login redirection (if you were pushed to the login page by the dashboard or admin UI).
- VirtualEntityController: preserve attribute values if possible across system updates that affect capability definitions or implementations.
- DynamicGroupController: it is now possible to set the primary attribute of a dynamic group, and determine its value dynamically. Trivial example: add the
binary_sensor.stateattribute to a group to show true when any light in the group is on. Refer to the docs for DynamicGroupController. - The
dist-configdirectory is now copied to the user data virtual path target when running in docker containers so that its contents are more easily accessible to docker users. - Fixed an issue in the core related to deleting certain objects (a Global Reaction was reported, but could have been many object types).
- Dashboard: further improvements to widget type guessing if we're not told by the entity configuration.
- Bring
dist-configversion ofusers.yamlinto line with current reality. - Fix the
rpi-status.shtool to work better with HTTPS enabled. - HassController: Bless Hass to 2024.5.2
Note that this build incorporates all changes for
userauthas well aslatestbranch changes not yet deployed for everyone else.Author of Multi-system Reactor and Reactor, DelayLight, Switchboard, and about a dozen other plugins that run on Vera and openLuup.
