Skip to content
This repository has been archived by the owner on Jan 7, 2023. It is now read-only.

[REQ] Support Piazzetta in 2022 (all or new models) #10

Open
robkrause opened this issue Dec 18, 2022 · 1 comment
Open

[REQ] Support Piazzetta in 2022 (all or new models) #10

robkrause opened this issue Dec 18, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@robkrause
Copy link

Description

I bought a Piazzetta P930 M-C just recently and tried our your impressive Homebridge Implementation. Unfortunately I get this error: _setAPILogin HTTP login request failed. Retrying... Reason: _setAPILogin did not get the expected JWT token back from API: {"Error":"INVALID_APP_ERROR","Success":false,"Source":"BRIDGE"}

Investigating using https://proxyman.io/ios I noticed that the auth flow seems to be slightly altered compared to your code. I'm unsure if this is only the case fore newer stoves. Can't create a branch/PR, therefor find my suggested code changes below.

Interest

Possible implementation

index.js Line 53:
["piazzetta", ["458632", "https://piazzetta.agua-iot.com/", "https://piazzetta-iot.app2cloud.it/api/bridge/endpoint/"]],

index.js Line 93:
const HTTP_REQ_PIAZZETTA_APP_VERSION_VALUE = "1.9.0";
Readme Line 53
"name": "<stove name, MUST be the same than one you configured in official stove mobile app, and you now want to control from HomeBridge, use '-' for Piazzetta>",
@robkrause robkrause added the enhancement New feature or request label Dec 18, 2022
@robkrause robkrause changed the title [REQ] Enter a brief description of requested enhancement/feature [REQ] Support Piazzetta in 2022 (all or new models) Dec 18, 2022
@securechicken
Copy link
Owner

Thanks a lot for having checked and explored this properly @robkrause, very useful.
Unfortunately I'm not using Homebridge anymore, and as a consequence does not maintain the plugin - which can still be forked and updated elsewhere if need be.
But I recall that last year I was exploring similar issues, Piazzetta asked some changes to the API maintainer (Micronova) to enforce going through their own endpoint, so likely they indeed changed the way the authentication is done (and possibly even API calls).
I leave this issue open so that the community can benefit from your solution!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants