I have a chamberlain with the round yellow button myQ that is constantly reporting openings and closings in SmartThings. Sometimes the wall button will not operate the door but manually removing power for a few seconds to the BlaQ fixes it for maybe a few days before the wall button becomes inoperative again. The door is not physically opening and closing as reported in SmartThings but it’s a concern though.
Hi @PpYey, it sounds like maybe your device is rebooting or resetting frequently or unexpectedly? Can you try to take a few screenshots of logs from the device (go to the device’s web page) and also take note of the Uptime metric to see if it has rebooted recently.
Thank You Nate…my wall control is model 41A7185-1, I’ve been searching the community for any issues with this control if any reported.
Here is a screenshot of the logs…it does appear to be rebooting every few minutes…
Time level Tag Message
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;32mI (35571) gdolib: cmd=000 (UNKNOWN) byte2=00 byte1=00 nibble=0
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;33mW (35572) gdolib: Unhandled command: 000 (UNKNOWN)
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;31mE (35573) gdolib: RX buffer read error, 1 pending messages.
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;33mW (35643) gdolib: Oversized packet received: 20 bytes, messages pending: 1
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;32mI (35645) gdolib: received rolling=00eb346 fixed=a31002f016 data=02000108
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;32mI (35646) gdolib: cmd=308 (PAIRED_DEVICES) byte2=02 byte1=00 nibble=1
12:52:26 [I] [secplus_gdo:103]e[1;31m[gdo_main_task]e[0;32m
Paired devices: 2 remotes, 255 keypads, 255 wall controls, 255 accessories, 255 total
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;33mW (35717) gdolib: Oversized packet received: 20 bytes, messages pending: 1
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;32mI (35719) gdolib: received rolling=00eb347 fixed=a31002f016 data=01000208
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;32mI (35720) gdolib: cmd=308 (PAIRED_DEVICES) byte2=01 byte1=00 nibble=2
12:52:26 [I] [secplus_gdo:103]e[1;31m[gdo_main_task]e[0;32m
Paired devices: 2 remotes, 1 keypads, 255 wall controls, 255 accessories, 255 total
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;33mW (35793) gdolib: Oversized packet received: 20 bytes, messages pending: 1
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;32mI (35795) gdolib: received rolling=00eb348 fixed=a31002f016 data=02000308
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;32mI (35797) gdolib: cmd=308 (PAIRED_DEVICES) byte2=02 byte1=00 nibble=3
12:52:26 [I] [secplus_gdo:103]e[1;31m[gdo_main_task]e[0;32m
Paired devices: 2 remotes, 1 keypads, 2 wall controls, 255 accessories, 255 total
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_task]e[0;37m
e[0;32mI (35805) gdolib: SYNC TASK: Getting all paired devices
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;33mW (35828) gdolib: Sent command: GET_PAIRED_DEVICES
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;33mW (35830) gdolib: TX pending, waiting, 0ms since last TX
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;33mW (35831) gdolib: TX pending, waiting, 2ms since last TX
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;33mW (35832) gdolib: TX pending, waiting, 3ms since last TX
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;33mW (35834) gdolib: TX pending, waiting, 5ms since last TX
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;33mW (35913) gdolib: Oversized packet received: 20 bytes, messages pending: 1
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;32mI (35915) gdolib: received rolling=00eb349 fixed=a31002f016 data=00000408
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;32mI (35916) gdolib: cmd=308 (PAIRED_DEVICES) byte2=00 byte1=00 nibble=4
12:52:26 [I] [secplus_gdo:103]e[1;31m[gdo_main_task]e[0;32m
Paired devices: 2 remotes, 1 keypads, 2 wall controls, 0 accessories, 255 total
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;33mW (35987) gdolib: Oversized packet received: 20 bytes, messages pending: 1
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;32mI (35989) gdolib: received rolling=00eb34a fixed=a31002f016 data=05000008
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;32mI (35991) gdolib: cmd=308 (PAIRED_DEVICES) byte2=05 byte1=00 nibble=0
12:52:26 [I] [secplus_gdo:103]e[1;31m[gdo_main_task]e[0;32m
Paired devices: 2 remotes, 1 keypads, 2 wall controls, 0 accessories, 5 total
12:52:26 [I] [secplus_gdo:032]e[1;31m[gdo_main_task]e[0;32m
Synced: true, protocol: Security+ 2.0
12:52:26 [I] [secplus_gdo:034]e[1;31m[gdo_main_task]e[0;32m
Client ID: 1638, Rolling code: 5038015
12:52:26 [D] [number:012]e[1;31m[gdo_main_task]e[0;36m
'Rolling Code': Sending state 5038015.000000
12:52:26 [D] [select:015]e[1;31m[gdo_main_task]e[0;36m
'Security+ protocol': Sending state security+2.0 (index 2)
12:52:26 [V] [mqtt:477]e[1;31m[gdo_main_task]e[0;37m
Publish(topic='esphome/34b7da61236c/select/security__protocol/state' payload='security+2.0' retain=1 qos=0)
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;33mW (36067) gdolib: Oversized packet received: 20 bytes, messages pending: 1
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;32mI (36068) gdolib: received rolling=00eb34b fixed=a31002f016 data=02000108
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;32mI (36070) gdolib: cmd=308 (PAIRED_DEVICES) byte2=02 byte1=00 nibble=1
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;33mW (36136) gdolib: Oversized packet received: 20 bytes, messages pending: 1
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;32mI (36138) gdolib: received rolling=00eb34c fixed=a31002f016 data=01000208
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;32mI (36139) gdolib: cmd=308 (PAIRED_DEVICES) byte2=01 byte1=00 nibble=2
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;33mW (36210) gdolib: Oversized packet received: 20 bytes, messages pending: 1
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;32mI (36212) gdolib: received rolling=00eb34d fixed=a31002f016 data=02000308
12:52:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;32mI (36213) gdolib: cmd=308 (PAIRED_DEVICES) byte2=02 byte1=00 nibble=3
12:52:45 [D] [esp32.preferences:114]
Saving 1 preferences to flash...
12:52:45 [V] [esp32.preferences:126]
sync: key: 1292607660, len: 4
12:52:45 [D] [esp32.preferences:143]
Saving 1 preferences to flash: 0 cached, 1 written, 0 failed
12:52:51 [I] [safe_mode:041]
Boot seems successful; resetting boot loop counter
12:52:51 [D] [esp32.preferences:114]
Saving 1 preferences to flash...
12:52:51 [V] [esp32.preferences:126]
sync: key: 233825507, len: 4
12:52:51 [D] [esp32.preferences:143]
Saving 1 preferences to flash: 0 cached, 1 written, 0 failed
12:54:13 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;33mW (142783) gdolib: Oversized packet received: 20 bytes, messages pending: 1
12:54:13 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;32mI (142786) gdolib: received rolling=00eb350 fixed=a01002f016 data=40600281
12:54:13 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;32mI (142787) gdolib: cmd=081 (STATUS) byte2=40 byte1=60 nibble=2
12:55:51 [V] [mqtt:477]
Publish(topic='esphome/34b7da61236c/sensor/uptime/state' payload='241' retain=1 qos=0)
More logs…seems to be something about oversized packets??
12:57:10 [V] [mqtt:477]
Publish(topic='esphome/34b7da61236c/sensor/wifi_signal_rssi/state' payload='-62' retain=1 qos=0)
12:59:19 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;33mW (449178) gdolib: Oversized packet received: 20 bytes, messages pending: 1
12:59:19 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;32mI (449181) gdolib: received rolling=00eb350 fixed=a01002f016 data=40600281
12:59:19 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;32mI (449182) gdolib: cmd=081 (STATUS) byte2=40 byte1=60 nibble=2
13:00:51 [V] [mqtt:477]
Publish(topic='esphome/34b7da61236c/sensor/uptime/state' payload='541' retain=1 qos=0)
13:02:10 [V] [mqtt:477]
Publish(topic='esphome/34b7da61236c/sensor/wifi_signal_rssi/state' payload='-61' retain=1 qos=0)
13:04:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;33mW (755570) gdolib: Oversized packet received: 20 bytes, messages pending: 1
13:04:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;32mI (755573) gdolib: received rolling=00eb350 fixed=a01002f016 data=40600281
13:04:26 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;32mI (755575) gdolib: cmd=081 (STATUS) byte2=40 byte1=60 nibble=2
13:05:51 [V] [mqtt:477]
Publish(topic='esphome/34b7da61236c/sensor/uptime/state' payload='841' retain=1 qos=0)
And here is the reboot again…
13:07:10 [V] [mqtt:477]
Publish(topic='esphome/34b7da61236c/sensor/wifi_signal_rssi/state' payload='-61' retain=1 qos=0)
13:07:21 [E] [api:128]
No client connected to API. Rebooting...
13:07:21 [I] [app:125]
Forcing a reboot...
13:07:21 [V] [esp-idf:000]
e[0;32mI (930937) gpio: GPIO[1]| InputEn: 0| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
13:07:21 [V] [esp-idf:000]
e[0;32mI (930938) gpio: GPIO[2]| InputEn: 0| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0
13:07:21 [V] [mqtt:477]
Publish(topic='esphome/34b7da61236c/status' payload='offline' retain=1 qos=0)
13:07:21 [V] [esp-idf:000]
e[0;32mI (930944) MQTT_CLIENT: Client asked to disconnect
13:11:17 [V] [mqtt:477]
Publish(topic='esphome/34b7da61236c/sensor/wifi_signal_rssi/state' payload='-62' retain=1 qos=0)
13:11:26 [V] [mqtt:477]
Publish(topic='esphome/34b7da61236c/sensor/uptime/state' payload='245' retain=1 qos=0)
13:14:38 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;33mW (437444) gdolib: Oversized packet received: 20 bytes, messages pending: 1
13:14:38 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;32mI (437446) gdolib: received rolling=00eb705 fixed=a01002f016 data=40600281
13:14:38 [V] [esp-idf:000]e[1;31m[gdo_main_task]e[0;37m
e[0;32mI (437448) gdolib: cmd=081 (STATUS) byte2=40 byte1=60 nibble=2
13:16:17 [V] [mqtt:477]
Publish(topic='esphome/34b7da61236c/sensor/wifi_signal_rssi/state' payload='-61' retain=1 qos=0)
13:16:26 [V] [mqtt:477]
Publish(topic='esphome/34b7da61236c/sensor/uptime/state' payload='545' retain=1 qos=0)
Nate, I have posted logs and screenshot my Web UI…Let me know if you find anything interesting…Thanks!
@PpYey Thanks for posting. Yes I see the problem.
It’s rebooting because the Native API is enabled, but you don’t have any native API client connected (Home Assistant or Hubitat). SmartThings uses Konnected Cloud, so you don’t need the Native API for SmartThings.
The solution is to edit the device settings in the Konnected app, and disable Native API. Then apply the firmware update.
1 Like
Thank You Nate…I did have it integrated with Hubitat as well as SmartThings but had issues with the Alexa integration, so I removed it from Hubitat and just left it integrated with SmartThings and Alexa…so that’s why the API was enabled…Anyways, I just applied the new firmware update disabling the Native API…I’ll have to get back to you later to see if that actually fixed the SmartThings opening and closing issue.
1 Like
@nate - Not sure if this is the same issue but I have been seeing this behaviour as well.
Here are screenshots of a situation I encountered this morning. Screenshot 1 is a list of events for the garage door coming into Smarthings. Screenshot 2 is the device settings in the Konneced app. Screenshot 3 is from the MyQ app.
As you can see from my Smartthings dashboard I am receiving a significant number of events coming through that do not seem to be correct. I do not have the Local Native api enabled.
You can see that the last event in Smarthings is “open” even though the MyQ appp is showing “Closed”
So my wall panel is showing that the garage door is open even though the door is closed.
Please advise if I should be trying a different setting or if you require any more info the debug.
Thanks,
SManCan
@nate - I upgraded to version 1.3.1 and has been stable for a few days now so 
However, I am still having significant issues with the events that are coming through to Smartthings.
For example:
Note that sometimes the last event lands on ‘open’ vs. ‘closed’ or vice versa which then displays the wrong status on my wall panel.
Shouldn’t the events coming through to Smarthings from the Konnected cloud line up with the logs? The logs look as I would expect and don’t show multiple ‘open’ ‘closed’ messages during opening and closing.
In this example I went through an Open and Close using the supplied garage door opener remote.
@SManCan thank you for the detailed screenshots and especially the timestamps! This helped me correlate the logs in our cloud backend and identify the problem!
I just pushed a fix. It shouldn’t happen again!
The device itself is working perfectly (as the logs suggest) but there was a bug in our cloud that was erroneously sending ST a closed state when the position percentage was updated during opening and closing. That’s fixed now.
I’m still working with SmartThings to enable a new device profile that will enable full visibility into the opening position percentage, light, lock and other features of the device. Until then, ST is supposed to ignore those other properties.
Thanks for helping get to the bottom of this.