Garage door local options
2 Likes
I spent some time yesterday deleting the old driver and app and installing this package via the package manager. The device reports the battery and all activity correctly, but I can't perform any activities on the door. I press open or close in the device and nothing happens (I also don't see anything in the log to indicate an attempted activity). Is this to be expected? Or did I misread the previous posts and this package will definitely no longer work?
Did you rename your door in Hubitat? I had that issue when I changed the name in Hubitat (Overhead Garage Door) whereas logging into the MyQ app had it as "Garage Door". When they matched, it worked, when I renamed it, they stopped working. I just changed the name in MyQ app to match Hubitat, and all was good again.
@ lpakula Thanks, that is a good though t - I have since made them the same.
I may have missed an error before after all. I am seeing these in the device logs:
MissingMethodExceptionNoStack: No signature of method: user_driver_brbeaird_MyQ_Garage_Door_Opener_832.parse() is applicable for argument types
What is it saying after "argument types". Looks like something is missing in the parse() code
@lpakula Thanks for the reply! Here is the entire error:
org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_brbeaird_MyQ_Garage_Door_Opener_832.parse() is applicable for argument types: (java.lang.String) values: [zw device: 11, command: 6603, payload: FD , isMulticast: false]
Possible solutions: close(), push(), main(java.lang.String), use([Ljava.lang.Object;), wait(), run() (method parse)
Looks like a zwave device that cannot be parsed. What are you linking that is zwave to this app? Is that the door sensor?
@lpakula I am trying to link the myq device itself. It has a tilt sensor attached to it. Did I pick the wrong driver?
Maybe? Might need the authors of this integration to chime in. My MyQ needs and external sensor, so for me it's the "MyQ Garage Door Opener" driver, When I check Hubitat Package Manager, View Apps and Drivers, these are the versions I'm seeing:
-
MyQ Garage Door Integration Documentation | Community Thread
- MyQ Lite v3.2 (app)
- MyQ Garage Door Opener v3.2 (driver)
- MyQ Garage Door Opener-NoSensor v3.2 (driver)
@lpakula Thank you again! Which driver are you using in the device itself? I tried using the 3.2 "No-Sensor" driver (I did not have it installed before) this time, and I am seeing this error:
org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_brbeaird_MyQ_Garage_Door_Opener_NoSensor_833.sendOpen() is applicable for argument types: () values: []
I'm using the sensor driver since I have a contact sensor on the door. Do you have garage door device installed? I suspect there is nothing for the app to point at since.
Now that you have the driver/app installed, might be cleaner to remove the device/app (leave the drivers/app code), and re-run the app to mount the door device properly.
PLEASE NOTE
New installs of this driver are failing with login errors. It's not only on Hubitat, but on many other third party, unapproved by Chamberlain/Liftmaster apis attempting to use the MyQ system.
Many HE users are converting to local garage door methods. Some suggestions at this link
@bobbyD Kindly change the title of this thread to
[Broken] MyQ Lite Application
3 Likes
Done!
2 Likes
My MyQ Lite app is failing at Login. I've read the posts about local control of the MyQ Chamberlain door opener, but I must say I am scared off by them. I don't want to get into soldering terminals or hooking up a Security 2.0 device and cluttering up my garage. It's already cluttered by a Homelink Bridge I needed to make my Homelink in my Honda Pilot work with the Liftmaster. I read somewhere a long time ago about using IFTTT to interface with MyQ. Is that backdoor still open?
What did you expect in light of this announcement from Chamberlain:
3 Likes
I believe IFTTT still works.
From what I have been reading on Reddit and other sites, Chamberlain might have also broke that integration. Besides, who wants the multiple seconds or minutes of lag with IFTTT, they are so slow compared to local control or even direct to MyQ site via their app.
1 Like
Yeah, for all those reasons, I absolutely don't recommend it, but I was just answering the question... Too bad they seem to have broken that too.
2 Likes
There are a couple of entertaining threads about it on the Home Assistant forums. There are lots of angry users over there. Home Assistant is removing their MyQ Integration around Dec 1 because of Chamberlain's changes.
5 Likes
Yep, that is one of the other sites I stumbled across.
1 Like
