[Broken] MyQ Lite Application

[dman2306]

Yeah, he has that command line based method because ST doesn't provide a way to do the initial auth locally. So for HE I started with his code base but then made the additions to support the local auth which HE does allow as of 2.2.9. I agree with you, I can't see anything in his code that explains why he removed that closing message.

[jbferr]

@dman2306 Have you had a chance on your end to see what I was seeing on closer/Open devices ?

[dman2306]

Can you provide debug logs? I’ve never used the momentary buttons. That was just directly opined from SmartThings

[kwoolf]

@jbferr

@dman2306 I am having issues with the Momentary Button Tile (Garage Door Closer/Opener Device). What I noticed is that when activating the the on command it was getting into a continuous loop and calling the myqapi over and over again and you could see the state flipping to on/off over and over again and the garage door was going nuts and causing high CPU on the habitat lol. I spent about an hour just randomly trying things in the Momentary Button driver and I think I have it in a working state however I'm sure their is a better way than what I did. I commented line 46,47, and 56. I only ever use the on command so I'm not sure if this will work on other commands but so far so good.

I had this problem as well. Activating the garage door (using the nosensor version) gets into a neverending loop. Here is what the log shows (over and over):

app:412021-10-12 12:43:35.072 pm debugDoor open button push detected: Event name momentary value: pushed deviceID: 113 DNI: CG0844007976 Opener

app:412021-10-12 12:43:35.056 pm debugDevice already in desired state. Command ignored.

app:412021-10-12 12:43:34.975 pm debugDoor open button push detected: Event name momentary value: pushed deviceID: 113 DNI: CG0844007976 Opener

app:412021-10-12 12:43:34.961 pm debugDevice already in desired state. Command ignored.

Had to remove the device to stop it. This was initiated by using the "momentary buttons" created by the MyQ app, which I had used (and had been previously working) with some rules. I was able to fix this by using the "Garage door" (not garage door opener/closer) device instead, which seems to work just fine. Not sure what changed from before the recent API break though.

[jbferr]

yeah if you comment the lines i suggested it will resolve the problem but the "on" command is the only one that works with my suggestion. The only reason I use this is for alexa routines since it only supports on/off

[672southmain]

Dominick (@dman2306), one minor issue that may be related to the direct port from SmartThings: The Debug log toggle doesn't turn off automatically 30 minutes after turning it on. No big deal, it's easy to turn it off manually.

[dman2306]

Can you try this file https://raw.githubusercontent.com/dcmeglio/hubitat-myq/momentary_button_fix/devicetypes/brbeaird/momentary-button-tile.src/momentary-button-tile.groovy ?

[dman2306]

Hmm it should, I'll have to see why. The code to turn it off is definitely in there.

[672southmain]

FYI, samples from the log:

They stopped when I manually turned the Debug log switch off this morning, after updating when you fixed a few days ago, much longer than 30 minutes in the past.

[gecco2003]

Same process for me. Take about 10 minutes after the update and repair to work again but it did the trick. Thanks for the post.

[jbferr]

@dman2306 Submitted a pull request on your branch the one you proposed did not work.

[RickNY]

I was hoping someone could help.. When I try sending commands to my garage doors (open, close) - they are failing and the logs are indicating:

2021-10-13 10:42:26.205 am errororg.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_app_brbeaird_MyQ_Lite_136.sendCommand() is applicable for argument types: (java.lang.String, java.lang.String) values: [CG08468-----, open]

(masked the last 5 of the ID above)

I updated my Hubitat this morning, and repaired the MyQ lite application with HPM.. Not sure if I did something to break this or not.

Thanks
Rick

[672southmain]

Did you follow Dominick’s instructions after doing an HPM update / repair?

@dman2306

I published the new version. You will need to update and do two things:

1. In the app, re-enter your MyQ username and password and login
2. Go to the screen where you select your MyQ devices and go through that workflow (make sure to click Done at the end!)

Everything should work after that. There is no need to do a separate token generation like with SmartThings, everything is handled in the app automatically.

That was sufficient for me to get it working again.

[RickNY]

Yes, I did both of those steps

[dman2306]

Looks like you updated the app but not the driver.

[RickNY]

Not sure what happened, since it was installed with HPM.. At any rate, I ended up removing everything related to it and installing it again and now its working.

[robert2]

No luck here, I removed it and tried to reinstall and get this error:

There was a problem updating devices:
java.lang.NullPointerException: Cannot get property 'deviceNetworkId' on null object.
Line number: 611
Last successful step: Sensor Indexing

[dman2306]

I’ve only seen that if the device driver isn’t installed.

[robert2]

Redid the driver and the app code, the issue I get now is the door keeps opening and closing on its own, the momentary button keeps pressing off and on, not sure what's up there.

app:2112021-10-14 02:21:41.733 pm debugDevice already in desired state. Command ignored.

app:2112021-10-14 02:21:41.671 pm debugDevice already in desired state. Command ignored.

Which is now causing my hub to freak out and have high cpu load, a ton of functions and logs coming through. This happens if I use the momentary buttons or if I use the actual door device itself.

[dman2306]

Yeah there is a reported bug with the no sensor version I’m going to dig into further this weekend but someone posted a workaround a little bit back in the post.