Great project! I already have an board and it works, but due to security concerns it’s not in use so far. Is there a more secure version of firmware, e.g. to set a individual PIN or usage of biometric data to open/close the garage door while hide this options in MQTT and http access? I have also a Tuya integrated “Garage door button” which I can ask Alexa to open the door and have to enter a PIN. But this is an door opener and I do not have additional sensors. I would like to have all sensors and information from the Hörmann device, and see it on the tablet, but do not want that someone open the garage door, e.g. via my tablet in the kitchen, wihtout entering a PIN at least. Many thanks!
Hi Jurbot,
Which board do you have and do you have a hub like Home Assistant, OpenHAB, …) Who will handle the Mqtt requests? Is your tuya directly connected to alexa?
I handle this with Esphome on the board. Therefore the board is only communicating to the hub in a encrypted channel. In the I have then the possibility to expose the door to alexa with a pin. The tabled is logged in the companion App (In case of home assistant) with a user and therefore dont need to enter the pin.
On the board I deactivated the web access and the Wifi Access Point fallback for security concerns.
Thanks for your reply. I am bought the “Tynet RS485 Bridge - DIY Hörmann MQTT Adapter - ESP32-S3 Dev Board” which works, with “HCPBridgeMqtt_tynet” Firmware. It works in HomeAssistant, but as mentioned, this firmware provide an web based access and without authentication and I would like to have a PIN entry when using in HomeAssistant. Is that possible?
The Tuya Alexa based device is a separate device, which is connected like a wall switch, with Tuya Chip and Alexa support. By default, it requires a PIN entry which I like to have. But this solution not provide any other sensors, it’s just a switch.
Tynet board is already a good start.
The flashed firmware dont give you the possibility neither to limit access on the web interface, web api or mqtt message. The only security layer is the home network. Any user or device in the network can control the door. In home assistant you have then possibly to protect your cover using a this for example. If you exposed the cover to alexa in home assistant it will ask you to set a pin but this will only be required to control if from alexa.
The Esphome port of this project give you the possibility to limit access in your local network also.
1 Like
Hi there.
Does anyone have a board with finished flashed firmware left?
I have a Supramatic P3 drive.
Shipping to Austria.
Thanks in advance.
As my e3 motor is now working the first boards got shipped. Some boards almost ready but I have ordered some new esp as the one installed has poor wifi connection. I have also ordered some more PCB to use all my parts I have left.
I will look everybody asking for a board and contact you by DM.
1 Like
Hi, I’m also looking for PCB compatible with Supramatic E3. Where is possible to buy PCB from Grifford or how to contact him? Thx
I have starting contact the people looking for an E3 board. Please be careful tysonPower or Giffords board are for the E4 series(HCP 2 protocole) and are therefore not compatible.
1 Like
Ok, in this case, can I preorder 2 pcs of the PCB for E2? It is aslo compatible with Lineamatic H2?What is the price? Are You able to send it to CZ?
Hey,
i‘m planning to install the esp to my second Garage door where i also have the hörmann HKSI-1 plugged in for the venting at the moment.
I‘m not interested in getting the data from the HKSI-1 into HA but i want to ask if everything works fine using the esp and the HKSI-1 together at one motor plugged together with the y-cable?
So did you have any problems in the last months or is everything working fine?
Thanks in advance for sharing your experiences!
Hey all,
I made an attempt to get the 3 Series drives to work with only an ESP and RS485 transceiver in esphome. The 4 Series board should basically work in the 3 Series drives with that (mind the pinout thou, that is different!)
Here is the repo: GitHub - Rezoran/hoermann_door: Control Hörmann doors directly via MQTT with ESPhome
Is at the moment working in my SupraMatic E3 for a few days:
Feel free to open an issue if something is not correct or not working
nice that was my next step.
I will shortly put my boards on sale on tindie. So I think that it will be my last batch.
PS your repo don’t allow any issue for the moment.
Hallo,
i have a problem and need a little help.
I‘ve installed one prebuild PCB for my left garage door. Everything works fine with installing it and using it in haos via mosquitto broker. So i‘ve decided also installing a second one for my Right Garage door. Both have the hörmann supramatic 4 E motor.
After connection i‘ve set the wifi credentials, the mqtt user, pw and ip and also disabled the wifi of the PCB. Next the bus Scan… haos explored the new device and i could see both now. But then the problems started:
- only the new device showed the entitys for the control, but only the light switch works. No reaction from my door to the other switches. The old device lost his entities for the control of the door.
- i plugged the new one out and made a bus scan - no reaction via the hörmann remote or the buttons on the motor. Also no change in haos with the old and new PCB device. I also unplugged the old and made a bus scan- no reaction from my door. I killed the electricity for both motors and restarted them without the bridges plugged in. Now they do their work. Then i tried to make it before i installed the second pcb. Just plugged the old one in, started a bus scan and after that both of my garage doors stopped working again. So again killed the electricity, umplugged the old pcb, new bus scan on both motors and now they do their work again…
- i can‘t delete both devices from mqtt in haos to start completely new.
So what have i done wrong? As far as i see i‘m Not the only one using more pcbs at several doors…
Also i have no idea how to reach the ui on the pcbs after i disabled their own wifi…
Thanks for your help. I want my one working door back and maybe after that give the second door a new try…
Maybe a naming collision issue if both of your board share the same name.
You say you have a pre build PCB so I assume it’s one from Tyson. Maybe you should open issue on his GitHub project.
The part I didn’t understand is that when you
You have reset both doors doing a Buscan left door with the old know working pcb and right door nothing connected to it?
Then right door stops working without any device connected to it and with no error code?
When you motor are not responding is there a small point flickering on the screen?
Else I can suggest you to use the Esphome port for example my repo
Maybe the cable got a damage causing the problem.
To connect to your web gui once you deactivated the AP you need to find the IP address of it. Check your router manual how to find them.
As Yannik wrote, i guess you got a device ID conflict in MQTT, just had a customer having similar issues that reached out via email. The solution is to just change the Device ID in the webui, that’s it. If you got the boards from me, feel free to send me an email to [email protected] 
Alos, the WEBUI is always reachable over the IP of the device, just type it into the webbrowser instead of 192.168.4.1.
If you wan’t to make a factory reset in case you can’t reach the webui over your wifi just hold the boot button for more than 5 seconds and release it. After this you will have the AP modea gain to access the device and configure it again
regards,
Manuel
Thank you both for your help.
I‘ve reached both pcbs via their ips and yes i guess the problem is or maybe was the same device id.
I‘ve changed the id from the second pcb. Tomorrow i will connect them to the hörmann motors again start the bus scan and see if both motors are working.
The pcbs are from you tyson. I try it on my own. If i have no success i will send you an email. Thank you!
Good morning,
i’ve tested it again. Still not working.
“Old” PCB (which was working until yesterday when i connected the new one) is reachable in my wifi via ip. The mqtt data in the basic config should be right. I gave the device id “hcpbridgel” and the device name “Garagentor links”.
After connecting to the motor and the bus scan you can see the device in mqtt in HAOS. But the entities are all grey and the connection status is “offline”. Via ip the ui of the pcb is still reachable and shows the state “door open” (which is correct). The buttons for “down, up, etc.” in the ui cause no physical reaction only the light button works.
The new PCB is also reachable in my wifi and i gave the device id “hcpbridger” and the device name “Garagentor rechts”. The mqtt data in the basic config are correct.
After connecting to the motor and the bus scan the motor shows error code “.07” which means “error with communication” and the device ist not found in mqtt in HAOS (yesterday i could see the device in HAOS).
So for now i will try the factory reset of both PCBs giving compelety new device ids and names (which i havent used before) and then give it another try… I will see…
So after the factory reset an renaming them all to new “never seen before” names everything works fine and like suppossed! I’m very happy!
Thanks for all your work for this project!
happy to hear that it now works!
1 Like
I would be interested in two boards, if you still have ones available.