ha-wyzesense VS docker-swag

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.

I have a NAS on .0.181 and a swag container (on a different port than nginx) on .0.180 that points to my public facing services. For obvious reasons, I don't want my public domain to point to any other ports/addresses on my home network. Additionally, as elegant as swag is, it requires authentication and so won't work for simple local DNS. I now have one local domain for each server and an nginx instance on each that resolves to my different services on each.

OP is even linking the Github... https://github.com/linuxserver/docker-swag

I have an UnRAID server with a few services (Jellyfin, Nextcloud, etc.) running on it behind Linux Servers' SWAG reverse proxy container, which is built on Nginx and Let's Encrypt. This is pointed to a DuckDNS link, which is then pointed at my domain with a CNAME. So I can access Jellyfin, for example, at jellyfin.mydomain.com. A few weeks ago, due to seemingly unrelated issues, I got a new modem/router, an Arris SURFboard G34. For the first few weeks, everything was working as before. But now, when on my LAN, I can't get to my services at the proxied domain. It times out every time. There are no errors in SWAG's logs, nothing seems amiss in the router's web interface, and the services are available both at their IP:port address and, when not on my LAN, I can access them at the domain no problem.

Reverse proxy, probably? I use Docker SWAG, setup here, with DuckDNS and it works really well for me. There are of course many ways to reverse proxy, as I linked to earlier.