Hi,
I’m trying to use esphome with the cover component used in esphome.
I’m using a low level shifter and an wemos s2
I can connect to the wemos but I don’t see messages from the unit. I’m using this config
esphome:
name: garagedeur
friendly_name: Garagedeur
esp32:
board: esp32-s2-saola-1
framework:
type: arduino
# Enable logging
logger:
# Enable Home Assistant API
api:
encryption:
key: "************"
ota:
- platform: esphome
password: "58bcb8662f9cc5c509fb260cf0be3497"
wifi:
ssid: home
password: *****
domain: .lan
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "Garagedeur Fallback Hotspot"
password: "********"
web_server:
port: 80
captive_portal:
uart:
rx_pin: GPIO19
tx_pin: GPIO20
baud_rate: 9600
cover:
- platform: tormatic
device_class: garage
name: Novoferm 563s
Here some phofos
Karosm
(Karosm)
2
I imagine, that esphome uses CDC lor logging on S2.
Try with:
logger:
baud_rate: 0
Also inspect carefully your soldering.
Logger I had also, but nothing happes when sending or receiving data
14:57:53 [D] [cover:076]
'Novoferm 563s' - Setting
14:57:53 [D] [cover:084]
Position: 100%
14:57:53 [I] [tormatic.cover:201]
Fully opening gate
14:57:53 [I] [tormatic.cover:312]
Sending gate command Opened
Also when I use the remote nog data is receiving. Is there a debug option on the uart, so I can see it there is some communciation??
Karosm
(Karosm)
4
I mean to set the baud rate to 0, to make sure logger doesn’t spam the line.
Uart has debug option:
...
debug:
direction: BOTH
dummy_receiver: true
after:
delimiter: "\n"
sequence:
- lambda: UARTDebug::log_string(direction, bytes);
Did check the solering again and debug but nothing
16:05:25 [D] [uart_debug:114]
>>> 08:3D:00:00:00:06:01:04:00:0A:00:01
16:05:26 [D] [uart_debug:114]
>>> 08:3E:00:00:00:06:01:04:00:0A:00:01
16:05:26 [D] [uart_debug:114]
>>> 08:3F:00:00:00:06:01:04:00:0A:00:01
16:05:26 [D] [uart_debug:114]
>>> 08:40:00:00:00:06:01:04:00:0A:00:01
16:05:26 [D] [uart_debug:114]
>>> 08:41:00:00:00:06:01:04:00:0A:00:01
16:05:27 [D] [uart_debug:114]
>>> 08:42:00:00:00:06:01:04:00:0A:00:01
16:05:27 [D] [uart_debug:114]
>>> 08:43:00:00:00:06:01:04:00:0A:00:01
16:05:27 [D] [uart_debug:114]
>>> 08:44:00:00:00:06:01:04:00:0A:00:01
16:05:28 [D] [uart_debug:114]
>>> 08:45:00:00:00:06:01:04:00:0A:00:01
16:05:28 [D] [uart_debug:114]
>>> 08:46:00:00:00:06:01:04:00:0A:00:01
16:05:28 [D] [uart_debug:114]
>>> 08:47:00:00:00:06:01:04:00:0A:00:01
16:05:29 [D] [uart_debug:114]
>>> 08:48:00:00:00:06:01:04:00:0A:00:01
16:05:29 [D] [uart_debug:114]
>>> 08:49:00:00:00:06:01:04:00:0A:00:01
16:05:29 [D] [uart_debug:114]
>>> 08:4A:00:00:00:06:01:04:00:0A:00:01
16:05:29 [D] [uart_debug:114]
>>> 08:4B:00:00:00:06:01:04:00:0A:00:01
16:05:30 [D] [uart_debug:114]
>>> 08:4C:00:00:00:06:01:04:00:0A:00:01
16:05:30 [D] [uart_debug:114]
>>> 08:4D:00:00:00:06:01:04:00:0A:00:01
16:05:30 [D] [uart_debug:114]
>>> 08:4E:00:00:00:06:01:04:00:0A:00:01
16:05:31 [D] [uart_debug:114]
>>> 08:4F:00:00:00:06:01:04:00:0A:00:01
16:05:31 [D] [cover:076]
'Novoferm 563s' - Setting
16:05:31 [D] [cover:084]
Position: 100%
16:05:31 [I] [tormatic.cover:201]
Fully opening gate
16:05:31 [I] [tormatic.cover:312]
Sending gate command Opened
16:05:31 [D] [uart_debug:114]
>>> 08:50:00:00:00:06:01:06:00:0A:00:03
16:05:31 [D] [uart_debug:114]
>>> 08:51:00:00:00:06:01:04:00:0A:00:01
16:05:31 [D] [uart_debug:114]
>>> 08:52:00:00:00:06:01:04:00:0A:00:01
16:05:32 [D] [uart_debug:114]
>>> 08:53:00:00:00:06:01:04:00:0A:00:01
16:05:32 [D] [uart_debug:114]
>>> 08:54:00:00:00:06:01:04:00:0A:00:01
16:05:32 [D] [uart_debug:114]
>>> 08:55:00:00:00:06:01:04:00:0A:00:01
16:05:33 [D] [uart_debug:114]
Karosm
(Karosm)
6
I have no idea about the protocol used and if gate should reply or not.
Neither what is the meaning of the second byte that increases on your log…
Have you managed to get it working? I’m in the same situation and I’m not sure why it isn’t.
