Although the attempt by some people to provide logs is appreciated, The provided logs have been entirely unhelpful…
All the logs provided so far have been of the plugin running… The plugin startup and initialization is missing, and that is where EVERYTHING happens.
During the last set of changes to the MyQ API, I added Web Fallback to the plugin. This plugin is the ONLY plugin that does Web Fallback… Whatever Chamberlain is doing (My devices are still able to log in using the API), Web Fallbacvk should allow the plugin to work.
Chamberlain HAS changed the Web interface (first time in almost three years) so that the Web Fallback no longer works…
So… I am attaching an update, v1.51… This update will NOT get the plugin working, but it should get me the information I need…
I need the logs showing everything from “************** STARTING ****", through to " STARTUP COMPLETE **********”.
Here is another log. Hope it includes useful information. Remember I am new to Vera. Getting Liftmaster devices integrated into Vera is a unexpected bonus.
Awesome start. Logs in, detects doors, and creates devices. It created a device for each door and each place in my account, and none of them actually control a door. Log attached
According to the logs, the startup was successful… There is login, thereis verification of login, there is retrieval of devices.
So… the fact that they don’t work is a DIFFERENT problem…
The logs show that you have 4 devices, two gateway devices and two opener devices… What physical hardware do you have??? It is mis-detecting the gateway(s) as openers… I will need to tweak the detection algorithm.
Please post logs showing the plugin processing a request to open or close one of the real doors.
According to the logs, the startup was successful… There is login, thereis verification of login, there is retrieval of devices.
So… the fact that they don’t work is a DIFFERENT problem…
The logs show that you have 4 devices, two gateway devices and two opener devices… What physical hardware do you have??? It is mis-detecting the gateway(s) as openers… I will need to tweak the detection algorithm.
Please post logs showing the plugin processing a request to open or close one of the real doors.[/quote]
I have 2 WD750 openers. They are chamberlain openers with MyQ and WiFi built in.
I can redo the opener setup because I understand there is now a process to have them included and use only one “place” (I assume this is what is translating to 2 separate gateways). Prior to things not working on Nov 2nd, I never saw any gateway devices. The plugin detected 2 doors that were the actual doors, regardless of the gateways used. The new version is actually detecting 4 doors (none if which it can connect too).
I’ll get you some additional logs once i get home. I thought I caught an open attempt in the log, but copy/paste from putty via remote access isn’t easy.
That took care of device discovery. Now im down to just the 2 appropriate GDOs showing as devices. Now it just says cant connect to devices.
They default to locked mode… so with a single click on the undetected device, i can get it to open the door.
When the door is open, it shows as cant detect and locked. If i click it once, it updates to show the door as unlocked. If i click lock quickly enough while it shows as unlocked, it will close the door.
Thanks so much for the help. Its very close. Attached is a new set of logs. Opened the door from closed state/cant detect. Then “closed” twice to get it to close.
Note, when operating a garage door, it takes at least a minute to complete an open or close operation… wait for the plugin to pull the updated status (every 5 seconds when enhanced status is enabled)… clicking every 10 to 20 seconds just gets everything confused…
[quote=“cybrmage, post:854, topic:180826”]yet another try… v1.56…
Note, when operating a garage door, it takes at least a minute to complete an open or close operation… wait for the plugin to pull the updated status (every 5 seconds when enhanced status is enabled)… clicking every 10 to 20 seconds just gets everything confused…[/quote]
Bingo!!! everything appears to be working normally again. I’'ll do some more testing during the day tomorrow when the beeping before the door closing doesn’t drive my wife nuts, but at first run, this seems solid. Status updating as expected, Open/Close working as designed, showing up as garage doors and light switches. I think you have once again worked your magic!!
v1.60 (Version ID: 34952) November 10, 2017
– fixed - web api changes
– fixed - MyQ api changes
– changed - code refactoring
– fixed - plugin non-operational when MyQ account is linked to a Nest accout
Is there a way to create a motion sensor associated with this plugin to tell the open/close state of the garage door? It can be useful to trigger the house mode.