Three Dominant Themes
| Theme | Supporting Quote(s) |
|---|---|
| 1. High cost and implementation complexity of PoE/Ethernet | “PoE is not obvious to implement … uses more expensive components, takes up more space, makes emissions certification harder… a bag of worms you’d rather avoid.” – jwr “It gets considerably more expensive when you want to place any meaningful data signal nearby.” – solarkraft “Ethernet is already one of the most expensive standards because you need magnetics for isolation. Adding power on top of that is genuinely expensive.” – throwup238 |
| 2. Confusing ESP‑32 naming/lineage and lack of clear roadmap | “The ESP32‑S3 is called “S3”, but this part doesn’t look like a simple S3 variant … there is no E21 or plain E2.” – lwrless “Given their history, I’d guess < $6 a piece for a dev board, <$2 for the chip at scale.” – ricardobeat References to older chips (RMII, ESP32‑POE boards) illustrate the shifting naming scheme.” – elcritch |
| 3. Desire for more integrated or cheaper alternatives (e.g., single‑pair Ethernet, Thread) | “I’m more hopeful for single‑pair Ethernet … deterministic, faster than CANBUS, with power delivery.” – elcritch “A full‑module add‑on in this power class is about $7 at 1k units; custom PCB could drop it to $3.” – easygenes “Just like a coffee machine gets pricier when you add espresso or milk, adding PoE raises cost dramatically.” – ldng |
TL;DR
- PoE/Ethernet integration is pricey and cumbersome, due to magnetics, isolation, certification, and component costs. - Espressif’s naming scheme is erratic (S3, S31, E22) leaving users uncertain about chip families and pricing expectations.
- Many wish for cheaper, more integrated alternatives (single‑pair Ethernet, Thread) and better value‑priced modules.
These three threads best capture the discussion’s focus on cost, naming confusion, and the search for more efficient networking solutions.