Skip to content

Conversation

drc38
Copy link
Collaborator

@drc38 drc38 commented Jul 6, 2021

Hi @lbbrhzn, this function can be used for a custom service call when ready as referred to in #34

@jeremycoppey
Copy link
Collaborator

Ok guys,
Good news, my charger just (month old) got a firmware update released.
So I can test this feature from the moment you merge this into main.
You are talking about the firmware_url any idea where I can locate this?
The charger product page has a link to a firmware page: https://www.se.com/ww/en/download/document/MFR4341700/
But behind the download button is a zip file containing the file with the firmware.
If I read your code you need the update file directly.
Or should I ask Schneider for a public url where the file is hosted?

@drc38
Copy link
Collaborator Author

drc38 commented Jul 6, 2021

Ok guys,
Good news, my charger just (month old) got a firmware update released.
So I can test this feature from the moment you merge this into main.
You are talking about the firmware_url any idea where I can locate this?
The charger product page has a link to a firmware page: https://www.se.com/ww/en/download/document/MFR4341700/
But behind the download button is a zip file containing the file with the firmware.
If I read your code you need the update file directly.
Or should I ask Schneider for a public url where the file is hosted?

Hi Jeremy, there's still a bit or work required before this function can be used in HA as a custom service. So it won't be available after the merge. Your charger may accept the zip file directly, otherwise you could unzip and load to onedrive or similar cloud server. The metric "FW.Status" can be used to monitor the update process. I take it your charger supports the Firmware Management profile?

@jeremycoppey
Copy link
Collaborator

Yes my charger supports the following:
Core, FirmwareManagement, Reservation, SmartCharging

I will do a manual update then.
Looks like it adds some extra features:
image

Do you know what they mean with this feature? (see page 7 of the release notes)
EVlink_charging station_Release_Note_R07_run17.pdf

@drc38
Copy link
Collaborator Author

drc38 commented Jul 6, 2021

Clock aligned values are for accurately reporting energy used in given time periods eg 30min or 1hr required by Energy Retailers / Billing solutions. Not really of use for most personal applications.

If you can hold off the manual update it would be useful to be able to test this feature when it's available. My charger is already on the latest firmware.

@jeremycoppey
Copy link
Collaborator

sorry I just updated.
But as they release frequently I don't think I will be waiting long for a new firmware update.

Thanks for the clarification.

@lbbrhzn
Copy link
Owner

lbbrhzn commented Jul 6, 2021

hi @drc38, these changes look ok, thanks! I cannot download new firmware for my Wallbox charger myself, so I was not able to fully test it.

Just a minor point: the pre-commit check for the formatting is failing. Did you run a pre-commit check before you pushed your changes? Just use pip install pre-commit to install

@drc38
Copy link
Collaborator Author

drc38 commented Jul 6, 2021

@lbbrhzn, thanks I wasn't sure whether the pre-commit process was supposed to do the reformatting or whether I needed to do it locally.

@lbbrhzn
Copy link
Owner

lbbrhzn commented Jul 6, 2021

@lbbrhzn, thanks I wasn't sure whether the pre-commit process was supposed to do the reformatting or whether I needed to do it locally.

You need to do it locally. The pre-commit actions are also done as an action on GitHub, and it will result in failed checks if there are still some formatting issues remaining.

@lbbrhzn lbbrhzn merged commit 60ba1ce into lbbrhzn:main Jul 6, 2021
@drc38 drc38 deleted the dev2 branch July 7, 2021 08:46
drc38 added a commit that referenced this pull request Dec 16, 2021
change to hard reset, trigger post_connect and reset reconnects
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants