4 ms·

Always seamed to me overengineered. Maybe is because I'm skeptical about automations, and I like physical buttons, one button that does something, and automatio

Always seamed to me overengineered. Maybe is because I'm skeptical about automations, and I like physical buttons, one button that does something, and automations made in solid and reliable ways (such as mechanical relays for example). But if I need something "smart", and I have a couple of devices in my house, with a couple of automations (basically for laziness, not something I couldn't have done by pulling some extra wires and with mechanical timers and relays), I do them in the most simple and clean solution. Now all the automations rely on a local MQTT server where my devices connects to an a ~300 lines python program, that communicates with the MQTT server and applies all the automations, and also exposes a simple REST API to do things with a simple `curl` if I need so. Everything (MQTT server and python script) runs on my home router that has OpenWRT on it. I find it simpler to express automations with code than with complex web interfaces or yaml configuration files that are as complex as a program.

gerdesj 4y ago
So you have your solution ... for you: cool. The rest of us need some assistance for something that is not our expertise. We need the bollards that are put down the sides of the 10 pin lanes to hit a strike. Not sure why you are complaining about needing a Mossie - I assume that refers to Zwave2MQTT. Zwave actually works these days in HA, thanks to a lot of work in a very short period of time. At work I have 40 odd windows with Zwave detectors and it used to be a bit hit and miss. At home I have been doing very long term trials of Zwave underfloor heating controllers. I have 10 zones of electric underfloor heating and two of them are running Heltuns (v1) at the moment - three years so far. One of them has run away madly twice ie run at high current and hot but not since a firmware update. Strangely enough one of the old controllers ran hot too after a power outage, recently (investigation ongoing). You describe handwritten Python programs whilst complaining about YAML configs elsewhere. How do you generalise your stuff?
PaulHoule 4y ago
I have to admit I feel the same way. For instance business people are drawn to products aimed at solving the "integration" problem between different enterprise products like a moth to a flame. What's ironic is that the "integration problem" is much less of a problem than developing user interfaces or database application. From the viewpoint of a coder an "integration problem" is often ten lines of Python which can be completed in less time than it takes to wait for a salesperson to pick up the phone or that you could spend waiting for the documentation of an integration framework to load in your web browser. You generally avoid the devilish data modeling problems that turn up in applications work.

gerdesj 4y ago

So you have your solution ... for you: cool. The rest of us need some assistance for something that is not our expertise. We need the bollards that are put down the sides of the 10 pin lanes to hit a strike. Not sure why you are complaining about needing a Mossie - I assume that refers to Zwave2MQTT. Zwave actually works these days in HA, thanks to a lot of work in a very short period of time. At work I have 40 odd windows with Zwave detectors and it used to be a bit hit and miss. At home I have been doing very long term trials of Zwave underfloor heating controllers. I have 10 zones of electric underfloor heating and two of them are running Heltuns (v1) at the moment - three years so far. One of them has run away madly twice ie run at high current and hot but not since a firmware update. Strangely enough one of the old controllers ran hot too after a power outage, recently (investigation ongoing). You describe handwritten Python programs whilst complaining about YAML configs elsewhere. How do you generalise your stuff?

PaulHoule 4y ago

I have to admit I feel the same way. For instance business people are drawn to products aimed at solving the "integration" problem between different enterprise products like a moth to a flame. What's ironic is that the "integration problem" is much less of a problem than developing user interfaces or database application. From the viewpoint of a coder an "integration problem" is often ten lines of Python which can be completed in less time than it takes to wait for a salesperson to pick up the phone or that you could spend waiting for the documentation of an integration framework to load in your web browser. You generally avoid the devilish data modeling problems that turn up in applications work.