I wonder if I could quiz the community to see if anyone is in a similar situation.

I have an Itron EM425-UK & EK410-UK Meter and Communications Hub combination (SMETS1 but meter updated to allow transition between suppliers etc). The hardware is communicating via the O2 Telefonica 2g network on 900Mhz to the DCC and I can see up to date 30min usage values (with a 24 hour delay) on the octopus app.

My SMETS1 Glow CAD is displaying the current electricity usage correctly and broadcasting electricity usage (and standing charge/cost per unit) correctly locally via MQTT to home assistant. It is also sending this data correctly to Hildebrand so it can be seen in the bright app.

Unfortunately the Glow CAD is not displaying or broadcasting gas usage data locally on MQTT. It is correctly retrieving the standing order and cost per unit values (which have changed recently). I am told by Jane at Glow that it is however able to collect this data and send this to bright (30 minute updates) - again these values are visible in the app.

Does anyone have any similar experiences with the Glow SMETS1 CAD and this meter combination?

Any tips or advice?

Support ticket in with Glow.

Please see MQTT data below.

Many thanks,

Rob

General device info:

{
    "software": "v1.8.13",
    "timestamp": "2023-03-20T18:02:40Z",
    "hardware": "GLOW-IHD-01-1v4-SMETS1",
    "wifistamac": "REDACTED",
    "ethmac": "REDACTED",
    "smetsversion": "SMETS1",
    "eui": "REDACTED",
    "zigbee": "1.2.5",
    "han": {
        "rssi": -69,
        "status": "joined",
        "lqi": 124
    }

Electricity:

{
    "electricitymeter": {
        "timestamp": "2023-03-20T18:02:33Z",
        "energy": {
            "export": {
                "cumulative": 0,
                "units": "kWh"
            },
            "import": {
                "cumulative": 25939.449,
                "day": 14.809,
                "week": 14.809,
                "month": 411.664,
                "units": "kWh",
                "mpan": "not available",
                "supplier": "---",
                "price": {
                    "unitrate": 0.3301,
                    "standingcharge": 0.479
                }
            }
        },
        "power": {
            "value": 0.512,
            "units": "kW"
        }
    }
}

Gas:

{
    "gasmeter": {
        "timestamp": "2023-03-20T18:02:29Z",
        "energy": {
            "import": {
                "cumulative": 0.125,
                "day": 0,
                "week": 0,
                "month": 0,
                "units": "kWh",
                "cumulativevol": 11138.7,
                "cumulativevolunits": "m3",
                "dayvol": 0,
                "weekvol": 0,
                "monthvol": 0,
                "dayweekmonthvolunits": "m3",
                "mprn": "unsupported",
                "supplier": "---",
                "price": {
                    "unitrate": 0.1024,
                    "standingcharge": 0.2684
                }
            }
        }
    }
}

I'd be grateful if anyone can point me in the right direction.

At the time the electricity meter showed

Today - 7.3 kWh £2.33

This Week - 58.0 kWh £17.40

This Month - 271.7 kWh £80.29

The latest (approx) MQTT message https://gist.github.com/REBELinBLUE/c1f1d3bc9bf492a96d2ddbb04e28985e

Today = Standing Charge + (Unit Rate * Day) = 0.5783 + (0.24012 * 7.308) = 2.33309696

This Week = (Standing Charge * 6 for Saturday) + (Unit Rate * Week) = (0.5783 * 6) + (0.24012 * 58.026) = 17.40300312

This Month = (Standing Charge * 26) + (Unit Rate * Month) = (0.5783 * 26) + (0.24012 * 271.758) = 80.29399976

This all lines up, but with gas it doesn't, the meter says

Today - 4.4 kWh £0.57

This Week - 35.0 kWh £3.63

This Month - 171.3 kWh £17.92

The latest (approx) MQTT message https://gist.github.com/REBELinBLUE/fe4daacf0e91e65efdcccdc8278bfde6

Today = Standing Charge + (Unit Rate * Day) = 0.31392 + (0.0588 * 4.378) = 0.57399936

This Week = (Standing Charge * 6 for Saturday) + (Unit Rate * Week) = (0.31392 * 6) + (0.0588 * 35.028) = 3.9431664

This Month = (Standing Charge * 26) + (Unit Rate * Month) = (0.31392 * 26) + (0.0588 * 171.319) = 18.2354772

Today is correct but this week and this month are not, however I have realised if I don't include the standing charge for the current day it is (i.e if I multiply by 5 and 25 instead)

I can't figure out the reason for this, does anyone have any idea?

"software": "v1.9.1",

"hardware": "GLOW-IHD-01-1v4-SMETS2"

Is that up to date or should I be getting it updated somehow? Thanks.

the device I am using to display data does not have energy, but it does have volume (for watering plants). I was going to convert daily gas kwh from a SMETS1 meter to volume but I can't see a Calorific Value in my MQTT. Does the meter just assume a CV or not put it on MQTT. An alternative is to timestamp changes and calculate a power and use the electrical power capability to pretend gas is electricity.

thanks

When restarting Home Assistant, when the sensors are first set up, they end up defaulting to unknown/unavailable if it connects to the MQTT broker between messages. I realise that is typically only 10 seconds to wait before the value is populated, but it would be nice for it to simply populate with the last value immediately.

I started setting the flag on my own messages I publish and it works well, so would be a nice addition!

Thanks for consideration - and Happy New Year!

There is an open Pull Request to address this, please can you merge this? https://github.com/megakid/ha_hildebrand_glow_ihd_mqtt/pull/55

Thanks

I guess this will depend on if this information is actually available to IHD over ZigBee.

Currently I have to go to the meter and a sequence of buttons to access the 'TOUMaxtix' to read my 'Rate 1' and 'Rate 2' usage values.

Being able to log these even if just at the end of each day would be very helpful.

Thanks,

Mark

I currently am on a Economy 7 tariff but am considering changing to a supplier that has 3 rates over the day to support heat pumps.

At the moment the data has cumulative import values (IE Rate 1 + Rate 2 + Rate n), for the Meter, Day, Week, and Month and also shows the unit cost and the standing charge, The unit cost value changes at night time.

My problem is I cannot multiply the unit price by the Day Reading as some of the units are at the night rate and the rest at the day rate.

Can the MQTT Data please be extended to ADD

1) an array of Current, Day, Week, Month, and Rate values for each of the import charging rate is enabled on the meter? IE for my meter I would have 2 values in the array

2) an Index to indicate which rate is import charging rate is currently active (IE for my case Overnight rate index 0 and for day time 1.

The above would make a massive difference to the functionality.

For some reason the figures are not always matching. What's strange though is that the mqtt received values are higher than the actual display, which I thought would be the other way round if anything/delay.

It seems to be the Gas that's wrong. I understand the gas is only updated once every 30 mins however the value on the display should be able to report the same as the unit is sending to Home Assistant via MQTT surely?

Example: https://photos.app.goo.gl/ooejnw5h8vJnPcPs7

Thanks,

James

I already control most of these devices to optimize use of cheep overnight and free solar power, but I am very interested in extending that to make these devices use ZERO power when I am being paid to reduce consumption and many times the import unit rate.

Can ideally the local MQTT api (if not then the web API) include data that indicates that a "deal" period has started and what the payment rate for reducing power is?

I am not sure that the energy companies publish these data values but if they do please expose them to home automation users.

It would be really useful for the (rare) times the CAD loses comms.

I'm using openHAB with my MQTT broker, so it would be possible to create some rule to handle it, but I'm just wondering if I'm missing something. How do other people handle this?

Suggestions welcome.

{
    "electricitymeter": {
        "timestamp": "2024-01-20T19:08:06Z",
        "energy": {
            "export": {
                "cumulative": 0,
                "units": "kWh"
            },
            "import": {
                "cumulative": 8923.032,
                "day": 9.088,
                "week": 75.893,
                "month": 317.976,
                "units": "kWh",
                "mpan": "redacted",
                "supplier": "Octopus Energy",
                "price": {
                    "unitrate": 0.3308,
                    "standingcharge": 0.4277
                }
            }
        },
        "power": {
            "value": 0.453,
            "units": "kW"
        }
    }
}

Can anyone tell me what I need to do?

I have Home Assistant pulling in info from our Glow IHD/CAD on a SMETS2 meter. This all works nicely - I can see our daily, weekly, monthly and total import values (kWh), along with daily standing charge and unit rate. However, I've never been able to pull today's actual financial cost across. When on a fixed tariff this would just be a simple calculation, but we are on Octopus Agile so I'm foxed as to how to calculate daily cost across each half-hourly tariff. It appears the simplest option would be to import 'Cost so far today' from the Glow, but it doesn't seem to be exposed as a sensor on MQTT/Home Assistant.

Is there some clever way to do this, that I'm just not familiar with, or does it all boil down to half-hourly calculations in Home Assistant every day?

Thanks!

I've got this setup and working really well however; I'd like to put the CAD on a separate network (I use this for most IoT devices). A firewall rule prevents communication between the normal and IoT LAN however; when I open up the two MQTT ports (1833 & 8883) the CAD cannot connect.

Looking at the logs, the CAD tries to call my MQTT broker but on some off ports (49500+).

Does anyone know if the CAD communicates on any other port to send the MQTT data beyond the standard MQTT ones?

I don't think this is a timing issue. I've just checked the total gas kWh for yesterday, as an example. Bright reports 10.8755 kWh. Home Assistant reports 10.66 kWh.

Can anyone suggest why this might be happening? I'm a novice in all this. Does Bright receive kWh from the smart meter, or is it converting to kWh from cu.m.? Might any conversion be the root cause of the differences?

I've received my T&H sensor, it's joined/bonded successfully. Hurrah!

I've added the config suggested by https://forum.glowmarkt.com/index.php?p=/discussion/345/mqtt-glow-cad-hildebrand-temperature-sensor using my Glow IHD MAC (as in use already for the Elec/Gas metering) & TH Sensor MAC (as displayed in the bonding screen on the IHD)

Can't see an obvious way to either check that the data is being transferred - or to display it... any help gratefully received.

I'm getting an MQTT feed but the Export data is 0. Is there anything special I need to do to get the Export figures? I'm on Octopus Agile Outgoing if that makes a difference.

Thanks

For example, taking the example from the announcement blog (https://medium.com/@joshua.cooper/glow-local-mqtt-f69b776b7af4), perhaps there could be a new sub-section for "money" under "import"?

glow/F1A8D1ED18E7/SENSOR/electricitymeter{
"electricitymeter": {
   "timestamp": "2022–06–01T16:32:16Z",
   "energy": {
     "export": {
       "cumulative": 0,
       "units": "kWh"
     },
     "import": {
       "cumulative": 201.95,
       "day": 1.05,
       "week": 0,
       "month": 0,
       "units": "kWh",
       "mpan": "9012224001407",
       "supplier": "— -",
       "price": {
         "unitrate": 0.20862,
         "standingcharge": 0.28403
       }
       "money": {
         "day": 0.50,
         "week": 1.22,
         "month": 10.83,
         "perhour": 0.07,
         "units": "GBP"
       }
     }
  },
  "power": {
    "value": 0.063,
    "units": "kW"
  } 
 }
}

It's more of a "nice-to-have" as the current data is sufficient to calculate these numbers downstream (as long as they have been recorded for the whole time period), but given that the Display/CAD is already calculating them it probably wouldn't take much to read them and add them to the Local MQTT message?

However, I'd like to take the MQTT feed directly into InfluxDB via Telegraf. I know I can feed it from HA into InfluxDB but I'd like to cut out HA from the loop if possible.

I can subscribe to the feed from the CLI but I can't make sense of how to parse the feed in Telegraf for input to Influxdb.

Has anyone done this and able to help?

I have been using the Glow API to get half hourly readings, but that has now failed and the data sits at 0.02 kWh all the time. I have a glow stick and can read the data live via the glow app on my phone so I now its getting the data from my meter.

2022-11-05 11:38:12: mosquitto version 2.0.11 starting
2022-11-05 11:38:12: Config loaded from /etc/mosquitto/mosquitto.conf.
2022-11-05 11:38:12: Loading plugin: /usr/share/mosquitto/go-auth.so
2022-11-05 11:38:12:  ├── Username/password checking enabled.
2022-11-05 11:38:12:  ├── TLS-PSK checking enabled.
2022-11-05 11:38:12:  └── Extended authentication not enabled.
2022-11-05 11:38:12: Opening ipv4 listen socket on port 1883.
2022-11-05 11:38:12: Opening ipv6 listen socket on port 1883.
2022-11-05 11:38:12: Opening websockets listen socket on port 1884.
2022-11-05 11:38:12: Connecting bridge (step 1) glowmqtt1 (glowmqtt.energyhive.com:8883)
2022-11-05 11:38:12: mosquitto version 2.0.11 running
2022-11-05 11:38:12: New connection from 127.0.0.1:43990 on port 1883.
2022-11-05 11:38:12: Client <unknown> closed its connection.
2022-11-05 11:38:12: Connecting bridge (step 2) glowmqtt1 (glowmqtt.energyhive.com:8883)
2022-11-05 11:38:12: Connection Refused: not authorised
2022-11-05 11:38:12: Client local.core-mosquitto.glowmqtt1 closed its connection.

I have added a Username and Password to Users in Home Assistant’s Settings -> People. The MQTT section of the CAD is set-up with my Bright App credentials, as I don’t have any others that I could put in those fields. The password is long at 20 characters but only contains upper case, lower names and numbers – no special characters. These credentials are also listed in my glow.conf file. The IP address is Home Assistant’s.

It is probably something simple I’ve missed but I feel I’m going round and round in circles. All help and comments appreciated.

{"electricitymeter":{"timestamp":"2022-10-28T11:08:05Z","energy":{<...>,"import":{"cumulative":14803.247,<...>,"power":{"value":0.080,"units":"kW"}}}

{"electricitymeter":{"timestamp":"2022-10-28T11:08:15Z","energy":{<...>,"import":{"cumulative":14803.247,<...>,"power":{"value":0.088,"units":"kW"}}}

{"electricitymeter":{"timestamp":"2022-10-28T11:08:15Z","energy":{<...>,"import":{"cumulative":14803.247,<...>,"power":{"value":0.088,"units":"kW"}}}

{"electricitymeter":{"timestamp":"2022-10-28T11:08:35Z","energy":{<...>,"import":{"cumulative":14803.248,<...>,"power":{"value":0.079,"units":"kW"}}}

Notice that instead of a new message being sent at 11:08:25, the 11:08:15 message is resent a second time at 11:08:25. Does anyone else have this issue? Note that if you don't parse the timestamp and just use the message arrival time this will hide the error, but you're using an invalid power reading for that duplicated timestamp.

I'm using mosquitto_sub to output these messages, so there's really nothing between the CAD and the printout that could be causing this error, seems to be a bug in the meter or CAD, depending on which one generates the timestamp?

I came across a post from Jane on one of the Home Assistant forums...

"do you all have L&G electricity meters? From speaking to L&G and Igloo we learnt there is a known bug on this meter which results in extremely low day/week/month consumption values, this is what you are seeing. The values are 1000 times lower than they should be which is why they seem to not appear at all.

L&G have advised that this is fixed in firmware version 38040202 or later - you can check your version in the Bright App (no idea if it is in the MQTT feed). You will need to ask your supplier to have your meter firmware updated; we recommend that you contact the Smart Meter Technical team.

We’ve had a few BG customers get very inaccurate replies from BG Customer Service - and are seeing if we can pursue this on your behalf via the DCC BG Account manager."

I seem to have this exact issue. Has anyone managed to contact British Gas and get their meter firmware updated? I'm sceptical about getting through to someone that will help and not sure I'll have the patience to resolve this :D

How is the firmware updated anyway, is it pushed down or does someone need to come out to my meter? I guess I'm asking if British Gas would eventually update the meter themselves, or if it is something I have to ask for.

One last question, why does the 'combined Glow in home display (IHD)' and Mobile App appear to show the correct data, but the MQTT values are wrong? are they using different data?

thanks

Tim

I am posting it below as it was not as easy to get working as the electricity and gas and it may help someone .

Message 0 received on glow/441793525A64/SENSOR/glowsensorth1/040D84282535 at 10:46:

{

   "glowsensorth1": {

       "040D84282535": {

           "timestamp": "2023-02-24T10:46:18Z",

           "temperature": {

               "value": 20.061,

               "units": "°C"

           },

           "humidity": {

               "value": 58,

               "units": "%"

           },

           "battery": {

               "value": 100,

               "units": "%"

           },

           "rssi": {

               "value": -79,

               "units": "dBm"

           }

       }

   }

}

Note the use of double and single quotes !!!!

mqtt.yaml

  - name: "Kitchen Humidity"

     state_topic: "glow/441793525A64/SENSOR/glowsensorth1/040D84282535"

     state_class: measurement

     unit_of_measurement: "%"

     unique_id: a11674d8abfe42a885b0d80b0f2de03b

     value_template: "{{ value_json['glowsensorth1']['040D84282535']['humidity']['value'] }}"

  - name: "Kitchen Temperature"

     state_topic: "glow/441793525A64/SENSOR/glowsensorth1/040D84282535"

     state_class: measurement

     unit_of_measurement: "C"

     unique_id: 36743e3ac47f49808606cdb2685a4b91

     value_template: "{{ value_json['glowsensorth1']['040D84282535']['temperature']['value'] }}"

On the CAD display, on the electricity pages, I can scroll through today's cost, today's usage and today's kgCO2 figure, but in the MQTT messages being output, the kgCO2 figure is missing. Is this being calculated internally, if so is there a formula? If it is being picked up directly from my meter, is it possible to have this value added to the MQTT feed?

I've been looking at getting glow data (via the API and MQT) into influxb. In order to make sure I understood the data properly, I started to compare data received via API vs. that received by MQTT vs. data shown on the Bright App.

I thought it would be useful to summarise some of the conclusions (apologies if I'm restating parts of other posts):-

1. I have found it MUCH easier to do everything in UTC, displaying in local time as required. If not, a very large rabbit hole awaits... All the comments below are based on the data being in UTC
2. Read the API docs carefully three times. Then read again. Then read again.
3. API data for different aggregation periods (daily, hourly, half-hourly, minute) is only self-consistent if the time stamp relates to the START of the relevant period. [ I think I noticed another post confirming this] ==> GOOD
4. Glow MQTT data (electricity consumption today) is consistent with API data:- e.g. I have P1D data for a given day == 17.326kWh vs last Glow MQTT reading for the day == 17.328 kWh ==> GOOD
5. I had a look at local MQ data last night - this was identical to Glow MQTT data for my sample ==> GOOD
6. The local MQTT timestamps and Glow MQTTs timestamp (for the same data) are not quite the same - for me there is a difference of 8s (glow = local + ~ 8s). Looks like either DCC or Glow are not using original timestamps on the Glow MQTT flow? ==> ODD..
7. The Bright App 30min / hour / day data is shown in LOCAL time (BST). The data for half hour / hour data is identical to the API data (after adjusting for timezone offset). Note that the "day" data will NOT be identical as the API summation is from midnight UTC to midnight UTC, whereas the App summation is from 23:00 UTC to 23:00 UTC . ==> GOOD - Expected Behaviour.
8. "Current Day" data on the App does NOT agree with Local MQTT / Glow MQTT "Consumption Today. I was expecting App (current Day) to be [MQTT (current day) + MQTT(last reading yesterday) - MQTT (23:00 yesterday)]. Not investigated this properly, but it looks like the App totals start aggregating at around 23:30 UTC, not 23:00 UTC. ==> BAD

Has anyone found anything that conflicts with the above?

Any idea what is happening re: point (8) in particular? I'd be interested to know what is going on re: (7) also [technical interest, really]

One last point: I like the new Local MQTT feed. It removes a few dependencies, makes it a whole lot simpler, plus makes pricing data available via MQTT. I'll probably continue with a mix of local MQTT + API as (i) I want historical data also.

Pete.

This happens a few times a day and messes up my graphs. It also breaks the graphs in the Bright app. I can just ignore these values so they don't get added to my local database, but was wondering what causes it.

Whenever one of these bad readings comes in, the cumulative import and export values are null when they are normally a number (even if it is 0.000). The signal from the meter seems ok, LQI is always between 240 and 248 and RSSI -38 or -39.

bad:

{"electricitymeter":{"timestamp":"2022-10-09T01:00:38Z","energy":{"export":{"cumulative":null,"units":"kWh"},"import":{"cumulative":null,"day":0.446,"week":31.237,"month":39.994,"units":"kWh","mpan":"MPAN SSWG","supplier":"---","price":{"unitrate":0.33020,"standingcharge":0.44120}}},"power":{"value":-8388.608,"units":"kW"}}}` from `glow/1234935253D4/SENSOR/electricitymeter

normal:

{"electricitymeter":{"timestamp":"2022-10-09T01:00:48Z","energy":{"export":{"cumulative":0.000,"units":"kWh"},"import":{"cumulative":8999.761,"day":0.450,"week":31.241,"month":39.998,"units":"kWh","mpan":"MPAN SSWG","supplier":"---","price":{"unitrate":0.33020,"standingcharge":0.44120}}},"power":{"value":0.194,"units":"kW"}}}` from `glow/1234935253D4/SENSOR/electricitymeter