Did you end up making the changes to the code or rewrite it?
Thomas(@thomas.c.howard),
Thank you for porting myQ from ST. Everything is working for me. The only problem I have is inability to use the garage opener in the event section(When this happens) of Alexa routines in order, for example, to create a notification in Alexa when garage door is opened. In the original ST implementation the garage opener is shown in the Alexa event section, but it is not shown in HE. Did you make any porting changes related to this or it's Alexa skill problem in HE?
Honestly, when we did the port, we did as few changes as possible to get it to work. I will take a look when I get home tonight...
Ok, thanks
Thomas, I finally got around to installing my new garage door opener and your code. Thank you for your efforts with the conversion of the app and driver. I did want to point out a few edits I had to make to the app code since I got errors during install.
- You updated the namespace of the driver from "brbeaird" to "tchoward" but you didn't update all the addChildDevice() calls
- I chose not to create push buttons and only the garage door and I got an error while the code was trying to add the child device with the namespace.
- I update lines 350 and 363
- I don't have any light devices but that code would need to be updated too with the proper namespace and driver code would need to be included
Thanks for detailing these changes, I was having the same issued until I updated per your post, then it worked.
Hi, just starting my migration from ST and am trying to get my GDs setup...after entering myChamberlain login details I only get 1/3 of my doors to show up. Any ideas on what to try? PS - I do have the homekit enabled myq hw.
Any chance you could update the code on your github repo soon? I'm having a hard time making the garage door to work with hubitat...
I'm getting the following errors logged with this app:
I tried commenting out the notify part on line 1001 in the app code and then the error changed to this:
Just commented out lines 118 and 126 in the device code and the error disappeared. Not sure if this will have any downstream effects though. Thoughts?
Hot damn... I got it to work.. finally! My mistake was I neglected to create the device driver - myQdevice.groovy. What it was doing was logging into myq and getting the correct info but when it came time to create the virtual button it would error out. Once I installed the driver it was fine.
So here is what I did.. hopefully this can help someone..
Installed the myQAapp code as a user app. Installed the myqdevice as a custom driver in drivers code. I changed every instance of "brbeaird" to "tchoward" - which for me was lines 262,350,363. I also commented out commented out lines 118,126 of the driver code to get rid of the line 1001 error as mentioned by destructure00. I have not noticed any ill effects from it. However, I still have the null object error -
[error]java.lang.NullPointerException: Cannot invoke method currentValue() on null object on line 477 (sensorHandler)
anyway, it seems to be working just fine and for now I will ignore the error as it does not seem to effect anything. Thanks to everyone that has posted their fixes!
How is yours setup? In ST I used an app that combined the tilt sensor and the relay I'm using so it was just one button I had to press and that button showed the state as well. Could also make some automation with it. Without that in HE I have two separate buttons I have to have on the dashboard and I've lost control via Alexa. Any suggestions?
Virtual Buttons and Rules are an amazing deal this month... 
10 for FREE, use as many times as you want.
Create a Virtual Button (Virtual switch with Auto Off) and have it monitored in a Rule that pokes your two existing buttons and put the new one on your dashboard.
How would the virtual switch tile indicate open or closed if it's auto off?
I was thinking you wanted a pushbutton like gets mounted on the wall in the garage. Doesn't have to be auto off... you could use the Tilt sensor to turn it off instead.
If sensor is open display virtual switch as on or if it's closed display it as off? I guess I don't understand how this is accomplished. I understand how to make the virtual button trigger the relay. Right now the relay is set up as a momentary switch. Do I have that set up wrong?
I don't actually know how you have it setup.. when I read your #39 I thought.. oh maybe I have an AHHHA moment in my pocket. Apparently I think too highly of what's in my pocket!!
A Virtual Switch can go on... and cause a Rule to start relay. Another Rule for the Tilt Sensor. When it changes state, it turns off the Virtual Switch. That would also be able to be used by Alexa.
The wording's really close in this example..
I have a Virtual Garage Door Opener called "Pod Bay Doors"
I have a Rule called "the Pod Bay Doors"
Thus I can say to Alexia, pod bay doors open and the Virtual Garage door opener fires the RULE that opens my garage door.
I do not have the two independent elements of Relay + tilt sensor. The Linear is both BUT the Tilt Sensor is integrated to the Linear so it did the combining that you'll have to do via Rules.
I just use a contact sensor on each of my doors and a separate button for each door which also displays the status. All I used was the MyQ app. I can even tell Google home to open/close instead of on/off.
The app combines the sensor and button.
