I’ve get my key in a week but i’ve applied for the key when @evanjd first told us the new method of the public api key
Only took me a few days after applying to get the information I needed. Mind you, I did this back in March when @evanjd first wrote about it.
When I return to HA to complete the configuration it says “Please follow the link and authenticate before pressing Submit.”
Vorformatierter TextSun May 12 2019 23:09:07 GMT+0200 (Mitteleuropäische Sommerzeit)
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/app/homeassistant/data_entry_flow.py", line 64, in async_init
return await self._async_handle_step(flow, flow.init_step, data)
File "/usr/src/app/homeassistant/data_entry_flow.py", line 98, in _async_handle_step
result = await getattr(flow, method)(user_input) # type: Dict
File "/usr/src/app/homeassistant/components/logi_circle/config_flow.py", line 141, in async_step_code
return await self._async_create_session(code)
File "/usr/src/app/homeassistant/components/logi_circle/config_flow.py", line 174, in _async_create_session
account_id = (await logi_session.account)['accountId']
File "/usr/local/lib/python3.7/site-packages/logi_circle/__init__.py", line 66, in account
return await self._fetch(ACCOUNT_ENDPOINT)
File "/usr/local/lib/python3.7/site-packages/logi_circle/__init__.py", line 205, in _fetch
resp.raise_for_status()
File "/usr/local/lib/python3.7/site-packages/aiohttp/client_reqrep.py", line 935, in raise_for_status
assert self.reason # always not None for started response
AssertionError
Whats the problem? 
That error is saying that the Logi API is returning a non-OK return code when hitting the account information endpoint. The fact that it’s getting to this point means you are successfully authenticating, but may not have the right scope to request account data (in this case, the account API requires the circle:accessories_ro or circle:accessories scope).
When you go through the auth flow, what permissions do you see here? You should see the following:
11 days later, still no keys. This is getting very annoying…
To those stuck without an API key (@ImmoNl, @Patrick_HA, etc), I’ve fixed up the old version of the logi_circle integration and published it here: https://github.com/evanjd/hass-logi-circle/tree/legacy. This should work fine from the custom_components folder on HA 0.92. Make sure you use only one component at a time, ie. don’t run logi_circle_legacy and logi_circle concurrently - I haven’t tested it but I doubt it’ll work.
This obviously won’t see the enhancements the official API based plugin will, but hopefully prevents anyone from being stuck an old version of HA while they wait for their API key.
Also - sorry! I probably wouldn’t have released the change if I knew so many people would have trouble getting their API key. 
1 Like
Thanks for that!
Did I miss something?
When I click the snapshot image in Lovelace I get a small movie of the last movement. That’s great! Never noticed that before.
When I click the snapshot image in Lovelace I get a small movie of the last movement. That’s great! Never noticed that before.
You didn’t miss anything - I added that to the hass-logi-circle version. 
Thanks,
obviously not your fault, but there is just no reply coming from logitech. Sucks I spent 500 bucks for bad service
Has anyone gotten a response from Logitech to their form fill in a while? I submitted mine over two weeks ago and I haven’t heard anything one way or the other yet. I am curious if anyone filled out the form who was also using duckdns? How did you handle Step 6 with proving you have a working URI/URL? I originally submitted it with: https://www.myservername.duckdns.org/api/logi_circle but obviously that only gives them a 404 page. Will that prove to them I own it or do I have to do something else?
I originally submitted it with: https://www.myservername.duckdns.org/api/logi_circle but obviously that only gives them a 404 page.
As long as the 404 is generated by HA, you should be fine (based on what the Logitech rep told me).
1 Like
I also use duckdns. I filled the url the same way as you did. Still no responds from Logitech.
Can everyone who hasn’t got their API key quickly DM me the date you requested access? I’ll bug the Logitech rep to see what the situation is.
I did submit mine and received a reply on April 25th but I never corrected the issue because I wasn’t sure what to give them.
You have submitted a request that contained an invalid or non-working Redirect URI. Please correct this issue and then resubmit the form again.
Thank you,
-Aron
–
Aron Rosenberg
Head of Engineering
Logitech Home Video Group
I’m not sure what the correct redirect url would be?
That’s what is confusing to me, my HA url is http:// not Https:// if my ip for my HA is 74.56.67.55:3213 would I send them https://74.56.67.55:3213/api/logi_circle
I’m sorry if this is a stupid question
You need to have a valid ssl-certificate. Not sure if plan ip-addressis accepted, the instructions only talk about URI.
I’m still waiting for reply to my API-request I made on february. I’ve made later again couple of times.
You need to have a valid ssl-certificate. Not sure if plan ip-addressis accepted
That’s right. I think you’d struggle to get a CA to issue a cert for a bare IP, so it’s unlikely Logi would accept that as a redirect URI.
I’ve had my integration with the new method for awhile now and the other day I started getting errors from the component. All related to 404 responses. I anyone else experiencing this? Currently on 0.93.1
Error 1
Status code 404 returned when updating recording_disabled to False
Error 2
Exception in _call when dispatching 'logi_circle_reconfigure': ({'entity_id': ['camera.living_room'], 'mode': 'RECORDING_MODE', 'value': False},)
Traceback (most recent call last):
File "/home/homeassistant/.homeassistant/custom_components/logi_circle/camera.py", line 63, in _call
await method(**filtered_params)
File "/home/homeassistant/.homeassistant/custom_components/logi_circle/camera.py", line 153, in set_config
await self._camera.set_config('recording_disabled', not value)
File "/srv/homeassistant/lib/python3.6/site-packages/logi_circle/camera.py", line 97, in set_config
request_body=payload)
File "/srv/homeassistant/lib/python3.6/site-packages/logi_circle/__init__.py", line 205, in _fetch
resp.raise_for_status()
File "/srv/homeassistant/lib/python3.6/site-packages/aiohttp/client_reqrep.py", line 942, in raise_for_status
headers=self.headers)
aiohttp.client_exceptions.ClientResponseError: 404, message='Not Found'
Error 3
Exception in _call when dispatching 'logi_circle_record': ({'entity_id': ['camera.living_room'], 'duration': 20, 'filename': Template("/home/homeassistant/.homeassistant/www/security/camera/record_camera.living_room.mp4")},)
Traceback (most recent call last):
File "/home/homeassistant/.homeassistant/custom_components/logi_circle/camera.py", line 63, in _call
await method(**filtered_params)
File "/home/homeassistant/.homeassistant/custom_components/logi_circle/camera.py", line 171, in download_livestream
ffmpeg_bin=self._ffmpeg.binary)
File "/srv/homeassistant/lib/python3.6/site-packages/logi_circle/live_stream.py", line 72, in download_rtsp
rtsp_uri = await self.get_rtsp_url()
File "/srv/homeassistant/lib/python3.6/site-packages/logi_circle/live_stream.py", line 52, in get_rtsp_url
stream_resp_payload = await self.logi._fetch(url=url)
File "/srv/homeassistant/lib/python3.6/site-packages/logi_circle/__init__.py", line 205, in _fetch
resp.raise_for_status()
File "/srv/homeassistant/lib/python3.6/site-packages/aiohttp/client_reqrep.py", line 942, in raise_for_status
headers=self.headers)
aiohttp.client_exceptions.ClientResponseError: 404, message='Not Found'Is the device you’re trying to interact with definitely online? Logi’s API will 404 if the device is switched off or unreachable.
1 Like