Thanks, that did it! I was putting 259 thinking that was my Device ID! Anyway, when it showed up, it said “Closed”, which it was. I then opened it from Things and now it says “Unknown” and I can’t close it with Smarthings. The logs show " Door Status: unknown". The timer for the door being open is working correctly (i.e: 3 minutes), so communication is working partially. Any ideas?
Yeah, that happens sometimes. Have you tried using the Refresh button? Sometimes it helps to leave that screen and come back to it after tapping Refresh if it still says Unknown.
Yes. Refresh will update time since I opened, but status will still say “Unknown”. The second I close it with the native chamberlain app, smartthings picks up the status as closed properly. The issue is when the door is opened.
I have the same problem. Also I don’t get garage door notifications unless the smartthings app is open
Have you tried pulling the screen down to refresh? That will re-synchronize the interface and usually corrects errors where the interface is displaying something that does not reflect the correct state of the device. The refresh button does not correct the issue because the real state of the door is not changing (the device type knows it is open, and when you refresh it gets “open” again, so the interface is not instructed to update itself).
You can view the current state of the device by logging into the IDE and, under your door in the My Devices tab, looking at the “Current States” section. The “Door Status” attribute will show the true state of the door as known by the device handler, and will most likely be the correct status.
Adam
@steveganz thank you very much!! I’m up and running, new mission is getting the ridiculous garage opener to work.
Thanks
Hi,
The current state on the IDE says Unknown and the contact sensor says open. Pulling down to refresh from within app doesn’t fix the issue as it still says Unknown. To add, hitting refresh in the app is the only thing that turns it back from Unknown back to Closed after I close it.
This is exactly what happens to mine as well…
My notifications don’t work unless the app is open either.
Hopefully this will get worked out eventually 
I think it will be pretty sweet when we can add this to our tool set.
Updated the GitHub with a new version. This one optimizes the open/close timings to try avoiding the “Unknown” status issue. It also consolidates the “Door Name” and “Door ID Override” preferences into a single preference. The single “Door Name” preference operates the same as before, just with a single field: If you provide a door name, it will search for it like usual. If you provide a Device ID instead, it will always use that ID.
Adam
2 Likes
Thanks. Unfortunately, it’s still not working for me. Now, when I open the door, the status is still Closed (before it said Unknown) until I refresh and then it goes to Unknown. I also pasted what I see in the IDE below as well.
4c7f2e0b-78d7-4319-b0c2-1116d9c81dc2 6:14:08 AM: debug Door Status: unknown
4c7f2e0b-78d7-4319-b0c2-1116d9c81dc2 6:14:08 AM: debug Sec Token: Left Blank on purpose
4c7f2e0b-78d7-4319-b0c2-1116d9c81dc2 6:14:07 AM: debug Logging In to Webservice
4c7f2e0b-78d7-4319-b0c2-1116d9c81dc2 6:14:07 AM: debug Refreshing Door State
4c7f2e0b-78d7-4319-b0c2-1116d9c81dc2 6:13:30 AM: debug Final Door Status: closed
4c7f2e0b-78d7-4319-b0c2-1116d9c81dc2 6:13:25 AM: debug Opening Door
4c7f2e0b-78d7-4319-b0c2-1116d9c81dc2 6:13:19 AM: debug Door Status: closed
4c7f2e0b-78d7-4319-b0c2-1116d9c81dc2 6:13:18 AM: debug Sec Token: Left Blank on purpose
4c7f2e0b-78d7-4319-b0c2-1116d9c81dc2 6:13:15 AM: debug Logging In to Webservice
4c7f2e0b-78d7-4319-b0c2-1116d9c81dc2 6:13:15 AM: debug Refreshing Door State
contact: open
switch: on
doorStatus: unknown
lastDoorAction: 24 Seconds
Good stuff, @essidle! This update seems to have eliminated all of the status flakiness I’ve been seeing.
Unfortunately that’s still an issue for me as I current status doesn’t update either unless I go to the device and hit “Refresh”.
@mbhelfman, that’s what I was occasionally seeing prior to @essidle’s update last night. Did you save and publish the latest code?
Yes, I updated the code and setup my garage door all over again this morning. It seems the behavior is identical to previous versions.
To summarize, I am seeing two issues:
-
status not updating automatically consistently
-
when I open the door, “door status” goes to Unknown
BTW: When new code is published, do you have to delete the device type, device, etc or can you just update the device type code and re-publish?
I just updated the code and it works flawless!! Great job Adam!!
@Ben any chance you can help me out setting up the ridiculous garage opener?? My goal is to have the garage door open when I arrive. Maybe this last update will fix that and I’ll try it tonight.
Anthony
@bflorian may be the better man for that help @antman2 - hopefully he can find some time to read this thread
@Ben LOL good point!
Is the modified MyQ version not working for you, @antman2?
@steveganz I’m just having an issue figuring out the proper steps to get this up and running.
As far as the Ridiculous Automated My Q Garage Door.
I created a new smart app with the code provided. Was that the right move?
Once I do/did that where do I find it in the ST’s app??
Thanks,
Anthony