ATC_MiThermometer VS wireguard-vyatta-ubnt

I want to do a little IOT project where I establish a MQQT-Broker on my Raspberry Pi and send it readings from my measurement devices (xiaomi Mijia-LYWSD03MMC). The plan is for these devices to connect to my ESP32, allowing me to transfer data to the broker on the Pi. I've successfully connected my ESP32 to my Wi-Fi and to my broker, but I'm experiencing significant difficulties in connecting it to my two measurement devices. I have essentially followed the instructions provided in this GitHub repository (https://github.com/atc1441/ATC_MiThermometer) as best as I could. I also checked some other repos but they didn't really help me as they were too big/complex...

If you get off WiFi and on Bluetooth: https://github.com/atc1441/ATC_MiThermometer They last a year with a single CR2032 which is hard to do with WiFi.

I then copied this Python script to the Raspberry Pi 4 and was able to read the temperature and humidity! (https://github.com/atc1441/ATC_MiThermometer/tree/master/contrib/python)

I’m using 16pcs Xiaomi Thermometer LYWSD03MMC BLE thermometer around the house with custom ROM from here https://github.com/atc1441/ATC_MiThermometer

I use the Xiaomi (pronounced Show Me) Mi Temperature and Humidity monitors (version 2) and flash the firmware with a 'open source' version (here or the older one here). I've found battery life good (8 months + with the newer software on one sensor) and bar from one corrupt display (right next to an outdoor electricity feed - well the box is handy and dry) then they have just run and run and run.

The thermometers in screenshot are Xiaomi Thermometer LYWSD03MMC with ATC custom firmware. Their bluetooth broadcast data collected by some cheap chinese ESP32 board and ESPHome addon in Home Assistant.

You can replace their firmware with one which is more open and broadcasts the values without needing to connect to the device: https://github.com/atc1441/ATC_MiThermometer

Joining serverless environments like AWS Lambda to a mesh network has traditionally been difficult because you can't directly access the network interfaces on the hosts that run your functions. The NetBird netstack mode addresses this by providing a simulated TUN device and a SOCKS5 proxy that targets that device. This allows your Lambda function to access other services in your NetBird network via the proxy.

NetBird simplifies Kubernetes access with its zero-configuration approach, leveraging WireGuard's simplicity and strength. It seamlessly integrates with various tools, offering transparency and high reliability as an open source solution.

WireGaurd

As for remote access, you will need another computer to install tailscale or wireguard vpn to access your local devices https://www.youtube.com/watch?v=AkKz7Vza1rw and the official docs for up to date advice https://www.wireguard.com/ this doesn't require much to run, you can use any old family computer or some old quad core 2nd-4th gen intel desktop for 30 bucks off facebook marketplace. You can also use that same computer to run klipper if you install proxmox and have two separate linux virtual machines.

Um modo mais avançado de se proteger é utilizando protocolos de VPN mais modernos, como o WireGuard. Muitos provedores de VPN oferecem suporte a este protocolo, que além de muito simples de usar e além do mais é open source.

here u find out how wireguard works https://www.wireguard.com/

WireGuard is a VPN protocol developed several years ago which is exremely fast, lightweight, and uses state-of-the art cryptography. Its performance blows legacy VPN's out of the water.

Try vanilla. It solved all my problems bar none.