08-16-2025, 01:05 AM
Hi, thanks for the quick answer and the video tours.
I noticed in the videos you’re using a board that has ESP32 + RS-485 together, alongside the Server-Mini (CM4). I only have the Server-Mini (no ESP32 board).
Questions/clarifications:
1. Is an ESP32 board (e.g., KC868-A8S) required?
The repo you shared (https://github.com/hzkincony/esphome-kc868-ha) is not a Home Assistant add-on repository. It’s an ESPHome external component, which runs on an ESP32 and speaks the HAv2 private RS-485 protocol.
→ If I only have the Server-Mini (CM4) with its RS-485 pins on GPIO14/15, can I still integrate HAv2 directly without an ESP32?
2. If direct CM4 ↔ HAv2 over RS-485 is supported (no ESP32):
• Please share the actual Home Assistant integration/add-on (HACS repo or Docker image) that talks the HAv2 private protocol over serial.
• Minimal config example would help (serial device path /dev/ttyS0 or /dev/ttyAMA0, baud/parity, how to list multiple HAv2 boards by address, and how entities are exposed—MQTT discovery vs native HA integration).
• Any docs/SDK/protocol description for the CM4 path are appreciated (even under NDA).
3. If direct CM4 is not supported:
• Please confirm the official path is to use an ESP32 + RS-485 transceiver running ESPHome with your kc868_ha component, and that the Server-Mini only hosts Home Assistant.
• In that case I’ll add an ESP32 bridge.
4. Alternative firmware option:
• You mentioned you can “send change baud rate protocol.” Do you also provide a Modbus RTU firmware for HAv2? If yes, I can use HA’s built-in Modbus integration over the Server-Mini’s RS-485 port. A register map (coils/inputs/holding regs) would be great.
My setup constraints:
• Hardware: Server-Mini (CM4) with RS-485 on GPIO14 (TX) / GPIO15 (RX).
• Goal: Control multiple HAv2 boards on the same bus.
• Preference: Direct CM4 ↔ RS-485 if supported; otherwise I’ll add an ESP32.
It would be great if you can send me change bout rate protocol for bulk provisioning.
Thanks for clarifying which of the two paths is officially supported on a Server-Mini-only setup, and for the correct repo/instructions if the CM4 direct serial path exists.
I noticed in the videos you’re using a board that has ESP32 + RS-485 together, alongside the Server-Mini (CM4). I only have the Server-Mini (no ESP32 board).
Questions/clarifications:
1. Is an ESP32 board (e.g., KC868-A8S) required?
The repo you shared (https://github.com/hzkincony/esphome-kc868-ha) is not a Home Assistant add-on repository. It’s an ESPHome external component, which runs on an ESP32 and speaks the HAv2 private RS-485 protocol.
→ If I only have the Server-Mini (CM4) with its RS-485 pins on GPIO14/15, can I still integrate HAv2 directly without an ESP32?
2. If direct CM4 ↔ HAv2 over RS-485 is supported (no ESP32):
• Please share the actual Home Assistant integration/add-on (HACS repo or Docker image) that talks the HAv2 private protocol over serial.
• Minimal config example would help (serial device path /dev/ttyS0 or /dev/ttyAMA0, baud/parity, how to list multiple HAv2 boards by address, and how entities are exposed—MQTT discovery vs native HA integration).
• Any docs/SDK/protocol description for the CM4 path are appreciated (even under NDA).
3. If direct CM4 is not supported:
• Please confirm the official path is to use an ESP32 + RS-485 transceiver running ESPHome with your kc868_ha component, and that the Server-Mini only hosts Home Assistant.
• In that case I’ll add an ESP32 bridge.
4. Alternative firmware option:
• You mentioned you can “send change baud rate protocol.” Do you also provide a Modbus RTU firmware for HAv2? If yes, I can use HA’s built-in Modbus integration over the Server-Mini’s RS-485 port. A register map (coils/inputs/holding regs) would be great.
My setup constraints:
• Hardware: Server-Mini (CM4) with RS-485 on GPIO14 (TX) / GPIO15 (RX).
• Goal: Control multiple HAv2 boards on the same bus.
• Preference: Direct CM4 ↔ RS-485 if supported; otherwise I’ll add an ESP32.
It would be great if you can send me change bout rate protocol for bulk provisioning.
Thanks for clarifying which of the two paths is officially supported on a Server-Mini-only setup, and for the correct repo/instructions if the CM4 direct serial path exists.