A couple of days ago, one of my two GDO Blaqs started cycling between open and closed states in smartthings. Actual door state, info in the konnected app and the device status page reflect no activity.
If in an false open state in smartthings and view or refresh the connection in linked services, it goes back to closed. A few minutes later, it will go into a false open state again.
It appears to return to closed on what seems to be a heartbeat/refresh of the sercice every few minutes, but almost instantly return to open. Rinse, repeat.
The other GDO Blaq does not behave this way.
Gor them both at the same time arount the end of last year, and they have been fine until this week.
I attempted removing it from konnected, but it remained in the cloud feeding the linked service in smartthings.
Deleted it from smartthings, and of course it came right back due to the linked service.
Is this still working for you? I’m having the same issue (opposite state though, mine says closed when open instead of open when closed). I had support delete it from the cloud and I re-added it, but about 2-4 hours later it’s acting up again. I also can’t delete it from the cloud via the app as I keep getting a “Failed to deregister device. Please try again.” error code. Now I’m back to square one with empty Device info: IP address, ESPHome version, & Konnected project version.
I’m noticing it keeps rebooting as well with either a watchdog timeout or exception/panic reason. The error says: “No client connected to API. Rebooting…”
I think I found out the “No client connected to API. Rebooting”. error. Last firmware I installed I forgot to disable the “Local Native API”; and it’s constantly looking for Home Assistant or Hubitat, which I don’t have. So, I’ll have to manually update the firmware as I can’t seem to get the one get the Konnected Cloud to recognize my device in the app after forgetting it and two my firmware is already: 1.4.1.4 and 1.4.1.1 won’t install due to the version number being lower. But, I still don’t think this will fix the Konnected Cloud or SmartThings errors I’m having.
@nate Do you have any insite as to what might be going on?
After support removed it, i went into Konnected and deleted it and then ST and deleted as well. Added it back in konnected, and re-registered it, which added it back in ST.
No issues since. Mine seemed to be some odd ghost issues on the ST side.
Disable the Local Native API if you do not have a local client (Home Assistant, Hubitat) integrated. If enabled, and no client is connected, it will reboot every 15 minutes by design.
Okay, I got a firmware updated to finally not give me the no client found due to not having a local API. So, no more rebooting due to that every 15 minutes. I still got 2 reboots last night due to a “task watchdog”. But at the time of writting this my GDO blaQ has an uptime of over 10 hours since that last reboot due to this “task watchdog”.
I’m still having the issues within SmartThings though. First issue is the same as suXor. After the garge door is open it will state it is closed within SmartThings, but via MyQ or Konnected Web API it is open. (See first photo below.) Second issue in SmartThings is when I go to open or close the garage door, it cycles randomly as an example: opening…, closed, opening…, closed, open and vise versa: closing…, closed, closing, closed. (See second photo below).
The other issue I’m having is if I try to follow what suXor did and try to deregister it from the Konnected app I get a “Failed to deregister device. Please try again.” error code. (See third photo below). Then the next problem is; I had support yesterday deregister my GDO, but after I registered it again it wanted me to create a new firmware. Which was fine, but the version was older (1.4.1.1) then the current (1.4.1.4) one I had so I couldn’t update it. Is there a way to deregister my device and when I register it again it won’t bug out so I can one have it report the correct firmware I have and two allow me to deregister via the app so I can test what suXor did to fix the SmartThings integration?
@MPHDodgeDaytona Thanks for your patience. I did some research and I think I identified an issue with some inconsistent data on your device on our cloud back-end that is causing this problem. I fixed it up for your device.
Can you please check again now and let me know if the problem is fully resolved?
The first thing I tried was to deregister my device via the Konnected App and was going to reregister it just like suXor did, but this still gives me the “Failed to deregister device. Please try again.” error. So, I just wanted to let you know that error is still present. I don’t know if it’s due to the cloud inconsistencies or there is bug within the App itself. Just FYI I have the Android version with the latest update I can get from the Google Play Store: 1.6.5. FYI, I don’t want to deregister my device if need be, but thought you should know just in case there are problems with the deregistation process.
Next, I checked the SmartThings intergration as I couldn’t deregister and reregister my device. I can confirm that both problems I was having are now fixed. The issue: opening…, closed, opening…, closed, open and vise versa: closing…, closed, closing…, closed issue only happened while opening or closing the GD via SmartThings. The other issue where it would say the door was closed in SmartThings, but was open in MyQ or the Konnected Web API only happened if someone used the physical Chamberlian/Liftmaster Door Button and it become out of sync. I checked both ways lastnight and can confirm that SmartThings reports the correct state no matter the way the door was opened or closed. I even rebooted the GDO Blaq via the Web API afterwards to makes sure it wasn’t a fluke and I had no problems afterwards.
This comes to my last issue other than not being able to deregister my device via the Konnected App. I still get a reboot reason of a “task watchdog” (See photo below). This seems to only happen once, 20-60 minutes after a reboot I do manually via the Web API. It only seems to reboot via this “task watchdog” once as confirmed by my Router’s uptime reports. I’m not sure if this is a major problem or if it even should be happening, but after that “task watchdog” reboot everything seems to run smoothly.
Thanks for confirming! I thought that would fix it and I’m glad that you’ve confirmed that. It looks like the same issue is affecting a handful of other devices, so I’ll roll out the fix permanently. Thank you for helping me get to the bottom of that!
There’s no need to de-register your device. I’m not sure why you’re getting that error – I couldn’t find any logs of a failed de-register attempt in the last 12 hours, so I don’t know what’s going on there. I did notice that your device ID is registered to a different email address than the one you’re using here in the community forum. Could that be it?
The task watchdog reboot is normal and nothing to be concerned about. It happens automatically if something hangs or takes too long, most commonly a WiFi glitch or brief internet outage. It’ll reboot and reconnect automatically if and when that happens.
