Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Request: Support TCP Connections to CC2530 #665
Downlad the lastest https://github.com/letscontrolit/ESPEasy/releases
When it is ready close the flashing tool
Then its complete the device will get devicename ESP-Easy-0 check your router for the IP or you will get directed after the setup of the Wifi the first time you connected to the device.
You can also try to use ser2net on Linux then use that port.
sudo socat -d -d pty,raw,echo=0,link=/dev/zigbee tcp-connect:IP:PORT
NOTE THIS! Make sure the zigbee2mqtt is not using the same channel as WIFI.
I have been using a similar configuration to this for months, but using an OpenWrt AP with USB connected CC2531 instead of ESP8266 with UART connected CC2530. (I am also using the same principle in a different location with CC2530 connected to OpenWrt AP via USB UART dongle, but this is less elegant).
I am using ser2net on the OpenWrt remote radio side, and socat on the zigbee2mqtt server side. The server side is a bit complicated with an extra systemd unit for socat and dependencies etc. Despite this complexity and to my surprise, it has been working flawlessly.
Allowing direct specification of a TCP endpoint in zigbee2mqtt would greatly simplify this case, which is what I believe Eistee is requesting. I'm sure there are also people running zigbee2mqtt in containers who would appreciate this.
e.g. rather than
configuration could be like
This would require adding TCP support to zigbee-shepherd (bypassing serialport) and updating zigbee2mqtt to pass through the configuration.
My systemd unit files for socat and zigbee2mqtt
And the relevant part of my zigbee2mqtt configuration.yaml