Hi,
Just got my inverter and battery installed last. My first post here.
The clock seems to be set to GMT+1 so bst, but it seems 1 hour ahead of what it should be so it's 11 o clock but the system thinks it's 12.
Can't find where to set the time, can anyone advise?
Thanks
Neil
It's on the account settings page of the web portal.
Set it to GMT and the systems will adjust for BST starting and ending.
Once you've changed it there, you might need to sync the inverter time. That's via the web portal too, my Inverter page, the little cog (remote control), then scroll down to time and date and press the button (send if I recall correctly).
Ah, now I see. Thanks for the help!
Hello, my first post having had a battery and inverter installed yesterday.
I am slightly bemused with the time showing on graphs etc. They all show approx. 1 hour ahead of real time.
I have set the time manually as GMT (+0). I have tried syncing the inverter, but nothing seems to change.
Am I doing this incorrectly?
Chris
chickenlegs Try "Sync Inverter Time" on the Account page on the web portal. Givenergy change the time on the inverters twice a year and it's feasible yours was built/tested during GMT and it didn't get the time sync after commissioning. Personally, I'd prefer the inverters to be set to UTC/Zulu (same as GMT) and then use the web page to convert dates and times to local timezone, but that's not the design and it's probably a step too far at this stage.
Thank you Tim. I was just about to sync the inverter time and looked at a graph to see if the time was correct and for some unknown reason, it would appear to have re-established the correct time. Perhaps it takes longer than I expected it to.
Thank you for taking the trouble to respond.
Just when you have that syncing feeling, everything turns out well in the end
(Sorry). 🤣
Hi, first comment here, really loving the GivEnergy platform, have a GIV-HY5.0 inverter with 9.5 battery.
I cannot get the time to display correctly in the web portal, or in the Android app. Let's focus on the web portal. I've followed this thread, and looked at many other posts. Current situation:
/v1/inverter/{serial}/system-data/latest is showing most recent data around 13:30Z - which indicates that the time on the inverter is correctly set, and in UTC.[Update 1] I think I've spotted what is happening. At 14:45 BST, if I look at the system data, the most recent update is still displayed at around 15:30. If the system was still displaying new entries at GMT+2, I'd expect to see more recent data. Scrolling down the list of data reveals that the roughly five minutes apart pattern of data points is disrupted between 14:30 BST and 14:45 BST, with entries seemingly being "doubled up" i.e. GMT+1 (or BST), and GMT+2
If my theory is correct, I should see new data points at the top of the list from just after 15:30 BST....
[Update 2] It's now just gone 15:05 BST, and I can see new "duplicate" data points up to 15:05. It definitely seems that the data, uploaded by the inverter in UTC, is then rendered into the configured timezone and stored in the database. Confusingly setting the timezone to GMT appears to result in "UK time", which is currently BST. Once you know this, it's simple, even if technically incorrect. We should be thankful that the designers and implementation team did the right thing in basing all timestamps on UTC 👍️
[Update 3] It's now just gone 15:30 BST, and the latest new data in the web portal, and in the Android app, is shown at around 15:30 🙂
Next question - if I configure the web portal to charge the battery from 02:00 to 05:00, will that be construed as UTC, or back-converted from BST to UTC 01:00 to 04:00 ? As an experiment, I have set a timed charge to 100% in web portal, 02:00 to 03:00. Getting the settings values from web portal "remote control", and from the API, suggests this has been stored as UTC. I'll update this thread tomorrow with the answer.
[Update 4] Confirmed - the system charged the battery from 02:00 to 03:00 UTC. Nice !
[Update 5] A week later, I've looked again, and the charging is using BST, not UTC. I've rechecked the data from last week, and either something has changed in the system, or more likely I read it incorrectly. So the charging happens on BST.