Gridwatch and the pumped readings

Jan 07, 2025 Last reply: 1 year ago 6 Replies

Just occurred to me that the pumped system is a two way system. That is, it uses electricity from the grid during low demand to pump water into the reservoir, then in high demand it returns the electricity to the grid (minus whatever).



For a true record, should the dial be plus and minus (like the interconnects) to record when electricity is being extracted, and when it is being returned?



Assuming, of course, that the extra data is available.



Just a passing thought.


Cheers


Dave R



Tell Dinorwig that.

They (national griddont record what they use. Only what they generate, France is the reverse.

If it were, Id have included it

This one:

formatting link
does show negative when storing the pumped hydro. She doesn't show batteries because currently they only get discharge and not charging data. The source code is published so you can check where the data comes from (looks to be Elexon).

Theo

Ah, I think the pumping data is from NESO:

formatting link

Ooh. That looks like it might have more data than I found.

But when I downloaded the link

formatting link
in her code it just told me the data had moved.

Andy

You have to follow the redirects:

$ wget

formatting link
20:52:12--
formatting link
data.nationalgrideso.com (data.nationalgrideso.com)... 172.64.151.109, 104.18.36.147, 2606:4700:4400::6812:2493, ... Connecting to data.nationalgrideso.com (data.nationalgrideso.com)|172.64.151.109|:443... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location:
formatting link
[following]

--2025-01-15 20:52:12--

formatting link
api.nationalgrideso.com (api.nationalgrideso.com)... 34.140.245.51 Connecting to api.nationalgrideso.com (api.nationalgrideso.com)|34.140.245.51|:443... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location:
formatting link
[following]

--2025-01-15 20:52:12--

formatting link
api.neso.energy (api.neso.energy)... 104.18.14.14, 104.18.15.14, 2606:4700::6812:f0e, ... Connecting to api.neso.energy (api.neso.energy)|104.18.14.14|:443... connected. HTTP request sent, awaiting response... 302 Found Location:
formatting link
[following]

--2025-01-15 20:52:13--

formatting link
83025b28472d6aa2bf5ae59f3724aa78.eu.r2.cloudflarestorage.com (83025b28472d6aa2bf5ae59f3724aa78.eu.r2.cloudflarestorage.com)... 141.101.90.96, 141.101.90.98, 141.101.90.99, ... Connecting to 83025b28472d6aa2bf5ae59f3724aa78.eu.r2.cloudflarestorage.com (83025b28472d6aa2bf5ae59f3724aa78.eu.r2.cloudflarestorage.com)|141.101.90.96|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 255824 (250K) [application/octet-stream] Saving to: ‘demanddataupdate.csv’

demanddataupdate.csv 100%[=======================================>] 249.83K --.-KB/s in 0.04s

2025-01-15 20:52:13 (5.70 MB/s) - ‘demanddataupdate.csv’ saved [255824/255824]

That works. Thank you.

I now have their data back to 2009, right up to date.

Andy

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required