[linky] Fixes for change in Enedis API on 2024 December 20

[lo92fr]

Fixes for Linky Enedis December web site change

This pull request is about fixing the linky addon after the change that was made on Enedis side to the Web Site.
This is linked to issue:
#17936

Description

Mainly, changes are :
- URL for data is now mes-mesures-prm and not mes-mesures.
- Dto format have changed : mainly merge data & date, field renaming, and moving.
- Some changes on date format.

[lolodomo]

Thank you @lo92fr , I will review and test.

[lolodomo]

I still have Java 17 and Java 21 on my dev PC so it should be easy to build a JAR for Java 17.
But in case I would have only Java 21, do you know what is the maven command to execute to build a JAR compatible with Java 17 / OH 4.3 ?
@holgerfriedrich I am sure you know ;)

[holgerfriedrich]

@lolodomo Hopefully it is just:

mvn install -Pj17 -Dohc.version=4.3.0

https://community.openhab.org/t/openhab-5-x-snapshot-requires-java-21/160890/5

[lolodomo]

@lo92fr : does not work for me => Error requesting 'https://alex.microapplications.enedis.fr/mes-mesures-prm/api/private/v1/personnes/xxxxx/prms/yyyyy/donnees-energetiques?mesuresTypeCode=ENERGIE&mesuresCorrigees=false&typeDonnees=CONS&dateDebut=2023-01-01': {"message":"Internal server error. Please try again","code":"INTERNAL_SERVER_ERROR"}

Will see if it work in next tries (next hours).

[lo92fr]

if it work in next tries (next

It still work on my side, strange.
Does the xxx in URL correctly formatted with something like MPSxxxYYY ?

Laurent.

[lolodomo]

Does the xxx in URL correctly formatted with something like MPSxxxYYY ?

3 letters then 3 numbers and then 3 letters.
Starts by N in my case.
If I correctly remember, it is the reference of my counter?

[lo92fr]

If it's still does not work, can you please:

• check that you have the new version of the website. Look like this:
  

• When you load the page, take a look on the browser debugger, new URL appears at the bottom of the list.
  Is it the same and does it works correctly in your browser session ?

Thks,
Laurent.

[lolodomo]

Yes, I have the same page on their website.
The requests are similar, the binding request just has an additional parameter "dateDebut".
When I run in my browser session while I am logged to the website, the binding URL works well!

[lolodomo]

Now the binding is working! Even after I disconnect from the website in my browser.
Maybe you need to connect at least one time to the new website version ?

[lolodomo]

This was changed very recently, just before releasing 4.3. We don't need to pass a ZonedDateTipe; DateTimeType just needs an Instant as parameter. So you do not need TimeZoneProvider .

[lo92fr]

Hello @lolodomo,

I'm not sure to understant. Do you say to use the DateTimeType constructor that take an instant, something like this.
updateState(PEAK_TIMESTAMP,
new DateTimeType(days.datas.get(days.datas.size() - 1).dateDebut.toInstant(zoneOffset)));

The matter is that I still need to find a zoneOffset in this case.
The Enedis API return a LocalDateTime at offset of the current zone.
The DateTimeType if I undestand correctly want a universal time.

So somewhere we need to convert from local to universal using a timezone ?

Laurent.

[lolodomo]

@jlaur is our specialist with date. Please advice.

[jlaur]

If days.datas.get(days.datas.size() - 1).dateDebut is a LocalDateTime, the implementation is already correct. If it is an Instant there is no need to convert to ZonedDateTime.

[lolodomo]

The fix fails for me.
It worked just one time apparently because.i previously opened a session on the website but the next days it failed.