ha-wyzesense VS watchtower

You may be able to buy a Wyze usb bridge for v1 and use it to connect with the Wyze sense v2 sensors via the HACS Wyze Sense Component. The integration is no longer supported, but I'm using v2 sensors with the v1 hub.

Yes. There is a standard HA integration that can be used for controlling lights and cameras. If you want to use motion and contact sensors, you have to config a HACs integration (https://github.com/kevinvincent/ha-wyzesense).

Thanks, Ill look into Aqara. I run HA and keep everything local. If I got Wyze I would get the Sense kit and use this HACS component instead of relying on cloud or Wyze app

There is an outstanding patch to add the v2 support to the Home Assistant driver using the existing v1 USB Dongle: https://github.com/kevinvincent/ha-wyzesense/pull/211

Are you talking about this project? https://github.com/kevinvincent/ha-wyzesense

I'm using ha-wyzesense through HACS. Unfortunately the clock is ticking on these sensors and I'm trying to move away from them. Sometimes the sensors themselves freeze, other times it's the integration breaking since its just a reverse-engineered hack. And they are going to die permanently one day anyway...

The original one yes - https://github.com/kevinvincent/ha-wyzesense. There are a few others but I am using this one for the last year.

Related: https://github.com/containrrr/watchtower

> if you're using the docker image, upgrades are a breeze. Just bump the tag on the image, redeploy, and you're done.

Or you could just run Watchtower beside it and it will automatically update your docker containers. https://github.com/containrrr/watchtower If you are OK with automated updates.

So i primarily use containers on my local machine walled off from the internet, so it's not a big concern for me. Watchtower [1] is popular among home server users too which automatically updates containers to the latest image.

For production uses I think companies generally build their own containers. They would have a common base linux container and build the other containers based off that with a typical CI/CD pipeline. So if glibc is patched, it's probably patched in the base container and the others are then rebuilt. You don't have to patch each container individually, just the base. Production also minimizes the scope of containers with nothing installed except what's necessary so they have few dependencies.

[1] https://github.com/containrrr/watchtower

You can use Watchtower (https://containrrr.dev/watchtower/) that solves problem of manual pulling on VPS.

I checked https://containrrr.dev/watchtower/ and Arguments, but I don't understand where to attach that using portainer.

Again, there are options to automate some of the burden here by using tools such as Watchtower.

Have you ever deployed a Docker app on a server, but everytime you push a new version of your image to a Docker registry you need to manually restart your app? If you want to automate this restarting, this blog post is for you! I am now going to show you how you can do this with literally 1 simple command using Watchtower!