5 ms·
I love what author did and I'd probably do the same, I guess I'll replicate author path. It all depends on requirements, but I also dislike python, I want to do
by waterCalendar 3y ago
I love what author did and I'd probably do the same, I guess I'll replicate author path. It all depends on requirements, but I also dislike python, I want to do something in python (and I've started something but a bit against main trends), but packages and recent step to get rid of signatures is a big no from my side. Too many news here and there about "enriched" versions of packages regarding python - and I know other tech stacks have it too, but looks like they have it less. I would not see it as problem if HA had dependencies statically linked, which in python terms would mean just copied fixed versions into HA repo.
Anyway what is wrong with HA/OpenHAB? It's too "enterprise" or rather too rich and therefore seems heavy to run - VM with at least 2GB of RAM? No, thanks.
What requirements I have for smart home:
- made for tinkering people - preferable approach as in open-hardware initiatives where one electric motor can be used either for water pump engine or spinning table saw, so you can use it with things you already have and you have some indications about how to connect it all together in various cases
- something designed for the cheapest hardware (nowadays rpi comes quite cheap though but it is not truly open and there are availability issues)
- something doing only what is necessary and not cloud-first
- option for build time removal of unused features
- no need for hot loaded plugins
- build based on tools with long term compatibility in mind (again, sorry custom extensions for each new language in the world)
- real time system or at least good separation of control vs deployment/etc
- designed as optional extension to existing world with switch-off mechanism
- no need for vast ecosystem as long as it is based on freely available standards
- nice to have feature is to provide scripting scenarios, can be deployed independently from main control board
- should be cross-platform on native level, so in the end going to C, no heavy vms or interpreters, nice to have runnable on bare metal
- things like reports presentation should be done not in the hardware which has actuators, data should be kept in another piece of hardware e.g. PC
- jdiez17 3y agoYou don’t need a real-time OS.