thermostat VS aiomysql

all the past data could be used to run simulations/verify models, but really this should be a thing that learns along the way. Like you move into a house, install thermostat and temp sensors, and then as it runs it gets better and better at cooling your house. Many hard coded things need to be turned into dynamic ones, heater functionality needs to be added, and a handful of other quality of life things need to be added, but the idea is that someone could git clone it and go even as is. https://github.com/G4te-Keep3r/thermostat ***project summary**\*Custom thermostat that does more than simple on/off cycling. The 2 main goals that it started with was to not have it 80+ degrees during the day like the old thermostat would, and for the overall consistency of temperature to be better (old thermostat had almost a 10+ degree swing before it cycled back on). This started out so simple as "build a better thermostat" and just kept getting more complicated.

Use asyncio lib for mysql, for example – aiomysql

No, as I said, async db connection is the key. You can do that with SQLAlchemy using the databases library, but since you are not using SQLAlchemy it makes more sense to use the underlying db driver, aiomysql, directly.