I replied on the other thread you made but felt I should highlight something you mentioned about the IFTTT integration and internet loss.
Due to the fact that this SmartApp and device handler are not part of the official SmartThings stuff it won’t run locally on your hub. So if your internet is cut, this still won’t work.
First of, thank you for the amazing work. Made the purchase completely worth it!
Second I would like to volunteer some info for the less experienced users in order to ease the installation a bit. If you disagree with the post for whatever reason I would be happy to remove it.
To install I followed these steps:
Hope this helps.
Can anyone confirm that this still works? Mine can’t seem to find my Maker any more
It’s still working for me.
Thanks worked great for me. Thanks for your work on it!
Thanks much Joe, this was very helpful
Its been a while but I originally set it up with the Wemo app. I had that hub before I switched to Smarthings. Now via somethings I can voice control the door with my Amazon echo\dots. This device uses the ip to connect. From my experience those are the easiest to connect. I would suggest you get power to it and hit the button that connects and look for the led signal that indicates its searching. Then start the add device in smartthings and it should be searching too. When they find each other just follow the prompts.
I added my signal lead into the existing door open limit switch (the one that shuts off the motor when the door opens) by soldering leads from the button to open/close the door and put one contact across both sides of that switch wired to the maker signal leads. You can read the status of that switch to tell if the door is open or closed. I flipped the logic that says a made switch (it’s really closed when door is up) means the door is open. When its an open contact that says the door is open. No need to reverse your thinking about the state of the switch. When you check the app open is open closed is closed.
I have seen others purchase a limit switch to wire in but I just used the ones that are already there. I’m sure that also works but it seemed redundant.
This works great. There are more garage door opener equivalents but from what I saw those were 20-50 dollars more. Maybe that has changed. Good Luck.
My Wemo Maker isn’t recognized any longer either.
I got it to work for me again. I selected ‘Refresh client secret’ in the OAuth settings, then readded my Maker.
Thank you so much for this - I just got this set up a bit ago and so far, it has been successful. I’m hoping it continues working in the long run.
Any chance of getting the WeMo Dimmer set up, too? 
First of all - Thank you for making this. I’ve used it with my WeMo-Maker on my garage door for months now and it works flawlessly. I have a request and don’t know if feasible, but thought it wouldn’t hurt to ask.
Currently, when my garage door is shut, it shows that the “Contact is Open” and when the door is open it shows “Contact is Closed.” Would there perhaps be a way to be able to customize the name of “Contact” as well as the “Open” & “Closed” values? I have a workaround using IFTTT and pushover, but it doesn’t respond nearly as quickly as pushes from the SmartThings app which currently pushes “Contact is Closed” whenever someone opens the garage door. Considered editing script, but didn’t want to mess with a good thing as not familiar with that code.
Just thought I’d ask. Thanks!
Thank you for pulling this together it is exactly what I am looking for. I have the device handler and smart app set up and published in my IDE (can see it from my mobile) but when I attempt to discover my wemo maker nothing is found. I am able to control the maker via the Wemo app on iOS. Has anyone been able to solve it not being discovered? It is running firmware WeMo_WW_2.00.10926.PVT-OWRT-Maker. Any suggestions?
I don’t think you can change the name “Contact” as it’s part of the capability for the device handler.
If you want to invert the contact so that when the door is open, it says “Open” you can configure this under the device settings (the cog when on the device screen - then toggle “Invert Sensor”. That might be the best you can do without writing something more custom.
How long did you wait? Mine can sometimes take a good few minutes before it’ll discover them.
@Kriskit This works awesome I have been using it to automate my gas fireplace. Thank you! I was wondering if you have Git Hub integration for this device handler? I have been trying different combinations of your user, repository, and branch but have been striking out.
I ended up letting is sit and monitored the live logging - as you shared, it was eventually detected and started working. I do occasionally see it go offline but so far it’s up and running. Thanks!
Thanks that worked. I had tried that but did not realize the branch is case sensitive, I had the M in WemoMaker lower case.
I know this is an old comment but I have found that mine constantly goes offline or is offline making it very unreliable. How reliable has this been for others? Are there things I can do to troubleshoot or improve reliability? Any help would be greatly appreciated.
I did have it do this when I originally made it and some had commented on the device handler I got the bulk of the code from that this had happened there too. However, I’m unsure what changed though as I haven’t had them report as being offline for months now so I’m not sure why this would happen 
