I've managed to use MSR UI on iOS devices to some degree*, so that although UI elements (e.g. rule sets) are not visible in portrait mode, you've seen them in landscape. Now with recents builds (24302) this does not work anymore, elements (rule sets, entities) are not anymore visible in landscape mode.
Does anyone have similar experiences? Using iOS 18 and Safari/Chrome browser.
( *Drag & drop of rule conditions have never worked on a mobile)
Hi @toggledbits,
I have lots of logs with this:
<Engine:ERR> Assignment to alarm ignored -- expression-driven global cannot be set by assignmentAny hints to where look at to avoid this? Thanks.
Hi @toggledbits
I'd like to update my controllers with these new features, but I'm struggling to find any guidance in the docs - and in general to understand the context.
Could you please elaborate more? Thanks.
I have the following ACL defined:
groups: admin: users: - admin applications: true api_acls: # This ACL allows users in the "admin" group to access the API - url: "/api" group: admin allow: true log: true # This ACL allows anyone/thing to access the /api/v1/alive API endpoint - url: "/api/v1/alive" allow: trueAnd I have authenticated to MSR as "admin" user. However, I'm getting "access denied" when trying to access http://*******:8111/api/v1/log
So what I'm missing, is my ACL incorrectly defined?
Using build 24302 on Docker.
Thanks to @toggledbits for adding a custom CSS. I've started doing a darker Reactor style.
Here's the file: https://gist.github.com/dbochicchio/825098ac13b7f8cac22012eae37ff7ce
A couple of things are still too bright and I'll eventually catch-up. Just place it under your /config directory, naming the file as customstyles.css. Hard refresh your browser.
Hi!
In Home Assistant I sometimes uses the TTS, either to my Sonos or Google speakers. With reactor in Vera I also use TTS.
But in MSR I can't select the TTS-service. It's simply not there. Am I missing something, or is this the case, so far?
Thanks!
/Fanan
Hi
I have just connected a bunch of EzloPi controllers to MSR to import some ESP based devices etc.
They all seemed to have worked and imported in to MSR apart from I have one missing device. It is a Digital Gas Sensor device.
This is how that device looks in the Ezlo API.
Devices Info:
_id: "10696001" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "level_sensor" subcategory: "" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Digital" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"Items Info:
_id: "20696001" deviceId: "10696001" hasGetter: true hasSetter: false name: "smoke_density" show: true valueType: "substance_amount" scale: "parts_per_million" value: 2.7472610473632812 valueFormatted: "2.75" status: "idle"There is also an Analog Gas sensor that one did import in to MSR OK.
68d63dab-b871-4f44-912b-cf6e0b9eb4c6-image.png
Devices Info:
_id: "10696000" deviceTypeId: "ezlopi" parentDeviceId: "10696000" category: "security_sensor" subcategory: "gas" gatewayId: "457a5069" batteryPowered: false name: "Gas Sensor Analog" type: "sensor" reachable: true persistent: true serviceNotification: false armed: false roomId: "" security: "no" ready: true status: "idle" parentRoom: true protectConfig: "default"Items Info:
_id: "20696000" deviceId: "10696000" hasGetter: true hasSetter: false name: "gas_alarm" show: true valueType: "token" enum: 0: "no_gas" 1: "combustible_gas_detected" 2: "toxic_gas_detected" 3: "unknown" valueFormatted: "no_gas" value: "no_gas" status: "idle"And this is how this MQ2 Gas Sensor looks like on their dashboard:
Digital
cb77dfa3-4af5-4d06-9635-89207a716a89-image.png
Analog
4fb4da1b-e946-4b89-876c-bcd9f5699b6c-image.png
They have an EzloPi website here you can create your own sensor projects using ESP boards, which is very interesting stuff!
And I just wrote on the Ezlo forum here, how to connect an EzloPi controller to MSR.
THANKS.
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.A couple of things for you @toggledbits, since you mentioned that this release has new features and some tweaks are expected.
Local expressions cannot be deleted. Pushing the X button has no effect for me.
When cloning an entity action, the result is strange (first is cloned one, second is the original action):
a92ea094-9e2c-4aaa-bf47-2d07a6ffdbd0-image.png
When changing the action on the cloned element, the params are added to the original one. See screenshot:
92ac3011-83c8-466b-bd23-47d483ad7a52-image.png
Dark theme has a couple of strange contrasts. One is visible in the previous screenshots (white text on yellow background). Another one is in groups (blue text on blue background):
9b3c4988-53ef-44e6-9672-30e744cacb75-image.png
Overall, I found blue, yellow, red and green (in buttons and forms) to be too bright.
On the bright side:
I love the new script action: thank you! The dark theme is a great start to avoid getting blinded at night I promise I'll try very soon the new features around actions. Thanks!@toggledbits
I just upgraded to version MSR 24293, bare metal running on Fedora. Upon restart, I am getting a error banner:
I followed the new directions about npm
npm i --no-save --no-package-lock --omit dev
Any idea what the issue is?
Seems like switching the UI to the newly added dark mode (thank you for this) does nothing. The UI stays in light mode and only a few buttons turn into dark mode (see screenshot)
Things I have tried:
Hard refresh
Different browser
Different computer
Restarting Reactor
Failed troubleshooting attempts:
No errors in Chrome console
No relevant errors in Reactor log (can still PM the full log file)
Reactor version: latest-24293-ea42a81d
Hardware: Odroid N2+
Linux version: Ubuntu 24.04.1 LTS
3df2806f-9146-485b-9ec1-d056e91cefe5-image.png Dark mode enabled
ff823023-c079-4684-b01f-d6ac6527d31a-image.png Light mode enabled
Good morning,
I have a service MQTT service that needs a restart occasionally. The add-on (Smartbed MQTT) is for the smart bed base for my bed. It has a "safety light" that I can control from HAAS & MSR as a light entity, and also moves the head of the bed to a preset at bedtime, and then lies it back flat in the morning The problem is, from time to time, the light becomes "unavailable" Restarting from the Add-ons tab in HAAS always fixes it, but I should be able to detect when it happens when "light.tempur_pedic_safety_lights" is not true or false, i.e., unavailable.
What I don't know how to do is how to restart that service. Does anybody have experience in restarting add-ons from MSR?
Running:
Reactor (Multi-hub) latest-24212-3ce15e25 ZWaveJSController [0.1.24232]HAAS:
RPi5-64 (8GB) Core 2024.7.3 Supervisor 2024.08.0 Operating System 13.0 Frontend 20240710.0
Hi!
Is it possible to generate two additional log files, the first being the replica of what is displayed on screen by the Rule History widgets and the other with Recently Changed Entities?
And could I configure the generation of one file per day, and delete the older ones? For example, store the last 5 days?
And being more ambitious, does Windget have an icon to open these TXT files in the navigated?
Well, we're approaching Christmas, so here's my request to Santa Claus @toggledbits 🙂
Hi @toggledbits
I'm working on a controller to generate llm response from a prompt in reactor. I have http response coming thru an http request action at the moment, capturing the response inside a local variable. So, it's practically sync.
I want to create a controller, so I don't have to rely on a proxy (and have a simpler architecture), and duplicate absurd http actions, but AFAIK in the current implementation, actions are async only. But if I have multiple requests going on, I cannot be sure what it's really inside an attribute. I also thought that something like a correlation id when sending the request could be used to identity multiple responses, but I wanted to double check with you before starting with something too complicated. I also noticed that some actions in home assistant (ie forecast) are sync and I'm wondering if you have any plan or hint to address this situation. Thanks.
Thanks.
@togglebits I am curious as to why the tilt_sensor.state (primary) = NULL. I believe it should show true or false. I have to use binary_sensor.state instead in my rules.
Again, not sure if this is related to Reactor/ZwaveJSController implementation or the actual Z-Wave JS UI docker version. I have copied, below, the attributes of the tilt sensor in hopes it can help.
Thanks in advance.
Reactor version 23302
ZWaveJSController version 23254
Z-Wave JS UI version 9.3.0.724519f
zwave-js version 12.2.3
@toggledbits I have noticed after upgrading both Reactor and ZWaveJSController to version 24257 that two of my devices/entities, TILT-ZWAVE2.5-ECO and Zooz ZSE18, had their entity re-named in an unusual way and also appears to be duplicated.
Reactor version 24257
ZWaveJSController version 24257
Z-Wave JS UI version 9.18.1
zwave-js version 13.2.0
Vestibule Motion Sensor State attributes/partial screenshot of entities it created. All entities have the same attributes.
motion_sensor.state=true x_zwave_values.Notification_Home_Security_Motion_sensor_status=8 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=23 zwave_device.valueId=[113,"Notification","Home Security","Home Security","Motion sensor status","Motion sensor status"] zwave_device.version_info=nullTilt Sensor Door State and Tilt Sensor Door State Simple attributes/partial screenshot of entities it created. All entities have similar attributes with exception of x_zwave_values.Notification_Access_Control_Door_State = 22 or 23.
tilt_sensor.state=true x_zwave_values.Notification_Access_Control_Door_state=22 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"] zwave_device.version_info=null tilt_sensor.state=true x_zwave_values.Notification_Access_Control_Door_state_simple=22 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"] zwave_device.version_info=null tilt_sensor.state=false x_zwave_values.Notification_Access_Control_Door_state=23 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state","Door state"] zwave_device.version_info=null tilt_sensor.state=false x_zwave_values.Notification_Access_Control_Door_state_simple=23 zwave_device.capabilities=[113] zwave_device.endpoint=0 zwave_device.failed=null zwave_device.manufacturer_info=null zwave_device.node_id=24 zwave_device.valueId=[113,"Notification","Access Control","Access Control","Door state (simple)","Door state (simple)"] zwave_device.version_info=nullI'm slowly migrating all my stuff to MQTT under MSR, so I have a central place to integrate everything (and, in a not-so-distant future, to remove virtual devices from my Vera and leave it running zwave only).
Anyway, here's my reactor-mqtt-contrib package:
GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor
GitHub - dbochicchio/reactor-mqtt-contrib: Contrib MQTT templates for Reactor
Contrib MQTT templates for Reactor. Contribute to dbochicchio/reactor-mqtt-contrib development by creating an account on GitHub.
Simply download yaml files (everything or just the ones you need) and you're good to go.
I have mapped my most useful devices, but I'll add others soon. Feel free to ask for specific templates, since I've worked a lot in the last weeks to understand and operate them.
The templates are supporting both init and query, so you have always up-to-date devices at startup, and the ability to poll them. Online status is supported as well, so you can get disconnected devices with a simple expression.
Many-many thanks to @toggledbits for its dedication, support, and patience with me and my requests 🙂
Need Testers
-
@gwp1 said in Need Testers:
I have noticed that the TOOLS>Restart Reactor button does not work
Make sure you've done a hard refresh on the browser to ensure that it has loaded all the latest files for the UI.
Failing that, hit F12 (usually) in your browser to open a Developer window, and then hit the Restart button and see if anything gets logged on the browser side.
-
@toggledbits Completely slipped my mind to approach it from the browers. Derp.
Yep.
Logged in as the default
adminwith updated pwd.Hubitat C-7 2.3.9.193
Home Assistant 2024.10.4
running ZST10-700 fw 7.18.3
MSR on RPi4 bare metal Model B 2GBs, SSD
MSR: latest-24302-751a06b6
MQTTController: 24257
ZWave Controller: 23257 -
@toggledbits said in Need Testers:
@tamorgen said in Need Testers:
I'm not seeing the login.html in the reactorui directory
Oy. OK. Fresh build is now up.
@tamorgen said in Need Testers:
those reactions are hanging.
I'm running this in my house, not seeing any issues. The engine is the same for 24115 and userauth; they are completely in sync except for the required elements to support user authentication, which has nothing to do with reaction. Still, anything is possible, but I wouldn't be able to discern much without the usual rules still applying: when things aren't going as expected, look at the logs... follow the posting guidelines...
Slow day at work. I was able to remote into my home server and installed the updated release. The login functions properly, and I'm not seeing the hanging reactions as I was this morning.
This is really great. Now I can securely access my reactor UI remotely if I have the need. The only thing that would make it better is 2FA, but this is a fantastic update.
-
@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.
-
@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.
-
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)
-
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.
Using MSR on Docker (Synology NAS), having InfluxDB, Grafana & Home Assistant, Hubitat C-8
-
@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. -
@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
-
@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?
