New action service to update access token

This release brings a new action service to inject access tokens from the browser into Home Assistant. It is a little but significant addition leading to the next little thing I am working on: Semi-automated update of Novafos data in Home Assistant using an extension in the browser.
But already now the action service can be used like so:

curl -X POST -H "Authorization: Bearer <long lived HA token>" -H "Content-Type: application/json" -d "{\"access_token\": \"<1523 character token from Novafos>\"}" http://homeassistant.local:8123/api/services/novafos/update_token

You can make a shell script or whatever already now to use the action service.
For now I consider the feature unstable as it has only been tested like above, and not end-to-end with the Chrome extension coming up.

Full Changelog: v4.1.4...v4.2.0

v4.1.4

What's Changed

• Add list of municipality supplier id by @NicolaiSoeborg in #15
• Novafos updated the API endpoint.

New Contributors

• @NicolaiSoeborg made their first contribution in #15

Full Changelog: v4.1.3...v4.1.4

Fix warning on sensor state type.

Full Changelog: v4.1.2...v4.1.3

v4.1.2

Fixes Home Assistant 2023.3 warning.

Full Changelog: v4.1.1...v4.1.2

Update to latest Home Assistant standards

Update code to fully remove deprecated sensor type constants.
Updated Hacs Home Assistant requirement to minimum 2022.8

Full Changelog: v4.0.0...v4.1.1

Add support for district heating data.

This release adds support for district heating data in addition to water metering data.
Expect things to break because I do not have access to this data myself. Please report any issues on #12 .

The release also marks the selenium update as mature enough to graduate from a development branch to the main branch.

Full Changelog: v3.0.2...v4.1.0

Release for automated login

This is an experimental release.

To use the new attempt at automated login you mist read the README carefully at it relies on setting up a Docker container with some extra necessities. Otherwise do not update, and just keep on applying the access token once in a while like it has been required since the mid-September release. To use the new method you need to remove and setup the integration again.

If you do update, everything 'should' work as if nothing new happened.

Full Changelog: v3.0.2...v4.0.0-alpha

Set required token length to 1200.

It appears some tokens are also shorter than 1506. Now set at 1200 for a simple sanity check.

Fix for #11 - re-adding integration fails on authentication validation

Just a fix for #11 - the integration still attempted to login when adding the integration, something which fails now.
The validation is disabled. In fact you can put anything in the use/pass fields, as they are not used currently.

Please ask your local water supplier/KMD Easy-energy to allow access without reCAPTCHA blocking.

Longer tokens exist.

Fix #10 for longer tokens

Full Changelog: v3.0.0...v3.0.1