notes:smets - pup.casa Docs

Trace: • rpi2b-0 • thinkpup • labrador • pup2k • alpine • hw • niko

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

# SMETS

Short for //Smart Metering Equipment Technical Specifications//, SMETS exists in a few variants: SMETS1, SMETS1+, and SMETS2.

## Glossary

### SMETS1

The first variant of smart meters, SMETS1 is notable for not being as interoperable between energy providers as other variants. SMETS1 meters can be upgraded to SMETS1+.

### SMETS1+

A variant of SMETS1 that back-ports the interoperability features from SMETS2, which brings enrolment into the DCC (Data Communications Company)

### SMETS2

SMETS, but interoperable. Seems to use a communications service (3G?) that is provider-agnostic.

## Octopus Energy

We just switched from British Gas (who said that maybe in a few months they might fix our SMETS1 meter, which had gone offline and required top-up codes to be entered manually on the unit itself), to Octopus Energy (who sent an engineer out to replace our SMETS1 meter with a SMETS2 one as soon as we told them it was still in prepaid mode and was about to cut our energy off). Octopus provided a new IHD, and also provide an API with half-hourly energy usage statistics. The IHD supports WiFi, and connects to the Chameleon Cloud service over MQTT-TLS (port 8883).

## Crimes

My first thought here was to just redirect the DNS query for the MQTT server to my own, however when I did that, the IHD failed to connect. Turns out: for once, an embedded device that uses encrypted connectivity, actually verifies the CA certificate of what it's connecting to.

Search

Navigation

Print/export

Tools