Umstellung der verwendeten PegelAlarm-API auf Version 1.1

[jstrassmayr]

Is your feature request related to a problem? Please describe.
The currently used PegelAlarm-API version 1.0 is deprecated and will be discontinued within 2025.

Describe the solution you'd like
The adapter should use version 1.1 of the PegelAlarm-API. Therefor a username and password are necessary which can be requested from office@pegelalarm.at. I won't post it here.

Describe alternatives you've considered

Additional context

[github-actions]

Thanks for reporting a new issue @jstrassmayr!

1. Please make sure your topic is not covered in the documentation
2. Please attach all necessary log files (in debug mode!), screenshots and other information to reproduce this issue
3. Search for the issue topic in other/closed issues to avoid duplicates!
4. Ensure that you use the latest available beta version of this adapter (not the current stable version): 1.3.8

---

Otherwise this issue will be closed.

[simatec]

Are there any other options besides username/password?
I would have to include the whole thing in the code and thus this would be public here on Github and anyone could use the data elsewhere

[jstrassmayr]

yes, the idea was to only provide a username/password but if it's public here that's not good.
I see 2 options:
Option A would be to extend the UI:

1. An input field "email" associated with a button "request api-key" and
2. Another input field "api-key" associated with a "save" button.

Process: The user enters his email address which triggers a REST-API endpoint whose logic send an api-key to the given email-address. The user then needs to copy the api-key from the email-address and paste it into the 2nd input field

Option B would include a registration on the pegelalarm.at page using email/password where the user can apply for an API-key for ioBroker.

I have not thought about both options in detail. Do you have any preferences or see dis-/advantages?

[simatec]

I would prefer option A

[jstrassmayr]

Ok, cool. We'll discuss this internally and I will come back to you with next steps.

[simatec]

Is there any update on this? Some users are reporting problems with the API...

[jstrassmayr]

The problems that occured last week happened due to the integration of Cloudflare into our infrastructure. We solved them and everything should work just fine now.

I'll come back to you regarding API-keys and possible changes before we discontinue the currently used service in the adapter.

[simatec]

thank you for your feedback and effort