Hey @scooter_seh… Nice work!!! I just installed the 1.14 binding and I was getting the “Could not connect to MyQ service” error. Turned up the logs and saw this error message
19:23:26.254 [TRACE] [nhab.binding.myq.internal.AccountData] - myq accountId: <Truncated>
19:23:26.259 [TRACE] [.openhab.binding.myq.internal.MyqData] - Requesting URL **https://api.myqdevice.com/api/v5.1/Accounts/%ACCOUNT_ID%/Devices**
19:23:26.611 [WARN ] [che.commons.httpclient.HttpMethodBase] - Cookie rejected: "$Version=0; TS01dfdd0d=015ca84662b9d0775c19839e2ae91f43dc9b82bbb60dbffd8b3142384de887496831d26dad562c5ee013e13cac0deda8e0df62c510; $Path=/; $Domain=.api.myqdevice.com". Illegal domain attribute ".api.myqdevice.com". Domain of origin: "api.myqdevice.com"
19:23:26.617 [TRACE] [.openhab.binding.myq.internal.MyqData] - Received MyQ JSON: {"code":"404.401","message":"Not Found","description":"Account not found."}
19:23:26.622 [TRACE] [.openhab.binding.myq.internal.MyqData] - myq ReturnCode: 404.401
19:23:26.629 [TRACE] [.openhab.binding.myq.internal.MyqData] - myq ReturnCode: 404.401
19:23:26.634 [ERROR] [enhab.binding.myq.internal.MyqBinding] - Could not connect to MyQ service
However, the call to https://api.myqdevice.com/api/v5/My/?expand=account had a response that was pointing to a v5 API instead of v5.1
"Devices": {
"href": "http://api.myqdevice.com/api/v5/Accounts/<AccountID>/Devices"
},
I tried a POSTMAN call to the v5 API from the response and I was getting a proper response without the errors.
So… Would you be able to update the binding to pick the API URL from response instead of hard coding it? Pretty please? 
edit: Corrected the binding version