P
@toggledbits said in Can you run MSR on Home Assistant OS ?:
If you have to go into the container to make changes, something is wrong in the configuration. Nothing inside the container should ever need to be changed. Everything that is "mutable" and configurable by the user should be in the data directory external to the container. So... this comment has me puzzled...
Had to edit entity config file recently to batch update entity names
@cw-kid Initially, I wanted to run MSR on HA. But HA OS keeps a lot of things locked down (for better and worse) and occasionally you have to go into the container's directory to make changes and HA OS basically makes that impossible.
@toggledbits And Docker can be made even easier with Portainer on top!
In my experience I have found that it will just make up random lines, so you have to monitor is very closely and always tell it not to change anything else other than what you have requested.
It is good for making large repetitive changes though.
After spending some time I think I got it figured out. Thanks to @Crille for the Inspo expression. I created a similar one that would basically deduct the extra light that is added when the lights are on. Basically when the lights are off, the expression gives the true value of the light sensor, and when they're on it deducts the 30lx from the true value. 30lx is probably too much but It seems to work now. The sunrise/sunset trigger is just temporarily there to ensure the lights still turn on and off as back up.
Wow! Thank you all for the suggestions! I think setting a pulse to go true for one hour is going to be the dirty and quick solution.
@Crille your expression is actually pretty neat.. I think it may solve my issue completely. Will trial this tomorrow! 
Hello all and happy holidays! I recently picked up a Zooz ZSE70, an outdoor multi sensor with an light sensor. The goal was to have my outdoor lights trigger once it got dark enough.
Today was the first day I was trialing my updated logic (screenshot below) soon after it got dark enough I observed the lights began to turn on and off every few seconds. Taking a look at the sensor history in HA it looks like once the light got below the threshold (35lx in my case) the lights would turn on great! However a few seconds later the sensor would update and the measured light would go above the threshold and the lights would turn off. After that the cycle would continually repeat every handful of seconds.
I need to think of a way to trigger the rule, but ignore the spike in the reading once the lights turn on. I could pulse the trigger to remain true for an hour ish so that as the light naturally fades in the evening it hopefully remains under the threshold. However that's a less than elegant solution in my case, so any tips would be appreciated!
One note: I cannot move the sensor so that the lights don't affect the readings.
Note: in the screenshot above, at the ~3:53pm mark where the levels flatten out, it was because I disabled the rule.
@toggledbits Very well said! When you make the switch give the new ZWA-2 Z wave antenna a try, it will fix a lot of any lingering problems.
@akbooer said in Single protocol?:
The opposite effect for me… when I finally gave up on Vera, I ditched all my Z-wave devices and switched to Shelly using WiFi for all wallbox switching devices. So, I’m at a loss to understand this comment…
Similar to what Patrick said below, I am not a fan of congesting an already congested wireless protocol. If I were to add 59 clients to my Wifi I would definitely see a degradation in performance. Also, these IOT devices don't really benefit much from using Wifi, the extra bandwidth is great but not really needed for day to day use when reporting states and sending commands. Also Wifi battery powered devices will not have the same battery life as Zigbee/Z Wave equivalents.
@akbooer said in Single protocol?:
Wi-Fi seems to give all the control I need, integrates easily with Apple Home, which I use as my main control, now. For some individual lights I use Zigbee, in the form of Philips Hue, which also has a native bridge to Apple Home, which also offers a secure cloud connection for off-site access. I’m slowly upgrading to Shelly Gen 4 devices which offer Matter protocol which will enable me to abandon the Homebridge software running on my NAS for further simplification.
As for Apple Home I have exposed all my Z wave devices and sensors through the Apple Home integration in HA.
What TV are you using? If LG, there was a recent WebOS 25 update that has completely broken HDMI CEC and E-ARC so that could be the source of your issue?
If not my best bet would be the switch being the culprit of your issues and HDMI-CEC is notoriously finicky to work with for even the most basic things.
Not sure if anyone could possibly use one protocol for everything however, in my case for my switches, plugs, door locks and some door/motion sensors they all are using z wave.
No specific reason why, it's mainly because I started with vera which had built in z wave so It was familiar to me when I switched over from HA.
I am currently using the Z Wave JS UI add-on, with a ZWA-2 antenna and for the most part been happy. The recent change to the ZWA-2 has helped my network A LOT. I live in a ~13,000sf home so range is big time for me, and with the new antenna the vast majority of my devices connect directly the controller. I have 59 nodes so my network isn't huge but not small.
My overall experience with Z Wave is ok though, I do tinker a lot and it's really easy to fudge something up with no apparent reason why. In my experience once you get network set and working well don't touch it. If something randomly happens (rare) it is kind of hard to troubleshoot as logs don't tell a whole lot, and my troubleshooting is usually just based on my experience with Z wave. The devices themselves are a bit more expensive than the Zigbee counterparts and I believe that has something to do with the fact that all z wave devices need to be licensed. No problem for me I do prefer to have devices that are vetted. Generally, I do see more newer devices being released with Zigbee support and not Z wave but aside from mmWave sensors I haven't really seen anything that I wanted.
I have deployed smaller scale <15 node networks at family members home and those work very well. A set it and forget it ordeal. Also could be because I don't mess with those networks after set up much 
IMO you can't go wrong between Zigbee or Z wave. I would stay away from any wifi devices though since you limited to what local control they offer, and definitely avoid, at all cost any cloud reliant devices for obvious reasons.
I recently bricked my Z-wave network somehow where I couldn't add any new devices so I opted to start fresh with the ZWA-2 and was impressed with its range! A lot of my devices talk directly to the controller now which has sped things up considerably as well.
Don't leave us hanging!! Show some pics of it in action. I need some Inspo to replace my Fire tablets as well that no matter what I do will randomly stop waking up
@toggledbits interesting, I totally understand the rationale why the controllers act this way. However, I feel like there are times where you’d want to batch update entities. Could this be added into the UI, similar to the purge dead entities action? Maybe an “update entity metadata” action?
@therealdb This did the trick thank you!!
Patrick, how should Reactor handle updated entity names and deleted ones for Z Wave JS? With HA it seems fairy instant with a restart that renames and deleted entities are updated but not the case with Z Wave JS.
Hello all.. been a minute! I recently rebuilt my Z wave network and migrated to a new z wave stick. In order to prevent any downtime I kept my original z wave network up and ran a docker version of Z Wave JS UI with my new controller. This way I could add device by device without having any devices down.
I finally moved all the devices over to my new stick today. The final step was to migrate everything from my Docker instance of Z Wave JS UI to the HA add-on of Z Wave JS UI. However during this migration some of the names didn't populate correctly which I later managed to import back into Z Wave JS UI. The issue was in Reactor it is stuck on the default names and the entities are not updating. I removed the controller from Reactor, restarted, hard refreshed, and added the controller back however the new entity names have not updated. Also it seems like the old entities from my previous instance of Z Wave JS UI are lingering and not being marked as dead (I believe a certain amount of time needs to lapse before they're marked as dead in Reactor).
My goal is to basically purge all the entities for the 'ZWaveJS' controller in Reactor so it can pull all the updated entity names and only the entities that exist in Z Wave JS UI. I cannot find a quick way to do this, I know entities can be deleted one by one, but with over 100 entities this would take long
I am guessing that if I added the controller with a new name in in the Reactor config it would pull the updated entities and names but I think that would break my rules since the entity IDs would change (I made sure to name all the entities the exact same as they were previously to prevent this issue).
Not yet!! I have been waiting for something with a little bit better audio, think Sonos level. Do report back though
@therealdb said in Advice on Storing and Backing Up Bind Mounts - Docker:
Yeah, containers are a game changer for manageability.
I just have a /home/casa/containers (where casa is the user) where I have my configs/storage. Easy to backup/mirror. In case of disaster recovery, just copy everything and I'm ready. For consistency, I save my docker-compose file in the same dir. Restoring a container is very easy.
Perfect thats exactly what I was thinking of doing! Since I am using Portainer their equivalent of Docker Compose is Stacks and Portainer has a handy built in GUI back up feature which backs all that up. Just need to figure out how to automate it and store it off the host for easy future retrieval.
@toggledbits said in Advice on Storing and Backing Up Bind Mounts - Docker:
@therealdb is spot on here. I do something very similar. His last point, having the docker-compose file with the volatile data, is particularly important to speeding recovery. Another tip: practice doing recovery, and write yourself a text file in the same directory with the steps to do it, so when it happens, you're not (a) doing it for the first time, or (b) trying to remember what worked two years ago.
As a side note, in a past life, I wrote a "high availability" subsystem for a routing product -- software that ran on a master system and a number of hot standbys that would bring up a standby quickly when the master failed. I have often thought about doing that for Reactor, but always conclude that our world doesn't really demand that level of response, no matter how "cool" it may be. It's so easy and quick to recover containers, I feel like lt's good enough, and my time is better spent on other features.
I did actually already kinda do a practice recovery to make sure Docker was the right choice for me. I used an old pi I had kicking around to tinker with to get familiar with Docker before doing a clean wipe and install of Ubuntu on my main driver. Transferred everything over from the old Pi to my main host (odroid N2+) and it was painless. On top of that I was also able to set up a few more containers that I wouldn't have otherwise set up because Docker is so damn easy.
In my lifetime with home automation I actually (*knocks on wood) haven't suffered a complete failure that isn't self inflicted. However I have moved hosts pretty often as my setup continues to grow in size and complexity so having Docker now will allow me to continue moving up without having to worry about spending countless hours trying to install packages via the CLI.
Hello all, after seeing Catman's posts about their disaster recovery and move to Docker I took that as a sign to migrate everything (aside from HA) to Docker. After a small learning curve I had Docker+Portainer up and running in a few days.
Instead of using named Volumes I opted to use Bind Mounts so I can easily edit conf files and any other file needed. I do understand the nuances that come with bind mounts, such as migration to a different host may require changing file structures, the possibility of someone editing the bind mount files and permissions but to me those aren't too big of a deal.
My question is what is the best way to keep a back up of these bind mounts? I currently have them stored in the /etc directory in another directory named on a per container basis. I was thinking to move it all to a /home/user/docker/ directory so that I can use a simple cp command to my mounted SMB share to backup all the container data files. Anyone else do it differently?
Side note: I finally got to flex the benefits of Docker with updating Reactor.. it was dead simple. I had no idea what I was missing out on lol!
