Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doesn't work with v6.6.x #63

Open
tronikos opened this issue Sep 14, 2024 · 4 comments
Open

Doesn't work with v6.6.x #63

tronikos opened this issue Sep 14, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@tronikos
Copy link
Collaborator

Filing this mostly for visibility.
See https://community.home-assistant.io/t/wallbox-pulsar-plus-integration/200339/1195 and #62
Someone will have to change the code to subscribe to redis channels instead of reading from redis keys. The implementation will also need to work for both <6.6 and >=6.6

@gllmlbrt
Copy link

Hi,
Noting that 6.6 version on copper SB (and others) makes the Root/SSH process unusable, I had to downgrade to factory default. And it all worked again. However, I am now stuck with a 5.2.5 vesion which is from early 2021. Needless to say that there has been several improvements first.

So is there a way to upgrade to a version 6.5.2. The first step would be a get our hands on the firmware update URL or package.
Then a method through SSH ?
Or I noted there is the feature via OCCP tools, but again it requires a specific URL to the upgrade pacakge.

I realise this is not directly related to this repo. I have searched elsewhere without success.

@jagheterfredrik jagheterfredrik added the bug Something isn't working label Dec 2, 2024
@toxuin
Copy link

toxuin commented Jan 9, 2025

Looks like you can indeed update to a specific version! In essence, wallbox's firmware update is just a dpkg install procedure.

Here's the script that does the updating: https://pulsar-repo.wall-box.com/pool/main/s/sys-update/sys-update-1.5.0-all.deb

I think it's kind of tricky though as that repo doesn't seem to contain any 6.x firmware at all - maybe it's just for restoring functionality?

When you click "update" in the app - it's the app on your phone that is downloading the .deb and sending it to the charger, then charger executing an "offline" install.
Where does the app get its .deb's - I don't know, however.

@jagheterfredrik
Copy link
Owner

The app gets an encrypted and signed tar.gz over a HTTP API. Inside is essentially a deb repo and some metadata.

@toxuin
Copy link

toxuin commented Jan 15, 2025

Yeah but how do we get this .tar.gz by ourselves, preferably any version we like? 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants