KenCony A16 v3 board discovered but has no entities

ESPHome
1

ESPHome has discovered my A16 board but says it has no entities. What do I have to do to complete this process? I am only interested in the digital inputs and outputs at this time. Do I need to have a statement in the YAML to specificly enable each input or output and if so what is the appropriate keyword?

Yes I have allowed all updates t y HomeAssistnt Yellow. And I have rebooted entire system many times. For what it is worth I am successfully using HA Yellow for numerous Z-wave light switches, 14 Ubiquity Cameras, 3 everything Lite presence detectors, and the HA voice assistant. But this KenCony A16 board is being very stubborn. Please help if you can.

2

Yes.

3

OK, expected that, but what exactly is that statement? I tried “enabel:” that was not accepted as a valid statement.

4

Try using the yaml @Karosm pointed you to.

5

If you are playing first time with esphome devices, may I suggest you to start with some “basic” Esp32 dev board. This Kincony can give hard time even for experienced user.

6

I looked over the referenced YAML and it is nearly the same as what i already have. A few naming differences, us of wifi rather than ethrrnet. I ws not able to see any place where DIO input or outputs, or any of the many other things for that matter, were specically ‘enabled’. My YAML verifies s valid whatever that means. I get commpleted comppile and flashes to the board. The board display lights up but only shows the time, and a reference to ‘tuya’ offline. Preessing th board’s ‘reset’ button does nothing helpful, just causes the connected laptop to beep.

7

If you have input or output pin configured, you don’t need to “enable” it anyhow.
Anyway, consider my suggestion above.

8

What board would you suggest. I really need inputs for existing wired switches at various doors.

9

I don’t know what your “switches at doors” are, but to start experimenting with Esphome I suggest plain Esp Wroom32 dev board.

10

OK, I will look into that thanks.

When I built by house in 1999 I placed ‘state of art’ magnets and reed relays at all doors and windows. That was the thing for home security at the time. Now everything is battery powered which seems moving backwards to me - all those batteries to check on. And the new battery things aren’t cheap either if you need 16 of them.

11

I agree with that.
Since reed switches are just “mechanical” switches, you can adapt them to any setup.

Reading your post again makes me wonder if your confusion with Kincony is not really esphome related but just some HA setup thing…

12

Could be I suppose. But what could it be? Surely someone has a working A16v3 board and can say what is needd to get from board being listed under ESPHome as 1 devise, but no entities. I have powered down the HomeAssistant box hoping that would cause a research for entities, Hve done many 'reboots of system, lots of resets. Have gone through entire ESPhome device builder process. And every time I get same results - no entities. Other devices have always just worked. and in fact it was that very feature that got m to try using HA in the first place. At one point I was able to gt to the KenCony Monitor which would let me enable various capabilities, though even with that the entities never showed up. Now I can’t get to that KenCony page and have no idea where it is hidden.

13

If you post your YAML we could comment.

14

OK, seems like a lot to post, but you asked.

esphome:
name: a16v3-board
friendly_name: a16v3-board
platformio_options:
board_build.flash_mode: dio

esp32:
board: esp32dev
framework:
type: esp-idf

wifi:
ssid: WA1DLZ
password: “ham-radio-hsmm-fcc-part97”

#manual_ip:
#Set this to the IP of the ESP
#static_ip: 192.168.0.189
#Set this to the IP address of the router. Often ends with .1
#gateway: 192.168.0.1
#The subnet of the network. 255.255.255.0 works for most home networks.
#subnet: 255.255.255.0

Enable fallback hotspot (captive portal) in case wifi connection fails

ap:
ssid: “WA1Dlz Fallback Hotspot”
password: “kzzws1cqL0OY”

#ethernet:

type: LAN8720

mdc_pin: GPIO23

mdio_pin: GPIO18

clk_mode: GPIO17_OUT

phy_addr: 0

#manual_ip:

static_ip: 192.168.0.189

gateway: 192.168.0.1

subnet: 255.255.255.0

dns1: 192.168.0.1

dns2: 8.8.8.8

logger:

api:
encryption:
key: “NE89nbrEFZKEW0SkesSSX71IxH2mhFZhxE8JnY19C6k=”

ota:

  • platform: esphome
    password: “a2bbe5387c73314b10b3070744de2274”

uart:

  • id: rs485
    tx_pin: GPIO13
    rx_pin: GPIO16
    baud_rate: 9600

remote_receiver:
pin:
number: GPIO2
ignore_strapping_warning: true

remote_transmitter:
pin:
number: GPIO15
ignore_strapping_warning: true
carrier_duty_percent: 100%

i2c:
sda: GPIO4
scl:
number: GPIO5
ignore_strapping_warning: true

pcf8574:

  • id: inputs_1_8
    address: 0x22
    pcf8575: false
  • id: inputs_9_16
    address: 0x21
    pcf8575: false
  • id: outputs_1_8
    address: 0x24
    pcf8575: false
  • id: outputs_9_16
    address: 0x25
    pcf8575: false

binary_sensor:

  • platform: gpio
    name: “KC868-A16-HT1”
    pin:
    number: GPIO32
    inverted: true

  • platform: gpio
    name: “KC868-A16-HT2”
    pin:
    number: GPIO33
    inverted: true

  • platform: gpio
    name: “KC868-A16-HT3”
    pin:
    number: GPIO14
    inverted: true

##---- 16 Digital Dry Contact Inputs ----

  • platform: gpio
    name: “A16v3_input1”
    pin:
    pcf8574: inputs_1_8
    number: 0
    mode: INPUT
    inverted: true

  • platform: gpio
    name: “a16v3_input2”
    pin:
    pcf8574: inputs_1_8
    number: 1
    mode: INPUT
    inverted: true

  • platform: gpio
    name: “KC868-A16-X03”
    pin:
    pcf8574: inputs_1_8
    number: 2
    mode: INPUT
    inverted: true

  • platform: gpio
    name: “KC868-A16-X04”
    pin:
    pcf8574: inputs_1_8
    number: 3
    mode: INPUT
    inverted: true

  • platform: gpio
    name: “KC868-A16-X05”
    pin:
    pcf8574: inputs_1_8
    number: 4
    mode: INPUT
    inverted: true

  • platform: gpio
    name: “KC868-A16-X06”
    pin:
    pcf8574: inputs_1_8
    number: 5
    mode: INPUT
    inverted: true

  • platform: gpio
    name: “A16-X07”
    pin:
    pcf8574: inputs_1_8
    number: 6
    mode: INPUT
    inverted: true

  • platform: gpio
    name: “KC868-A16-X08”
    pin:
    pcf8574: inputs_1_8
    number: 7
    mode: INPUT
    inverted: true

  • platform: gpio
    name: “KC868-A16-X09”
    pin:
    pcf8574: inputs_9_16
    number: 0
    mode: INPUT
    inverted: true

  • platform: gpio
    name: “KC868-A16-X10”
    pin:
    pcf8574: inputs_9_16
    number: 1
    mode: INPUT
    inverted: true

  • platform: gpio
    name: “KC868-A16-X11”
    pin:
    pcf8574: inputs_9_16
    number: 2
    mode: INPUT
    inverted: true

  • platform: gpio
    name: “KC868-A16-X12”
    pin:
    pcf8574: inputs_9_16
    number: 3
    mode: INPUT
    inverted: true

  • platform: gpio
    name: “KC868-A16-X13”
    pin:
    pcf8574: inputs_9_16
    number: 4
    mode: INPUT
    inverted: true

  • platform: gpio
    name: “KC868-A16-X14”
    pin:
    pcf8574: inputs_9_16
    number: 5
    mode: INPUT
    inverted: true

  • platform: gpio
    name: “KC868-A16-X15”
    pin:
    pcf8574: inputs_9_16
    number: 6
    mode: INPUT
    inverted: true

  • platform: gpio
    name: “KC868-A16-X16”
    pin:
    pcf8574: inputs_9_16
    number: 7
    mode: INPUT
    inverted: true

##---- 16 Digital Output switches ----
switch:

  • platform: gpio
    name: “A16-Y01”
    id: out_y01
    pin:
    pcf8574: outputs_1_8
    number: 0
    mode: OUTPUT
    inverted: true

  • platform: gpio
    name: “A16-Y02”
    id: out_y02
    pin:
    pcf8574: outputs_1_8
    number: 1
    mode: OUTPUT
    inverted: true

  • platform: gpio
    name: “A16-Y03”
    id: out_y03
    pin:
    pcf8574: outputs_1_8
    number: 2
    mode: OUTPUT
    inverted: true

  • platform: gpio
    name: “A16-Y04”
    id: out_y04
    pin:
    pcf8574: outputs_1_8
    number: 3
    mode: OUTPUT
    inverted: true

  • platform: gpio
    name: “A16-Y05”
    id: out_y05
    pin:
    pcf8574: outputs_1_8
    number: 4
    mode: OUTPUT
    inverted: true

  • platform: gpio
    name: “A16-Y06”
    id: out_y06
    pin:
    pcf8574: outputs_1_8
    number: 5
    mode: OUTPUT
    inverted: true

  • platform: gpio
    name: “A16-Y07”
    id: out_y07
    pin:
    pcf8574: outputs_1_8
    number: 6
    mode: OUTPUT
    inverted: true

  • platform: gpio
    name: “A16-Y08”
    id: out_y08
    pin:
    pcf8574: outputs_1_8
    number: 7
    mode: OUTPUT
    inverted: true

  • platform: gpio
    name: “A16-Y09”
    id: out_y09
    pin:
    pcf8574: outputs_9_16
    number: 0
    mode: OUTPUT
    inverted: true

  • platform: gpio
    name: “A16-Y10”
    id: out_y10
    pin:
    pcf8574: outputs_9_16
    number: 1
    mode: OUTPUT
    inverted: true

  • platform: gpio
    name: “A16-Y11”
    id: out_y11
    pin:
    pcf8574: outputs_9_16
    number: 2
    mode: OUTPUT
    inverted: true

  • platform: gpio
    name: “A16-Y12”
    id: out_y12
    pin:
    pcf8574: outputs_9_16
    number: 3
    mode: OUTPUT
    inverted: true

  • platform: gpio
    name: “A16-Y13”
    id: out_y13
    pin:
    pcf8574: outputs_9_16
    number: 4
    mode: OUTPUT
    inverted: true

  • platform: gpio
    name: “A16-Y14”
    id: out_y14
    pin:
    pcf8574: outputs_9_16
    number: 5
    mode: OUTPUT
    inverted: true

  • platform: gpio
    name: “A16-Y15”
    id: out_y15
    pin:
    pcf8574: outputs_9_16
    number: 6
    mode: OUTPUT
    inverted: true

  • platform: gpio
    name: “A16-Y16”
    id: out_y16
    pin:
    pcf8574: outputs_9_16
    number: 7
    mode: OUTPUT
    inverted: true

15

Please edit your post to insert code tags, so it becomes readable.

Also post what it is written on your Esp32 module casing.
The config I posted link uses S3 chip but you don’t use that configuration on yours.

1 Like
16

And while you’re about it, the log from compiling and upload, followed by it booting.