As @lcavalli rigthy says, first of all, check that the include path is correct.
After that, as I also recommend in the FAQ, I would start with a basic configuration, like the example yaml in repo, with just the Kyo Unit, 1 Zone and 1 Area configured.
Have you checked the basic configuration?
Once the basic configuration works, add al lthe Zones, Areas, Outputs you have…
Let me know
I used it for month, essentially I only replaced the existing bentel_kyo32.h with the new one. so i guess the path is not the issue, as well also the yaml… I will check again
Hi everyone,
I configured the connection with my Kyo32G control panel and everything works perfectly. However, I can’t understand how to perform the partializations. can someone help me. Thank you.
Hello Lorenzo
First of all, congratulations on the fantastic integration
I wanted to ask you if it is possible to implement the possibility of individually excluding zones also in HA lovelace dashboard
Thank you
Hello Folgore 
good question… it was a change I had in my backlog for a while and I released it today with version v2024.4.26
I was only able to test it with Kyo32, probably on exchanges with fewer zones it will have to be modified.
Let me know 
Hello, maybe my latest version with include and exlude zone command can fit for this? Let me know
hello Loremzo,
you were very quick, I can confirm that the integration has been installed and works perfectly on my kyo32G.
thanks big!!!
Good to hear 
If you would like, you can contribute to the project
Have a nice weekend
if it can be useful to you (if you don’t already have them) I have the (BIS)
BIS is a package of dynamic libraries (dlls) that can be used to develop customized software to integrate Bentel Security products with complex automation systems. The package contains three libraries capable of communicating with the OMNIA, KYO100 and KYO300, KYO Unit, FireClass100 and FireClass 200 series control panels.
Let me know
HI
Yes, I’ve already have this DLL package thanks anyway
Hi, I’m using the exact same setup as your project with the WeMos D1 Mini. Everything was working fine until I updated to the latest version of ESPHome (version 2024.7.3). After the update, I started receiving the following error in the logs:
[11:45:16][E][sendMessageToKyo:744]: No response from the serial port
[11:45:16][W][component:237]: Component took a long time for an operation (110 ms).
[11:45:16][W][component:238]: Components should block for no more than 30 ms.
The first time I encountered this error, it was due to an issue with the RX/TX connection. After switching the cables, everything worked fine. But now it’s not working anymore. Has anyone else experienced this problem? I also tried reverting to a previous version of ESPHome, but the error persists. Can it be some hardware failure, based on your experience?
Thanks
Dan
mmmh, strange… are you using the latest version of code found on my github? (v2024.4.26) ?
Yes, it is the last one, I checked it again.
Hello Lorenzo,
thank you for that integration, it’s very useful.
I only have one little question about your github description.
On the image wiring.png you are showing to connect the esp using the 3v pin, but on the photo BentelKYO32G-Connections.jpg you seem to use the 5v pin of the wemos.
Does it change anything ?
Hello Julien,
I think is the same… the Max3232 chip supports both 3.3V and 5V input… If I don’t remember bad I used the 5V pin on this old Wemos D1 mini, but in any case try it and let me know.
Buongiorno. Installando espkyogate 2024.4.26 ho il seguente errore
INFO ESPHome 2024.8.3
Qualcuno può aiutarmi?
INFO Reading configuration /config/esphome/espkyogate.yaml…
Failed config
esphome: [source /config/esphome/espkyogate.yaml:3]
‘name’ is a required option for [esphome].
includes:
- ./src/bentel_kyo32.h
Buongirno Lorenzo Deluca
ho installato espkyogate 2024-04-26 e mi da i seguenti errori.
Mi puoi aiutare?
Ho notato che rispetto alle versioni precedenti non viene dichiaratao il wi-fi e altro.
non ho nessuna esperienza di yaml
grazie in anticipo
Vincenzo
INFO ESPHome 2024.8.3
INFO Reading configuration /config/esphome/espkyogate.yaml…
Failed config
esphome: [source /config/esphome/espkyogate.yaml:3]
‘name’ is a required option for [esphome].
includes:
- ./src/bentel_kyo32.h
Ciao Vincenzo, sei sicuro di essere partito dal mio ultimo yaml?
Questo era un problema che è stato introdotto con le ultime versioni di ESPHome che ho risolto mesi fa.
Hi Lorenzo,
You were right both are working so I kept the same as the description in the github page!
Everything is working fine thanks for the great work!
Perfect! enjoy