Reverse proxy & API ACL

[wmarcolin]

A small tool I built for my own MSR install, shared in case it helps someone else.

It is a read-only web page that runs next to Reactor, on its own port, and answers a few questions the UI cannot:

• Dead references - rules and reactions pointing at devices that no longer exist
• Where do I use a rule / reaction / global? - who references it; a reaction nobody calls never runs
• reactor.yaml - checks syntax, missing entity ids and common group selector mistakes
• Entities - every entity with its canonical id and capabilities, also as JSON or CSV
• Set rules - rules currently in SET state, newest first
• Log viewer - the Reactor log filtered by level or text
• Find any text - search across rules, reactions and expressions

One Python file, standard library only. It never writes anything: it only reads the Reactor storage, config and log files. It has no login, so keep it on your local network.

Download and install instructions:

reactor-tools/tools/reactor-inspect at main · wilsonmarcolin/reactor-tools

Contribute to wilsonmarcolin/reactor-tools development by creating an account on GitHub.

Disclaimer: shared as-is, for anyone who finds it useful. I do not provide support and I take no responsibility for its use. Use it entirely at your own risk. This is an independent project, not affiliated with Reactor or its author.

[gwp1]

@wmarcolin this is very cool. It's picking up changes I made many many months ago that have impact on rulesets that haven't been called since those changes - so I never noticed they wouldn't have run.

Nicely done!

[wmarcolin]

@gwp1 said in Reactor Inspect - a small read-only helper panel for MSR:

@wmarcolin this is very cool. It's picking up changes I made many many months ago that have impact on rulesets that haven't been called since those changes - so I never noticed they wouldn't have run.

Nicely done!

I hope I can help. Since I’ve been using MSR for many years, we naturally tend to forget where we used a variable or a rule we created, or we edit the reactor.yaml file and aren’t sure if the structure is correct—or even with the expanded use of Dynamics, we can still make mistakes. In other words, our environments are becoming increasingly complex, so any help can make things easier.

[wmarcolin]

A quick update: @toggledbits kindly pointed out that Reactor will stop writing the plain JSON storage files at some point, keeping only the dval format. Reactor Inspect reads the JSON files today, so I will work on a version that reads dval.

Nothing to change for now: the current version keeps working while the JSON files are there. I will post here when the new version is on GitHub.

Thanks Patrick for the heads-up!

[wmarcolin]

Reactor Inspect v1.1 is on GitHub.

@toggledbits pointed out that Reactor will stop writing the plain JSON storage files and keep only the dval format. v1.1 now reads the dval files, with JSON only as a fallback, so it will keep working after that change. Before switching, the new reader was checked against all 907 storage files of my install: identical results.

Also in this version:

• rules that entered SET at the same moment are listed in a fixed order
• the version number is shown in the page header

@gwp1, since you have it installed, updating is the same download over the old file:

cd /home/youruser/tools
wget -O reactor_inspect.py https://raw.githubusercontent.com/wilsonmarcolin/reactor-tools/main/tools/reactor-inspect/reactor_inspect.py
sudo systemctl restart reactor-inspect

Details and version history:

reactor-tools/tools/reactor-inspect at main · wilsonmarcolin/reactor-tools

Contribute to wilsonmarcolin/reactor-tools development by creating an account on GitHub.

Thanks Patrick for the heads-up, and thanks gwp1 for the feedback!

[gwp1]

@wmarcolin updated - thank you for this.