If you know how to use Python I have no doubt you can get the readings to HA without using node-red. I don’t know how to do that so I figured learning to use node-red would be easier.
Here is a screen shot of my node-red flow:
I have ringed the nodes that are relevant to getting the power readings to MQTT. /dev/tty/AMA0 is the serial input, Calculations are the functions (the relevant ones are shown below). And Annex Meter, Running cost and Power readings are the MQTT outputs.
The bit in Calculations that splits off the power readings is:
var output = msg.payload.split(" ");
var rp1 = parseFloat(output[1]).toFixed(0);
var rp2 = parseFloat(output[6]).toFixed(0);
var rp3 = parseFloat(output[11]).toFixed(0);
I used these as well but don’t find them as accurate as fibaro or aeotec sensors. Im still hunting for a decent outdoor light sensor after my aeotec broken but I am not paying £50
The trouble with the clamp meters is they’re not necessarily that accurate - they can be affected by all sorts of things and accuracy changes with consumption ( low currents are detected with far less accuracy. ) I have one on the main supply and one on my solar PV spur… with a bit of tweaking and a fudge factor I’ve managed to get the PV reading within around 3%, which is about as good as it gets, but the main supply is only within 10% or so. Plus of course, there’s no chance of measuring gas use this way ( though there are solutions which attempt to read the digits on the meters. )
Unfortunately, until the energy companies are forced to give us real time access to our data, it’s what we’re stuck with In theory, “the industry” is aware of the need and again, in theory, should allow you to buy your own CAD ( consumer access device ) which the energy company then facilitates you pairing to your HAN. These CADs then provide the data you need. See https://www.beama.org.uk/asset/EBA9BBB9-756E-48A0-B6C38EBFBC3EEEAB/ amongst other things.
I think everyone needs to lobby the energy companies to get this sorted.
Sadly I dont think this will ever happen.
Some energy providers may give access as a product feature, but in reality there are not enough people who want to own their consumption data (or perhaps who understand that their detail consumption data has value that they are not being compensated for).
If it ever happens there will probably be some kind of tradeoff - such as being charged a premium rate for charging EVs (to cover future shortfall from fuel duty)
OVO fall into my definition of “Some energy providers may give access as a product feature”.
I think if they will give an API to get the data its great - kudos to them!
But I dont see it becoming widespread. IMO the ROI to build and support the API is dubious.
Maybe OVO can justify it with good marketing as a smart home/maker/hacker friendly provider, but I dont see many other providers following.
Actually, I’ve had a very interesting response from Hildebrand which seems to change everything! Here’s the reply:
The really good news is that now that the SMETS2 regime is in place, the suppliers are no longer a barrier because in addition to selling the IHD/CAD we are also a DCC Other User (a process which involved building our own connection to the DCC and passing extensive tests and audits) - this means that you can switch to whoever offers you the best deal and we can then sell you our SMETS2 IHD/CAD :
We also provide our customers with API access to their data.
Apparently there are a few suppliers who are still being rather slow about installing SMETS2 meters - so before making your final choice, we recommend that you double check.
The IHD/CAD they offer isn’t mega expensive ( 65 quid, not sure if that’s inc VAT ) so would seem to provide the perfect solution! They also do have a solution for SMETS1 apparently but I haven’t looked into that. They’ve also sent me the API details, and it’s pretty standard JSON stuff, though they can also publish via MQTT apparently. Electricity meter readings are updated every 10 seconds, and gas every 30 minutes ( dictated by how often the meters themselves send updates. )
It’s not tied to the supplier ( one advantage of having a third party device rather than a supplier API. ) If you have a SMETS2 meter, Hildebrand handle the pairing via the DCC - at least that’s how I believe it works. You can then switch suppliers as you wish.
If you have SMETS1, I think that might be more tricky. There was talk about integrating SMETS1 meters with the later system but since I don’t have one I’ve not really bothered to find out.
Such a shame that the DCC solution was not designed by default from the ground up to allow the consumer to have access and ownership of their usage data Its great that Hildebrand is closing the gap.
The Hildebrand/Glow CAD simply accesses the PAN (Personal Area Network) created by the SMETS2 meters and the ‘Comms Hub’ part of the Smart Meter ecosystem in your property. It can access this PAN because it talks to the DCC to enable a secure connection. This CAD then uploads the meter data to its own servers (over Wi-Fi) and then allows you to access that data via an API.
I’m in the process of moving to Octopus to use the Agile tariff as, even though I have no PV etc, it is still going to be much cheaper. However, moving back to Octopus is turning into a farce.
Who provides this CAD? Was there anything fancy you had to do to get access to the MQTT on it? Sorry if these are silly questions but i haven’t heard of this or know any energy supplier giving access to the data.
I just got a Conbee-II and have it setup with deConz and the deConz integration on HA. I have tried to pair my smart meter but have no way of doing this. I tried turning off and on the ihd device to see if this triggers something but no luck.
I have the one that OVO supplied which is the Aclara SGM1412-B. The meter does have the zigbee logo, but I’ve no idea how to pair it with my conbee stick.
I looked at this a while back and found this, so seems not:
### Security
Security has been considered very carefully for Smart Meters. The communications network is not part of the internet, it is a closed network only accessible to parties with the right security keys and physical connections. Additionally there is no central database containing customers’ information, the information is only stored on the Smart Meters and sent through DCC onto Suppliers and other parties who have a right to that data and where the customer has given them permission. The customer information inside messages is encrypted and only the receiving party can look at the data, the DCC cannot view the data. The parties receiving the data undergo a rigorous security assessment at the beginning and then have regular security audits.
In theory, “the industry” is aware of the need and again, in theory, should allow you to buy your own CAD ( consumer access device ) which the energy company then facilitates you pairing to your HAN. These CADs then provide the data you need. See 
