For one i use my EmonPi as sole home automation engine.
I live in an old farm off-grid with only 6 PV panels. I have to drive my power consumption harshly in winter time…
I have 1 EmonTx and 4 EmonTh in the house.
I do write glue scripts in bash as mqtt publishers or suscribers and publish whatever I want to store as mqtt topics to be picked by EmonCMS.
On the Pi, I’m running GitHub - jchdel/weewx: WeeWX code repository to publish weather data.
I use GitHub - jchdel/mpp-solar: Python package to communicate to MPP Solar PIP-4048MS inverters (and similar) to publish inverter data.
I wrote a small 1-wire2mqtt script also for a couple of sensors (should publish in my github).
I have a wifi2mqtt relay.
Plan to introduce zigbee2mqtt next week, with a couple of smart-plugs and Utility meter reader to start with.
The script to pilot my 23 years old dumb fuel heater via the relay is about 60 lines of bash and takes quite a lot of parameters fetched from EmonCMS via it’s API into account.
The whole point to me for home automation is automation. Therefore I do not need an interface to pilot the house. Just some dashboards and a way to visualize timeserie values. That’s perfectly done by the OEM team so I do not have to reinvent the wheel as a geek 
and I, as a geek I’m, just dump a couple of bash lines on top of an already complete infrastructure!
Thanks guys!
1 Like