In the UK, there are three (or four, depending on how you count them) types of device associated with smart meters.
Electricity meters are designed to last, and contain a radio that lets them communicate use to the distributor. What type of radio depends on where in the country you are.
The Gas meter is battery powered, and tries to send data to the electricity meter every half hour, over Zigbee. This works better for some than for others.
Then there's the in-home display, you get one with the meter but it's not required for reporting -- it's purely a display. At some point between the meter being installed and us moving in the one that goes with our house went walkabout, so we don't have one. Except we actually sort-of have two: our supplier makes a small box (with an ESP32 in it) that sends them near-realtime data (and also, happily, completes the otherwise-unreliable Zigbee mesh because the junk I have in the garage blocks the signal) and before that arrived I got a Hildebrand Glow, which talks MQTT to my Home Assistant.
The electricity meter receives the current price if it's a normal non-dynamic price, and the Glow can read that, but can also cope with Octopus Agile with its half-hourly pricing because it's able to fetch that data over the Internet.
The raw metering data isn't quite available to everyone in open formats, but there are procedures that one may go through to be able to receive data and at least one company then makes that data available to the consumer. It's not as fine-grained as the data available on the local Zigbee mesh, which is why those same companies also sell hardware that'll join said mesh. Unfortunately the mesh isn't open for use by arbitrary hardware.
You can also get random monitoring devices that sit on the consumer side of the meter and give you whatever capabilities you buy, and it sounds like the article is an example of one of those, rather than of a smart meter. The author would probably be better off with an actual smart meter, if that's an option.
Electricity meters are designed to last, and contain a radio that lets them communicate use to the distributor. What type of radio depends on where in the country you are.
The Gas meter is battery powered, and tries to send data to the electricity meter every half hour, over Zigbee. This works better for some than for others.
Then there's the in-home display, you get one with the meter but it's not required for reporting -- it's purely a display. At some point between the meter being installed and us moving in the one that goes with our house went walkabout, so we don't have one. Except we actually sort-of have two: our supplier makes a small box (with an ESP32 in it) that sends them near-realtime data (and also, happily, completes the otherwise-unreliable Zigbee mesh because the junk I have in the garage blocks the signal) and before that arrived I got a Hildebrand Glow, which talks MQTT to my Home Assistant.
The electricity meter receives the current price if it's a normal non-dynamic price, and the Glow can read that, but can also cope with Octopus Agile with its half-hourly pricing because it's able to fetch that data over the Internet.
The raw metering data isn't quite available to everyone in open formats, but there are procedures that one may go through to be able to receive data and at least one company then makes that data available to the consumer. It's not as fine-grained as the data available on the local Zigbee mesh, which is why those same companies also sell hardware that'll join said mesh. Unfortunately the mesh isn't open for use by arbitrary hardware.
You can also get random monitoring devices that sit on the consumer side of the meter and give you whatever capabilities you buy, and it sounds like the article is an example of one of those, rather than of a smart meter. The author would probably be better off with an actual smart meter, if that's an option.