Need Testers

gwp1

@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 Reactions issue I noted has also not reappeared.

I have noticed that the TOOLS>Restart Reactor button 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

@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.

gwp1

@toggledbits Completely slipped my mind to approach it from the browers. Derp.

Yep.

Logged in as the default admin with updated pwd.

tamorgen

@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.

toggledbits

@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)?

gwp1

@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

@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.

toggledbits

@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.

gwp1

@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.

toggledbits

Build 24120

Mostly code cleanup and tightening around application restriction.
Should fix Tools > Restart Reactor issue

toggledbits

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.

tunnus

@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)

Pabla

@tunnus Yes this would be a good improvement to the docs.. you weren't the only one who made this mistake lol!

tunnus

well, I actually knew to rename this file, but it took a while to find that template (as I've used MSR container for years now and did not remember the location of dist-config)

noelab

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

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

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

Features/suggestion that I image:

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

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

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

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

imaging it:

tunnus

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

@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...

toggledbits

@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-config to your data directory (as dist-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

@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 stream

But reactor.log file seems to in place when checked via terminal:

noelab

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

2024/05/08 21:20:46	stdout	stream /var/reactor/logs/reactor.log not open boolean [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

Reactor-Editor / Reactor-ui-Status Errors

every X days field uneditable

Darker Reactor style

Which user to install nodejs as ? Debian Linux

Reactor (Multi-System/Multi-Hub) Announcements

OpenAI Controller for Reactor

Thanksgiving lighting took a holiday

Reference error - null object

Trouble Configuring Multi-System Reactor Logic Across Devices

MSR UI on a mobile browser

ZWaveJSController - Warning/Error Traceback - Registering action set volume for Aeotec Siren 6 (ZW164)

[Reactor] Assignment to alarm ignored -- expression-driven global cannot be set by assignment

[Reactor] [Dev] Clarifications/Docs for refreshCapabilities and Entity action implementations return types

Access to log file viewer denied

TTS in MSR?

Should MSR import this device type from an Ezlo controller?

A couple of things about Reactor 24293

Error on start for MSR after update to 24293

Dark Mode not Working - 24293

Is there a way to restart an add-on in HAAS from MSR?

Need Testers

Build 24120

Recent Topics