I got the free one, but not sure when they would start charging for something that arguably should be free. But to clarify my last post, you cannot “OPEN” a Chamberland Garage or Gate opener. Google can tell you it’s open, it can tell you it’s closed, it can close it, but no opening.
By using the HA integration you create a pin and every time I ask Google with HA, it asks me for the pin, then it opens the covers, but with the Chamberland to Google direct integration you can only close, which totally sucks.
Unless you see somewhere else that this was resolved, I ran into the same issue as the people in the above mentioned thread.
Figured I would share that here, always good to put as much knowledge into these threads as possible
That was my frustration, charging 1 buck a month to only be able to close the door, and see if it is open or closed. I much prefer using HA to control the door I have a webhook through IFTTT and a super secret pass phrase to open or close the garage door. Works great!
I also have an automation that will open the garage door based on my presence detection between a set time frame. Say 5:00-7:30 at night (not my actual time frame) or the typical times we get home. Outside of that time frame I need to use my super secret phrase to open or close the door.
No, sorry. I saw a picture of a lady saying, “OK Google, close the garage door.” And assumed it would go both ways! Definitely a bit strange that it only closes…
Garage stopped functioning last night after midnight. So I am assuming that Chamberlain updated their api.
My Q Error from Log:
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 216, in async_setup
hass, self
File “/usr/src/homeassistant/homeassistant/components/myq/init.py”, line 36, in async_setup_entry
myq = await pymyq.login(conf[CONF_USERNAME], conf[CONF_PASSWORD], websession)
File “/usr/local/lib/python3.7/site-packages/pymyq/api.py”, line 167, in login
await api.authenticate(username, password)
File “/usr/local/lib/python3.7/site-packages/pymyq/api.py”, line 124, in authenticate
await self.update_device_info()
File “/usr/local/lib/python3.7/site-packages/pymyq/api.py”, line 140, in update_device_info
“get”, “Accounts/{0}/Devices”.format(self.account_id)
File “/usr/local/lib/python3.7/site-packages/pymyq/api.py”, line 83, in request
data = await resp.json(content_type=None)
File “/usr/local/lib/python3.7/site-packages/aiohttp/client_reqrep.py”, line 1040, in json
return loads(stripped.decode(encoding))
File “/usr/local/lib/python3.7/json/init.py”, line 348, in loads
return _default_decoder.decode(s)
File “/usr/local/lib/python3.7/json/decoder.py”, line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File “/usr/local/lib/python3.7/json/decoder.py”, line 355, in raw_decode
raise JSONDecodeError(“Expecting value”, s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
@djonk what region are you in? I’m just collecting regional info that might help us understand if there is a pattern. I am in US East and it’s the same (not working).
Still experiencing this issue unlike some of you above who have seen it resolved. Removed the integration and setting it up again allows me to login but doesn’t load any entities.
Logger: homeassistant.config_entries
Source: config_entries.py:951
First occurred: 1:23:52 PM (1 occurrences)
Last logged: 1:23:52 PM
Config entry '[[email protected]](mailto:[email protected])' for myq integration not ready yet: Error requesting data from https://accounts.myq-cloud.com/api/v6.0/accounts: 403 - Forbidden; Retrying in background
FYI the “fix” (the one with the few lines you paste into the Advanced SSH Add-On) did not work for me. I will try again tonight and update this comment if it starts working.
