You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Setup fails because ChargerFirmware requires fields no longer returned by the API #400
The failure is dues to ChargerFirmware does not contain the fields CurrentVersion and IsUpToDate. Making those optional locally solves the issue for me.
Thanks for the report and for pinpointing the fields involved — that matches what we found.
This looks like the same root cause as #359: the ChargerFirmware validation model in zaptec/validate.py requires CurrentVersion, IsUpToDate (and a few other fields) even though the code that consumes them (poll_firmware_info() in zaptec/api.py) already handles them being absent — e.g. for a charger that's been added but not yet fully initialized/online. So the validation model was stricter than necessary and rejected a valid API response.
The fix is already up in #397, which relaxes ChargerFirmware so only ChargerId stays required and DeviceType, IsOnline, CurrentVersion, AvailableVersion, IsUpToDate all become optional — matching what your local workaround does. It just hasn't merged yet. Given that in your case this results in the setup of the integration failing, underpins the importance of the fix. Let's see if @sveinse can get it integrated in the next release.
Activity
rhammen commentedon Jul 14, 2026
Thanks for the report and for pinpointing the fields involved — that matches what we found.
This looks like the same root cause as #359: the
ChargerFirmwarevalidation model inzaptec/validate.pyrequiresCurrentVersion,IsUpToDate(and a few other fields) even though the code that consumes them (poll_firmware_info()inzaptec/api.py) already handles them being absent — e.g. for a charger that's been added but not yet fully initialized/online. So the validation model was stricter than necessary and rejected a valid API response.The fix is already up in #397, which relaxes
ChargerFirmwareso onlyChargerIdstays required andDeviceType,IsOnline,CurrentVersion,AvailableVersion,IsUpToDateall become optional — matching what your local workaround does. It just hasn't merged yet. Given that in your case this results in the setup of the integration failing, underpins the importance of the fix. Let's see if @sveinse can get it integrated in the next release.Danhe046 commentedon Jul 14, 2026
Awesome! Yes, PR 397 does exactly what i did locally!