core: Linky Integration: cannot connect with my valid credentials
The problem
Cannot connect on linky integration with my valid credentials (but working on https://mon-compte-particulier.enedis.fr/). I have the issue: " Erreur inconnue: merci de réessayer plus tard (pas entre 23h et 2h)". I try to add it since since few weeks. It works fine on Enedis and EDF website. it does not work either with the intergation in configuration.yaml file or directly in the lovelace UI.
Environment
- Home Assistant Core release with the issue: 107.1
- Last working Home Assistant Core release (if known): NA
- Operating environment (Home Assistant/Supervised/Docker/venv): Docker On Asustor NAS
- Integration causing this issue: Linky
- Link to integration documentation on our website: https://www.home-assistant.io/integrations/linky/
Problem-relevant configuration.yaml
linky:
- username: 'xxx'
password: 'xxx'
Traceback/Error logs
Logger: homeassistant.components.linky.config_flow
No Data
Source: components/linky/config_flow.py:82
Integration: linky (documentation, issues)
First occurred: 11:20:41 (2 occurrences)
Last logged: 11:39:41
Additional information
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 79 (20 by maintainers)
Commits related to this issue
- Deactivating broken Linky integration Component has been disabled while Enedis integration is being worked on as detailed on this issue: https://github.com/home-assistant/core/issues/33634 — committed to Giom-V/Home-assistant by Giom-V 4 years ago
- Deactivating broken Linky integration Component has been disabled while Enedis integration is being worked on as detailed on this issue: https://github.com/home-assistant/core/issues/33634 — committed to Giom-V/Home-assistant by Giom-V 4 years ago
Quelle bande de pénibles …
It’s not available. Actually coding it right now.
Linky integration will be removed in 0.114.0, and Enedis integration will come next.
It’ longer than expected and first time for me dealing with OAuth2.
I’ll tell you when you can test the next integration.
Sorry for the delay.
Maybe we can use this project : https://github.com/bokub/linky ?
Hi @Quentame ,
It seems that both ENEDIS and GRDF share the same API ? ENEDIS https://data.enedis.fr/api/v1/console/datasets/1.0/search/ GRDF https://opendata.grdf.fr/api/v1/console/datasets/1.0/search/
If so, do you think your upcoming code will be OK for both Link and Gazpar ?
By the way, thanks a lot for your job on HA integration ;o)
hello, i’m not a HA user but i could give you some info which is similar with other integration or other box. Enedis have implemented the API to let everyone play with the sandbox environment, but only professionnal could access to the production environment. i will explain: end-user needs to give acknowledge (in french consentement) directly inside his own enedis accompt, this acknowledge is converted in a code send to a professionnal entity which have already signed a contract with Enedis. This contract is needed to allow the professionnal structure to recieve the client_id and client_secret for the real environment (the production one).
So no end-user could use the API authorization (Oauth2), only company is allowed to perform the complete job to recieve access_token and refresh_token.
i did that way for lifedomus box.
I have my own company, i have signed a contract with enedis, publish a web server to establish the dialog with end-user, gave enedis access to test the mecanism, then recieve the 2 client_id and client_secret. I have published a little Html page which forward the user into enedis step (consentement), store on a public server an application to recieve the code generated by enedis (on uri_redirect URL), this URL finalize and use this code to get the token (access_token and refresh_token), then forward the 2 token to the end-user application.
Then and only then end-user application could call enedis API with access_token to request for linky data.
Why closing this issue because, even if the maintainer is responsive, the pylinky will be updated when the bug will be fixed, so we can keep this issue open to avoid multiple issues reported for the same problem???
I like the concept but I’m not a fan of hosted services, also I can’t find the code for this app anywhere, i doubt this is open source.
The
Linkyintegration platform has been remove because the API has been discontinued.A new
Enedisintegration will be created but other integrations that I maintain needs my attention now:iCloud,Synology DSM.I’ll let you know when the time comes. During this time, you can join the HA French speaking Discord server, where we speak about the integration and workarounds : https://discord.gg/jGy9uMM
Sorry guys but not available on 0.112 it’s harder than expected.
Will be OK to Beta test 😃
@Quentame please reopen to track the pylinky upgrade
Why don’t use : https://enedisgateway.tech/ ?
If you need any beta testers for Enedis new integration, I’m in 😉
OK guys, thanks to our long video call with @jluc2808, it will be faster than expected ! 🎉
We are working together to bring you a fix on this.
And I think it will be an opportunity to add some new features (let’s see what happen next 😉) ! It can be on 0.112.0, we will need testers on this when at beta stage.
I have seen a plugin with Domoticz, perhaps this could help for development : https://github.com/guillaumezin/DomoticzLinky
yes i made a contract (beetween my society and enedis) get the ability to exchange token (special client_id / secret_id in production). With these items i’m able to complete the Oauth2 dialog which allow to start the data transfert itself. It’s what we discuss with @Quentame.
I might be able to help and give it a shot but I may need to get Enedis in the loop, and that is not the easy part 😃
@quentame , ok i havn’t seen you gave me a link to discord , i’m now registered a connected if you want to chat , my name jluc2808
Okay so the issue is comming from the underlying library.
So we should all follow this issue Pirionfr/pyLinky#28 The maintainer is responsive and I hope a solution to come soon.
Closing this issue.