Linky : use the API, not the HTTP webpage


Just a comment and a call for volunteers… the Linky binding suffers of unstability because it parses the HTTP website endpoint, not the API, so it depends on parsing the presentation layer that changes frequently, and on some cookies for authentication that are not done for API calls. A non-sense for maintainability :slight_smile: .

If a motivated developer wants to use the real API (endpoints that send raw data and where we authenticate in OAuth), it is here and some examples are here