Bjorn-CPT

Hi everyone, Just a quick update: I've managed to update the Node-RED flow to handle the new encrypted password requirement for the Sunsynk API (using RSA encryption with a dynamic public key, based on the PHP example shared earlier). It's working perfectly now, pulling stats without issues. @Gary Waterworth (GitHub: gdwaterworth ==> https://github.com/gdwaterworth/Home-Assistant---E-Linter-Logger---Sunsynk), thanks for the original repo! Since it's marked as no longer maintained, would you prefer I submit a pull request with these changes, or should I fork it and maintain a separate version? Happy to share the updated flow JSON either way. Details on changes below. Let me know if anyone wants the full export (sanitised for sensitive info). Cheers, Bjorn Short Summary of ChangesUpdated token endpoint to /oauth/token/new. Added nodes to generate nonce/sign, fetch dynamic public key, and encrypt password using Node.js crypto module (RSA_PKCS1_PADDING). Revised headers to prefer "deflate" encoding and match latest working User-Agent/Accept values to avoid compression errors. Modified login request to use the base64-encoded encrypted password instead of plain text. Ensured compatibility with existing flow structure; tested on Python-free Node-RED (uses built-in crypto). No other major alterations—stats pulling resumes as before.

BjornCPT: I am new to the forum, so waiting for my login to be approved. I managed to build the relevnat nodes and got the flow up and running again. I can share the extra nodes and code here, but can update the original in summary: 1. Updated Global Vars with new url 2. Added a function to generate Nonce and Sign 3. HTTP node to pull Public Key from Sunsynk 4. Function to encrypt the password 5. Then link to the existing "Create Request for Login" node with some code changes.