esphome / esphome/feature-requests
Custom networking components
- Dominant language
- No language data
- Stars
- 450
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the problem you have/What new integration you would like**
ESPHome has hardcoded dependency to AsyncTCP.
It would be great if at least api server can use other communication options.
E.g. Having ESPHomeTCP interface - fallback connectivity scenarios can be possible. Or new ways of communication using serial, i2c, lo-ra...
**Please describe your use case for this integration and alternatives you've tried:**
For my home automation I would rather try to use wired-serial communication with devices as much as possible. Would someone else be interested in alternative networking implementations?
Following things might become possible:
- usb attached devices
- one wire mesh
- long range radio
- vpn, proxyng
- mocked api clients for unit testing
**Additional context**
I am ready to start working on this kind of component
1. extract AsyncTCP-like interface for esphome just enough for api server
1. Add default implementation using AsyncTCP
1. Add possibility to create custom c++ networking components.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.