esphome:
  name: kc868-a4
  platform: ESP32
  board: esp32dev

# Enable logging
logger:

# Enable Home Assistant API
api:

wifi:
  ssid: "KinCony"
  password: "xxxxxxxx"


captive_portal:

web_server:
  port: 80

remote_receiver:
  pin:
    number: 23
    inverted: True
  dump: all

 
remote_transmitter:
  pin:
    number: 22
  carrier_duty_percent: 50%

switch:
  - platform: template
    name: "TV Power"
    turn_on_action:
      - remote_transmitter.transmit_nec:
          address: 0x00BD
          command: 0x807F
          repeat:
            times: 10
            wait_time: 50ms
    turn_off_action:
      - remote_transmitter.transmit_nec:
          address: 0x00BD
          command: 0x807F
          repeat:
            times: 10
            wait_time: 50ms

Is there any possibility of RS485 connection ?

Hello everyone!

I have same problem like this posting https://www.kincony.com/forum/showthread.php?tid=1178

Did you solve this problem?

Problems I am facing.

1. KC868-H32B is setup with magnetic contactor and RC snubber. but sometimes it goes down. MQTT No response.

2. When it was not working. The setup page like this.


subnet mask and gateway changed.
3. When connecting included WIFI antenna. KC868-H32b goes down.

I look forward to your feedback..

Attached Files

Thumbnail(s)
   

Hello, after creating some rules in the IFTTT page I got this error message you see in the image. it looks like something related to the name. it just does it to me with IFTTT number 3 and 4. how can i solve?

Attached Files

Thumbnail(s)
   

Hi. Is the Alexa module still needed in the h32bs or is it already built-in there?

KinCony ESP32 application course is published on the udemy online course platform for everyone to learn for free. At the same time, we will publish on the online course platform of Espressif's official website, and we will continue to produce more courses based on ESP32 applications.
https://www.espressif.com/en/ecosystem/i...ge/courses

can this controller be updated from version 4.13.26 

allow for MQTT option?  4.13.26  4.13.26 4.13.26

Hi. I'm planning to connect the protection fuses before the relays, and not after as shown in the tutorials. This way I would be able to have one fuse for a group of channels (for example all lights in an area/room).

I do so because of 2 reasons: (1) Such connection is viable in my house because, for example, the wiring to all the lights for the living room is being passed through a single connections-box. Using wiring of different protected circuits in the same box is prohibited by law in my country. (2) Grouping circuits use fewer fuses and save space in the power distribution box.

Can such a connection cause any problem? The relays module has a varistor per channel, and I read online that a fuse has to be connected over the circuit with the varistor. My question regards the location of the fuse. Schematically, I'm asking whether it is critical to have the fuse on the closed-circuit between the varistor and the device (like you suggest in your tutorials), or is it also fine to connect the fuse to the feeding phase (leaving the closed circuit between the varistor and the consumption end device without any protection, as shown in the diagram below). I don't really understand the theory behind the varistor's operation, so I don't know if it may be a problem leaving it with the device in a closed circuit without protection on it.
   

Thanks for the help!

Hi.
I noticed there are blue capacitors attached to the load terminals of the OMRON relays module (can be seen in the picture attached below).
Can you please explain what is their purpose? what they are needed for?

   

I have set up my KC868-H32B with MQTT in late august 2021 (I have over a hundred devices working flawlessly with MQTT). I use the inputs to monitor doors and gates and the relays to act as push buttons or switch on/on devices that do not remain on for a long time nor change often.



In the last two weeks, the KC868 started to freeze (not accepting MQTT commands nor reporting status).
Power-cycling it solved the issue at first but not anymore.

I tried to upgrade the firmware today and it did not change anything.

I configured the HC868-32B to use UDP (and not MQTT anymore) and started issuing commands as described here but it also stops working after about 10 mn. Moreover, the Web interface does not answer anymore either (only ping keeps working).

My network and my MQTT broker are working OK (as mentionned over a hundred MQTT devices are working flawlessly).

Please advise.