I managed to use Python to access the API. My code is here if anyone's interested: https://github.com/benshep/scripts/blob/master/get_energy_usage.py I used asyncio to do requests asynchronously (unlike other code that's been posted here - so it should be faster), and I probably need to write something to refresh the token periodically.

Found a slight issue: trying to fetch the most recent readings, there are always a set of zero readings at the end of the time series. I can filter these out, but it would be nice if these were returned as NaNs instead.

Some time ago I built a Python library to interface with the official HTTP offering, it also deals with some of the quirks in data retrieval. I have been using this API for about seven or eight months and it has been working well.

I use it to return data to a custom smart hub that displays usage and cost alongside temperature and other smart device status, it runs on a raspberry Pi 3 with a 7 inch touch screen.

I would love some feedback / improvements or other people using the library. It requires Python 3 and is available here: https://github.com/ghostseven/Hildebrand-Glow-Python-Library

Thanks

attempt since 10:00:-

{"SOURCE": "internet", "elecMtr": {"0702": {"00": {}}}, "gasMtr": {"0702": {"00": {}}}, "gid": "70B3D521E0004D70", "gmtime": 1758705416, "hversion": "GLOW-IHD-02-1v4-SMETS1", "pan": {"euis": [], "join": "0", "lqi": "28", "nPAN": "00", "rssi": "A6", "status": "rejoin_failed"}, "smetsVer": "SMETS1", "time": "0068D3B708", "ts": "2025-09-24 09:16:56", "upTime": "000A8907", "zbSoftVer": "1.2.5"}

this was the 09:30 version (and typical of normal files ):-

{"SOURCE": "internet", "elecMtr": {"0700": {"06": {"17": "05"}}, "0702": {"00": {"00": "000001DCB968", "01": "000000000000", "02": "000000000000", "07": "3066688E", "14": "02"}, "02": {"00": "00"}, "03": {"00": "00", "01": "00000001", "02": "000003E8", "03": "43", "04": "9B", "06": "00", "07": "1100025431640", "08": "19P0305160"}, "04": {"00": "FFFFFFDB", "01": "000A5A", "30": "000000", "40": "000000"}}, "0705": {"00": {"00": "00D5", "01": "00000000"}}}, "ets": "2025-09-24 08:30:06", "gasMtr": {"0702": {"00": {}}}, "gid": "70B3D521E0004D70", "gmtime": 1758702609, "hversion": "GLOW-IHD-02-1v4-SMETS1", "pan": {"euis": [], "join": "0", "lqi": "44", "nPAN": "00", "rssi": "AD", "status": "joined"}, "smetsVer": "SMETS1", "time": "0068D3AC11", "ts": "2025-09-24 08:30:09", "upTime": "000A7E10", "zbSoftVer": "1.2.5"}

GET: https://api.glowmarkt.com/api/v0-1/resource/[...]/meterread

{'status': 'OK', 'name': 'Smart Meter, gas consumption', 'resourceTypeId': '[...]', 'resourceId': [...]', 'data': [[1753520321, 92316]], 'units': 'm3', 'classifier': 'gas.consumption'}

This seems to report 92316 cubic meters of gas where the actual figure in 92.316 (as reported on the CAD and with my provider etc) so is out by a factor of 1000

GET: https://api.glowmarkt.com/api/v0-1/resource/[...]/meterread

{'status': 'OK', 'name': 'Smart Meter, electricity consumption', 'resourceTypeId': '[...]', 'resourceId': '[...]', 'data': [[1753520321, 15019494]], 'units': 'Wh', 'classifier': 'electricity.consumption'}

And this seems to report 15019494 Wh of electricity, or 15,019.494 kWh where the correct figure (again from provider and your CAD and my existing smart meter) is 1,501.9494 kWh so is out by a factor of 10

I've put a fudge factor in my script to retrieve these for now, but thought you might want to correct the units and/or numbers

It looks like (atm) that we had a some sort of DOS attack on mqtt authentication.

I will be reviewing stuff, but it caused major internal issues and I may need to decouple the mqtt feed further from our core systems.

This will inevitably make the mqtt more delayed and less reliable.

I will advise you before I make any major changes.

$SYS/broker/connection/core-mosquitto.glowmqtt1/state

rather than

SMART/HILD/${MAC}

Given the issue is widespread I imagine it is an HA library that has been broken - does anyone have an idea what it might be.

I can successfully perform Step 1.Authenticate, i.e., obtain “valid”:true, and a “token”. I also retrieve an undocumented "isTempAuth":false.

So, then I move to Step 2. Get all virtual identities, using:

·        GET,

·        "contentType":application/json,

·        “applicationId":b0f1b774-a586-4f72-9edd-27ead8aa7a8d,

·        and my token.

But I get an exception - “Request failed for https://api.glowmarkt.com returned code 400. Truncated server response: {"error":"bad request","message":"bad request"}”

Have been banging my head for a long time now, any ideas, or anyone else found this?

Using "Postmaster", I've had no problem with https://api.glowmarkt.com/api/v0-1/auth to get my token

But when I enter the token into https://api.glowmarkt.com/api/v0-1/virtualentity I just get "400 Bad request"

{

    "error": "bad request",

    "message": "bad request"

}

I've tried everything - things which I guess shouldn't make a difference like changing the order of parameters; moving from input parameters to the raw: body. Submitting without parameters also, so I'm obviously missing something.

Any suggestions greatfully received, thanks Geoff

<edit> - started investigating Glowmarkt's Swagger UI and I do seem to get some response via this method

for instance using https://api.glowmarkt.com/api/v0-1/resource via "Postmaster" I get 400 bad Request, but authorising and submitting via Swagger I do get the expected response </edit>

{'error': 'missing required elements -veTypeId,/resources or autocreate/'}

Has anyone else seen this? I only just got my smart meter and although data is coming through to the Bright app, my energy supplier can't see it yet. Do I just need to wait, or am I submitting my request wrong?

I'm using Python, calling

response = rq.post("https://api.glowmarkt.com/api/v0-1/virtualentity", headers='"Content-Type": "application/json", "applicationId": strAID, "token": strToken)'

All help gratefully received

I'm querying the API at: https://api.glowmarkt.com/api/v0-1/resource/<<MyResourceId>>/readings?from=2024-06-17T00:00:00&to=2024-06-18T23:59:59&period=P1D&offset=-60&function=sum

But I'm struggling to understand why I'm seeing two sets of data returned.

{

"status": "OK",

"name": "electricity consumption",

"query": {

"from": "2024-06-17T00:00:00",

"to": "2024-06-18T23:59:59",

"period": "P1D",

"function": "sum"

},

"data": [

[

1718582400,

14.003

],

[

1718668800,

12.683

]

],

"units": "kWh",

"classifier": "electricity.consumption"

}

Does anyone know why I'm seeing this?

Thanks.

I recently got AC coupled battery storage and Shine seems to hold the data I want for Home Assistant, but I can't figure out how to get it.

However I have recently had my meters upgraded to SMETS2 so I now have access to GAS as well as electric via the Glow API. Unfortunately the gas consumption data is frequently missing, either for a full day, or for parts of a day. The Octopus API seems to have it all

Has anyone else experienced this and can anyone advise how to resolve this?

New user.

Is there an api call to request back filling, I currently have data from late August but need from at least 11 Aug as E.On are useless 😎

G

Is it just me?

I've just joined the community and discovering how to use the API. I do not have a CAD and am instead obtaining the DCC data from midnight last night (which is fine for my purposes now).

So far I've created a token with Auth and can see my Virtual Entries. When i attempt to do a 'current' or 'meterread' for 'electricity consumption' I get no data or not implemented. And then when i try to use the resource period for 'readings' as per below it gives me the usage for the timeframe (eg 1 hour). How can i change this to get the last raw/absolute meter reading?

api .. /resource/{id}/readings?from=2023-01-23T00:00:00&to=2023-01-23T23:59:59&period=PT1H&offset=0&function=sum

Two questions really, can i use a different value for 'function=' above to get raw value (know of sum or avg)? Or is there another endpoint I can use to get the last DCC meter reading?

Thanks in advance,

Jarad

I'm using the API to retrieve the cost of consumed electricity for a given time period covering one or more days, with a 30 minute aggregation level. I can't work out whether the values returned include the standing charge, or just the cost of the electricity - it seems to vary, and I can't see a pattern for when it does. Is it supposed to include the standing charge, and if so is it in only one of the 30 minute periods (presumably 00:00 to 00:30 am)?

Thanks

I'm trying to access web-based data from glowmarkt. I'm trying to use a Node Red HTTP request node to send Bright app userid and password to https://api.glowmarkt.com/api/v0-1/auth embedding the content type and applicationId in headers. I've spent hours researching the use of the HTTP request node but keep getting statusCode: 500.

To try to find where the problem lies, I tried using the example cURL from a command prompt on my Raspberry Pi, substituting my own credentials

curl -X POST -H "Content-Type: application/json" -H "applicationId: b0f1b774-a586-4f72-9edd-27ead8aa7a8d" -d '{"username": "MYBRIGHTIDHERE", "password":"MYBRIGHTPASSWORDHERE"}' https://api.glowmarkt.com/api/v0-1/auth"

The response was a string with a token in. When I used the next cURL example:

curl -X GET -H "Content-Type: application/json" -H "token:MYVERYLONGTOKENRECEIVEDINTHELASTSTEPPASTEDINTOHERE" -H "applicationId:b0f1b774-a586-4f72-9edd-27ead8aa7a8d" “https://api.glowmarkt.com/api/v0-1/virtualentity"

I just got a /> prompt (By the way, it looks like enter a single greater than character causes the text to become quoted). After pressing enter a couple of times, I got:

curl: (3) URL using bad/illegal format or missing URL

curl: (6) Could not resolve host: application

I can't progress the Node red implementation to receive historical data until I've sorted out why the examples from the API Documentation don't seem to work from a command prompt. I have seen that there are Postman and Swagger means to access the data and that others have created Python and HA integration but I'd just like to use Node red.

Does anyone have any idea what's not right here?

Hildebrand are potentially looking into exposing more of their API's to the public, with this in mind what features or changes would you like to see?

I hope we can use this discussion to bounce around some ideas, especially if people use the current API in different ways or have different needs.

For me at this stage I hope that they can fix some of the minor bugs / inconstancies with the current cost reporting (not a major issue at all and is easy worked around). As to new features I am all ears 😀

I'd literally just installed a SMETS2 IHD with local MQTT at a second property within 30 mins of the feed stopping, so don't know if this is a coincidence or if something specific to me has gone wrong,

>openssl s_client -connect api.glowmarkt.com:443
CONNECTED(00000003)
depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = R3
verify return:1
depth=0 CN = *.glowmarkt.com
verify error:num=10:certificate has expired
notAfter=Jan 24 08:01:21 2023 GMT
verify return:1
depth=0 CN = *.glowmarkt.com
notAfter=Jan 24 08:01:21 2023 GMT
verify return:1
...

In Domoticz, you simply need to add hardware "MQTT Client Gateway with LAN Interface," just use "none" as the publish topic. Then import my Node Red flow into Node Red ( import is on the main menu accessed top right. ) You'll also need to create virtual sensors of type Electric ( Instant + Counter ) for Import and Export, a Gas Meter for Gas, and I also have a user variable which is a signed version of the current grid power ( -ve = export. )

https://bit.ly/3aBG8wr

You'll need to double-click on the Hilderbrand SMQTT node and change the Topic, then click on the edit button next to "Hildebrand Encrypted MQTT" and set your username/password under "security." Both of these details will be supplied when you get MQTT access from Hildebrand. Finally, change the "idx" values in the various "Update..." nodes to match your virtual devices/variable ( or just remove them if you don't use them. )

Since the data's updated every 10 seconds or so ( for electricity ) it opens up quite a few possibilities. For example, I have an event script which turns on an air source heat pump in my office if average export for the last 5 minutes is higher than 650W AND the Honeywell EvoHome zone setpoint is above 18 degrees. It also lowers the zone by one degree and sets the heat pump one degree higher ( so I use gas if there's no sun, and the heat pump when there is, but still control either source via the Honeywell wall thermostat.... ) This is all reverted if average export drops below 200W.

I am trying to understand how I could use the API to get a view on KWh used for the R1 rate (day) and KWh used for the R2 rate (offpeak).

Do we have access to the R1 and R2 values through the API?

Or do I need to load all 30 min data into a respository/db and do some grouping there?

Ideally, I would like to use Python.

Thanks!

I am currently trying to display the current electricity cost on my system - similar to the home page on the Bright App, I have the electricity.consumption value returned correctly with the correct "units" (W). However when requesting the electricity.consumption.cost value I get the same "data" and "units" values returned from the electricity.consumption call.

The request I am using is,

"https://api.glowmarkt.com/api/v0-1/resource/f6def7be-993a-409f-9c67-7a919a853efa/current"

JSON returned is,

{

"status": "OK",

"name": "electricity cost",

"resourceTypeId": "78859e39-611e-4e84-a402-1d4460abcb56",

"resourceId": "f6def7be-993a-409f-9c67-7a919a853efa",

"data": [

[

1671015029,

353

]

],

"units": "W",

"classifier": "electricity.consumption.cost"

}

As you can see the "units": "W"

Thanks all in advance

Curtis

Which is working except when I am exporting the grid I get these sort of values when for example IHD is showing -1.000

ihd1 — ImgBB (ibb.co)

Does anyone know how to adjust the template so its reads correctly on hassio?

Thanks!

[ [ 1666825200, 0 ], [ 1666828800, 0 ], [ 1666832400, 0 ]]

I have checked that the gas resourceId is still correct.

Electricity readings are coming through fine.

Has anyone else experienced this?

MQTT found in this Home Assistant instance.
Starting glow2mqtt.py...
MQTT connected...
Connected to Glow MQTT broker...
Configuring Home Assistant...
{'elec_imp': 42749.539, 'watt_now': 454}
{'elec_imp': 42749.542, 'watt_now': 461}
Traceback (most recent call last):
  File "/glow2mqtt.py", line 240, in <module>
    mqttg.loop_forever()
  File "/usr/lib/python3.10/site-packages/paho/mqtt/client.py", line 1756, in loop_forever
    rc = self._loop(timeout)
  File "/usr/lib/python3.10/site-packages/paho/mqtt/client.py", line 1164, in _loop
    rc = self.loop_read()
  File "/usr/lib/python3.10/site-packages/paho/mqtt/client.py", line 1556, in loop_read
    rc = self._packet_read()
  File "/usr/lib/python3.10/site-packages/paho/mqtt/client.py", line 2439, in _packet_read
    rc = self._packet_handle()
  File "/usr/lib/python3.10/site-packages/paho/mqtt/client.py", line 3033, in _packet_handle
    return self._handle_publish()
  File "/usr/lib/python3.10/site-packages/paho/mqtt/client.py", line 3327, in _handle_publish
    self._handle_on_message(message)
  File "/usr/lib/python3.10/site-packages/paho/mqtt/client.py", line 3570, in _handle_on_message
    on_message(self, self._userdata, message)
  File "/glow2mqtt.py", line 83, in process_msg
    if '00' in data['elecMtr']['0702']['04']:
KeyError: '04'
s6-rc: info: service legacy-services: stopping

I have to restart the add-on manually and it then runs for an indeterminate period before crashing with the same error.

I bought the SMETS1 GlowStick a few months back. I got remote MQTT activated and started reading the MQTT information from glowmqtt.energyhive.com, everything was great, in the sense that I was getting instant and cumulative (daily and reading) kWh consumption for both gas and electricity.

I bought he IHD recently (for local MQTT), and after receiving it, I started using it. It's still working for most things, but I lost the instant gas consumption on the way...

This is the case for the application, the API and MQTT, but it's most obvious to me for MQTT because I have full logs from monitoring.

I can clearly see it's the case, because I have stuff logged and what used to work stopped working. I used to get the instant gas from value['gasMtr']['0702']['04']['00'] and that was working perfectly fine. I've got months of readings to prove it.

Since I got the IHD, this is what I receive on the MQTT topic. As you can see, instant reading (0702.04.00) is there for the electricity meter but absent for the gas meter:

{
    ...,
    "elecMtr": {
        "0700": { ... },
        "0702": {
            "03": { ... },
            "00": { ... },
            "04": {
                "30": "000000",
                "40": "000000",
                "01": "002710",
                "00": "0000022C"
            },
            "02": { ... }
        },
        "0705": { ... }
    },
    "gasMtr": {
        "0702": {
            "03": { ... },
            "00": { ... },
            "04": {
                "30": "000000",
                "40": "000000",
                "01": "006E14"
            },
            "02": { ... }
        },
        "0705": { ... }
    },
    ...
}

Now that I have local MQTT, I can also confirm that on the local MQTT sensor topics

Electricity:

{
    "electricitymeter": {
        "timestamp": "2022-11-18T17:50:24Z",
        "energy": {
            "export": { ... },
            "import": { ... }
        },
        "power": {
            "value": 0.569,
            "units": "kW"
        }
    }
}

Gas:

{
    "gasmeter": {
        "timestamp": "2022-11-18T17:50:25Z",
        "energy": {
            "import": {
                "cumulative": 56942.363,
                "day": 28.18,
                "week": null,
                "month": null,
                "units": "kWh",
                "cumulativevol": 56942.363,
                "cumulativevolunits": "kWh",
                "dayvol": 28.18,
                "weekvol": null,
                "monthvol": null,
                "dayweekmonthvolunits": "kWh",
                "mprn": REDACTED,
                "supplier": "---",
                "price": {
                    "unitrate": 0.11812,
                    "standingcharge": 0.28476
                }
            }
        }
    }
}

According to the both the App and API, I am supposed to be on off peak between 23:30 and 08:30.

Unfortunately, there is a gap between 01:30 and 03:30 (when energy goes back to peak) but neither the App or API detect it.

The kWh (consumption) returned by the API for every 30 min slots is correct, but the cost is wrong, since the rates applied are wrong.

https://api.glowmarkt.com/api/v0-1/resource/{{resourceId}}/readings?from=2022-11-03T00:00:00&to=2022-11-03T09:27:38&period=P1D&offset=-60&function=sum

I have response:

{"status":"OK","name":"electricity consumption","resourceTypeId":"{{resourceTypeId}}","resourceId":"{{resourceId}}","query":{"from":"2022-11-03T00:00:00","to":"2022-11-03T09:27:38","period":"P1D","function":"sum"},"data":[[1667433600,0]],"units":"kWh","classifier":"electricity.consumption"}

Can someone explain, what I'm doing wrong?