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 !