At the moment the KC868 inputs are instantaneous which is a problem for signals that glitch occasionally from things like noise coupled onto the input lines.  Would it be possible to add a debounce capability where you can specify that an input has to be asserted for x seconds, x user-settable, before it gets reported as an asserted input?  What I'm thinking of is adding a per-input capability where you can specify that it needs to be asserted for (say) 5 seconds before it's treated as valid.  The overall range would be maybe 0-60s, 0s = instant response, > 0s = input must be asserted for that long before it's reported as asserted.

I have KC868-a8v3.1 board loaded with the current firmware V3.23.2

It is used for switching 24VAC to control AC ducts in conjunction with Home Assistant.

My challenge is that the Rumpus room duct (controlled by DO8 on KC868) is fed from a master upstairs duct (controller by DO2 on KC868) so both ducts need to be open for AC to reach the Rumpus room.
For ease of user operation I would like to setup the a IFTTT rule so that;
1. when a user turns on the Rumpus duct (D08) the upstairs duct will also activate (D02) (turn on could by by HA or RF on the KC868)
2. if the user subsequently turns off the Rumpus duct, the Upstairs duct will remain open.

Also, if the Upstairs duct is turned off, there should be a rule to turn on the Rumpus room duct, this is necessary to reflect through to the HA dashboard.

Using IFTTT I setup an IF condition on the DO8 which performs an action on D02.

I found that this doesn't work properly and the KC web page status indicator for D02 and D08 are not linked corectly by the rule.  At one stage the KC868 crashed and I had to relead the formward with the formward loader tool.

Can you please advise if IFTTT can be used for this sort of rules or is there another way on the KC868 to achieve this.

Regards

Hi.  My G1 isn't connecting to the mobile network.  This happens regularly.  A simple reboot sometimes corrects this but ultimately, a firmware flash is the only way to reinstate mobile connectivity.  However, when I try to re-flash the G1 with KCS_G1_V3.19.1.bin, the flash    
interface starts the erase process but when the installation process starts, it report that the device has been reset to firmware mode?
   

I'm using Tasmota web installer to flash.  It has always worked before.  How can I re-flash the G1?

Thanks in anticipation.

v3.23.2 improvement:
1: fixed undecoded IR signal are currently being reported to Home Assistant via MQTT.
2: fixed an issue where fast-switching relays might cause the system to restart.
3: added support new DM4, DM8, DM32 dimmer board.
4: added OLED screen displays the component loading progress during board startup.
5: added support MQTTS (TLS)

Attached Files

  KCS_A2V3_V3.23.2.zip (Size: 1.16 MB / Downloads: 279)
  KCS_A6V3_V3.23.2.zip (Size: 1.13 MB / Downloads: 251)
  KCS_A8V3_V3.23.2.zip (Size: 1.18 MB / Downloads: 291)
  KCS_A16V3_V3.23.2.zip (Size: 1.2 MB / Downloads: 313)
  KCS_A32PRO_V3.23.2.zip (Size: 1.17 MB / Downloads: 276)
  KCS_AG8_V3.23.2.zip (Size: 1.14 MB / Downloads: 262)
  KCS_AIO_HYBRID_V3.23.2.zip (Size: 1.37 MB / Downloads: 262)
  KCS_ALR_V3.23.2.zip (Size: 1.14 MB / Downloads: 252)
  KCS_B4_V3.23.2.zip (Size: 1.19 MB / Downloads: 231)
  KCS_B4M_V3.23.2.zip (Size: 1.19 MB / Downloads: 228)
  KCS_B8_V3.23.2.zip (Size: 1.19 MB / Downloads: 245)
  KCS_B8M_V3.23.2.zip (Size: 1.19 MB / Downloads: 251)
  KCS_B16_V3.23.2.zip (Size: 1.19 MB / Downloads: 278)
  KCS_B16M_V3.23.2.zip (Size: 1.19 MB / Downloads: 222)
  KCS_B24_V3.23.2.zip (Size: 1.19 MB / Downloads: 266)
  KCS_B24M_V3.23.2.zip (Size: 1.19 MB / Downloads: 222)
  KCS_B32M_V3.23.2.zip (Size: 1.19 MB / Downloads: 248)
  KCS_DM4_V3.23.2.zip (Size: 1.19 MB / Downloads: 243)
  KCS_DM8_V3.23.2.zip (Size: 1.19 MB / Downloads: 238)
  KCS_DM16_V3.23.2.zip (Size: 1.16 MB / Downloads: 250)
  KCS_DM32_V3.23.2.zip (Size: 1.19 MB / Downloads: 231)
  KCS_F4_V3.23.2.zip (Size: 1.18 MB / Downloads: 244)
  KCS_F8_V3.23.2.zip (Size: 1.18 MB / Downloads: 248)
  KCS_F16_V3.23.2.zip (Size: 1.19 MB / Downloads: 270)
  KCS_F24_V3.23.2.zip (Size: 1.19 MB / Downloads: 252)
  KCS_F32_V3.23.2.zip (Size: 1.2 MB / Downloads: 247)
  KCS_G1_V3.23.2.zip (Size: 1.15 MB / Downloads: 244)
  KCS_KC_TA_V3.23.2.zip (Size: 1.15 MB / Downloads: 208)
  KCS_N10_V3.23.2.zip (Size: 1.06 MB / Downloads: 234)
  KCS_N20_V3.23.2.zip (Size: 1.06 MB / Downloads: 227)
  KCS_N30_V3.23.2.zip (Size: 1.06 MB / Downloads: 244)
  KCS_N60_V3.23.2.zip (Size: 1.07 MB / Downloads: 232)
  KCS_T16M_V3.23.2.zip (Size: 1.14 MB / Downloads: 233)
  KCS_T32M_V3.23.2.zip (Size: 1.16 MB / Downloads: 259)
  KCS_T64M_V3.23.2.zip (Size: 1.16 MB / Downloads: 219)
  KCS_T128M_V3.23.2.zip (Size: 1.16 MB / Downloads: 237)
  KCS_TR_V3.23.2.zip (Size: 1.11 MB / Downloads: 242)
  KCS_Z1_V3.23.2.zip (Size: 1.29 MB / Downloads: 273)

v2.2.19 improvement:
1. fixed Tuya app temperature can't work with automation bug.

Attached Files

  KCS_KC868_A8_V2.2.19.zip (Size: 789.73 KB / Downloads: 260)
  KCS_KC868_A8M_V2.2.19.zip (Size: 806.05 KB / Downloads: 209)
  KCS_KC868_A8S_V2.2.19.zip (Size: 807.48 KB / Downloads: 256)
  KCS_KC868_A16_V2.2.19.zip (Size: 797.24 KB / Downloads: 300)
  KCS_KC868_A16S_V2.2.19.zip (Size: 807.61 KB / Downloads: 213)
  KCS_KC868_A32_V2.2.19.zip (Size: 787.34 KB / Downloads: 233)
  KCS_KC868_A32M_V2.2.19.zip (Size: 805.27 KB / Downloads: 218)
  KCS_KC868_A64_V2.2.19.zip (Size: 787.27 KB / Downloads: 218)
  KCS_KC868_A128_V2.2.19.zip (Size: 787.15 KB / Downloads: 227)
  KCS_KC868_AG_V2.2.19.zip (Size: 765.22 KB / Downloads: 209)
  KCS_KC868_AI_V2.2.19.zip (Size: 789.59 KB / Downloads: 221)
  KCS_KC868_AIO_V2.2.19.zip (Size: 807.13 KB / Downloads: 217)
  KCS_KC868_AK_V2.2.19.zip (Size: 767.57 KB / Downloads: 215)
  KCS_KC868_AM_V2.2.19.zip (Size: 783.01 KB / Downloads: 210)
  KCS_KC868_AP_V2.2.19.zip (Size: 785.16 KB / Downloads: 214)
  KCS_KC868_ASR_V2.2.19.zip (Size: 762.28 KB / Downloads: 229)
  KCS_KC868_E16S_V2.2.19.zip (Size: 791.95 KB / Downloads: 221)
  KCS_KC868_UAIR_V2.2.19.zip (Size: 768.45 KB / Downloads: 217)
  KCS_KC868_A2_V2.2.19.zip (Size: 795.73 KB / Downloads: 219)
  KCS_KC868_A4_V2.2.19.zip (Size: 782.69 KB / Downloads: 220)
  KCS_KC868_A4S_V2.2.19.zip (Size: 806.4 KB / Downloads: 253)
  KCS_KC868_A6_V2.2.19.zip (Size: 744.52 KB / Downloads: 328)

My A32 pro got stuck, no response. 
In tuya app it shows me that the device is online, but when turn on any switch in the app, no response in the device.

Also i can’t login to the device setup by the IP address.

The device shows on the display the word “welcome”, it blinks every 5 seconds, and it doesn’t show the ip address on the display.

What should i do in this case?

Attached Files

Thumbnail(s)
   

1. support 0.001kwh precision.
   
you can download by bootloader.exe tool by RS485.
ARM BIN file download:

  N102030_KU_V20_260305SP.zip (Size: 14.12 KB / Downloads: 239)

bootloader.exe tool: 
   KC868 Controller Bootloader.zip (Size: 8.56 KB / Downloads: 77)
   
1. set baud rate=38400bps.
2. open com port.
3. power on Nx board, during LED fast blink when the "bootloader Detect" button right now. Then board will go to bootloader mode.
4. open BIN file
5. press "Download" button, begin download firmware, after finished, press "Run" button, ARM CPU begin work.

Hello admin,
I am using the KinCony KC868-A6v3 and  kincony ALR lora board and developing custom firmware with Arduino / PlatformIO.
The SSD1306 OLED works with the factory firmware, but when I upload my own firmware the LCD stays blank.
Could you please tell me:

1. What GPIO pins are used for the OLED I2C (SDA / SCL)?
   
2. What is the I2C address (0x3C or 0x3D)?
   
3. Do we need to initialize any IO expander or controller before using the OLED?
   
4. Do you have a simple Arduino example to initialize the onboard OLED?
   

Hi all. I have a question. I am using a B24M configured as MQTT with Home Assistant. After it was damaged, I bought a new device. How can I replace the device while keeping the existing integrations (so that a new device is not created, but it replaces the damaged one)?  From what I see, the device is identified using a UID in the MQTT broker, so I guess I would need to somehow replace that.

KinCony B32M ESP32 smart controller based on ESP32-S3-WROOM-1U (N16R8) wifi chip. Support 32 channel MOSFET output, 4 channel 1-wire GPIOs, 3 free GPIOs, 4 channel ADS1115 16bit analog input ports. One SD card using SPI bus. B32M include DS3231 high precision RTC clock chip. LCD display will show wifi and ethernet IP address and Tuya connection state. B32M have RS485 port. You can write any code by Arduino IDE / MicroPython / ESP-IDF development tool to ESP32 module. We will supply Arduino / ESP-IDF demo code for different samples. Everyone can modify and change the code for your own smart home automation system project. it support use by ESPHome for home assistant or tasmota firmware for smart home automation DIY. B32M use KCS v3 firmware, it support home assistant auto discovery function by MQTT, so without write any config code (zero code) for home assistant.

Model No. KinCony B32M
Description: KinCony 32 Channel ESP32-S3 Smart Controller – B32M
Power supply: 12-24V DC
Processor: ESP32-S3-WROOM-1U (N16R8)
Size: 264mm*83mm*56mm
interfaces: Ethernet(RJ45)-LAN 100Mbps IPv4/IPv6,WiFi,RS485,Bluetooth,USB-C,LCD,Tuya Module
RTC: DS3231 high precision chip (battery socket on PCB)
SD Card: SPI bus
Installation method: DIN RAIL
LCD: SSD1306 I2C display
Outputs:
32CH MOSFET Outputs, every channel use MAX 10A driver IC
Inputs:
ADS1115 16bit ADC: 2CH analog input DC0-5V (A1,A2) 2CH analog input 4-20mA (A3,A4)
32CH dry contact inputs (optocoupler isolation, long distance circuit for MAX 500 meters cable)
3 buttons: 1:ESP32 Reset 2:ESP32 Download 3:Tuya config
1-Wire GPIO: 4CH (with pull-up resistance on PCB)
free GPIO: 3CH (without pull-up resistance on PCB, connect with ESP32 pin directly)