Home Connect: alpha testers wanted

tdolder · August 28, 2019, 6:40am

Same problem, I have a .homeconnect-token-cache file in my config dir.
After a restart the plugin works again.

olloe · August 28, 2019, 1:14pm

I’ve had some problems lately, but I haven’t inspected much…
It seems it suddenly loses connection because right now HA thinks the dishwasher is still running at 38% done and 2 hours left. It’s been like that for a few days. Ran it again today but nothing updated.

marcomartins · September 15, 2019, 10:16pm

Hello,

does this component work offline? I have a setting on my home connect app to only work locally and not use the cloud, so they support working without internet connection.

Thanks

marcomartins · September 17, 2019, 7:49am

Here you can see the option for offline working.

Since I’m segregating the networks with the goal of removing internet access to my IOT lan, local connection is not working.

sjee · September 17, 2019, 8:05am

This integration is based in the API through the home connect server so offline is not going to work.

marcomartins · September 17, 2019, 8:41am

too bad we should avoid relying on cloud services.

I’ll inspect my network packages to see what can I find.

anon67474050 · September 23, 2019, 6:30pm

That’s the whole idea of Home Assistant, don’t rely on other parties right? “Your system should run at home, not in the cloud.” and “Reclaim your privacy”.

But keep up the good work with Home Connect, but connect locally

Kugelfang · November 21, 2019, 6:19pm

I just set everything up but I get the following error when trying to register the integration:

{
  "error": "unauthorized_client",
  "error_description": "request rejected by client authorization authority (developer portal)",
  "state": "XXXXXXXXXXXXX"
}

any idea on what I’m doing wrong?

DavidMStraub · November 21, 2019, 8:52pm

Are you using the most up-to-date version? I have changed many things in the past few days, also the redirect URI must be changed. The new version only works under HA 0.102.

Kugelfang · November 21, 2019, 10:44pm

Yes, I just installed everything fresh today:

Home Assistant 0.102
Home connect component via HACS: 0.2.1

DuckDNS HASSIO plugin:

{
  "lets_encrypt": {
    "accept_terms": true,
    "certfile": "fullchain.pem",
    "keyfile": "privkey.pem"
  },
  "token": "XXXXXXXXXXXX",
  "domains": ["AAABBBCCC.duckdns.org"
  ],
  "seconds": 300
}

to test that this is working I even forwarded the port 8123 in my router to 8123 of my HA which made my HA accessible from the internet via the DuckDNS adress:

The configuration.yaml looks like this:

http:
  base_url: https://AAABBBCCC.duckdns.org:8123
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem

homeconnect:
  client_id: !secret homeconnect_username
  client_secret: !secret homeconnect_password

And in the developer account is set up like this:

Access: Private
OAuth Flow: Authorization Code Grant Flow
Redirect URIs: https://AAABBBCCC.duckdns.org:8123/auth/external/callback
One Time Token Mode: Disabled
Proof Key for Code Exchange: Disabled

DavidMStraub · November 22, 2019, 8:19am

That all looks correct, strange …

Can you please try the following script using directly the Python module to make sure it is unrelated to Home Assistant:

from homeconnect import HomeConnect
import webbrowser

client_id = "..."
client_secret = "..."
redirect_uri = "https://..."

hc = HomeConnect(client_id, client_secret, redirect_uri)
webbrowser.open(hc.get_authurl())

auth_result = input("Paste authentication URL")

hc.get_token(auth_result)
appl = hc.get_appliances()
print(appl)

sharkdp · November 22, 2019, 8:56am

@Kugelfang note that client_id and client_secret are not your HomeConnect username and password (as indicated by your !secret homeconnect_username, !secret homeconnect_password settings)

Kugelfang · November 22, 2019, 5:52pm

ok but what are they? I was providing my actual user login credentials (so not the dev ones)

sharkdp · November 22, 2019, 6:00pm

Go to https://developer.home-connect.com/applications and click on “Details” for your application. It should show “Client ID” and “Client Secret (required)”.

Kugelfang · November 22, 2019, 6:39pm

well that did the trick!!! thanks a lot

cafoto777 · November 25, 2019, 10:49pm

Hi, I think I fix it. I can now start the oven, but not start any program. Someone has a better Oven look I can use… This is my first post here…

DavidMStraub · November 26, 2019, 7:53am

Unfortunately, starting oven programs is not allowed by the API at present. It requires a separate approval of a client application, which they will not grant for private developer applications I guess.

Once the component becomes an official part of Home Assistant, thanks to the new OAuth2 account linking feature described in the 0.102 release notes, this might however become possible at some point.

olloe · November 27, 2019, 7:28pm

This stopped working some time ago and I haven’t looked at it until now. Reinstalled via HACS and cannot make it work. edited the redirect url and even made a new app - no luck. I get nothing in the logs.

This worked at least a few months back. And from what I can see here I only should need to edit the redirect url?

DavidMStraub · November 27, 2019, 9:28pm

“Nothing in the logs” cannot really be unless you somehow didn’t enable the componnent. There would be at least an error. After installing via HACS, did you

Add the necessary entries to configuration.yaml?
Add the integration on the “Integrations” panel in Home Assistant?

olloe · November 27, 2019, 9:58pm

Thanks! I hadnt done anything in the integrations panel… Shame on me seems to work now