I've been interrested for a while already in hoermann-hcp protocol, but this seems to be the most closest and finished project to fit my needs. Is there a source where I can get this pcb boards?

I built 2 of these beauties with the boards from stephan192, before I noticed, that they don't work with my SupraMatic E2 doors. Boards are fully assembled, FW is flashed, tested, so you just have to flash ESP32 with your settings again and you are good to go.

Hi Stephan,

Sorry for bothering you but i've managed to source the PCB you designed and flashed both the ESP8266 and the PIC16 with your code to get it up and running in combination with my Hormann Promatic 4 door.

When i connect the PCD to the Hormann BUS:

• Initially nothing happens
• After toggling dip switch 8 (bus scan):
• The PCB is powered
• ESP8266 connects to the network (can ping the device)
• Lights on door start flahsing red/green rapidly (is supposed to happen on bus scan)
• As soon as bus scan finishes PCB loses power

Seems to my like the PCB is not recognized by the bus scan hence powering down the bus.

What could go wrong..?

• is the code not detecting the door?
• Is my PIC16 not flash succesfully?
• Something else?

any suggestions to point me in the right direction would be much appreciated

Thnx!

Hi Stephan, First of all thanks for all your nice work. I've managed to get my hand on a PCB made according to your design and it is working like charm.

I've noticed the presence of a toggle light option in the Pic16 code and was wondering if it is already possible to use this feature through MQTT... could not verify this to be true whilst looking through the esp8266 code.

Thanks in advance !

I've updated HA to the latest version, 2021.6.3, now, mqtt can't load due to the following message:

2021-07-24 11:48:32 ERROR (MainThread) [homeassistant.components.homeassistant] The system cannot restart because the configuration is not valid: Invalid config for [cover.mqtt]: 'position_template' must be set together with 'position_topic'.. Got OrderedDict([('platform', 'mqtt'), ('name', 'garage'), ('command_topic', 'garage/cover/set'), ('state_topic', 'garage/cover/state'), ('qos', 0), ('retain', False), ('payload_open', 'OPEN'), ('payload_close', 'CLOSE'), ('payload_stop', 'STOP'), ('position_open', 100), ('position_closed', 0), ('position_template', '{% if value == "open" %}100{% elif value == "closed" %}0{% else %}10{% endif %}')]). (See ?, line ?).

Any tips?

TIA

Hi Stephan,

Firstly, thanks for your work and your sharing. I discovered that it was possible to draw boards ourself and even ask to build of a small amount of boards from manufacturers or web sites. (Even if I still have to learn a lot before being able to draw a working circuit myself :-D )

I got a board from a participant to your HA Community Forum thread. My garage door is a SupraMatic E2, as far as I can understand from the Article Number on the motor box.

The participant was very kind to flash the PIC for me because I don't have any Microchip programmer. And I flashed the ESP myself.

I can trigger commands: open, close, venting and toggle lights. But the state is not reported, I always get "stopped" in the MQTT topic.

(The buttons on the motor box, the wall and remotes are still working as before, I do not have the error 6 like in the issue #3, but I don't have any UAP1 currently)

I'm quite newbie in hardware development and my first tests are with ESP32 dev boards using the esphome.io project. So, to investigate the problem a bit deeper, I moved your code to an esphome project. I had to use a "custom component" as this implementation is not common off course. I succeed to reproduce the same behaviour: sending commands but no state reports.

I added some logs, especially inside the "parse_input" function, and discovered that the PIC is communicating with the ESP but it always reports 0 in the "state byte".

Here are the logs:

[12:32:52][D][garage:223]: parse_input rx_buffer[0] = 85
[12:32:52][D][garage:224]: parse_input rx_buffer[1] = 0
[12:32:52][D][garage:225]: parse_input rx_buffer[2] = 2
[12:32:52][D][garage:226]: parse_input rx_buffer[3] = 0
[12:32:52][D][garage:227]: parse_input rx_buffer[4] = 0
[12:32:52][D][garage:228]: parse_input rx_buffer[5] = 87
[12:32:52][D][garage:229]: parse_input rx_buffer[6] = 0
[12:32:52][D][garage:236]: parse_input 3 = 0
[12:32:57][D][garage:223]: parse_input rx_buffer[0] = 85
[12:32:57][D][garage:224]: parse_input rx_buffer[1] = 0
[12:32:57][D][garage:225]: parse_input rx_buffer[2] = 2
[12:32:57][D][garage:226]: parse_input rx_buffer[3] = 0
[12:32:57][D][garage:227]: parse_input rx_buffer[4] = 0
[12:32:57][D][garage:228]: parse_input rx_buffer[5] = 87
[12:32:57][D][garage:229]: parse_input rx_buffer[6] = 0
[12:32:57][D][garage:236]: parse_input 3 = 0

Do you have an idea of what could be problematic ? Or where I should investigate more ?

I guess that the problem will be in the PIC code, but I wanted to confirm before going further.

I can share my esphome project code if it can help. I was planning to share it when it was ready.

Thanks in advance for your help!

Hello, your project is great and it's exactlhy what I needed for my Hormann doors. I'm trying to reproduce the board, and while browsing for parts, I've noticed that datasheet for AOZ1038PI says "4.5 V to 18 V operating input voltage range". As per the schematic, the input voltage is 24V. Is it safe to operate in that range? Also the 10u C0805 capacitors should be at least 25V I suppose?

Looking forward for your reply.

Regards

I recently built this project and I am pretty confident, that everything was soldered together and programmed correctly. Right now, a UAP1 and a button is connected to my SupraMaticE2 - this works so far. As soon as I replace the UAP1 with the board from this project, I get following output on my MQTT server:

[2021-05-11 16:39:46.695584] garage_links/cover/state stopped
[2021-05-11 16:39:46.695644] garage_links/sensor/garage/status offline

Unfortunately it does not respony to any of my issued commands:

[2021-05-11 16:41:12.825838] garage_links/sensor/garage/set CLOSE
[2021-05-11 16:41:18.133533] garage_links/sensor/garage/set TOGGLE
[2021-05-11 16:41:59.022011] garage_links/sensor/garage/set OPEN
[2021-05-11 16:42:01.973374] garage_links/sensor/garage/set OPEN

If I want to open close the door manually with the button, I just get fault "6." in the display. This points to a fault on the / open "Schlupftür". But I do not have a "Schlupftür" installed at all and the RJ25 plug with the shorting wire in X30 is placed correctly. As soon as I put UAP1 back in place everything works fine again. Connecting RPi with RS485 and running https://github.com/raintonr/hormann-hcp works too, so I guess the door and control unit are ok.

Any idea from the specialists on how I could debug here?

Hi,

would you mind adding the schematic and the layout as PDF files? As Eagle is not open source and I don't want to install it just to look at the schematic it would be handy to have those in PDF.

I was trying to produce a JLCPCB order list (see attachment), but the following parts are missing and very difficult to find. Are you able to suggest alternatives, or to modify the gerber with some more common ones?

The following should be ok:

• MCP1826S-3302E/DB ==> SPX3940AM3-L-3-3/TR
• ST485BDR ==> ST485EBDR
• ESP-12eSMD ==> ESP-12F(ESP8266MOD)
• 100u ==> RVT100UF16V67RV0120

But I'm having issues with the following:

• AOZ1283PI Can't be found.

• SRN6045TA-220M ==> VLS6045EX-221M or VLS6045EX-220M Lower max current, but is it needed? Also, i think this is a mistake; shouldn't the inductor be 22uH, reading on AOZ1283PI datasheet? So maybe VLS6045EX-220M is a better choice.

• PIC16F15324-I/SL ==> ? Candidates are: PIC16F15325-I/SL but it can't be found PIC16F18326-I/SL but it doesn't have 2 EUSART

I'm really not an electronic engineer and I don't have the skill to change the PCB, but I think that the buck regolator and PIC really need to be changed with more common ones.

RS485Interface_top_cpl.csv RS485Interface_top_bom.csv

The chip you use in the design is basically sold out in all normal shops and I was wondering if I could Replace the PIC16F15324-I/SL with the PIC16F15325-I/SL

Looking at the Datasheet https://ww1.microchip.com/downloads/en/DeviceDoc/PIC16F-LF-1532444-Data-Sheet-DS40001889C.pdf (from https://www.digikey.de/de/products/detail/microchip-technology/PIC16F15324-I-SL/6691276) it seems the only difference is bigger memory. (Not that I really know what I am looking at otherwise)

I also had to redo the power circuitry for similar reasons and ill upload that in a fork or something once i figure out how to actually use github and that it works.