ratgdo / esphome-ratgdo

ratgdo for ESPHome
GNU General Public License v2.0
310 stars 79 forks source link

Does not work with Chamberlain RollerLift CR655MYQ #176

Closed anuragpathak21 closed 2 weeks ago

anuragpathak21 commented 4 months ago

I am using Australian Chamberlain RollerLift CR655MYQ model.

Tried ESPHome ratgdo with ratgdo 2.5 version following Version 2.5i Security + 1/2 Wiring Diagram but it doesn't work.

Below is the iwring diagram of the RollerLift

image

stevearmitage commented 4 months ago

my RATGDO arrived yesterday (16-Jan) I have the same issues connecting to my roller door (same model as above)

I have installed the latest ESPHome firmware

esphome
by ratgdo
Firmware: 2023.12.7 (Jan 17 2024, 11:18:45)
Hardware: 2.5i

I get the following notification in Home Assistant when the RATGDO reboots

GDO Workshop sync failed
Failed to communicate with garage opener on startup; Check the GDO Workshop Rolling code counter number entity history and set the entity to one number larger than the largest value in history.

The startup logs

11:20:41][I][app:102]: ESPHome version 2023.12.7 compiled on Jan 17 2024, 11:18:45
[11:20:41][I][app:104]: Project ratgdo.esphome version 2.5i
[11:20:41][C][wifi:573]: WiFi:
[11:20:41][C][wifi:405]:   Local MAC: BC:FF:4D:90:4F:B4
[11:20:41][C][wifi:410]:   SSID: [redacted]
[11:20:41][C][wifi:411]:   IP Address: 192.168.67.164
[11:20:41][C][wifi:412]:   BSSID: [redacted]
[11:20:41][C][wifi:414]:   Hostname: 'esp-gdo-workshop'
[11:20:41][C][wifi:416]:   Signal strength: -71 dB ▂▄▆█
[11:20:41][C][wifi:420]:   Channel: 11
[11:20:41][C][wifi:421]:   Subnet: 255.255.255.0
[11:20:41][C][wifi:422]:   Gateway: 192.168.67.1
[11:20:41][C][wifi:423]:   DNS1: 192.168.67.1
[11:20:41][C][wifi:424]:   DNS2: 0.0.0.0
[11:20:41][C][logger:439]: Logger:
[11:20:41][C][logger:440]:   Level: DEBUG
[11:20:41][C][logger:441]:   Log Baud Rate: 115200
[11:20:41][C][logger:443]:   Hardware UART: UART0
[11:20:41][C][ratgdo.number:021]: RATGDO Number 'Rolling code counter'
[11:20:41][C][ratgdo.number:021]:   Unit of Measurement: 'codes'
[11:20:41][C][ratgdo.number:025]:   Type: Rolling Code Counter
[11:20:41][C][ratgdo.number:021]: RATGDO Number 'Opening duration'
[11:20:41][C][ratgdo.number:021]:   Unit of Measurement: 's'
[11:20:41][C][ratgdo.number:027]:   Type: Opening Duration
[11:20:41][C][ratgdo.number:021]: RATGDO Number 'Closing duration'
[11:20:41][C][ratgdo.number:021]:   Unit of Measurement: 's'
[11:20:41][C][ratgdo.number:029]:   Type: Closing Duration
[11:20:41][C][ratgdo.number:021]: RATGDO Number 'Client ID'
[11:20:41][C][ratgdo.number:023]:  Type: Client ID
[11:20:41][C][switch.gpio:068]: GPIO Switch 'Status door'
[11:20:41][C][switch.gpio:090]:   Restore Mode: always OFF
[11:20:41][C][switch.gpio:031]:   Pin: GPIO16
[11:20:41][C][switch.gpio:068]: GPIO Switch 'Status obstruction'
[11:20:41][C][switch.gpio:090]:   Restore Mode: always OFF
[11:20:41][C][switch.gpio:031]:   Pin: GPIO15
[11:20:41][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'Dry contact open'
[11:20:41][C][gpio.binary_sensor:016]:   Pin: GPIO14
[11:20:41][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'Dry contact close'
[11:20:41][C][gpio.binary_sensor:016]:   Pin: GPIO12
[11:20:41][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'Dry contact light'
[11:20:41][C][gpio.binary_sensor:016]:   Pin: GPIO0
[11:20:41][C][light:103]: Light 'Light'
[11:20:41][C][ratgdo:081]: Setting up RATGDO...
[11:20:41][C][ratgdo:082]:   Output GDO Pin: GPIO5
[11:20:41][C][ratgdo:083]:   Input GDO Pin: GPIO4
[11:20:41][C][ratgdo:087]:   Input Obstruction Pin: GPIO13
[11:20:41][C][ratgdo:089]:   Rolling Code Counter: 39
[11:20:41][C][ratgdo:090]:   Client ID: 2155833
[11:20:41][C][ratgdo.sensor:012]: RATGDO Sensor 'Openings'
[11:20:41][C][ratgdo.sensor:012]:   State Class: ''
[11:20:41][C][ratgdo.sensor:012]:   Unit of Measurement: 'openings'
[11:20:41][C][ratgdo.sensor:012]:   Accuracy Decimals: 0
[11:20:41][C][ratgdo.sensor:012]:   Icon: 'mdi:open-in-app'
[11:20:41][C][ratgdo.sensor:013]:   Type: Openings
[11:20:41][C][ratgdo.lock:012]: RATGDO Lock 'Lock remotes'
[11:20:41][C][ratgdo.lock:013]:   Type: Lock
[11:20:41][C][ratgdo.binary_sensor:036]: RATGDO BinarySensor 'Motion'
[11:20:41][C][ratgdo.binary_sensor:036]:   Device Class: 'motion'
[11:20:41][C][ratgdo.binary_sensor:038]:   Type: Motion
[11:20:41][C][ratgdo.binary_sensor:036]: RATGDO BinarySensor 'Obstruction'
[11:20:41][C][ratgdo.binary_sensor:036]:   Device Class: 'problem'
[11:20:41][C][ratgdo.binary_sensor:040]:   Type: Obstruction
[11:20:41][D][api:102]: Accepted 192.168.67.4
[11:20:43][C][ratgdo.binary_sensor:036]: RATGDO BinarySensor 'Button'
[11:20:43][C][ratgdo.binary_sensor:044]:   Type: Button
[11:20:43][W][component:214]: Component api took a long time for an operation (0.28 s).
[11:20:43][W][component:215]: Components should block for at most 20-30ms.
[11:20:43][C][ratgdo.binary_sensor:036]: RATGDO BinarySensor 'Motor'
[11:20:43][C][ratgdo.binary_sensor:036]:   Device Class: 'running'
[11:20:43][C][ratgdo.binary_sensor:042]:   Type: Motor
[11:20:43][C][ratgdo.cover:014]: RATGDO Cover 'Door'
[11:20:43][C][ratgdo.cover:014]:   Device Class: 'garage'
[11:20:43][C][ratgdo.light:014]: RATGDO Light
[11:20:43][C][restart.button:017]: Restart Button 'Restart'
[11:20:43][C][safe_mode.button:022]: Safe Mode Button 'Safe mode boot'
[11:20:43][C][safe_mode.button:022]:   Icon: 'mdi:restart-alert'
[11:20:43][C][homeassistant.time:010]: Home Assistant Time:
[11:20:43][C][homeassistant.time:011]:   Timezone: 'AWST-8'
[11:20:43][C][web_server:168]: Web Server:
[11:20:43][C][web_server:169]:   Address: 192.168.67.164:80
[11:20:43][C][mdns:115]: mDNS:
[11:20:43][C][mdns:116]:   Hostname: esp-gdo-workshop
[11:20:43][C][ota:097]: Over-The-Air Updates:
[11:20:43][C][ota:098]:   Address: 192.168.67.164:8266
[11:20:43][C][api:139]: API Server:
[11:20:43][C][api:140]:   Address: 192.168.67.164:6053
[11:20:43][C][api:142]:   Using noise encryption: YES
[11:20:43][C][improv_serial:032]: Improv Serial:
[11:20:43][D][number:012]: 'Rolling code counter': Sending state 40.000000
[11:20:44][D][api.connection:1121]: Home Assistant 2024.1.3 (192.168.67.4): Connected successfully
[11:20:44][D][time:044]: Synchronized time: 2024-01-17 11:20:44
[11:20:45][D][esp8266.preferences:238]: Saving preferences to flash...
[11:20:49][D][number:012]: 'Rolling code counter': Sending state 41.000000
[11:20:50][D][esp8266.preferences:238]: Saving preferences to flash...
[11:20:57][D][number:012]: 'Rolling code counter': Sending state 42.000000
[11:21:00][D][esp8266.preferences:238]: Saving preferences to flash...
[11:21:10][D][ratgdo:545]: Triggering sync failed actions.
[11:21:10][D][number:012]: 'Rolling code counter': Sending state 43.000000
[11:21:15][D][esp8266.preferences:238]: Saving preferences to flash...
[11:25:31][I][ota:117]: Boot seems successful, resetting boot loop counter.

Here are how the device properties show in Home Assistant

Screenshot 2024-01-17 at 11 13 39 Screenshot 2024-01-17 at 11 13 30 Screenshot 2024-01-17 at 11 13 47

Would appreciate any ideas.

PaulWieland commented 4 months ago

This model door opener doesn't have a serial communication port. You have to use dry contact control protocol with it.

JustDFB commented 4 months ago

As in use the dry contract protocol that doesn't exist for EPSHome yet (coming soon)? If so, any ETA please as it appears there are a number of us in the same situation.... It does support 2.0 - unsure if that is relevant. Thanks

steveshacks commented 3 months ago

Bump. I also have this door and have been unable to get it working using Security protocol (red & white wires).

wotacs commented 3 months ago

Bump. I also have this door and have been unable to get it working using Security protocol (red & white wires).

Paul commented above that the CR655MYQ Opener does not support Security protocol.

We both need to use a dry contact to operate our doors. Bit of a shame, actually. I've just received my 2 units to control my doors. I guess my next step is going to be hacking the radio signal side of things, either the Remote to Motor (433.92Mhz) or preferably the Hub to Motor protocol, which may carry more information as it looks to be a bi-directional link.

PaulWieland commented 2 weeks ago

Dry contact support has been implemented in the ESP Home firmware.