Hello,

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 seem to have totally bricked my KC868-A16 rev 1.6.   Was trying to download arduino code to it which it did but never worked so then tried to put KCS back on the board which Downloaded mok but the board appears dead no lights on ethernet port at all.  I have since done an erase and reload KCS with the download tool and no joy.  HELP!!!

ACT PSU 继电器指示灯交替闪烁——短暂亮起然后熄灭——并且设备无法连接到 Home Assistant。

Hello,
I would like to buy a Kincony N10, but before I do, I’d like to know if it supports bidirectional reading for solar generation in ESPHome.
thx

Hey,

I've got a kinkony a16 board running esphome connected through ethernet cable to homeassistant.

[*]Installation method Home Assistant OS:
[*]Core 2025.9.4
[*]Supervisor 2026.09.3
[*]Operating System 16.2 

[*]ESPHome Device Builder:
 
Current version: 2025.9.2

[*]Everything works as expected but I need to update. I've updated esphome to 2026.9.1 without updating homeassistant and all the switches gone offline. I've done a restart then I just restored the previous system and all works again.

[*]Does the board require some special settings for esphome 2026.9.1 ?

Thanks!
[*]

Hi everyone,

I'm Ihor from Ukraine. For the past months we've been building oCBot — firmware and a cloud workspace that turn the KC868-A6 and KC868-A16 into process controllers for farms, homesteads and craft production. Our first use case is distilling; the same core runs cheesemaking, fermentation and greenhouses.

What it does on the board today:

• flashing from the browser in a couple of minutes, no toolchain;
  
• DS18B20 probes, analog inputs, RS485/Modbus devices, relays and PWM outputs;
  
• scenarios that drive a process stage by stage and only call the operator when a decision is needed;
  
• operator panels assembled from buttons and gauges without code, opened from a phone over Wi-Fi or remotely through our cloud (optional);
  
• several controllers working as one system, with a log of every run.
  

• After an OTA update or a reset (RST button, EN, esp_restart) the Ethernet link flaps and never gets an IP — only Wi-Fi comes up. A full power cycle brings Ethernet back. As far as we can tell from the schematic, the LAN8720 nRST is on RST_NET, which is not wired to any ESP32 GPIO, so firmware cannot reset the PHY itself. A software retry (esp_eth_stop/start) did not help on our boards. Our workaround: use the Wi-Fi address after OTA, power-cycle for LAN.
  
• There is no free DAC on the A16: GPIO25/26 are taken by the Ethernet RMII.
  

Attached Files

Thumbnail(s)
   
Image(s)
           

Getting inconsistent/wrong sensor readings from N20 over RS485 Modbus RTU — hoping for some guidance.

Setup: N20 connected via RS485 to a Server16 running Home Assistant, using the Modbus RTU integration (baud 38400, matching the N20 Modbus protocol spec).

Issue: Reading the temperature register (offset 64, float, Chip 1) gives inconsistent results. N20's own display shows 33.7°C, but Home Assistant reads back 24.38°C — sometimes correct, sometimes way off (even negative values occasionally). Current/power/energy readings on the integer registers seem fine, it's mainly the float-type registers (temperature, power factor) that come back wrong or inconsistent.

I've already tried:
- Different byte-swap orders (byte swap gives correct values sometimes, but not consistently)
- Re-tightening A/B terminals

Questions:
1. Is there a known/confirmed byte order for the float registers (temp, PF) on N20? The protocol doc mentions "CDBA format" — is there a simpler way to interpret this?
2. Any guidance on termination/grounding recommendations for the RS485 bus on N20 and Server16 specifically?
3. Is there a minimum recommended polling interval to avoid read collisions?

Any help appreciated — thanks!

Attached Files

Image(s)
   

  code.txt (Size: 422 bytes / Downloads: 58)

Hi. What is the situation regarding the analog inputs on the KC868-A6? Are all four 0–5V, or are two 0–5V and two 4–20mA? The reason I ask is that the system block diagram labels two as 0–5V and two as 4–20mA inputs, whereas the wiring diagram shows all four as 0–5V inputs.        

Hi all,

I am building a new home setup, with a Proxmox server hosting Home Assistant, Mosquitto, VictoriaMetrics and Grafana. I am about to install an N30 into my switchboard, and would like to collect data from it into VictoriaMetrics, as well as use the energy data for Home Assistant dashboards and automations. Ideally the energy data would be recorded into VictoriaMetrics at one second intervals, while Home Assistant should deal with a lower frequency of data, e.g. every 30 seconds.

What is the best (not necessarily simplest) way to do this? I can't find much documentation on the relative merits and functionality of the ESPHome vs KCS v3 firmware, how quickly the energy data updates, or which protocol would be best suited. Note the N30 will be connected by Ethernet, and I also have an Elfin EE11 RS485-Ethernet adapter if that's helpful. I'm also happy to install extra software (e.g. Telegraf) into Proxmox if that provides a better solution.

How do you connect a thermistor to an analog input?