Greetings to community !
It seems that our long-standing plans to build a house for our family will become a reality (at least from bank perspective…).
Since my profession is related to IT + I’m long therm HA user (but till now not equally with ESPHome) i decided to go my own way in “SmartHome question”.
I’ve been through a lot of brainstorming over the last year, with lot of questions, failures, etc…
I’ve set some principles that I don’t want to change and I won’t:
- Devices based/created on ESP32-S3 LAN PoE
Call me old fashioned, but even all my ESP32 devices are ROCK solid over WiFi i prefer the hardwired solutions. FTP/STP cables are cheap enough, versatile, and i would install them just “everywhere”…, in case of some future changes. PoE can solve need for additional power source. ESP can work as an independent device and doesn’t need in any cases some “middleware/device” to operate. - Thermostat should be based on ESP32 (cDIY made/custom frame)
- Light switches would be only momentary switches.
PRIMARY CONCEPT/Idea:
Because of upper mentioned benefits, my primary idea was to wire the house from electrical-high voltage perspective in old style, like a DUMB house. Put under thermostats/switches (use this two devices as examples) ESP32, SSR Relays and have a Smart solution, which easily allows to “convert” the house back to dumb in case of some horrific scenario. This concept is sadly not possible, because of space issues under “in wall” moountings. I’ve tried long enough to find somebody to project PCB based on ESP32-S3 PoE with custom dimensions and needed additional devices (sensors, relays…) to fit. I’m not able to do that by my own and I’m also shipwrecked finding someone. Of course within a reasonable budget and timeframe. This concept was cancelled.
SECOND CONCEPT/Idea:
Wire the house from electrical-high voltage perspective in a modern way. Everything (wires, relays, contactors) should be located in technical room. Under thermostats/switches should be ESP32 (without any additional components as in Primary concept) which should send via GPiOs signal to relays in technical room. Here comes another issue, wires lenght. I spent enough time reading issues about long wires, interference, voltage drops. This is again too huge risk of failure and such setup is not the right path. This concept was cancelled.
THIRD/FINAL CONCEPT/Idea with options:
This concept is based on second idea, so everything from switching and high voltage side is located in technical room, including one/multiple ESP32s connected to relay boards. From this point of view should be those ESP32s acting as “receivers”. They should receive command to “switch” some relay ON/OFF based on input from ESP32 located under thermostat/light switches. This is (from my perspective) very easy, straightforward, and incredible versatile solution. BUT it needs “middleware” to operate. To avoid this:
- option1: wire ESP32s around house and technical room via ModBus = honestly i hate this option. Maybe because i dont have enough experiences, im unfamiliar with code, and i think this protocol is obsolete. From the coding perspective, it would be also pain for me, to send/get values, responses. I did some ESPHome base ModBus TCP converters already, don’t like this.
- option2: wire ESP32s around house and technical room via CanBus = absolutely no experience.
- option3: HTTP requests. Again, from coding perspective should be this something new, but not unmanageable. ESP32s don’t like so much WebServers, and honestly except HTTP requests, i don’t need them. I find this again risky for long therm usage. Maybe it will work couple of days, maybe weeks, but as documentation mention, HTTP requests/WebServer is generating huge load to ESP
- option4: This option is just a cosmetic thing, not a “real” wire = Using additional (but call it primary) MQTT outside of HA, only for “this” devices. Integrating to HA should be done via most native way = ESPHome API, but the devices should “talk” to each-other via MQTT. The broker would be outside HA (eliminating at least one possible failure option). This should also prevent to have the same device duplicated in HA. Second MQTT broker should be running in HA as addon, for devices which needs direct HA integration for easier handling (tasmota, shelly mqtt etc…).
- option5: using different software “firmware” on ESP32s with better direct-interconnection options. Not idea which, how…
I’m sure that even though I don’t consider myself a newcomer, there are plenty of better informed and more knowledgeable users out there. If any of them would be willing to give their opinion on my knowledge, thinking, I would be very grateful !
Thank you for reading this far !