Skip to content

GE Cloud Direct failing to pull GivEnergy EVC data after clocks moved to BST #3711

@markbw999

Description

@markbw999

I woke up Sunday morning to a new problem with my EVC data via GE Cloud Direct. None of the entities have been created by predbat. I see this in the log...

2026-03-29 09:37:15.215240: GECloud: Device {'uuid': '31ae9ff1-3298-4910-9271-9a275d07ba79', 'serial_number': '54796066845362', 'type': 'GivEnergy', 'alias': None, 'online': True, 'went_offline_at': None, 'status': 'Available'}
2026-03-29 09:37:15.440376: GECloud: Warn: Failed to get data from ev-charger/{uuid}/meter-data?start_time={start_time}&end_time={end_time}&meter_ids[]={meter_ids}&page=1, response code 422

I did a quick AI search on error 422 and it suggests the api might be being sent incorrect data. I have included the log file.

The errors started a few seconds after 2am on Sunday so I'm pretty sure it is related to the move to BST over the weekend.

I have been trying to find a way to resync the EVC clock but without success. This morning I found out from Paul Landregan at GE (via a FB group) that the EVC doesn't compensate for BST - i.e. it always works on GMT.

So, it seems like the GE Cloud interface is not going to work for another seven months unless a workaround is put in place. Can you look into this please?

predbat.log

Metadata

Metadata

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions