Did you try to reboot your board by plug of motor or by shorting the boot pins on the pcb. This should publish the mqtt message. If it don’t work I would suggest you to flash the Esphome version. If you’re able to flash the pic16 you even get some new function like impulse and soft stop.
I did the reboots by powering off the motor. Shorting of the pins won’t delete everything on the board?
Where do I find this version, bitte?
no boot will not erase the memory (as far as I know).
Esphome E3 repository If any help needed you can open an issue in the github repo.
Thanks, but how do I flash it? Aurduino IDE? There are no *.ino files in the project when cloning the repo
Has anyone got this working with an ESP32 C3 Supermini and ESPHOME? Changing the board and pin-out is not enough.
I saw your issue in GitHub so I know you mean the uap-hcp (e4).
The code of the uap-hcp is designed for a multiple core esp so I don’t know if it will work on c3. For the E3 I was able to get it working with an esp-c3.
I will reply mote in detail on your GitHub issue.
I have the board uapbridge_pic16 from tindie, and I have it connected to my motor (WA 300 S4 Motor). I connected the ESP board to the Motor connector X52
. I am using the following settings:
substitutions:
name: "MYNET"
friendly_name: "MYNETWORK"
state: "State"
opening: "Opening"
closing: "Closing"
open: "Open"
closed: "Closed"
stopped: "Stopped"
venting: "Venting"
error: "Error"
pic16_com: "PIC16 Communication"
relay_state: "Relay state"
got_valid_broadcast: "Valid Status received"
error_state: "Error State"
prewarn_state: "Prewarn State"
light: "${friendly_name} Light"
sw_vent: "${friendly_name} Venting"
sw_light: "Switch Light"
btn_vent: "${friendly_name} Vent"
btn_impulse: "${friendly_name} Impulse"
esphome:
name: "${name}"
friendly_name: "${friendly_name}"
esp8266:
board: esp01_1m
external_components:
- source: github://14yannick/hoermann_door
refresh: 0s
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "MYNET Fallback Hotspot"
password: "A33HQAvt6Q"
api:
encryption:
key: !secret api_key_e3_supra
ota:
- platform: esphome
password: !secret ota_password
logger:
level: WARN
esp8266_store_log_strings_in_flash: False
baud_rate: 0 # Disable Serial logging to avoid conflict with uart bus on UART0
uart:
id: uart_bus
tx_pin: GPIO15
rx_pin: GPIO13
baud_rate: 19200
uapbridge_pic16:
id: garage_door_comp
uart_id: uart_bus
pic16_version: 2 #starting from V2 the Emergency stop gets replaced with a soft stop
cover:
- platform: uapbridge
name: ${friendly_name}
device_class: garage
switch:
- platform: uapbridge
venting_switch:
id: venting_switch
name: "${sw_vent}"
#uncomment if you want to use the switch insteat of the light component for light
# light_switch:
# id: light_switch
# name: "${sw_light}"
binary_sensor:
- platform: uapbridge
pic16_com:
name: "${pic16_com}"
relay_state:
name: "${relay_state}"
error_state:
name: "${error_state}"
prewarn_state:
name: "${prewarn_state}"
got_valid_broadcast:
name: "${got_valid_broadcast}"
output:
- platform: uapbridge
id: gd_light
light:
- platform: uapbridge
id: my_light
name: "${light}"
output: gd_light
text_sensor:
- platform: uapbridge
id: garage_door_state
name: "${state}"
#uncomment the line for custom text
# filters:
# - substitute:
# - "Opening -> ${opening}"
# - "Closing -> ${closing}"
# - "Open -> ${open}"
# - "Closed -> ${closed}"
# - "Stopped -> ${stopped}"
# - "Venting -> ${venting}"
# - "Error -> ${error}"
button:
- platform: uapbridge
vent_button:
id: button_vent
name: "${btn_vent}"
impulse_button: #is only implemented in PIC16 V2 firmware
id: button_impulse
name: "${btn_impulse}"
#optional BME Sensor
#i2c:
# - id: bus_1
# sda: SDA
# scl: SCL
# scan: true
#sensor:
# - platform: bme280_i2c
# temperature:
# name: "BME280 Temperature"
# pressure:
# name: "BME280 Pressure"
# humidity:
# name: "BME280 Humidity"
# address: 0x76
# update_interval: 10min
I can connect via HomeAssistant ESPHome builder plugin to the device. The device does not blink nor does it anything, but I am connected. This I can see on the logs. The dashboard also shows the control. But the standard control like close to close the door does not do anything. I also removed the control-unit and still it does not react. Any hint what I am doing wrong?
Hi,
I think it can be related to this issue.
Basically the communication of an supramatic E3 has been retro engineered. It looks like something is missing to work with some other model. Write me on tindie I can make you a proposal to solve this issue.
An update for Hörmann Liftronic 700-2, might be useful for someone:
I was able to get it working with hardware and code from @14yannick - M5 Atom lite, Tail485 module. Works very well.
Thanks @14yannick !
Hello
I have a board that provided me with @14yannick and a few weeks ago it stopped working.
suddenly one day the engine would not start and it only works if I disconnect the board.
If I reconnect the board the motor turns off until I disconnect it again.
I think the board is shorted. How can I check it?
hi 14yannick, how can i contact you privately, to ask for help to configure my esp32 rs485 board for the Promatic 4
Ok nice to hear. I just got a new Liftronic 700-2 installed and would be interested in getting to know how to get it working.
Hi, on the github there is a instruction how to build your board. I like the M5stack lineup. You can use an atom s3 lite with a rs485 tail or base and 120Ohm resistance a cable and you have your board. Or you can purchase a ready to use board from Gifford or Tyson. For the Firmware I recommend my repo
Ok thanks, I think a will order a ready made board then. But I was more after the compatibility with Liftronic 700-2. I know it supports the same protocol as the ones mentioned here but I don’t know if it will really work. Have anyone tested?
It seems like I’m the lucky one to get @14yannick:s last boards from Tindie. (You are generous!) How happy I am!
I currently have Qubino devices to trigger “impulse” and sensors on the doors and look forward for an upgrade.
I haven’t had the time or skills to create a board myself. But have from time to time been looking for finished ones.
However, looking at the code, it seems that the ESPHome part of the code hoermann_door/esphome/components/uapbridge/button/uapbridge_button.h at main · 14yannick/hoermann_door · GitHub do not implement stephan19:s all possible actions (up, down, stop, …). Is there a reason for this, or is it just that whoever implemented this didn’t find it necessary? Or that this was just an initial implementation? I hope that I can add these actions in a fork.
Hi, This actions are part of the Cover Component and therefore don’t need separate button.
In home assistant you board will Look something like this.
1 Like
Hi,
I have absolutely same board and absolutely same issue. After half year the board stopped working - there is short between +24V and GND. I found issue - the capacitor near the 5V stabilisator is dead (see picture of missing cap). I think You can see the same on Your board. I think it should be OK to simply remove the capacitor, @14yannick what do You think about it?
For me this sounds like a capacitor with a to small rated voltage was populated for C1. C1 is a simple 10µF cap in 0805 package, but its rated voltage should be at least 50V to not let C1 die over time.
In most cases leaving it out shouldn’t be a problem. But in some edge cases e.g. spikes or drops on the supply voltage C1 protects to rest of the circuit from beeing destroyed. In other words i would replace C1 with a cap with the right capacitance and rated voltage.
No sorry. I gave up.
I need some help. I use ESPHome and have wired my own esp32. Attached is a picture of the wiring. I have also attached my esphome config. I have tested to swap RX/TX in the config, but when i swap the light on RS485 don’t light up.
When i toggle the switch on the motor to do a bus Scan, the light on rs485 module lights up, but turns of again after a couple of seconds. And the status on the device never changes from disconnected.
esphome:
name: hcp-bridge
friendly_name: HCP Bridge
libraries:
- emelianov/modbus-esp8266
platformio_options:
board_build.f_cpu: 240000000L
board_build.flash_mode: qio
monitor_speed: 9600
monitor_filters: esp32_exception_decoder
lib_ldf_mode: deep+
external_components:
source: github://mapero/esphome-hcpbridge
refresh: 0s
esp32:
board: esp32dev
framework:
type: arduino
hcpbridge:
is_connected:
name: "HCPBridge Ansluten"
rx_pin: 17 # optional, default=18
tx_pin: 16 # optional, default=17
cover:
- platform: hcpbridge
name: Garageport
switch:
- platform: hcpbridge
name: Garagebelysning
logger:
baud_rate: 0 # Inaktiverar USB-loggning om UART0 används
api:
encryption:
key:XXXX masked XXXX
ota:
- platform: esphome
password:XXXX masked XXXX
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password