proxy.py VS hass-weatherflow2mqtt

[Not my project]

A very well features proxy server (Forward & Reverse + lots of other features).

https://github.com/abhinavsingh/proxy.py

The article gives a good summary of the quite complex landscape of concurrency in python. There's more to it, for example gil-free c-extensions, subprocesses and cross-machine (plus IPC) communication.

But I'm particularly bothered by the fact that many articles and tutorials look at concurrency as if it's only about factoring primes or writing a web server with many (perhaps even idempotent) parallel requests.

In reality, people will often want and need to combine multiple of these approaches, and then it gets VERY messy. I.e. try to combine a multiprocessing executor with multiple asyncio loops and boom you're in some very deep waters.

One project that does this (async loops inside multiple processes) is proxy.py - very enlightening to read its code base [1].

But I really, really wish python would do more to provide simple and robust abstractions for these kinds of tasks. My dream would be a robust actor system similar to erlang, but we'll probably never get that.

[1] https://github.com/abhinavsingh/proxy.py

Setup a VM with Hyper-V and restrict the internet access or disable it.(best way), or build yourself a proxy: https://github.com/abhinavsingh/proxy.py

See `proxy.py` examples for some inspiration :) https://github.com/abhinavsingh/proxy.py/tree/develop/examples

You can use a Weatherflow Tempest. It’s all-in-one and broadcasts its data via UDP on the local network. You’d be able to run the very simple weatherflow2mqtt and once in MQTT you can easily get it into MySQL, though for constantly-changing data like weather sensors you may want a time-series database like InfluxDB.