Direct reception from PWS (via AWEKAS URL)

[Timo-Beil]

Checklist

• I have filled out the template to the best of my ability.
• This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
• This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.

Time-consuming (superfluous?) setup of a DNS

Describe the solution you'd like

Most of Bresser's PWS have a freely addressable output which can be used, for example, for sending to AWEKAS. For such cases, the cumbersome spoofing would be unnecessary and you could address the data directly to the HA.
A third checkbox for direct access in the config would be nice.
I am too stupid to change your code so that it works without the domain redirection.

Describe alternatives you've considered

I wrote the IP of my HA into the PWS and have entered my normal local DNS IP (in router, not configurable) in your config, but no data

Additional context

[Timo-Beil]

Errata: "Stationstaste" contains the Awekas password, not the station ID

[lhw]

Can you verify that this is the format that is used by your station? https://www.awekas.at/board/index.php?file-download/3262/
i.e. can you check if your station is calling current.php on your HomeAssistant installation. The issue is that right I have to check how to add unauthenticated calls. Right now I require the connections to be authenticated, something your station has no capability to do.

[Timo-Beil]

Sorry, the API is the one used to integrate the AWEKAS cloud data into a website, not to read the station data directly.
I think my station is making authenticated calls with Station ID (= my ID) and Stationstaste (= my PW).
I tried to intercept the traffic between station and HA, but it is TLS 1.3 encrypted. When I have found some logs (HA server or KALI?), I will be back here.