Smart Home Automation Forum - All Forums

KCS VERSUS ESPHOME

Thu, 20 Aug 2026 23:21:58 +0800

I just bought a KinCony 32 Pro to control basically the lighting in my house. This was a retrofit: I replaced an old automation system with the KinCony on a DIY basis.
My plan is to use Home Assistant to control everything. Today, the KinCony A32 Pro physically controls the lights ON/OFF. Now I need to install the firmware, and the big question is: ESPHome or KCS?
I asked ChatGPT, Gemini, and Copilot, and they gave contradictory answers.
What ChatGPT said
ChatGPT initially recommended KCS + Home Assistant, arguing that KCS can integrate the A32 Pro through MQTT and MQTT Auto Discovery, and that I would not need ESPHome.
It cited KinCony’s forum, including a discussion where the administrator said that KCS and ESPHome cannot run simultaneously and recommended KCS v3 for users who do not know how to configure ESPHome.
It also cited the KinCony forum thread “A32 pro lost control”, where a user had flashed ESPHome and lost KCS. The administrator explained that KCS and ESPHome cannot coexist, and suggested enabling MQTT Auto Discovery in KCS to integrate the A32 Pro with Home Assistant.
Based on this, ChatGPT concluded:

I do not need ESPHome.
I can install KCS and integrate it with Home Assistant.
KCS + MQTT Auto Discovery is the simpler solution for my case.

What Copilot said
Copilot strongly disagreed and said Gemini was right and ChatGPT was wrong.
Its main argument is that KCS does not expose all 32 digital inputs of the A32 Pro to Home Assistant.
According to Copilot, KCS exposes:

Relays through MQTT
Basic sensors
Some internal states

But it does not expose DI1–DI32.
This is critical for my application because I want to use physical inputs/dry contacts to trigger automations such as:

Quote:Press a button → turn on one, two, or three lights.

Copilot says that without the digital inputs being available in Home Assistant, this type of automation cannot work as intended.
It also claims that KinCony has stated on its forum that if you want all inputs and outputs in Home Assistant, you should use ESPHome.
Copilot's other arguments are:

KCS + MQTT Auto Discovery does not automatically expose the 32 digital inputs.
Saying that KCS is simpler may be true for some smaller KinCony controllers, but not necessarily for the A32 Pro.
The A32 Pro uses multiple I/O expanders, and ESPHome provides a more complete mapping of its inputs and outputs to Home Assistant.

My questions
I do not want a generic comparison between ESPHome and KCS. I want the answer specifically for the KinCony KC868-A32 Pro + Home Assistant, considering that my primary objective is to control lighting and use the physical digital inputs for automations.
1. Who is technically correct: Gemini/Copilot or ChatGPT?
More specifically: Does KCS v3 with MQTT Auto Discovery expose all 32 digital inputs of the A32 Pro to Home Assistant, or do I need ESPHome for that?
2. If I need ESPHome on the KinCony A32 Pro:
Where is the latest official A32 Pro ESPHome YAML/configuration for Home Assistant?
Is this KinCony forum thread the correct/latest source?
https://www.kincony.com/forum/showthread.php?tid=5520
3. If KCS should be installed instead:
Is this the latest KCS version/configuration for the A32 Pro, including MQTT Auto Discovery?
https://www.kincony.com/forum/showthread...3#pid25773
I want to resolve the contradiction before flashing the controller, because KCS and ESPHome cannot coexist, so choosing the wrong firmware means having to reflash the device.
Please base the answer on the current KinCony A32 Pro documentation/forum information, not on assumptions about other KinCony models.
Summary: I need to decide between KCS + MQTT Auto Discovery and ESPHome for an A32 Pro whose relays control my lights and whose digital inputs will be used by Home Assistant for physical-button/dry-contact automations. The key question is whether KCS exposes the 32 digital inputs to Home Assistant.

KC868-AGv3

Thu, 20 Aug 2026 04:45:26 +0800

Hi Kincony and community.

I've just received my KC868-AGv3 RF/IR Smart Controller..

is there an example ESPHome configuration posted anywhere - I've been searching for some time and cannot find a an example I can use to get me started... I've installed a base ESP32 config on it and I see it on my network etc.. but keen to get it fully worked with all the RF/IR/Buzzer features..

Many thanks in advance.

KinCony B2 Smart Controller released

Mon, 17 Aug 2026 21:07:50 +0800

KinCony B2 ESP32 smart controller based on ESP32-S3-WROOM-1U (N16R8) wifi chip. Support 2 channel relay output, 4 channel 1-wire GPIOs, 4 channel ADS1115 16bit analog input ports. One SD card using SPI bus. B2 include DS3231 high precision RTC clock chip. LCD display will show wifi and ethernet IP address and Tuya connection state. B2 have I2C bus extender and RS485 port. B2 support use SIM7600E 4G module. 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. B2 use KCS v3 firmware, it support home assistant auto discovery function by MQTT, so without write any config code (zero code) for home assistant. KCS v3 support KinCony cloud service (official shop customer free 2 years), remote monitor and control device by webpage in anywhere. KCS v3 support KinCony board integrate to Loxone Miniserver. Support Apple HomeKit for Siri.

Model No. KinCony B2
Description: KinCony 2 Channel ESP32-S3 Smart Relay Controller – B2
Power supply: 12-24V DC
Processor: ESP32-S3-WROOM-1U (N16R8)
Size: 124mm*83mm*56mm
interfaces: Ethernet(RJ45)-LAN 100Mbps IPv4/IPv6,WiFi,RS485,Bluetooth,USB-C,LCD,I2C,Tuya Module, 4G SIM7600
RTC: DS3231 high precision chip (battery socket on PCB)
SD Card: SPI bus
Installation method: DIN RAIL
LCD: SSD1306 I2C display
Outputs:
2CH relay Outputs, every relay use by MAX AC270V/10A
Inputs:
ADS1115 16bit ADC: 2CH analog input DC0-5V (A1,A2) 2CH analog input 4-20mA (A3,A4)
2CH 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)

KC868-A8v3 PCB layout CAD file

Mon, 17 Aug 2026 16:44:33 +0800

KC868-A8v3 PCB layout CAD file

KC868_A8v3.1.zip (Size: 1.57 MB / Downloads: 18)

Current direction detection incorrect on channels 2 and 3

Thu, 13 Aug 2026 18:49:03 +0800

Hello,
I have also noticed another issue with the KinCony N30 when using the current direction detection.
My N30 has three rows/modules, and all of my current clamps are installed and wired in exactly the same physical direction.
However, when I enable the current direction detection, I get inconsistent results:

Module 1: current direction is detected correctly and the power values are positive.
Module 2: the power values are negative.
Module 3: the power values are also negative.

This happens even though the clamps on modules 1, 2 and 3 are installed in exactly the same direction.
Without current direction detection, the measured power values are otherwise consistent.
This makes me suspect that there may be an issue with the polarity/sign handling or current direction detection in the firmware for modules 2 and 3.
Could you please check whether the current direction detection is implemented identically for all three modules?
In particular, I would like to know whether there is a firmware configuration or calibration parameter that could cause modules 2 and 3 to have their current direction inverted compared with module 1.
The expected behavior is that, with all clamps physically oriented in the same direction, the three modules should report the same sign for the same direction of current.
Thank you.
Capture d’écran 2026-08-13 à 12.48.33.png (Size: 5.73 MB / Downloads: 48)
Capture d’écran 2026-08-13 à 12.48.10.png (Size: 5.36 MB / Downloads: 57)

MQTT Discovery: missing state_class for power sensors in Home Assistant

Thu, 13 Aug 2026 18:41:45 +0800

Hello,
I noticed an issue with the MQTT Discovery configuration generated by the N30 when the device is integrated into Home Assistant.
For example, Home Assistant creates the following entity:

Code:
sensor.n30_d0cf13020244_energy2_ch2_power

The N30 publishes this MQTT Discovery payload:

Code:
{

  "uniq_id": "D0CF13020244_sensor_energy2_power_ch2",

  "~": "homeassistant/sensor/D0CF13020244energy2_power_ch2",

  "name": "energy2_ch2.power",

  "device": {

    "name": "N30-D0CF13020244",

    "identifiers": "D0CF13020244",

    "manufacturer": "KinCony",

    "model": "N30"

  },

  "config_topic": "~/config",

  "avty_t": "D0CF13020244/avail",

  "unit_of_meas": "W",

  "dev_cla": "power",

  "val_tpl": "{{ value | float | round(1) }}",

  "stat_t": "~/state"

}

In Home Assistant, the entity is therefore detected with:

Code:
device_class: power

unit_of_measurement: W

but without:

Code:
state_class: measurement

The missing field in the MQTT Discovery payload is:

Code:
"stat_cla": "measurement"

Interestingly, some other N30 power sensors are correctly detected by Home Assistant with:

Code:
state_class: measurement

unit_of_measurement: W

device_class: power

For example,

Code:
sensor.n30_bl0910_1_power_6

already has the correct

Code:
state_class

.
This suggests that the issue is specific to some of the MQTT Discovery configurations generated by the N30 firmware, particularly the

Code:
energy*_ch*_power

sensors.
Could you please check the N30 firmware and add:

Code:
"stat_cla": "measurement"

to the MQTT Discovery configuration of all instantaneous power sensors?
The expected configuration would be:

Code:
"unit_of_meas": "W",

"dev_cla": "power",

"stat_cla": "measurement"

This would allow Home Assistant to correctly identify these entities as power measurements and use them properly for statistics and energy-related features.
Thank you.

solar production and consomation

Thu, 13 Aug 2026 16:36:39 +0800

Current sensor does not detect current direction
Hello,
I have a question regarding the current/power sensor on my KinCony device.
The circuit is connected to a 1100 W pump, with approximately 1000 W peak solar PV production.
I expected the sensor to detect the direction of the current and therefore show negative power when the solar panels are producing energy and sending it back through the circuit.
In the attached screenshot:

Green area: nighttime. The pump is running and consuming approximately 1100 W. This is normal.
Red area: daytime. The solar panels are producing around 400 W, with no consumption from the pump. However, the sensor still reports the power as positive instead of negative.

So it appears that the sensor measures the current magnitude but does not detect its direction.
Is this sensor supposed to be bidirectional?
If so, is there a specific orientation for the current transformer/sensor, or does it require a particular configuration to detect the direction of the current?
Could someone explain how the current direction is detected and how I should configure or install the sensor to obtain positive values for consumption and negative values for solar production?
Thank you.

Greenshot 2026-08-13 10.31.05.png (Size: 54.95 KB / Downloads: 65)

ai automation

Thu, 13 Aug 2026 14:56:10 +0800

Hi everyone,

I’m exploring how AI automation could work alongside Loxone for smarter home and building automation. Loxone already handles many rule-based tasks well, but I’m interested in where AI could add value without making the system unnecessarily complicated.

For example, AI could potentially analyze sensor data, learn usage patterns, optimize heating or lighting schedules, detect unusual energy consumption, or help automate certain routines based on changing conditions.

I recently came across Codeora Vision while looking into AI automation solutions, which got me thinking about how AI-based systems could complement existing automation platforms rather than replace them.

Has anyone here experimented with connecting AI services or machine-learning workflows with Loxone? I’d be particularly interested in practical approaches for integrating AI with Loxone Miniserver data, APIs, MQTT, or other compatible methods.

What AI automation use cases have you found genuinely useful in a smart home or building environment?

Connecting sensors to KinCony F16

Wed, 12 Aug 2026 22:29:15 +0800

- Without connecting the SHT30 temperature and humidity sensor, the LCD screen displays readings normally.

  1.jpg (Size: 309.65 KB / Downloads: 79)
- After connecting the SHT30 temperature and humidity sensor, the LCD screen displays distorted readings.

  2.jpg (Size: 290.54 KB / Downloads: 80)
- I tried setting the SHT30 address (I2C) to 0x44, but the address resets the next time the controller is polled.
- I also connected the RS485 JTH-2D1 temperature and humidity sensor to the RS485 port. Its address is: Temperature – 768; Humidity – 769

  3.jpg (Size: 67.67 KB / Downloads: 78)

  4.jpg (Size: 194.15 KB / Downloads: 59)
  5.jpg (Size: 67.67 KB / Downloads: 52)
- I also connected an analog soil moisture sensor to analog input A1, using an external 3.3V power supply.

  6.jpg (Size: 75.31 KB / Downloads: 55)
When the sensor is dry, the reading is 752.

  7.jpg (Size: 66.83 KB / Downloads: 54)
When the sensor is submerged, the reading is 757.

  8.jpg (Size: 70.13 KB / Downloads: 53)
When testing these sensors in an Arduino UNO R3, the readings are different.

  9.jpg (Size: 219.35 KB / Downloads: 56)
How do I configure them in the KinCony ESP32-S3 Tuya relay board – F16 (16A removable relay)?

CT Sensor Direction

Wed, 12 Aug 2026 08:40:58 +0800

From what I've read (and based on most other power monitoring systems) it's important to get the direction of the sensor correct. So, should it look like A or B?

Code:
A)

               (  )---- Sense Leads ------

Source >-------(--)------------------------> Load

               (  )

B)

         ---- Sense Leads ------(  )

Source >------------------------(--)-------> Load

                                (  )

Thanks!

4-20mA loop voltage consideration

Tue, 11 Aug 2026 14:21:07 +0800

Although the B4 and B4M devices allow connection of a 24Vdc supply it is not clear to me that the 4-20 mA analog inputs allow use of a 24 volt loop supply. The example drawings show 12 volt supply devices connected and I am concerned that I may damage the inputs by using a 24vdc loop. Please advise what is acceptable.

N60 Voltage reference

Tue, 11 Aug 2026 05:46:10 +0800

I'm in Texas, US with a normal 200a panel.
If I wanted to monitor 40 branch circuit can you explain how and what to use for voltage reference? Is it one per each 10? or is it like iotawatt that you use just one per the whole unit.

CAN-BUS Transceiver

Fri, 07 Aug 2026 16:07:15 +0800

what pins can be used for a CAN-BUS transceiver

KC868-A32 Malfunction After Seven Months of Continuous Operation

Mon, 03 Aug 2026 08:52:35 +0800

Hello,
I am an installation engineer in South Korea, and I have built a room control system using the KC868-A32.
The KC868-A32 board has been powered on continuously for approximately seven months without being turned off, and it has been used to control the lighting system.
Today, the lights suddenly stopped working properly. Whenever I turned the lights on, they turned off again shortly afterward.
I built the system to communicate with the board remotely via MQTT. The MQTT connection status showed that it was connected normally.
However, when I checked the “Monitor” page on the board’s web interface, the input and output status indicators were not displayed, unlike during normal operation.
Finally, I performed a factory reset, and everything started working normally again.
Could you please advise what may have caused this issue and how I can prevent it from happening again?
Do I need to continue performing a factory reset whenever this issue occurs, or is there another recommended solution?
Thank you.

  KakaoTalk_Photo_2026-08-03-09-50-14.png (Size: 21.84 KB / Downloads: 79)

  KakaoTalk_Photo_2026-08-03-09-50-25.png (Size: 21.58 KB / Downloads: 114)

  KakaoTalk_Photo_2026-08-03-09-51-29 001.png (Size: 11.97 KB / Downloads: 71)

  KakaoTalk_Photo_2026-08-03-09-51-29 002.png (Size: 20.41 KB / Downloads: 71)

F8 ESPHome yaml for home assistant with tuya

Mon, 03 Aug 2026 07:00:09 +0800

Code:
esphome:

  name: f8

  friendly_name: f8

  platformio_options:

    board_build.extra_flags:

      # WIFI_CONTROL_SELF_MODE = 0

      # WIFI_CONTROL_SELF_MODE = 1

      - "-DWIFI_CONTROL_SELF_MODE=1"

esp32:

  board: esp32-s3-devkitc-1

  framework:

    type: arduino

external_components:

  - source:

      type: git

      url: https://github.com/hzkincony/esphome-tuya-wifi-mcu

      ref: v1.3.1

# Enable logging

  # hardware_uart: USB_SERIAL_JTAG

# Enable Home Assistant API

api:

  encryption:

    key: "WeVOuL5oNhjXcfzXtTirlOwvtWvCD5yqIxd3oV4es1k="

ethernet:

  type: W5500

  clk_pin: GPIO42

  mosi_pin: GPIO43

  miso_pin: GPIO44

  cs_pin: GPIO41

  interrupt_pin: GPIO2

  reset_pin: GPIO1

i2c:

   - id: bus_a

     sda: 8

     scl: 18

     scan: true

     frequency: 400kHz

pcf8574:

  - id: 'pcf8574_hub_in_1'  # for DI1-DI4 Relay1-Relay4

    i2c_id: bus_a

    address: 0x24

    pcf8575: true

uart:

  - id: uart_1    #RS485

    baud_rate: 9600

    debug:

      direction: BOTH

      dummy_receiver: true

      after:

        timeout: 10ms

    tx_pin: 16

    rx_pin: 17

  - id: tuya_mcu_uart

    tx_pin: GPIO39

    rx_pin: GPIO38

    baud_rate: 9600

tuya_wifi_mcu:

  # tuya mcu product id

  product_id: gk6ok3aysk6lw1bb

  uart_id: tuya_mcu_uart

  wifi_reset_pin: 28

  wifi_led_pin: 16

switch:

  - platform: uart

    uart_id: uart_1

    name: "RS485 Button"

    data: [0x11, 0x22, 0x33, 0x44, 0x55]

  - platform: gpio

    name: "f8-output01"

    id: "f8_output01"

    pin:

      pcf8574: pcf8574_hub_in_1

      number: 8

      mode: OUTPUT

      inverted: true

  - platform: tuya_wifi_mcu

    name: f8-output1-tuya

    dp_id: 1

    # hide from homeassistant ui

    internal: true

    # bind other switch, sync state

    bind_switch_id: "f8_output01"

  - platform: gpio

    name: "f8-output02"

    id: "f8_output02"

    pin:

      pcf8574: pcf8574_hub_in_1

      number: 9

      mode: OUTPUT

      inverted: true

  - platform: tuya_wifi_mcu

    name: f8-output2-tuya

    dp_id: 2

    # hide from homeassistant ui

    internal: true

    # bind other switch, sync state

    bind_switch_id: "f8_output02"

  - platform: gpio

    name: "f8-output03"

    id: "f8_output03"

    pin:

      pcf8574: pcf8574_hub_in_1

      number: 10

      mode: OUTPUT

      inverted: true

  - platform: tuya_wifi_mcu

    name: f8-output3-tuya

    dp_id: 3

    # hide from homeassistant ui

    internal: true

    # bind other switch, sync state

    bind_switch_id: "f8_output03"

  - platform: gpio

    name: "f8-output04"

    id: "f8_output04"

    pin:

      pcf8574: pcf8574_hub_in_1

      number: 11

      mode: OUTPUT

      inverted: true

  - platform: tuya_wifi_mcu

    name: f8-output4-tuya

    dp_id: 4

    # hide from homeassistant ui

    internal: true

    # bind other switch, sync state

    bind_switch_id: "f8_output04"

  - platform: gpio

    name: "f8-output05"

    id: "f8_output05"

    pin:

      pcf8574: pcf8574_hub_in_1

      number: 12

      mode: OUTPUT

      inverted: true

  - platform: tuya_wifi_mcu

    name: f8-output5-tuya

    dp_id: 5

    # hide from homeassistant ui

    internal: true

    # bind other switch, sync state

    bind_switch_id: "f8_output05"

  - platform: gpio

    name: "f8-output06"

    id: "f8_output06"

    pin:

      pcf8574: pcf8574_hub_in_1

      number: 13

      mode: OUTPUT

      inverted: true

  - platform: tuya_wifi_mcu

    name: f8-output6-tuya

    dp_id: 6

    # hide from homeassistant ui

    internal: true

    # bind other switch, sync state

    bind_switch_id: "f8_output06"

  - platform: gpio

    name: "f8-output07"

    id: "f8_output07"

    pin:

      pcf8574: pcf8574_hub_in_1

      number: 14

      mode: OUTPUT

      inverted: true

  - platform: tuya_wifi_mcu

    name: f8-output4-tuya

    dp_id: 101

    # hide from homeassistant ui

    internal: true

    # bind other switch, sync state

    bind_switch_id: "f8_output07"

  - platform: gpio

    name: "f8-output08"

    id: "f8_output08"

    pin:

      pcf8574: pcf8574_hub_in_1

      number: 15

      mode: OUTPUT

      inverted: true

  - platform: tuya_wifi_mcu

    name: f8-output8-tuya

    dp_id: 102

    # hide from homeassistant ui

    internal: true

    # bind other switch, sync state

    bind_switch_id: "f8_output08"

binary_sensor:

  - platform: gpio

    name: "f8-input01"

    id: "f8_input01"

    pin:

      pcf8574: pcf8574_hub_in_1

      number: 0

      mode: INPUT

      inverted: true

  - platform: tuya_wifi_mcu

    name: f8-input1-tuya

    dp_id: 111

    bind_binary_sensor_id: f8_input01

    internal: true

  - platform: gpio

    name: "f8-input02"

    id: "f8_input02"

    pin:

      pcf8574: pcf8574_hub_in_1

      number: 1

      mode: INPUT

      inverted: true

  - platform: tuya_wifi_mcu

    name: f8-input2-tuya

    dp_id: 112

    bind_binary_sensor_id: f8_input02

    internal: true

  - platform: gpio

    name: "f8-input03"

    id: "f8_input03"

    pin:

      pcf8574: pcf8574_hub_in_1

      number: 2

      mode: INPUT

      inverted: true

  - platform: tuya_wifi_mcu

    name: f8-input3-tuya

    dp_id: 113

    bind_binary_sensor_id: f8_input03

    internal: true

  - platform: gpio

    name: "f8-input04"

    id: "f8_input04"

    pin:

      pcf8574: pcf8574_hub_in_1

      number: 3

      mode: INPUT

      inverted: true

  - platform: tuya_wifi_mcu

    name: f8-input4-tuya

    dp_id: 114

    bind_binary_sensor_id: f8_input04

    internal: true

  - platform: gpio

    name: "f8-input05"

    id: "f8_input05"

    pin:

      pcf8574: pcf8574_hub_in_1

      number: 4

      mode: INPUT

      inverted: true

  - platform: tuya_wifi_mcu

    name: f8-input5-tuya

    dp_id: 115

    bind_binary_sensor_id: f8_input05

    internal: true

  - platform: gpio

    name: "f8-input06"

    id: "f8_input06"

    pin:

      pcf8574: pcf8574_hub_in_1

      number: 5

      mode: INPUT

      inverted: true

  - platform: tuya_wifi_mcu

    name: f8-input6-tuya

    dp_id: 116

    bind_binary_sensor_id: f8_input06

    internal: true

  - platform: gpio

    name: "f8-input07"

    id: "f8_input07"

    pin:

      pcf8574: pcf8574_hub_in_1

      number: 6

      mode: INPUT

      inverted: true

  - platform: tuya_wifi_mcu

    name: f8-input7-tuya

    dp_id: 117

    bind_binary_sensor_id: f8_input07

    internal: true

  - platform: gpio

    name: "f8-input08"

    id: "f8_input08"

    pin:

      pcf8574: pcf8574_hub_in_1

      number: 7

      mode: INPUT

      inverted: true

  - platform: tuya_wifi_mcu

    name: f8-input8-tuya

    dp_id: 118

    bind_binary_sensor_id: f8_input08

    internal: true

##pull-up resistance on PCB

  - platform: gpio

    name: "f8-W1-io48"

    pin: 

      number: 48

      inverted: true

  - platform: gpio

    name: "f8-W1-io47"

    pin: 

      number: 47

      inverted: true

  - platform: gpio

    name: "f8-W1-io21"

    pin: 

      number: 21

      inverted: true

  - platform: gpio

    name: "f8-W1-io15"

    pin: 

      number: 15

      inverted: true

## without resistance on PCB

  - platform: gpio

    name: "f8-W1-io14"

    pin: 

      number: 14

      inverted:  false

  - platform: gpio

    name: "f8-433M"

    pin: 

      number: 40

      inverted:  false

  - platform: gpio

    name: "f8-io0"

    pin: 

      number: 0

      inverted:  false

sensor:

  - platform: adc

    pin: 5

    name: "f8 A1 Voltage"

    update_interval: 5s

    attenuation: 11db

    filters:

      - lambda:

          if (x >= 3.11) {

            return x * 1.60256;

          } else if (x <= 0.15) {

            return 0;

          } else {

            return x * 1.51;

          }

  - platform: adc

    pin: 7

    name: "f8 A2 Voltage"

    update_interval: 5s

    attenuation: 11db

    filters:

      # - multiply: 1.51515

      - lambda:

          if (x >= 3.11) {

            return x * 1.60256;

          } else if (x <= 0.15) {

            return 0;

          } else {

            return x * 1.51;

          }

  - platform: adc

    pin: 6

    name: "f8 A3 Current"

    update_interval: 5s

    unit_of_measurement: mA

    attenuation: 11db

    filters:

      - multiply: 6.66666666

  - platform: adc

    pin: 4

    name: "f8 A4 Current"

    update_interval: 5s

    unit_of_measurement: mA

    attenuation: 11db

    filters:

      - multiply: 6.66666666

web_server:

  port: 80

font:

  - file: "gfonts://Roboto"

    id: roboto

    size: 20

display:

  - platform: ssd1306_i2c

    i2c_id: bus_a

    model: "SSD1306 128x64"

    address: 0x3C

    lambda: |-

      it.printf(0, 0, id(roboto), "KinCony f8");

esphome yaml:

F8-HA-tuya.txt (Size: 8.68 KB / Downloads: 45)