When cloning, the system gives an error
I saved your branch from git and extracted the component folder from it - kincony_hx.
Placed this component in the custom_components folder and rebooted the server.
Question. What to do next?
What parameters should be set in the configuration file. Or what other steps to take
It works. Switch on switch off. I don’t know about digital inputs, how to connect them in this integration. And another question, Is the state of the switches remembered in the system?
As far as I know, this integration does not read any digital inputs. It only reads/writes the state of the relays. I have only tested the output relays. I don’t know if the state is remembered, but it is polled every x seconds.
Hello, how to read the status of digital inputs D1-D32? When the contacts are closed to GND, the mqtt explorer displays a change in the state of the inputs, but when trying to create a binary sensor on the mqtt platform, it does not respond to a change in the state of the physical input
And one more question, is it possible to control the relay output of another channel with a double click, for example, double click D1 turns on output 32?
Hello @KinCony
Do you have sellers in Europe? Or just sell on Aliexpress and Alibaba?
Thank you for your reply
yes, we only sell from Aliexpress or alibaba online store.
@KinCony Is it possible to reflash your voice module based on ESP8266 so that the old version KC868-H32 relay module can fully function with the Esphome protocol?
Alternatively, is it possible to replace the board on the voice module with an ESP32 board for this purpose?
Is it possible to reflash your voice module based on ESP8266 so that the old version KC868-H32 relay module can fully function with the Esphome protocol? >> sorry, this can’t.
is it possible to replace the board on the voice module with an ESP32 board for this purpose? >> you can add tuya adapter, that have ESP32 on adapter. will support use by tuya app and voice control by alexa and google home directly, but it’s not use for ESPHome.
I meant to create a transitional device from the voice module that can control the KC868-H32 module via the RS232 port using the Esphome protocol. This way, I can update the outdated device.
ok, sure, you can create “UART Switch” in home assistant according to H32 relay controller’s STRING format protocol.
Could you make a lesson on this topic or provide an example code for Esphome?
do you already have the ESP8266 voice module?
Yes, I have one of the earliest equipment sets.
KinCony KC868-H32 controller, voice control module on ESP8266, and a manual control board.
But unfortunately, I don’t have an RS232 MULTI SERIAL ADAPTER to connect them simultaneously. They have been out of sale for a long time.
I would like to know how I can connect the Voice Module and Manual Control Board at the same time.
There might be a solution on how to accomplish this.
I’m looking to utilize the Voice Module to control the KinCony KC868-H32 controller using ESPHOME.
I’m wondering if anyone has experience or suggestions on how to set up this configuration.
I think the best way is replace with KC868-H32B Pro smart relay controller, it support tuya app, alexa,google home, Apple Homekit and home assistant at the same time. Don’t wrong, we can send you one KC868-H32B+KC868-AK board (instead of manual control board), free for you, because of your topic has a long history and has also helped many DIYers. If you want, you can contact us by whatsapp.
2 Likes
Hello everyone, what is the current status for the support of these board in HA? Any long-term feedback form actual users? Thank you!
Hi Xilviu.
I bought a KC868-H32B back in July 2021 and although the hardware looks sturdy, the software is faulty: it keeps disconnecting from the MQTT server and the only way to get it back is to power it off, wait 12 hours and then power it on again.
Additionally, I had bought the 32 relay version because I expected to drive my heating system (4 valves and a pump) but after a couple of hours, the system was not longer responding, although I had inserted their RC snubber circuit as recommended.
Since then, I migrated from a Mosquitto server to EMQX, mostly to be able to monitor the Kincony connection to MQTT thru API calls to EMQX.
In terms of reliability, it did not change anything but at least, I was aware as soon as the Kincony mqtt connection dropped.
The support is very limited and hard to understand and I got so frustrated with the last disconnection that I decided to replace the Kincony by a way cheaper 8 channel Dingtian device.
Setup was a breeze and as mentioned in other posts, asking for a developer version upon finalizing the purchase, it can be flashed with ESPhome.
So far so good but only time will tell whether it was a good move.
Here is an update after 3 weeks of running the Dingtian device.
As long as Home Assistant and EMQX are running continuously, the Dingtian works flawlessly.
If either Home Assistant or EMQX are restarted, the Dingtian reconnects to EMQX but all sensors and switches become unavailable.
I fixed it in the same way than the Dahua2MQTT add-in by restarting the Dingtian a couple of minutes after either EMQX or Home Assistant is restarted.
Unlike the Kincony, it works 100% of the time 
I’m now thinking about buying another one to give it a try with ESPhome.
1 Like
Thank you for the info. This doesn’t look very promising. I am awaiting delivery for the same one (KC868-H32B), I will let you know how the tests go.
@bigramon I am now running the module for a test phase; so far it looks good. I did not use MQTT: I just setup the module in the TCP server mode, and I’m using the integration available here:
Maybe you can also give it a try.
I will report back as I test it further.