Is this still working?

[BerndKohl]

First of all thanks for contributing this component!

I just received my BWT Aqa Perla today and was eager to check if this integration would work.

I tried the first curl command curl -d "_method=POST&STLoginPWField=your_password&function=save" https://192.168.1.x/users/login -c cookie.txt --insecure --verbose But all I got was: `* Trying 192.168.1.x:443...

• Connected to 192.168.1.x (192.168.1.x) port 443 (#0)
• ALPN, offering h2
• ALPN, offering http/1.1
• TLSv1.0 (OUT), TLS header, Certificate Status (22):
• TLSv1.3 (OUT), TLS handshake, Client hello (1):
• TLSv1.2 (IN), TLS header, Certificate Status (22):
• TLSv1.3 (IN), TLS handshake, Server hello (2):
• TLSv1.2 (IN), TLS header, Finished (20):
• TLSv1.2 (IN), TLS header, Supplemental data (23):
• TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
• TLSv1.2 (IN), TLS header, Supplemental data (23):
• TLSv1.3 (IN), TLS handshake, Certificate (11):
• TLSv1.2 (IN), TLS header, Supplemental data (23):
• TLSv1.3 (IN), TLS handshake, CERT verify (15):
• TLSv1.2 (IN), TLS header, Supplemental data (23):
• TLSv1.3 (IN), TLS handshake, Finished (20):
• TLSv1.2 (OUT), TLS header, Finished (20):
• TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
• TLSv1.2 (OUT), TLS header, Supplemental data (23):
• TLSv1.3 (OUT), TLS handshake, Finished (20):
• SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
• ALPN, server accepted to use http/1.1
• Server certificate:
• subject: C=DE; ST=Some-State; O=BWT
• start date: Jan 1 00:24:34 1970 GMT
• expire date: Dec 27 00:24:34 1989 GMT
• issuer: C=DE; ST=Some-State; O=BWT
• SSL certificate verify result: self-signed certificate (18), continuing anyway.
• TLSv1.2 (OUT), TLS header, Supplemental data (23):

  POST /users/login HTTP/1.1 Host: 192.168.1.x User-Agent: curl/7.81.0 Accept: / Content-Length: 55 Content-Type: application/x-www-form-urlencoded

• TLSv1.2 (IN), TLS header, Supplemental data (23):
• TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
• TLSv1.2 (IN), TLS header, Supplemental data (23):
• TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
• old SSL session ID is stale, removing
• TLSv1.2 (IN), TLS header, Supplemental data (23):
• Mark bundle as not supporting multiuse < HTTP/1.1 301 Moved Permanently < Location: http://192.168.1.x:6080/vnc.html?resize=scale&autoconnect=true&show_dot=true < Content-Length: 0 < Connection: close < Date: Wed, 10 Apr 2024 15:53:28 GMT < Server: lighttpd/1.4.53 <
• Closing connection 0`

So apperently this does not work with the latest version of the board?

[MatthiasPiepke]

I'm not an expert on curl. But I don't see an error here. Did you try the second command "curl -v -b cookie.txt https://192.168.1.x/home/actualizedata --insecure" ? Did you find the cookie.txt file in the folder, where you called the curl command from? I think then it was successful. However, using curl commands is not essential for the BWT custom integration for HA. There is probably an easier way to find the right response items: Login in to your BWT webpage via webbrowser as usual. Once you are logged in, you can navigate manually to "https://192.168.1.x/home/actualizedata". Then you should receive a simple text like this: {"aktuellerDurchfluss":"0","aktuellerDurchflussProzent":"0","durchflussHeute":"15","durchflussMonat":"1019","durchflussJahr":"63","RegeneriemittelNachfuellenIn":"198","RegeneriemittelVerbleibend":"90"}

I hope that helps a bit.

[quintz]

Hi Matthias

when I enter the mentioned url I won't get a json response like yours... Did you enable something wihtin your Perla?

[BerndKohl]

Hi all, I think BWT changed their "interface" on newer boards or versions. They are no longer offering the HTML webpage but they are now redirecting each HTTP request to a VNC page where you have to enter the login code received after product registration.

Any ideas?

[MatthiasPiepke]

Mmhh. That would be very pitty. Maybe, we should contact BWT Support and ask for another API, which makes the Integration into HA possible. But thanks for your feedback, from now on I will avoid each FW update.

[BerndKohl]

Local API access will be available in an upcoming new firmware (currently scheduled for 2025) but a current beat version can be installed using a formal e-mail request to bwt.de.

This then includes a local API.

[cth18012017]

Hello or Hallo Bernd, have you more informations about this? Have you a solution? they install the bwt perla simplex one today. My App runs. My IP-Adresse with the vnc password access run, but the integration failes, see: https://github.com/MatthiasPiepke/BWT-Perla-Home-HA-custom-component/issues/3