Smart Home Automation Forum - G1

G1 cannot flash latest firmware

Thu, 12 Mar 2026 17:20:33 +0800

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
Screenshot 2026-03-12 090902.png (Size: 9.81 KB / Downloads: 96)
interface starts the erase process but when the installation process starts, it report that the device has been reset to firmware mode?

Screenshot 2026-03-12 091613.png (Size: 13.19 KB / Downloads: 88)

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

Thanks in anticipation.

Incoming SMS not reported via MQTT

Sun, 22 Feb 2026 05:12:12 +0800

Hello,
I am using Kincony G1 with SIM7600 module fw KCS 3.19.1 and MQTT integration.

According to the forum documentation, incoming SMS should be reported via MQTT STATE topic in this format:

Code:
{

 "sms_recv": {

 "phone": "+8612345678901",

 "content": "example"

 }

}

Unfortunately, I am unable to get this working.
My setup:

Device: Kincony G1
GSM module: SIM7600
Firmware: KCS v3.19.1
MQTT broker: working correctly
Home Assistant 2026.2.3
Topics:
G1/XXXXXXXXXXXX/SET - working (sending SMS works)
G1/XXXXXXXXXXXX/STATE - working (inputs, call_ring, etc.)

What works:

MQTT STATE reporting for inputs (input1…input12)
Outgoing SMS via MQTT (run_sms)

What does NOT work:

Incoming SMS and calling are not reported to MQTT
No (sms_recv) payload is published to STATE topic

Tests performed:

Clean SIM card (no stored SMS)
Very simple SMS content: TEST (no diacritics, no multipart)

When an SMS is received, no new MQTT message is published at all.

Question: Is sms_recv currently supported on Kincony G1 with SIM7600 in official KCS v3 firmware?

If yes:

Is there any additional configuration required?
Is SMS TEXT mode (AT+CMGF=1) required and handled automatically by firmware?

If not:

Can you confirm that incoming SMS → MQTT reporting is currently not supported / disabled for this hardware?

Thank you for clarification.

G1

Tue, 10 Feb 2026 08:44:09 +0800

Hi Admin,

I am planning to add a relay module to the G1, and I was wondering if you have any diagrams that I could use as a reference for how to properly add it.

This correct?

GPIO12 → relay IN
GND → relay GND
5V → relay VCC

12V+ → COM
NO → Siren+
Siren- → GND

Thank you for your help.

RS485 communicattion

Thu, 02 Oct 2025 16:57:18 +0800

Hello again,
I have one KC868-G1 and one KC868-AI could you please assit on how to connect each other with RS485 connection and use the G1 to read all digital inputs from the AI in home assistant.

The reason I need RS485 is for redundancy in case network drops.

Thank tou
Dimitris

KinCony G1 - RS485 with expansion card

Thu, 07 Aug 2025 07:25:31 +0800

Hello,
I've received a G1 device and my intention is to connect it with an RS485 IO expansion card 16In - 16Out (Maker: Eletechsup // N4D2E16).
The issue is that although I can send commands to the card and enable the Outputs by using custom RS485 protocol and IFTTT command (from the DI of the G1 board), I cannot receive info from N4D2E16 Inputs to the G1 in order to use them in Home Assistant.

How can I see the inputs of the board as well?
Tks
SSO

G1 fails to register incoming calls

Sun, 18 May 2025 21:50:52 +0800

Hi!

I've been using the G1 with 4G SIM as a gate opener for a few months now. Some time ago, the G1 stopped registering incoming calls (RING +441234567890 etc not appearing on screen) and the number was not being sent to my MQTT broker. I reflashed with the latest firmware available at the time (3.9.1) and everything started working OK again. The problem has returned. I've reflashed with the latest firmware (3.9.2) but the incoming call isn't being registered on the screen or being sent over MQTT. I can send and receive text messages OK and the 4G online signal is 64%. I can also make a test call from the G1 to my mobile which does cause my phone to ring.

When I first installed the G1, calls to it rang until I cancelled the call. Shortly after, incoming calls were rejected after 1 ring but the SSID was displayed on the screen and passed over MQTT, a better solution for my use case. The incoming calls are still rejected after 1 ring, but the call isn't being registered.

Is there something that I can do to return the incoming call/CallerID functionality?

Thanks,

Bodad

Hi again,

Scratch that. I tried a different SIM and it all worked fine. It must be something about the SIM which is a provider issue, not a G1 issue. However, it would still be helpful to have a setting that allows the number to ring a set number of times (or just until the CallerID is captured) and then rejects the call.

Thanks,

Bodad

G1 External Antenna for 4G

Sat, 29 Mar 2025 00:01:34 +0800

Hi,

Can you tell me what type of antenna I would have to buy if I wanted to position one away from the G1? Are all the three supplied antenna the same?

Thanks,

Bodad

G1 connection problem to KC868-A16v3

Thu, 27 Mar 2025 00:08:26 +0800

I get no Test SMS going out via A16v3

Test SMS with standalone G1 worked, so SIM ist OK.

Connected G1 GPIO 13 (TX) with A16v3 GPIO 40 (RX)
Connected G1 GPIO 14 (RX) with A16v3 GPIO 39 (TX)

Network/GSM is enabled on A16v3
GSM Bridge is enabled on G1

What might be wrong?

G1 Incoming Call Handling

Wed, 26 Mar 2025 19:12:31 +0800

Hi,

I've recently taken delivery of a G1 and it's working as per your YouTube videos. My application is as a gate opener, so I have a few requests for development into the KCS interface:

Add an option to reject (ie hang up) incoming calls once the CallerId has been captured (simple enabled/disabled switch).
Add the option of creating a "whitelist" of incoming numbers which are "allowed". If the CallerId is in the whitelist, it gets passed on via whichever protocol is used. Ideally, it would be helpful to have a name associated with the number so that it's easier to work out who is on the list and not.
Add the name from the whitelist to the CallerId e.g.

{
"call_ring": {
"phone": "+8612345678901",
"name": "Kincony Test"
}
}

4. Add MQTT to the IFTTT protocol as both an input and output.

Thank you,

Bodad

G1 keypad and LCD display information

Tue, 11 Mar 2025 21:26:28 +0800

The LCD screen displays the mobile signal strength in the top-left corner.
The LCD screen displays the time in the top-right corner.

Keyboard functions:

* Delete key
# Call key
When a call is received, the LCD screen displays "RING".

KCS v3 GSM MQTT protocol

Tue, 11 Mar 2025 21:01:29 +0800

MQTT:

Making a Call

{
"run_call": {
"phone": "+8612345678901"
}
}

Successful Response:

{
"run_call": {
"value": "success"
}
}

Failed Response:
Possible reasons: GPRS is not initialized, or the phone number is not set.

{
"run_call": {
"value": "error"
}
}

--------------------------------

Sending an SMS

{
"run_sms": {
"content": "sms content example",
"phone": "+8612345678901"
}
}

Successful Response:

{
"run_sms": {
"value": "success"
}
}

Failed Response:
Possible reasons: GPRS is not initialized, the phone number is not set, or the SMS content is not set.

{
"run_sms": {
"value": "error"
}
}

--------------------------------
MQTT STATE Reporting Received SMS and Incoming Calls

Incoming Call

{
"call_ring": {
"phone": "+8612345678901"
}
}

Received SMS

{
"sms_recv": {
"phone": "+8612345678901",
"content": "example"
}
}

GI - ESPHOME

Mon, 17 Feb 2025 18:41:45 +0800

Will G1 be suported under ESPHOME ?

Do you have information on how to send SMS from Home Assistant over Ethernet ?

ESP32-S3 Core Development Board ESP-IDF SSD1306 Demo

Sun, 26 Jan 2025 17:41:21 +0800

This driver was developed for generic SSD1306 OLED displays. Information on features and functionality are documented and can be found in the `ssd1306.h` header file. The SSD1306 component is a compact and simplified driver compatible with 128x64 and 128x32 displays. There are three font sizes supported, hardware and software scrolling capabilities, bitmap visualization, and more. This component has one font implemented now (i.e. 8x8 basic Latin + control + extended Latin) but is ideal for most use cases.

The example initializes a 128x64 SSD1306 display and demonstrates the following features:
- Display large text (x3)
- Display file receive and transmit bitmap icons
- Display medium text (x2)
- Display text
- Display countdown timer
- Display text scrolling up
- Display text scrolling down
- Display text paging down and up
- Display text scrolling horizontally from right and left
- Display text scrolling vertically downwards and upwards
- Display bitmap images
- Display inverted text and fadeout

Generic 128x64 SSD1306 OLED display example:

Code:
void i2c0_ssd1306_task( void *pvParameters ) {

    // initialize the xLastWakeTime variable with the current time.

    TickType_t          last_wake_time   = xTaskGetTickCount ();

    //

    // initialize i2c device configuration

    i2c_ssd1306_config_t dev_cfg         = I2C_SSD1306_128x64_CONFIG_DEFAULT;

    i2c_ssd1306_handle_t dev_hdl;

    //

    // init device

    i2c_ssd1306_init(i2c0_bus_hdl, &dev_cfg, &dev_hdl);

    if (dev_hdl == NULL) {

        ESP_LOGE(APP_TAG, "ssd1306 handle init failed");

        assert(dev_hdl);

    }

    //

    // task loop entry point

    for ( ;; ) {

        ESP_LOGI(APP_TAG, "######################## SSD1306 - START #########################");

        //

        int center = 1, top = 1, bottom = 4;

        char lineChar[16];

        uint8_t image[24];

        ESP_LOGI(APP_TAG, "Panel is 128x64");

        // Display x3 text

        ESP_LOGI(APP_TAG, "Display x3 Text");

        i2c_ssd1306_clear_display(dev_hdl, false);

        i2c_ssd1306_set_display_contrast(dev_hdl, 0xff);

        i2c_ssd1306_display_text_x3(dev_hdl, 0, "Hello", 5, false);

        vTaskDelay(3000 / portTICK_PERIOD_MS);

        // Display bitmap icons

        ESP_LOGI(APP_TAG, "Display bitmap icons");

        i2c_ssd1306_set_display_contrast(dev_hdl, 0xff);

        i2c_ssd1306_clear_display(dev_hdl, false);

        i2c_ssd1306_display_bitmap(dev_hdl, 31, 0, data_rx_img_32x32, 32, 32, false);

        vTaskDelay(500 / portTICK_PERIOD_MS);

        i2c_ssd1306_display_bitmap(dev_hdl, 31, 0, data_tx_img_32x32, 32, 32, false);

        vTaskDelay(1000 / portTICK_PERIOD_MS);

        // Display x2 text

        ESP_LOGI(APP_TAG, "Display x2 Text");

        i2c_ssd1306_clear_display(dev_hdl, false);

        i2c_ssd1306_set_display_contrast(dev_hdl, 0xff);

        i2c_ssd1306_display_text_x2(dev_hdl, 0, "{xTEXTx}", 8, false);

        i2c_ssd1306_display_text_x2(dev_hdl, 2, " X2-X2", 6, false);

        vTaskDelay(3000 / portTICK_PERIOD_MS);

        // Display text

        ESP_LOGI(APP_TAG, "Display Text");

        i2c_ssd1306_clear_display(dev_hdl, false);

        i2c_ssd1306_set_display_contrast(dev_hdl, 0xff);

        i2c_ssd1306_display_text(dev_hdl, 0, "SSD1306 128x64", 14, false);

        i2c_ssd1306_display_text(dev_hdl, 1, "Hello World!!", 13, false);

        i2c_ssd1306_display_text(dev_hdl, 2, "SSD1306 128x64", 14, true);

        i2c_ssd1306_display_text(dev_hdl, 3, "Hello World!!", 13, true);

        vTaskDelay(3000 / portTICK_PERIOD_MS);

        // Display Count Down

        ESP_LOGI(APP_TAG, "Display Count Down");

        memset(image, 0, sizeof(image));

        i2c_ssd1306_display_image(dev_hdl, top, (6*8-1), image, sizeof(image));

        i2c_ssd1306_display_image(dev_hdl, top+1, (6*8-1), image, sizeof(image));

        i2c_ssd1306_display_image(dev_hdl, top+2, (6*8-1), image, sizeof(image));

        for(int font = 0x39; font > 0x30; font--) {

            memset(image, 0, sizeof(image));

            i2c_ssd1306_display_image(dev_hdl, top+1, (7*8-1), image, 8);

            memcpy(image, font8x8_latin_tr, 8);

            if (dev_hdl->flip_enabled) i2c_ssd1306_flip_buffer(image, 8);

            i2c_ssd1306_display_image(dev_hdl, top+1, (7*8-1), image, 8);

            vTaskDelay(1000 / portTICK_PERIOD_MS);

        }

        // Page Down

        ESP_LOGI(APP_TAG, "Page Down");

        i2c_ssd1306_clear_display(dev_hdl, false);

        i2c_ssd1306_set_display_contrast(dev_hdl, 0xff);

        i2c_ssd1306_display_text(dev_hdl, 0, "---Page   DOWN---", 16, true);

        i2c_ssd1306_set_software_scroll(dev_hdl, 1, (dev_hdl->pages-1) );

        for (int page = 0; page < bottom+10; page++) {

            if ( (page % (dev_hdl->pages-1)) == 0) i2c_ssd1306_clear_scroll_display(dev_hdl);

            lineChar[0] = 0x02;

            sprintf(&lineChar[1], " Line %02d", page);

            i2c_ssd1306_display_scroll_text(dev_hdl, lineChar, strlen(lineChar), false);

            vTaskDelay(500 / portTICK_PERIOD_MS);

        }

        vTaskDelay(3000 / portTICK_PERIOD_MS);

        // Horizontal Scroll

        ESP_LOGI(APP_TAG, "Horizontal Scroll");

        i2c_ssd1306_clear_display(dev_hdl, false);

        i2c_ssd1306_set_display_contrast(dev_hdl, 0xff);

        i2c_ssd1306_display_text(dev_hdl, center, "Horizontal", 10, false);

        i2c_ssd1306_set_hardware_scroll(dev_hdl, I2C_SSD1306_SCROLL_RIGHT, I2C_SSD1306_SCROLL_2_FRAMES);

        vTaskDelay(5000 / portTICK_PERIOD_MS);

        i2c_ssd1306_set_hardware_scroll(dev_hdl, I2C_SSD1306_SCROLL_LEFT, I2C_SSD1306_SCROLL_2_FRAMES);

        vTaskDelay(5000 / portTICK_PERIOD_MS);

        i2c_ssd1306_set_hardware_scroll(dev_hdl, I2C_SSD1306_SCROLL_STOP, I2C_SSD1306_SCROLL_2_FRAMES);

        // Vertical Scroll

        ESP_LOGI(APP_TAG, "Vertical Scroll");

        i2c_ssd1306_clear_display(dev_hdl, false);

        i2c_ssd1306_set_display_contrast(dev_hdl, 0xff);

        i2c_ssd1306_display_text(dev_hdl, center, "Vertical", 8, false);

        i2c_ssd1306_set_hardware_scroll(dev_hdl, I2C_SSD1306_SCROLL_DOWN, I2C_SSD1306_SCROLL_2_FRAMES);

        vTaskDelay(5000 / portTICK_PERIOD_MS);

        i2c_ssd1306_set_hardware_scroll(dev_hdl, I2C_SSD1306_SCROLL_UP, I2C_SSD1306_SCROLL_2_FRAMES);

        vTaskDelay(5000 / portTICK_PERIOD_MS);

        i2c_ssd1306_set_hardware_scroll(dev_hdl, I2C_SSD1306_SCROLL_STOP, I2C_SSD1306_SCROLL_2_FRAMES);

        // Bitmaps

        ESP_LOGI(APP_TAG, "Bitmaps");

        i2c_ssd1306_display_text(dev_hdl, 1, "BATMAN", 6, false);

        int bitmapWidth = 4*8;

        int width = dev_hdl->width;

        int xpos = width / 2; // center of width

        xpos = xpos - bitmapWidth/2;

        int ypos = 16;

        ESP_LOGD(APP_TAG, "width=%d xpos=%d", width, xpos);

        i2c_ssd1306_display_bitmap(dev_hdl, xpos, ypos, batman, 32, 13, false);

        vTaskDelay(3000 / portTICK_PERIOD_MS);

        for(int i=0;i<128;i++) {

            i2c_ssd1306_set_display_wrap_arround(dev_hdl, I2C_SSD1306_SCROLL_RIGHT, 2, 3, 0);

        }

        vTaskDelay(2000 / portTICK_PERIOD_MS);

        i2c_ssd1306_clear_display(dev_hdl, false);

        i2c_ssd1306_display_bitmap(dev_hdl, 0, 0, fleischer, 128, 64, false);

        vTaskDelay(2000 / portTICK_PERIOD_MS);

        // Invert

        ESP_LOGI(APP_TAG, "Invert");

        i2c_ssd1306_clear_display(dev_hdl, true);

        i2c_ssd1306_set_display_contrast(dev_hdl, 0xff);

        i2c_ssd1306_display_text(dev_hdl, center, "  Good Bye!!", 12, true);

        vTaskDelay(5000 / portTICK_PERIOD_MS);

        // Fade Out

        ESP_LOGI(APP_TAG, "Fade Out");

        i2c_ssd1306_fadeout_display(dev_hdl);

        //

        ESP_LOGI(APP_TAG, "######################## SSD1306 - END ###########################");

        //

        //

        // pause the task per defined wait period

        vTaskDelaySecUntil( &last_wake_time, I2C0_TASK_SAMPLING_RATE + 10 );

    }

    //

    // free resources

    i2c_ssd1306_delete( dev_hdl );

    vTaskDelete( NULL );

}

The source code for the above example and component are available here:
- Example: https://github.com/K0I05/ESP32-S3_ESP-ID...306_task.c
- Component: https://github.com/K0I05/ESP32-S3_ESP-ID...sp_ssd1306

ESP32-S3 Core Development Board RTU, I2C, 1-wire Demo ESP-IDF Application

Sat, 25 Jan 2025 06:44:00 +0800

Hello,

This demo application utilizes RS-485, 1-Wire, and I2C under the ESP-IDF environment.

KinCony S3 Core Development Board RTU, I2C, 1-wire Demo Application
The demo application interfaces the following sensors:

The demo application interfaces the following sensors:

MODBUS RTU - RS2E radar precipitation sensor with temperature and humidity sensor
MODBUS RTU - WDC2E ultrasonic anemometer
I2C - BMP280 atmospheric pressure sensor
1-Wire - DS18B20 ground temperature sensor

The RS2E and WDC2E sensors are configured as MODBUS RTUs and interfaced to the core development board via the RS-485 port. The BMP280 sensor is interfaced to the core development board via I2C and the DS18B20 sensor is interfaced to the board via 1-wire.

ESP-IDF Components Library

The demo application attempts to connect to a WiFi network, once connected, the system clock is synchronized over SNTP and then it will poll all four sensors at a user-defined interval (6-seconds). As each sensor is polled the application prints the results via the serial debug port.

Serial debug port print example:

Code:
E (23447) RTU [APP]: ################## KINCONY-S3 ##################

I (23477) RTU [APP]: RS2E Air Temperature:        20.93°C

I (23517) RTU [APP]: RS2E Relative Humidity:      29.30 %

I (23527) RTU [APP]: RS2E Dewpoint Temperature:   2.35°C

I (23567) RTU [APP]: RS2E Precipitation Rate:     0.00 mm/h

I (23607) RTU [APP]: RS2E Precipitation Type:     No Rain

I (23647) RTU [APP]: WDC2E Wind Direction:        0°

I (23687) RTU [APP]: WDC2E Wind Speed:            0.00 m/s

I (23907) RTU [APP]: DS18B20 Ground Temperature:  22.25°C

I (23917) RTU [APP]: BMP280 Atmospheric Pressure: 994.46 hPa

G1 firmware flash problems

Sun, 22 Dec 2024 03:18:01 +0800

I have tried to flash firmware as shown in video sim7600e at comand...... and after flashing and repower the led display is blank and doesnt work tried many times same result.