Fronius Wattpilot Flex Home - invalid password

Has anyone managed to get the fronius wattpilot binding up and running with new gen “Fronius Wattpilot Flex Home” (FW: 42.10)?

Issue i have, I get wrong password :frowning:

What i did so far:

  • get binding
  • binding detects wattpilot
  • copy and paste autodetected Thing String (with minor modification) into my thing file
  • added password (same as used by App, which perfectly works)

Not sure issue is really related to new gen Wattpilot .. appreciate any hint.

Best regards, Dieter

P.S.: Sorry, worth to mention, above scenario is based on OH 5.1.1

Hi Dieter,

Fronius has changed the password hashing algorithm to BCrypt for newer models, which isn’t supported with openHAB 5.1.1.
I have implemented BCrypt password hashing in my underlying wattpilot4j library last week (Add support for BCrypt password hashing used by newer models by florian-h05 · Pull Request #41 · florian-h05/wattpilot4j · GitHub), and upgraded the version used by the add-on. The 5.2.0 snapshots include that change, but I will talk to the add-on maintainers about backporting this so it will be available in a 5.1.x patch release.

1 Like

Hi Florian,

thanks a lot for your fast feedback!

Sounds promissing, especially if it’s really just the hashing algorithm :wink:

Kind regards, Dieter

1 Like

Hi Florian,

as per release cycle i understood, next Openhab release could be expected mid of this year :frowning:

Have you managed to get any insides about a possible patch release?

Thanks a lot,

Dieter

My PR has been backported and the openHAB 5.1.2 patch release build is currently running, so you only have to wait for our CI server to complete the build :grinning_face:
Given that a full release build usually takes about 6 hours we can expect the build to finish in approx. 4 hours.

Wow, these are pretty good news!

Thanks a lot,

Dieter

1 Like

Thumbs up!

I can confirm, with 5.1.2 patch release i’m now able to log in and get the Wattpilot details!

Not related to this thread, but do you know any upgrade process to follow with this patch release?

Issue i have with this release, on Android (after App restart) i get a black design. I had to change from white to black and vice versa to fix it.

And more important, oh-link with action photos fires: “Uncaught (in promise) TypeError: cS().getDarkMode is not a function”, instead of the expected and with 5.1.1 working behaviour.

Also hairlines vanished between items in oh-list-card. Need to check whether this might be related to custom widgets.

Ah sh**, when backporting a fix something went wrong and some places weren’t changed … I will fix that.

Good catch, will fix that as well.

1 Like