Login error: Please check your username/password. #28
Comments
URL is https://espace-client-connexion.enedis.fr/auth/UI/Login but not longer available. |
Yes the captcha will be a problem |
Hi people 😊 ! It seems that some of the recent Linky issues from Home Assistant are coming from this. I have no issues with my account, maybe because it was created before the Enedis website refactor ... don't know. Here to help if needed ! Will update Home Assistant if needed. Thanks. |
I asked for an account in https://datahub-enedis.fr/data-connect/ . I will see if we can use it |
Me too 😜 |
So, have you tried using this new account ? Thks |
I did the same. @Pirionfr @Quentame, Regards,
|
yes |
I think PR are always welcomed 😊 |
Not checked yet sorry |
I fact getting metrics is easy. my problem is more about oauth2. |
A quick version has been made on https://github.com/plaurent-django/pyLinky.git on branch feature/enedis let me know if it can help. In my opinion, that's the best way to progress. |
Getting the data is not the problem here. it's the Authorization Code Grant Flow and the redirect_url that we must have. |
For autorisation I've understood HA has add a helper for managing oauth stuff. Not my expertise but perhaps something to investigate. |
I did my own try here : https://github.com/lasconic/pyLinky/tree/enedis_api One big question. The data available through this new API seems to be significantly different than the old one... What do we want to do in this library ?
|
Just added the customers v3 API. |
I think, making easy to access the raw API data and then change the current interface of the library and probably change the HA module features or do aggregation in the HA module it's a good Idea. And create a wrapper for retro compatibility, after that migrate de HA module. |
Well... Now I discovered that you need to have a company to be able to sign the contract with Enedis to get production credentials... So "easy access" to the API becomes relative. For example, most HA users who don't use the cloud service would not be able to use the module (except if they do have a company to sign the contract). |
It will be hard to scrap site because of captcha |
The "Netatmo" code owner talked to me about OAuth, and it's the same, he did ask to Netatmo to get production credentials with HA. I can ask him more details or maybe other HA members. OAuth is available for non Cloud users, see https://www.home-assistant.io/blog/2019/11/22/state-of-the-union/ I would prefer using the public API since it should be maintained, robust, documented, and stable (maybe also woking the night, if you know what I mean 😉) Also, I heard we can now have multiple Linky meter for one account ? So I agree with @Pirionfr we shoud break the current interface of the library to be more consistent with the new API. In the HA config flow we can make a list of linky meters to configure, and select the one we want. Sorry, I thought I would have more time, but I am working on 3 other HA integrations right now, so not having a lot of time. I don't think I'll help a lot here, but tell me if you want some advice about the HA integration, or updating the HA integration. |
Yes, they will need to be a company (personne morale) and sign the Enedis contract but then they can use the lib on the production env.
Indeed, you can have multiple "usage point".
The default is now 30 minutes apparently, but they collect the data in the morning for the whole previous day. The data is always available for full days... So you only get the data from the day before.. |
I updated my branch with a LinkyAPI class and LinkyClient is now a wrapper around this class and present a similar (if possible identical) interface to the current lib. It only considers the first 'usage point' for now, and it does the data aggregation for yearly, monthly, daily, hourly. https://gist.github.com/lasconic/e0cde0e0268e127df543fd8b67244933 |
Linked results looks identical as current version @lasconic, cool 😉 Maybe you should make a PR of it ? Could try to integrate to HA next week, or maybe you want to ? |
PR done : #29 I don't have a HA dev environment, so be my guest :) |
Good Job |
Version publish on pypi V0.5.0 |
Hi ! I started to implement it in HA but got issues with OAuth (a auth window is openning, then close immediatly). Also Enedis which repond to my application modification requests in about 5 days does not help. If anyone would like to take a look: Thanks. |
I will |
Moved my branch to https://github.com/hacf-fr/home-assistant-core/tree/linky/new-api |
Let's close this issue and follow here : home-assistant/core#33634 (comment) |
Hi guys, looks like you solved the linky integration issue, didn't you? (not sure I understood what you did). |
Hi there,
It seems i have a login error. (Tried within homeassistant and using python)
Any idea what i'm doing wrong ?
Regard,
pierre
The text was updated successfully, but these errors were encountered: