@toggledbits thanks.
I've modified the build.sh from the other add-on and set up docker hub. Despite not fully being able to understand what and where Linux read/write errors actually arise from, I've got the files built and pushed. Had to use a pi to build the arm and aarch, then Ubuntu in Windows to build the amd64 due to errors and warnings about architecture. Unsure if that has to be that way, or they should be buildable from one platform or not.
This was the better idea as when I tried to update the other add-on container, msr warned about node.js being out of date by doing it that way.
I've got my version loading from a local plug in and pulled/running from GitHub now on my test install. Only thing to work out
Only thing left to work out is why the alerts/entities aren't updating, but I'm thinking that's because the default in msr points to a dns name for HA. Which is likely resolving to my prod HA Yellow (incorrect login alerts on there also point to that). Was a rush before I needed to head away. I'll backup/remove and pull the new add-on to my prod. hardware once at a computer I can work properly from, then copy the rulesets etc into a backup for that and re-export it.
Appreciate the tips from you and @Pabla
It's a bit more work to build the files and pull into my own add-on but it's better I have the control and still run a supported HA install

Update: That was it, installed/updated Reactor on my HA Yellow, entities updating as expected

So, @toggledbits - thanks again.
It IS possible to update the docker container. It does survive a Home assistant restart..... but not a host reboot. The version reverts. So the container is rebuilt.

I've built a test Pi with HAOS on it for testing outside of Prod.
I created one test rule and one global expression while testing the updates.

Host reboot wiped out the global expressions again. @mrw298 There is definitely some fault with the add-on, this is a completely seperate install and hardware with no config, except the SSL and Reactor add-on installed.

I guess this leaves me to try to figure out where is safe to manually install reactor in HAOS and get round the "Error response from daemon: error while creating mount source path '[any path]': mkdir [any path]: read-only file system"
Update-
Actually the whole point of moving to HA Yellow was to be on a fully supported HAOS - So I'm going have to learn how to build my own local add-on to pull reactor into a supported container. My need is to run reactor on the same hardware as HA, and not have to rely on other plugin maintainers to stay in a supported MSR version

@toggledbits - have you considered building a Home assistant Add-on for Reactor at all?

Thanks again

@toggledbits @mrw298 was last showing online here in March.
Thats why I was reaching out in this forum for wider experience

Do you or @Pabla happen to be able to answer a more generic question about Docker in the context of HA (and i'll run the risk myself of something going wrong).

Kind of forgetting that MSA was installed via the add-on, it currently exists in a docker container in HA yellow, which i can see and access via SSH
Should upgrading it mean running commands inside the container, or somehow specifying the addon container by name to update MSR inside it?

I'm really trying to learn more about how docker updates/linux inter-relate, but MSR is literally the only use case i have for it. I'm not a linux specialist, more of Windows sysadmin with vmware etc and only touch linux/docker for Home Assistant/MSR and PiHole, so there is a lot of trial an error with this for me It's not yet clear about the possibilities or the best way to interact with docker after someone/thing else has created containers like in the add-on.

@toggledbits btw your guides are actually great when installing MSR from scratch, thanks for taking the time with the documentation, it really helped previously move from Vera to Pi and keep MSR on the same hardware.

Any tips really appreciated.

@Pabla I've been running Reactor for years across many platforms and never ever had an issue with backups doing weird things - until running the add-on install.
I never saw it with a docker install as per toggledbits installation guides.

This issue may be just related to the add-on as i've never heard of expressions disappearing before, until here and my install: https://github.com/mrw298/hassio-reactor-addon/issues

@toggledbits That I understand.
But in case I was unclear above. I had a lot of saved and working global expressions that were lost after a host restart. They referred back to one test expression I'd previously created. I then went to the backup to find that was the same

Is there a way I could update this docker container myself to the latest version of msr. The add-on maintainer seems absent and I don't want to fall behind.
Docker is not at all my speciality but I can follow guides/instructions.
I used docker-compose on the pi, but on the HA Yellow it looks like HA OS is is protected and wipes out anything not in the homeassistant directory or the installed plugin containers (including when I installed the docker-compose plugin).
Would it just be a case of logging into the container and running the normal docker pull commands, or running them outside the container but specifying the docker container in the command?

Many thanks!

Be Warned:
Just in case anyone else is using the Add-on in HA, There is an issue where global expressions all get deleted on host reboot.
I had created a test rule when i first installed the add-on. and restarted the host with no issues. I did this because on github add-on page people have complained global expressions get deleted on host reboot and I wanted to test)
Since then i've created 20 or so more and needed to reboot the host. I was greeted with all the new expressions missing, and only the test one i had deleted since showing again.
Interestingly a backup of the addon i had taken when everything was fine last night, contained only the test rule. So something isn't saving the live configuration properly somewhere.
My solution: (luckily had a backup of expressions.json from my old host)
export a reactor add-on backup, replace just the expressions.json using z-zip, reupload the backup and restore it.
I've checked /data/reactor/storage/ and the correct file is now there.
Unsure if this is related to the addon being latest-23063-c464b685 or not.

If anyone knows if i can/a way to update this version inside the docker container the add-on creates, i'm all for trying it.
Maybe I could have copied this into the docker container, but I wanted to make sure I also had a backup that was restorable and copying into docker isn't as simple.

@therealdb That was the whole problem - I Couldn't find the storage directory in the destination

Hi Pabla - Thanks for the tip. I disabled protection mode as I was trying to install my own docker container with MSR but kept hitting the write error above. (could only get the command to complete using \home and no subdirectories, but the files didnt appear still there and reactor looked running in cli but never presented the web page)

Update, found them for anyone else who needs them:
Inside the container at /data/reactor/storage/rules

Would be nice if there was a rules export/import option in the UI.

I suppose another question is, could I pull the updates to MSR in this container myself, the add-on maintainer isn't prompt to do that into the add-on.

(Once you have the rules into the addon initially, the HA plugin backup does handle them from there :
)

Info:
Home Assistant Yellow - 2023.12.3
Reactor Community Add-on
SSL/SFTP enabled on the HA Yellow

I'm trying to migrate from a Pi and MSR installed with docker compose to the community add-on inside HA.
I located all my rules etc in the pi at /home/pi/reactor/storage, but I cannot find where the addon created the storage folder/rules on the HA Yellow.
I've searched the homeassistant directory and everything in root also for these files using various methods including *.json and rule but I cannot locate them.

I've a lot of rules and expressions, so need to copy rather than recreate them as I cant just export/import from reactor. I also want to be sure I can take reactor backups when needed on the HA Yellow

I posted an issue in the add-on maintainers github but they seem to respond to nothing posted there.

Any tips appreciated.

I also tried to just install using docker-compose in HAOS instead, but kept hitting the "Error response from daemon: error while creating mount source path '/home/': mkdir /home/reactordocker: read-only file system" error no matter what permissions were assigned to a folder or where I created it. I think perhaps because somethings containerised in that OS

OK, Thanks for this. I do prefer to use constraints where they work (my thinking it prevents constant evaluations when not needed). I'll be extra careful in rules that are not often setting and have long time delays where something may or may not become true.
I'll move the constraints as set into condition groups and try that
Update: Scrubbed the constraints and rule is set. Thanks as always.

Hass 2022.11.5 on Pi
MSR latest-22337-1a0a685f

This rule should be true now? I noticed that the first rule seems to reset either on HASS or MSR restart and not pick up where it left off, but thats not my current query now. The parts of the rule that look for freezing temperatures have set the rule, and constraints are met.... so why is it reset still? I just added the extra constraint for the lux battery power. But shouldn't the rule re-assess when saved?
I'm not sure this rule has ever set since I created it.

@tbully
I've had this before too. Something has triggered (or not) .Being able to look up where it is present without going through all the rules would have been great. MSR has a great recent history and warnings now to help, but especially when changing things and you want to be sure you have caught everywhere things were defined.
This was last in vera for me but i'm sure it will happen again as I rebuild everything and my rules become more linked together.

Aside from search for this, When opening nested/closed rules in the UI, the reactions don't show without clicking edit. It does make it quite hard to open a few rules to have a quick glance at the trigger and reaction.
I might be missing something, but it would be great to be able (even if an option to turn this on or off) to also see the reactions when opening a rule to check it contains what you think it should, or when quickly comparing similar rules too.

@pabla Thank You!
Perfect guess on your part. This works as an example. Appreciate you pointing me in the right direction

@toggledbits also appreciate your intent to make the UI yaml friendly at some point too. This json/yaml thing caught me out, along with the code formatting required.

Thanks again to all

Side note to anyone using kiosk type modes (like in windows especially). It might seem nice to have the browser restart after x hours in the kiosk settings to take you back to a home/start page in HA, but that will break browsermod and force you to re-register the browser (so, the better way is to use MSR or another way to control that behavior, if you want it)

Hass: 2022.11.3
Hardware: Pi
MSR: latest-22310-a6da8097

I'm trying to use MSR in automations to change the page displayed on a wall tablet (Windows and Edge in Kiosk mode)
Example use would be motion detected will change to the security dashboard, or heating turns on, shows the heating dashboard.

I have Browser Mod installed and working and the entities are present in MSR. My only option for the entity which controls the page/dashboard displayed is "x_hass.call_service"

What I need to change is the state of the entity

Is this possible in MSR? Despite much searching i'm unsure what service to call to set the state?

I have tried using service: browser_mod.navigate but get an error
(this service detailed here https://smarthomescene.com/guides/how-to-setup-browser-mod-2-0-in-home-assistant/ )

Also trying to lay the data out like this with/out quotes and other variations has not helped

{
  "/home-overview/heating"
}

Massive upvote on all 3. Just like back in the old Vera days
(Unsure how easy update would be with the various ways of implementing MSR inside/outside docker etc) - unless a standard install method is specified, and one of the features of that is 'update' capability.
Docker-Compose please

With regret, my three Vera controllers (VeraSecure and VeraPlus) are now in a cupboard. It's been such a shame to see the support for vera drop to impossible from being able to get someone on the phone straight away over the years. A firmware update (official) killed one of them and support didnt replace it. EZLO secure never came to the UK.
I've been with vera since vera3 and had a LOT of automations in PLEG and Reactor on that platform.
Updates were few, and the hugely contributing people on the forums telling Vera/Ezlo support how to fix things often got banned when they raised concerns.

They had so much good potential and reasonably decent hardware in itself. I moved everything (60 z wave devices) and my alarm panel and weather station all into HA. It's been a pain, but with MSR at least I have some familiarity and less MASSIVE pains including devices like you get with over 50 or less on the Vera. At least in ZwaveJS when something goes wrong, its easy to check logs and reinterview/delete entities that aren't valid and sort it, without the exclude/include everytime (sometimes many times per device) on the other platform.
z stick on Pi with HA has less range and more tedious backup methods, and not as tidy package on the shelf, but at least its progressive.
And i'm able to update the z wave devices OTA without excluding and including into a different network to do it as a bonus.

@pabla The issue isn't rounding, the sensor is in Volts, i multiply by 10 to get % for gauges etc, so it's always rounded.
The issue is due to temperature and the accuracy of the sensor (ultrasonic), when the oil level is very close to for example 55 and 56% (5.5v/5.6v) and the oil expands, the reading will go from 55 to 56 and then 55 and then 56 over and over due to the tiny variance between the two readings. If that makes sense.
I can't set a rule to only track decreasing changes as we also fill up the tank sometimes too

@pabla Thank You!
I was going wrong with the title by missing the comma in preceding line, I had the rest right and indented the same before I took the code out, as it wasn't working.

And right again, I had tested the code with ${{content}} but it didn't work - most likely because I used the play button to the right and not above the reaction.

Really appreciated, i've updated my template I copy from, so that should be notifications sorted for everything now.

Seperate issue is the value on the sensor flaps up and down by 1% when its close to changing (temperature in the oil tank/expansion) and sends lots of notifications, just need to figure out how to address that. But off topic for this post

Apologies
Initial post updated

I'm trying to insert variables into notifications. I've tried
{
"message": "Oil Level is {{Oil_Level_V_to_Percent}}"
}

Also prefixing {{ with $ and a few other things.
I get the main body but the variable is missing, i.e "Oil Level Is"
Could someone please help me send the variable (and to title the notification would be great too)
Many thanks
Apologies

Hass: v2022.10.4
MSR: latest-22274-24dfd72c

The rule :