KC868-E16S/E16P demo configure for ESPhome

[admin]

ok, we have solved your problem by ANYDESK.

[matthewdresden]

ESP32 IoT Board Issue with ESPHome Firmware Installation

Solution:

The issue I had when flashing the firmware from command line using the esphome python pip was this: it produces 2 firmware files, `firmware.bin and firmware-factory.bin`. Kinkony was able to demonstrate flashing it from esphome which was deployed in Home Assistant OS. This gave me the oppurtunity to compare the difference between what was happening from Home Assistant (esphome) and esphome from command line.

The factory firmware file is what worked.

From here I also found in order to be able to upload flash updates without having home assistant OS plugged into the board with USB, I needed to add the key to the yaml file called `ota:`

[admin]

ok, good.

[tester]

Hello,

Can you confirm the pinout for E16P ?

esphome-devices from E16S a config we can limit to existing to a E16P device as :

| Pin    | Function            |
| ------ | ------------------- |
| GPIO36 | ANALOG_A1          |
| GPIO35 | ANALOG_A2          |
| GPIO34 | ANALOG_A3          |
| GPIO39 | ANALOG_A4          |
| GPIO16 | IIC_SDA            |
| GPIO15 | IIC_SCL            |
| GPIO4  | 433MHz Receiver    |
| GPIO13 | RS485_RXD          |
| GPIO32 | RS485_TXD          |

My understanding is that E16P do not have a Buzzer and a onBoard serial.

My understanding is that because of LAN8720 there is also :
  mdc_pin: GPIO23
  mdio_pin: GPIO18
  clk_mode: GPIO17_OUT

Is this correct ? Can you confirm that the second I2C socket Expansion port on E16P is indeed connected to the  I2C_PORT_NUM_0 ? Or if not which port/pin is this ?

Regards,
TR