v3.19.1 improvement:

Fixed PCF8574 driver issue for F4

Attached Files

  KCS_B8M_V3.19.1.zip (Size: 1.14 MB / Downloads: 69)
  KCS_B16_V3.19.1.zip (Size: 1.14 MB / Downloads: 56)
  KCS_B16M_V3.19.1.zip (Size: 1.14 MB / Downloads: 49)
  KCS_B24_V3.19.1.zip (Size: 1.14 MB / Downloads: 44)
  KCS_B24M_V3.19.1.zip (Size: 1.14 MB / Downloads: 42)
  KCS_B32M_V3.19.1.zip (Size: 1.14 MB / Downloads: 52)
  KCS_DM16_V3.19.1.zip (Size: 1.11 MB / Downloads: 41)
  KCS_F4_V3.19.1.zip (Size: 1.13 MB / Downloads: 45)
  KCS_F8_V3.19.1.zip (Size: 1.13 MB / Downloads: 51)
  KCS_F16_V3.19.1.zip (Size: 1.14 MB / Downloads: 57)
  KCS_F24_V3.19.1.zip (Size: 1.14 MB / Downloads: 48)
  KCS_F32_V3.19.1.zip (Size: 1.14 MB / Downloads: 45)
  KCS_G1_V3.19.1.zip (Size: 1.1 MB / Downloads: 40)
  KCS_KC_TA_V3.19.1.zip (Size: 1.09 MB / Downloads: 52)
  KCS_N10_V3.19.1.zip (Size: 1 MB / Downloads: 54)
  KCS_N20_V3.19.1.zip (Size: 1 MB / Downloads: 43)
  KCS_N30_V3.19.1.zip (Size: 1 MB / Downloads: 45)
  KCS_N60_V3.19.1.zip (Size: 1.02 MB / Downloads: 46)
  KCS_A2V3_V3.19.1.zip (Size: 1.11 MB / Downloads: 59)
  KCS_A6V3_V3.19.1.zip (Size: 1.08 MB / Downloads: 56)
  KCS_A8V3_V3.19.1.zip (Size: 1.13 MB / Downloads: 52)
  KCS_A16V3_V3.19.1.zip (Size: 1.15 MB / Downloads: 106)
  KCS_A32PRO_V3.19.1.zip (Size: 1.11 MB / Downloads: 58)
  KCS_AG8_V3.19.1.zip (Size: 1.09 MB / Downloads: 42)
  KCS_AIO_HYBRID_V3.19.1.zip (Size: 1.32 MB / Downloads: 44)
  KCS_ALR_V3.19.1.zip (Size: 1.08 MB / Downloads: 44)
  KCS_B8_V3.19.1.zip (Size: 1.14 MB / Downloads: 44)
  KCS_T16M_V3.19.1.zip (Size: 1.09 MB / Downloads: 40)
  KCS_T32M_V3.19.1.zip (Size: 1.11 MB / Downloads: 44)
  KCS_T64M_V3.19.1.zip (Size: 1.11 MB / Downloads: 54)
  KCS_T128M_V3.19.1.zip (Size: 1.11 MB / Downloads: 51)
  KCS_TR_V3.19.1.zip (Size: 1.06 MB / Downloads: 44)
  KCS_Z1_V3.19.1.zip (Size: 1.24 MB / Downloads: 39)

Purchased a Kincony Z1 controller last week.

Located the newest firmware. v3.18.0

launched the flash download tool 3.9.2

Settings at esp32s3, usb

My com port is COM4.

open my firmware v3.18.0, all default settings.

I hit "START", and nothing..  ??

Is there a button that I have to hit on the Z1 unit?

Couldn't find the Z1 forum here, sorry if in wrong area.

Thank you, looking forward to this Z1 being added to my system.

-Richard

Dear Support Team,

I am writing to request technical assistance regarding the Kincony N30 power monitoring controller. I am currently using the device with ESPHome via the Modbus interface (reading the BL0910 chips).

While the device is functioning correctly in terms of connectivity, I have encountered a significant limitation regarding energy consumption data.

The Issue: The Modbus energy registers (e.g., addresses 140, 142, etc., for Chip 1) only return integer values. Even when the sensors are configured to display 3 or more decimal places in ESPHome, the
data received from the device is always a whole number (e.g., 0.000 kWh, 1.000 kWh).

Technical Details:
Device: Kincony N30 (ESP32-S3 with W5500 Ethernet).
Interface: Modbus RTU over UART.

Observations: The Voltage (V) and Power (W) registers provide high-resolution data with correct decimals. However, the Energy (kWh) registers do not seem to transmit fractional increments.

Log evidence: My logs confirm the device is sending states like 0.00000 kWh even when a load is active, and only jumps to the next whole number after a full kWh has been consumed.
Example log snippet: [sensor:135]: 'bl0910_1_energy_1': Sending state 0.00000 kWh with 3 decimals of accuracy

My Questions:
Does the current firmware of the Kincony N30 support fractional energy readings (e.g., Wh or 0.001 kWh increments) via Modbus? Is there a specific multiplier or a different register address I should use to obtain higher-resolution energy data? Is there a firmware update available that addresses this resolution limitation?

Thank you for your assistance!

smoke sensor user manual:
  smoke_sensor_user_manual.pdf (Size: 2.56 MB / Downloads: 57)

wired gas sensor manual:
  gas-sensor-manual.pdf (Size: 1.84 MB / Downloads: 55)

Hi

I have A32 PRO board. I used KCS firmware. i'm a beginner with Home assistant and ESP. Today i was trying to integrate this with Home Assistant. I used .yaml file by ESPHome builder in HA, but i didnt know that this erase KCS firmware. Now when i try to flash KCS board didnt response on this. After flash in console i see:

Uploading stub...
Running stub...
Stub running...

is stub and send flash finish


But board didnt work. When I flash .yaml for esp home board is connect with HA, but for now i need KCS firmware, i have to fast repair ligts control by switches, becouse my wife is mad now ;d. 

Can you help me?

RU

Привет!
KCS в целом рабочая система, но настройка IFTTT через веб-интерфейс получается громоздкой, особенно когда нужно быстро и массово сопоставить входы и выходы (например DI1 → DO1 toggle и так далее).

Я сделал небольшое браузерное расширение (без Node-RED и без перепрошивок), которое добавляет на страницу /ifttt.html компактную панель для массовой настройки:

автоматическое определение DI/DO (из cookie Device, input_num / output_num)

Fill 1–16 / Fill 1–DOmax / Fill all (1–DImax)

массовое применение правил через POST /ifttt/save_channel

выбор триггера (single / double / hold / edges) и действия ON / OFF / TOGGLE

Скачать:
https://npekpacho.ru/downloads/kcs-mass-mapper-ext.zip

Было бы здорово увидеть официальный “bulk IFTTT mapper” прямо в KCS. Такая функция реально экономит время, а обещания «скоро добавим» длятся уже не первый год ?

EN

Hi!
KCS is a functional system, but the IFTTT web UI becomes quite heavy when you need fast bulk DI→DO mapping (for example DI1 → DO1 toggle for many channels).

I made a small browser extension (no Node-RED, no firmware changes) that adds a compact bulk-mapping panel to /ifttt.html:

automatic DI/DO detection (from the Device cookie: input_num / output_num)

Fill 1–16 / Fill 1–DOmax / Fill all (1–DImax)

bulk rule application via POST /ifttt/save_channel

trigger selection (single / double / hold / edges) and action ON / OFF / TOGGLE

Download:
https://npekpacho.ru/downloads/kcs-mass-mapper-ext.zip

It would be great to see an official “bulk IFTTT mapper” built directly into KCS. This kind of feature saves a lot of time, and the “coming soon” promise seems to be going on for years ?

Am I missing something on the site - do you make a diver to go over the front of this like I have for my F16?  The F16 is a cracking product but I need a second and would prefer PoE if possible, but due to location it must have a cover. 

Thank you,

S.

Hello,

Is the schematic diagram available for the B8M?
I am specifically looking to see if the INT pin 1 of the PCF8575 is connected to anything.
I have used the PCF8575 IC in other applications, and prefer to use the interrupt when possible.

Thank You

Hi Admin

Using ESPHome and Homeassistant, the publish_initial_state warning has been there for some time when compiling.  Is this an option we fix in YAML or something the ESPHome people will sort with their code ?

WARNING GPIO5 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq/#why-am-i-...pping-pins
WARNING The 'publish_initial_state' option has been replaced by 'trigger_on_initial_state' and will be removed in a future release
WARNING The 'publish_initial_state' option has been replaced by 'trigger_on_initial_state' and will be removed in a future release

Many Thanks..Peter