Arming Envisalink panel from MSR

[toggledbits]

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

[tamorgen]

@toggledbits,
Thanks for the updated version. I'll test it this evening after work.

I was only able to provide limited diagnostic information this morning before I headed to work. Reverting to 24115 latest version fixed the immediate issue of reactions not functioning, so everything would function normally while I was gone for the day.

If the reactions continue to hang with the revised version, I'll provide more detailed information and logs this evening.

[toggledbits]

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

[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:

1. create reaction
2. delete it
3. refresh browser
4. reaction is back...