<![CDATA[Smart Home Automation Forum

<![CDATA[Smart Home Automation Forum - Portal]]> https://www.kincony.com/forum/ Sat, 17 Oct 2026 14:57:29 +0000 MyBB <![CDATA[[Bug] A16v3 KCS 3.27.2 - SHT30/SHT31 fails after software reboot]]> https://www.kincony.com/forum/showthread.php?tid=9872 Sat, 17 Oct 2026 02:04:41 +0800 rokrok]]> https://www.kincony.com/forum/showthread.php?tid=9872 Hardware:

KC868-A16v3
KCS v3.27.2
KinCony SHT30 temperature/humidity sensor
I2C address 68 decimal (0x44)

Problem:
After a complete 12 V power cycle, the SHT30 works immediately and temperature/humidity values are displayed normally.
However, if I use Reboot from the KCS web interface, the sensor stops working.
The application log then shows:

Code:
i2c.master: I2C transaction unexpected nack detected

i2c.master: s_i2c_synchronous_transaction(872): I2C transaction failed

i2c.master: i2c_master_transmit(1074): I2C transaction failed

sensor: sht31 error, id=0

KCS retries the sensor, but it may remain unavailable.
How to reproduce:

Power off the whole A16v3 (12 V supply).
Power it on again.
SHT30 data appears immediately and works normally.
In the KCS web interface select Reboot.
After the reboot the SHT30 is no longer available and the log reports I2C NACK / sht31 error.
Remove 12 V power completely and power the A16v3 again.
SHT30 works immediately again.

I have tested this with two different SHT30 sensors.
Initially one sensor had an extended cable, so I suspected the I2C cable length. I then tested a second SHT30 with its original unmodified cable, and it failed immediately after the first KCS software reboot in exactly the same way.
Therefore the cable extension is not the cause.
A complete power cycle of the A16v3/sensor consistently restores operation, while a KCS software reboot can cause the sensor to fail.
It looks like the SHT30/I2C bus or sensor is not being correctly reset/reinitialized after an ESP32 software reboot.
Could you please reproduce this with an A16v3 + SHT30 and check the sensor/I2C initialization after software reboot?]]> Hardware:

KC868-A16v3
KCS v3.27.2
KinCony SHT30 temperature/humidity sensor
I2C address 68 decimal (0x44)

Code:
i2c.master: I2C transaction unexpected nack detected

i2c.master: s_i2c_synchronous_transaction(872): I2C transaction failed

i2c.master: i2c_master_transmit(1074): I2C transaction failed

sensor: sht31 error, id=0

KCS retries the sensor, but it may remain unavailable.
How to reproduce:

Power off the whole A16v3 (12 V supply).
Power it on again.
SHT30 data appears immediately and works normally.
In the KCS web interface select Reboot.
After the reboot the SHT30 is no longer available and the log reports I2C NACK / sht31 error.
Remove 12 V power completely and power the A16v3 again.
SHT30 works immediately again.

AIO-Hybrid-temperature-1.jpg (Size: 373.33 KB / Downloads: 27)

.jpg

4-20mA-temperature-sensor.jpg (Size: 127.23 KB / Downloads: 30)

.png

KCS-4-20mA-setting.png (Size: 48.75 KB / Downloads: 26)

.png

KCS-temperature.png (Size: 21.84 KB / Downloads: 28) ]]>
.jpg

AIO-Hybrid-temperature-1.jpg (Size: 373.33 KB / Downloads: 27)

.jpg

4-20mA-temperature-sensor.jpg (Size: 127.23 KB / Downloads: 30)

.png

KCS-4-20mA-setting.png (Size: 48.75 KB / Downloads: 26)

.png

KCS-temperature.png (Size: 21.84 KB / Downloads: 28) ]]> <![CDATA[KC868-A32 - TCP comunication problem]]> https://www.kincony.com/forum/showthread.php?tid=9869 Wed, 14 Oct 2026 14:49:39 +0800 Dm81]]> https://www.kincony.com/forum/showthread.php?tid=9869 I had to replace my kc868-H32B board (which worked for more than 4 years without problems) with the new kc868-32 board. The problem is that when I press the inputs a few times or turn the outputs on and off, the board loses connection (I observe this from the board's web server). The installed firmware is v2.2.14, and only the TCP server is active.
I had already reported this problem in the past with the kc868-a8 board and it seemed to be resolved, but that one also used to freeze often.
I can't understand where the problem is.
Do you have any suggestions or software to test this problem?
Thank you]]> I had to replace my kc868-H32B board (which worked for more than 4 years without problems) with the new kc868-32 board. The problem is that when I press the inputs a few times or turn the outputs on and off, the board loses connection (I observe this from the board's web server). The installed firmware is v2.2.14, and only the TCP server is active.
I had already reported this problem in the past with the kc868-a8 board and it seemed to be resolved, but that one also used to freeze often.
I can't understand where the problem is.
Do you have any suggestions or software to test this problem?
Thank you]]> <![CDATA[IFTTT]]> https://www.kincony.com/forum/showthread.php?tid=9865 Mon, 12 Oct 2026 21:48:46 +0800 newdos]]> https://www.kincony.com/forum/showthread.php?tid=9865
I wanted to use KCS firmware and IFTTT to control a relay on and off, by using an adc input from a potentiometer which would act as the temp setpoint, then if actual temp measured by temp sensor was below the adc setpoint, it switches the relay on. Problem seems to be you cannot use the actual adc value in ifttt to comapre to the temp sensor value(unless you tell me otherwise). So it looks like I will have to use arduino code. So my question would be how do i then monitor all the inputs, outputs, sdcvalues and temp sensors etc. Do I have to use home assistant or arduino web server Tasmota etc ?? no isea what is the best way to do this ?

TIA]]>
I wanted to use KCS firmware and IFTTT to control a relay on and off, by using an adc input from a potentiometer which would act as the temp setpoint, then if actual temp measured by temp sensor was below the adc setpoint, it switches the relay on. Problem seems to be you cannot use the actual adc value in ifttt to comapre to the temp sensor value(unless you tell me otherwise). So it looks like I will have to use arduino code. So my question would be how do i then monitor all the inputs, outputs, sdcvalues and temp sensors etc. Do I have to use home assistant or arduino web server Tasmota etc ?? no isea what is the best way to do this ?

TIA]]> <![CDATA[SSD not visible for install home assistant in pi imager]]> https://www.kincony.com/forum/showthread.php?tid=9864 Sat, 10 Oct 2026 16:20:56 +0800 Verresen]]> https://www.kincony.com/forum/showthread.php?tid=9864 <![CDATA[KC868-AI mDNS problem]]> https://www.kincony.com/forum/showthread.php?tid=9863 Sat, 10 Oct 2026 15:14:45 +0800 Konrad]]> https://www.kincony.com/forum/showthread.php?tid=9863 Let me start from the biegining.
I bought last year one KC868-AI and configured with HA on RPi5 and it works till now on firmware 2.2.18.
Last week I got two new boards for my new project I set one up on 2.2.21 firmware, also I got new RPI5 with HA flashed on it.
My problem is that I can't connect it to Home Assistant becase it can't see KC board by mDNS.
HA can see the board becase on ESP add on it has "Available" status.
KC works with static IP 192.168.1.230
I can't add manually Integration because I get this:

"Unable to connect to the ESPHome device. Make sure the device’s YAML configuration includes an `api` section."
Of course there's a line for API in the code.
I can ping KC board from Terminal in HA, I can log on to the board, but HA can't find it.
New RPi and KC boards are in same network. New set up of HA can find old board by mDNS, it is finding also all of my hardware by mDNS just not this board so it seems it's not the network.

Solutions I tried:
Downgrading to 2.2.18,
Changing name of the board in code,
Setting up new network on different TP-link router,
Setting up API without password in code,
Reseting compilation environment,
Uploading simple configuration with just few lines,
Changing port in yaml and tried to connect on different port,

Nothing worked. Need help, any solution?
I uploaded yaml in ZIP. Don't worry about encrypion keys, I'll change them later.

.png

Zrzut ekranu 2026-10-10 085324.png (Size: 29.42 KB / Downloads: 74)

.zip

868aidev1.zip (Size: 4.18 KB / Downloads: 26) ]]> Let me start from the biegining.
I bought last year one KC868-AI and configured with HA on RPi5 and it works till now on firmware 2.2.18.
Last week I got two new boards for my new project I set one up on 2.2.21 firmware, also I got new RPI5 with HA flashed on it.
My problem is that I can't connect it to Home Assistant becase it can't see KC board by mDNS.
HA can see the board becase on ESP add on it has "Available" status.
KC works with static IP 192.168.1.230
I can't add manually Integration because I get this:

"Unable to connect to the ESPHome device. Make sure the device’s YAML configuration includes an `api` section."
Of course there's a line for API in the code.
I can ping KC board from Terminal in HA, I can log on to the board, but HA can't find it.
New RPi and KC boards are in same network. New set up of HA can find old board by mDNS, it is finding also all of my hardware by mDNS just not this board so it seems it's not the network.

Solutions I tried:
Downgrading to 2.2.18,
Changing name of the board in code,
Setting up new network on different TP-link router,
Setting up API without password in code,
Reseting compilation environment,
Uploading simple configuration with just few lines,
Changing port in yaml and tried to connect on different port,

Nothing worked. Need help, any solution?
I uploaded yaml in ZIP. Don't worry about encrypion keys, I'll change them later.

.png

Zrzut ekranu 2026-10-10 085324.png (Size: 29.42 KB / Downloads: 74)

.zip

868aidev1.zip (Size: 4.18 KB / Downloads: 26) ]]> <![CDATA[KC868-A16 and Tuya]]> https://www.kincony.com/forum/showthread.php?tid=9861 Fri, 09 Oct 2026 16:35:34 +0800 newdos]]> https://www.kincony.com/forum/showthread.php?tid=9861
just got my board working now but I cannot use the tuya app. Whenever i scan the QR code from within KCS I just get the message 'Device_already_bind' (see pic) and therefore the board does appear in the app so rendering app of no use. The licence is all enabled in KCS (see pic). Thanks for your help.

.jpg

09-10-2026 09-23-55.jpg (Size: 69.17 KB / Downloads: 73)

.png

IMG_0215.PNG (Size: 377.48 KB / Downloads: 76) ]]>
just got my board working now but I cannot use the tuya app. Whenever i scan the QR code from within KCS I just get the message 'Device_already_bind' (see pic) and therefore the board does appear in the app so rendering app of no use. The licence is all enabled in KCS (see pic). Thanks for your help.

.jpg

09-10-2026 09-23-55.jpg (Size: 69.17 KB / Downloads: 73)

.png

IMG_0215.PNG (Size: 377.48 KB / Downloads: 76) ]]> <![CDATA[N30 (KCS): energy counters of BL0910 #2 and #3 published as 0 kWh at boot]]> https://www.kincony.com/forum/showthread.php?tid=9860 Fri, 09 Oct 2026 16:34:06 +0800 dominique_manas@hotmail.com]]> https://www.kincony.com/forum/showthread.php?tid=9860
I found an issue with the energy counters on the N30 running KCS firmware (version: v3.27.2), integrated in Home Assistant through MQTT discovery.

What happens:
Each time the N30 restarts (firmware flash, power cut, reboot), the channels of BL0910 #2 and #3 (Energy 2 and Energy 3, all 10 channels each, plus energy_total) publish energy = 0 kWh for a moment, then the real value again a few seconds later.
BL0910 #1 (Energy 1) does not do this. Its channels only go unavailable during the restart and come back with the correct value, never 0.

The counters are not lost inside the N30: after the restart the values continue from where they were (e.g. 258.062 kWh -> 0 -> 258.062 kWh).

Why it is a problem:
Home Assistant treats energy sensors as increasing counters (state_class: total_increasing). A drop to 0 is seen as a meter reset, and the return to the real value is counted as new consumption.
This morning the N30 restarted 3 times after a firmware flash. Each channel of Energy 2 and Energy 3 was counted as consuming its whole counter value 4 times. For example, one channel with 258 kWh got 1032 kWh of phantom consumption added in one morning. I had to correct the statistics by hand.

Request:
Please do not publish energy values until the real counters have been read from the BL0910 chips at boot. Publishing nothing (or keeping the previous retained value) is fine. Publishing 0 is not.
It would also help to know why only chips #2 and #3 behave like this and not chip #1.

Thank you.]]>
I found an issue with the energy counters on the N30 running KCS firmware (version: v3.27.2), integrated in Home Assistant through MQTT discovery.

What happens:
Each time the N30 restarts (firmware flash, power cut, reboot), the channels of BL0910 #2 and #3 (Energy 2 and Energy 3, all 10 channels each, plus energy_total) publish energy = 0 kWh for a moment, then the real value again a few seconds later.
BL0910 #1 (Energy 1) does not do this. Its channels only go unavailable during the restart and come back with the correct value, never 0.

The counters are not lost inside the N30: after the restart the values continue from where they were (e.g. 258.062 kWh -> 0 -> 258.062 kWh).

Why it is a problem:
Home Assistant treats energy sensors as increasing counters (state_class: total_increasing). A drop to 0 is seen as a meter reset, and the return to the real value is counted as new consumption.
This morning the N30 restarted 3 times after a firmware flash. Each channel of Energy 2 and Energy 3 was counted as consuming its whole counter value 4 times. For example, one channel with 258 kWh got 1032 kWh of phantom consumption added in one morning. I had to correct the statistics by hand.

Request:
Please do not publish energy values until the real counters have been read from the BL0910 chips at boot. Publishing nothing (or keeping the previous retained value) is fine. Publishing 0 is not.
It would also help to know why only chips #2 and #3 behave like this and not chip #1.

Thank you.]]> <![CDATA[Bricked KC868-A16]]> https://www.kincony.com/forum/showthread.php?tid=9859 Wed, 07 Oct 2026 23:46:31 +0800 newdos]]> https://www.kincony.com/forum/showthread.php?tid=9859 <![CDATA[It looks like it's broken.]]> https://www.kincony.com/forum/showthread.php?tid=9857 Tue, 06 Oct 2026 09:39:02 +0800 abc123]]> https://www.kincony.com/forum/showthread.php?tid=9857