Smart Meter Check homebrew.n3rgy.com any way to refresh?

Qyburn

Hi,

Does anyone know how to get https://homebrew.n3rgy.com to carry out a fresh check, rather than returning cached results? For me it's still showing details of the meter installed on 1st April, not the one installed on 20th June.

Ildhund

I don't, sorry.

That said, I just ran a check using the second sign-in option (house no. and postcode) instead of MPAN. I got a fresh record: "Cache: 2025-06-26 09:18:14.035861 [no cache]". I might of course have got that with the first option, too - I'll never know.

Could it be that Elexon still haven't caught up with your new meter? You could compare the ESME GUID Homebrew is quoting with the one on the meter itself. 

Rather worryingly, for the first time Homebrew didn't retrieve certification details about my communications hub

Qyburn

Thanks, I didn't try that because we don't have a house number, however it worked with name and postcode. Still returned the cached result though ..

Cache: 2025-06-18T07:03:33.412Z [cached]

Qyburn

This morning it says it's grabbed fresh data ..

Cache: 2025-06-30 06:13:03.976328 [no cache]

However it's still showing the old comms hub, installed on 1st April 2025 not the replacement fitted on 20th June.

Ildhund

Odd. In my earlier comment, I suggested that Elexon hadn't caught up with your new meter. That may well be the case, but I was mistaken in thinking that Elexon was responsible for storing details like the IDs of equipment on the smart meter network. It's the DCC itself that keeps track of each device with its MAC address so that it can route messages correctly. I'm not sure whose responsibility it is to keep those records updated, but I expect it's the supplier, who probably instructs a data processor to carry out the actual updating. Armed with your Homebrew information, you should be able to get your supplier to do the necessary. 

Qyburn

Octopus is able to read the meter so the current comms hub is clearly working and communicating. I think what this shows is that "Homebrew" isn't actually talking to the comms hub, it must be pulling data saved *somewhere*.  Is it looking up what's on record against the MPAN?

Qyburn

Answer from N3rgy is that they're reading the data from DCC, not stored data held by themselves. So it looks like a screw up by Octopus, but since they seem able read data I don't hold much hope of them fixing something that only affects third parties.

"These details are being provided by the DCC. Could you please communicate with the respective supplier to ensure that information is updated accordingly. Please note that this data is not maintained on the n3rgy side"

Ildhund

Qyburn said:

... it looks like a screw up by Octopus, but since they seem able read data I don't hold much hope of them fixing something that only affects third parties.

Who says it only affects third parties? Of course these databases of equipment data should be maintained and updated. Think of the many metering systems still masquerading as RTS-controlled because somebody couldn't be bothered to update the central MTC record when the RTS itself was dismantled. How do you imagine Octopus' troubleshooting would go when they stop being able to read data?

Thanks for clearing up my misapprehension that Homebrew was actually querying the meter/CH itself.

Qyburn

Ildhund said:

Qyburn said:

... it looks like a screw up by Octopus, but since they seem able read data I don't hold much hope of them fixing something that only affects third parties.

Who says it only affects third parties? 

That's just a wild guess given that Octopus are reading the meter mostly OK and I got what I would call a slightly snotty response from them to that effect when I asked them why they'd stopped collecting export data ..

"Regarding your request, your ombudsman case has already been closed, and all the remedies have been implemented. Since you’ve had a new meter installed and it’s now communicating, I’ll be closing your Octopus complaint."

Meanwhile Bright stopped working at the same time as Octopus stopped collecting export,