just got response from logitech guys on my form: "I received your API credentials request, but we don’t allow use of *.local domains for redirect URI’s as they can be hijacked easily and don’t have proper CA support. If you can setup a proper DNS name, feel free to resubmit the request form.
". - so no .local domain name, guys, Needs to define true globally accessible DNS name… I have one, but struggling to open my HA to dark space ))))
The form requires a valid, globally accessible DNS name, but hass doesn’t have to be listening on it. The auth redirect is done entirely in your browser. Off the cuff, a couple options are:
a) Submit a URL on a domain you control. Let the auth redirect 404, and change the URL to point to your local hass instance and resubmit.
b) Submit a URL on a subdomain you control. Set up a static route on your local network to point that subdomain to your local home assistant instance.
I will update the docs to warn about that though. Sorry. 
I am so looking forward to this change. Do you have any idea in which build it will be released?
No idea. I’m at the mercy of HA maintainers for when my PR will be reviewed.
I did get one review comment around 5-6 weeks ago saying the PR was too big, so the PR I have open right now implements only a very small part of the updates. If/when that’s merged, another PR will follow to add the rest of the functionality back.
2 Likes
Do the new stream component released in the 0.90 will work with the logi circle , using the api key?
Nope. From the release notes:
Each camera integration will need to be individually updated, for the first version we have only added support for the generic camera integration.
It doesn’t look like a big lift to add support but I won’t tackle that until my currently completed work is merged.
On that - the first PR is close to being merged (it’s been reviewed), I just need to add tests for the config flow. Been busy but hope to finish that in the next few days.
2 Likes
I downloaded your branch the other day and replaced the stock Circle component with yours, plugging in the credentials I got from Logitech. Worked perfectly, though I restored the current one afterwards as I want to stay stock for now. Really looking forward to the work you’ve been doing getting integrated. Thanks.
1 Like
This morning I updated to 0.92 which is using the new OAuth2.
But I can’t get it integrated with HA. After I logged in the account, went back to HA to press Submit, I got “Please follow the link and authenticate before pressing Submit.”
Funnily enough, I just opened an issue on this.
The annoying thing is, I’m sure I had the pickle error when I was testing but I can’t remember exactly what I did to fix it. I thought I just deleted the pickle file but that didn’t work for me this time. I’m probably missing something really silly and going to look like a dummy.
1 Like
Thank you for opening this issue. Big thanks!
I’ve responded on Github. Sorry for the trouble folks!
1 Like
By the way, a quick update:
The changes released in 0.92.0 only include the migration to the public API, there are no new features. I’m currently breaking all the other work I did into smaller chunks to raise PRs for gradually. I expect to raise individual PRs for:
- Live stream support (branch already done, will raise PR tonight)
- Device info, ie. grouping entities by device, showing model names, firmware etc (expect to raise that tonight as well)
- Migration from cloud pull to push (soon)
- Adding binary sensor for motion (a while away, as I can’t raise this until the migration to cloud push is merged).
Good news is that because of some backend changes, overridding the component with all the features now should work fine. I’ll update the hass-logi-circle repo with all these features in the next few days for those who want to play with this stuff now.
1 Like
Amazing stuff. I’ll try to find some time to test your latest branch.
Anyone received there api key already? It’s been a week and still no message from Logitech.
Same here, not a sound. Can’t really update to 0.92 until i get the keys, don’t want to lose my camera integration. Frustratingly slow handling of the requests.
Took a couple of weeks for me. I was just fortunate to have found out about the requirement well before the new component was released. To be honest I’d completely forgotten I requested it by the time it arrived.
From Logitech:
We got a large number of credentials requests and it will take another week to go through the backlog.
So hopefully not long now guys.
Also, I have clarified Logitech’s rules about what redirect URIs are valid. You can see them here:
To clarify, you are not required to expose HA externally, though that is the easier route. You are allowed to use something like netlify (a free static host) and just a page up at /api/logi_circle that says “This is a static page that I will manually proxy to my HA instance when authenticating with Logi Circle” (or something to that effect). Just make sure you have control over the fully qualified domain name, eg. my-logi-redirect.somefreehost.com is fine, somefreehost.com/my-logi-redirect is not.
I will raise a PR shortly to fix up the docs (I mention .local as a valid domain, I now know that’s not accepted by Logi, my bad).
Did anyone get their api keys?
I requested them 3 time already, but still nothing.
No, nothing. Startend to think is all just a hoax… /jk