Glow / Hildebrand Display - Local MQTT Access - Template Help

Hildebrand have just released new firmware for their Glow consumer access device (CAD) and display which provides local MQTT access to smart meter data:
Glow — Local MQTT

As a newbie I would appreciate assistance in coding the sensors via templates (value_template) in configuration.yaml

The MQTT output from the Glow device:-

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
       }
     }
  },
  "power": {
    "value": 0.063,
    "units": "kW"
  } 
 }
}

I am currently working on configuring this at my end and shifting away from the DCC integration.

Jane replied to one of my emails this morning and announced the new feature officially as I have seen it on the device yesterday. Thank you Jane for being awesome!

Will come back and update this post when I have news (and post as well)

UPDATE 15 JUN
Renamed unique_id for smart_meter_electricity_import_day and smart_meter_gas_import_day to _today. This is a breaking change and will need some manual cleanup. You will need to search for the old entity and delete it. And you will need to edit the new entity and remove _2 from the ID. Because the unique_id has changed this created a new entity altogether.

Also, I have updated the templates for Electricity Import (Today) and Gas Import (Today). This is because in some cases the meter would report a value of 0. This will then reset the cost, and in some cases it could happen at a bad time of the day and mess up the costs in the Energy dashboard. The new template will check if the value is 0 and the current time is past 00:01, and use previous value, otherwise just use the new value.

UPDATE 10 Jun 23PM
Undone this for now, will check tomorrow with a fresh pair of eyes
Updated the entities smart_meter_electricity_import and smart_meter_gas_import again comparing them to previous value. If they are less, the value is skipped. This is in an attempt to avoid issues with Energy dashboard counting much more used energy than in reality.

Note: If for any reason your meter reports a big increase at random, this change will not update your entities even if the new value (lower) is actually correct. If your meter has this behaviour, change the template to == 0 instead of < entity

UPDATE 10 Jun

No code changes. Just added some Bonus Content at the end of this post with my Lovelace setup for Energy monitoring.

UPDATE 8 Jun 14PM
Updated the device_class of smart_meter_electricity_power and smart_meter_gas_power as I have erroneously set it to energy instead of power

UPDATE 8 Jun 12PM

Updated the entities smart_meter_electricity_import and smart_meter_gas_import in order to overcome 0 values. Yesterday the mqtt feed received a value of 0 twice in a row from the Gas Import which basically added aprox 35,000kwh on my gas consumption for that 30 min interval in the Energy dashboard. That is because my current meter reading is a bit over 17,000.

To avoid, i have templated the value to be the previous one only if the received value is 0. So the entity will be stagnant rather than reset.

UPDATE 7 Jun 14:30PM

Updated Gas icons to fire. I forgot to change them when duplicating from Electricity

UPDATE 7 Jun 14PM

I have removed the word Energy from the entities names and ids. The below has been updated so just follow the instructions. If you have set it up before this update, and you decide to update too, make sure to remove the old entities and update your energy configuration.

INSTRUCTIONS

Start by setting up your MQTT details on the IHD (there is no need for Hildebrand to enable MQTT at their end). My software version is v1.8.12. As this is a new feature, I would expect that some of you might not see the configuration until the device updates. The settings steps can be seen in the video on this article Glow — Local MQTT. Here at last … free upgrade in version… | by Joshua Cooper | Jun, 2022 | Medium

Create the following entities in Home Assistant. Please make sure to use the correct device ID and replace the word REDACTED with it. The ID is the device MAC without the colons, can be found either on the IHD or on the Bright app under Devices.

mqtt:
  sensor:  
    - name: "Smart Meter Electricity: Export"
      unique_id: "smart_meter_electricity_export"
      state_topic: "glow/REDACTED/SENSOR/electricitymeter"
      device_class: "energy"
      unit_of_measurement: "kWh"
      state_class: "total_increasing"
      value_template: "{{ value_json['electricitymeter']['energy']['export']['cumulative'] }}"
      icon: "mdi:flash"
    - name: "Smart Meter Electricity: Import"
      unique_id: "smart_meter_electricity_import"
      state_topic: "glow/REDACTED/SENSOR/electricitymeter"
      device_class: "energy"
      unit_of_measurement: "kWh"
      state_class: "total_increasing"
      value_template: >
        {% if value_json['electricitymeter']['energy']['import']['cumulative'] == 0 %}
          {{ states('sensor.smart_meter_electricity_import') }}
        {% else %}
          {{ value_json['electricitymeter']['energy']['import']['cumulative'] }}
        {% endif %}
      icon: "mdi:flash"
    - name: "Smart Meter Electricity: Import (Today)"
      unique_id: "smart_meter_electricity_import_today"
      state_topic: "glow/REDACTED/SENSOR/electricitymeter"
      device_class: "energy"
      unit_of_measurement: "kWh"
      state_class: "measurement"
      value_template: >
        {% if value_json['electricitymeter']['energy']['import']['day'] == 0 
          and now() > now().replace(hour=0).replace(minute=1).replace(second=0).replace(microsecond=0) %}
          {{ states('sensor.smart_meter_electricity_import_today') }}
        {% else %}
          {{ value_json['electricitymeter']['energy']['import']['day'] }}
        {% endif %}
      icon: "mdi:flash"
    - name: "Smart Meter Electricity: Import (This week)"
      unique_id: "smart_meter_electricity_import_week"
      state_topic: "glow/REDACTED/SENSOR/electricitymeter"
      device_class: "energy"
      unit_of_measurement: "kWh"
      state_class: "measurement"
      value_template: "{{ value_json['electricitymeter']['energy']['import']['week'] }}"
      icon: "mdi:flash"
    - name: "Smart Meter Electricity: Import (This month)"
      unique_id: "smart_meter_electricity_import_month"
      state_topic: "glow/REDACTED/SENSOR/electricitymeter"
      device_class: "energy"
      unit_of_measurement: "kWh"
      state_class: "measurement"
      value_template: "{{ value_json['electricitymeter']['energy']['import']['month'] }}"
      icon: "mdi:flash"
    - name: "Smart Meter Electricity: Import Unit Rate"
      unique_id: "smart_meter_electricity_import_unit_rate"
      state_topic: "glow/REDACTED/SENSOR/electricitymeter"
      device_class: "monetary"
      unit_of_measurement: "GBP/kWh"
      state_class: "measurement"
      value_template: "{{ value_json['electricitymeter']['energy']['import']['price']['unitrate'] }}"
      icon: "mdi:cash"
    - name: "Smart Meter Electricity: Import Standing Charge"
      unique_id: "smart_meter_electricity_import_standing_charge"
      state_topic: "glow/REDACTED/SENSOR/electricitymeter"
      device_class: "monetary"
      unit_of_measurement: "GBP"
      state_class: "measurement"
      value_template: "{{ value_json['electricitymeter']['energy']['import']['price']['standingcharge'] }}"
      icon: "mdi:cash"
    - name: "Smart Meter Electricity: Power"
      unique_id: "smart_meter_electricity_power"
      state_topic: "glow/REDACTED/SENSOR/electricitymeter"
      device_class: "power"
      unit_of_measurement: "kW"
      state_class: "measurement"
      value_template: "{{ value_json['electricitymeter']['power']['value'] }}"
      icon: "mdi:flash"
    - name: "Smart Meter Gas: Import"
      unique_id: "smart_meter_gas_import"
      state_topic: "glow/REDACTED/SENSOR/gasmeter"
      device_class: "energy"
      unit_of_measurement: "kWh"
      state_class: "total_increasing"
      value_template: >
        {% if value_json['gasmeter']['energy']['import']['cumulative'] == 0 %}
          {{ states('sensor.smart_meter_gas_import') }}
        {% else %}
          {{ value_json['gasmeter']['energy']['import']['cumulative'] }}
        {% endif %}
      icon: "mdi:fire"
    - name: "Smart Meter Gas: Import (Today)"
      unique_id: "smart_meter_gas_import_today"
      state_topic: "glow/REDACTED/SENSOR/gasmeter"
      device_class: "energy"
      unit_of_measurement: "kWh"
      state_class: "measurement"
      value_template: >
        {% if value_json['gasmeter']['energy']['import']['day'] == 0 
          and now() > now().replace(hour=0).replace(minute=1).replace(second=0).replace(microsecond=0) %}
          {{ states('sensor.smart_meter_gas_import_today') }}
        {% else %}
          {{ value_json['gasmeter']['energy']['import']['day'] }}
        {% endif %}
      icon: "mdi:fire"
    - name: "Smart Meter Gas: Import (This week)"
      unique_id: "smart_meter_gas_import_week"
      state_topic: "glow/REDACTED/SENSOR/gasmeter"
      device_class: "energy"
      unit_of_measurement: "kWh"
      state_class: "measurement"
      value_template: "{{ value_json['gasmeter']['energy']['import']['week'] }}"
      icon: "mdi:fire"
    - name: "Smart Meter Gas: Import (This month)"
      unique_id: "smart_meter_gas_import_month"
      state_topic: "glow/REDACTED/SENSOR/gasmeter"
      device_class: "energy"
      unit_of_measurement: "kWh"
      state_class: "measurement"
      value_template: "{{ value_json['gasmeter']['energy']['import']['month'] }}"
      icon: "mdi:fire"
    - name: "Smart Meter Gas: Import Unit Rate"
      unique_id: "smart_meter_gas_import_unit_rate"
      state_topic: "glow/REDACTED/SENSOR/gasmeter"
      device_class: "monetary"
      unit_of_measurement: "GBP/kWh"
      state_class: "measurement"
      value_template: "{{ value_json['gasmeter']['energy']['import']['price']['unitrate'] }}"
      icon: "mdi:cash"
    - name: "Smart Meter Gas: Import Standing Charge"
      unique_id: "smart_meter_gas_import_standing_charge"
      state_topic: "glow/REDACTED/SENSOR/gasmeter"
      device_class: "monetary"
      unit_of_measurement: "GBP"
      state_class: "measurement"
      value_template: "{{ value_json['gasmeter']['energy']['import']['price']['standingcharge'] }}"
      icon: "mdi:cash"
    - name: "Smart Meter Gas: Power"
      unique_id: "smart_meter_gas_power"
      state_topic: "glow/REDACTED/SENSOR/gasmeter"
      device_class: "power"
      unit_of_measurement: "kW"
      state_class: "measurement"
      value_template: "{{ value_json['gasmeter']['power']['value'] }}"
      icon: "mdi:fire"

This will bring in all the entities that are relevant to our use.

On top, we need to create 2 entities that track today’s costs for each of the energy type. They are not included in MQTT so we will need to create the templates and do the calculations ourselves:

template:
  sensor:
    - name: "Smart Meter Electricity: Cost (Today)"
    unique_id: smart_meter_electricity_cost_today
    device_class: monetary
    unit_of_measurement: "GBP"
    state_class: "total_increasing"
    icon: mdi:cash
    state: "{{ (
        states('sensor.smart_meter_electricity_import_today') | float 
        * states('sensor.smart_meter_electricity_import_unit_rate') | float 
        + states('sensor.smart_meter_electricity_import_standing_charge') | float
      ) | round(2) }}"
  - name: "Smart Meter Gas: Cost (Today)"
    unique_id: smart_meter_gas_cost_today
    device_class: monetary
    unit_of_measurement: "GBP"
    state_class: "total_increasing"
    icon: mdi:cash
    state: "{{ (
        states('sensor.smart_meter_gas_import_today') | float 
        * states('sensor.smart_meter_gas_import_unit_rate') | float 
        + states('sensor.smart_meter_gas_import_standing_charge') | float
      ) | round(2) }}"

Reload your HA config (manually configures mqtt and templates) or restart HA for the entities to become available. You should now have 17 new entities.

Due to limitations on how HA works, these cannot be grouped in devices in their current form. That is because we are not doing MQTT Discovery not are we creating these devices via an Integration. I am considering looking into a custom HACS integration, but I do not have much experience with it so it will be a learning curve for me.

For anyone used to using the DCC integration, these numbers match those ones but they are updated much more frequently, around 6 seconds, as soon as the IHD pushes in an update. No more cloud need, and for anyone using the old MQTT integration, no more need to run DCC integration in parallel just to get the unit price and standing prices (and costs) - However we owe terrible respect to the people that are working on that helping people that do not have the IHD :slight_smile:

Now onto the HA Energy side of things. The entities we need to use are as follow:
Smart Meter Electricity: Import
Use an entity tracking the total costs: Smart Meter Electricity: Cost (Today)
image

Smart Meter Gas: Import
Use an entity tracking the total costs: Smart Meter Gas: Cost (Today)
image

And that should be it :slight_smile:

As these are long term statistics, despite the entities providing you values (like the total of Import), the Energy dashboard will not show historical data, not even for the day. The stats will be populated from the moment you create your entities. As the statistics get populated everything should look as expected.

If anyone has any info to save me some research time about custom HACS integrations, that would be great. For any other help, please @ me in this thread.

Hope this helps!

PS: I have chosen to exclude information about Gas Export because it is highly unlikely any of us exports gas into the grid :slight_smile: but also information about the IHD status, the HAN network or the serial numbers of the meters. The full MQTT topic is at the end of this post, and if anyone needs help setting up extra entities let me know.

PPS: I do not (yet) have solar panels so I can’t quite help in terms of export information aside from making that entity available. I would expect you guys to have 3rd party software (enphase, tesla etc) handling that part of the process and integration that way?

Full MQTT available messages. Redacted for privacy:

glow/REDACTED/STATE{
   "software":"v1.8.12",
   "timestamp":"2022-06-07T10:04:58Z",
   "hardware":"GLOW-IHD-01-1v4-SMETS2",
   "ethmac":"REDACTED",
   "smetsversion":"SMETS2",
   "eui":"REDACTED",
   "zigbee":"1.2.5",
   "han":{
      "rssi":-52,
      "status":"joined",
      "lqi":192
   }
}

glow/REDACTED/SENSOR/electricitymeter{
   "electricitymeter":{
      "timestamp":"2022-06-07T10:05:22Z",
      "energy":{
         "export":{
            "cumulative":0.000,
            "units":"kWh"
         },
         "import":{
            "cumulative":4626.900,
            "day":2.885,
            "week":12.718,
            "month":59.715,
            "units":"kWh",
            "mpan":"REDACTED",
            "supplier":"REDACTED",
            "price":{
               "unitrate":0.19880,
               "standingcharge":0.23760
            }
         }
      },
      "power":{
         "value":0.429,
         "units":"kW"
      }
   }
}

glow/REDACTED/SENSOR/gasmeter{
   "gasmeter":{
      "timestamp":"2022-06-07T10:05:36Z",
      "energy":{
         "export":{
            "cumulative":0.000,
            "units":"kWh"
         },
         "import":{
            "cumulative":17257.783,
            "day":0.489,
            "week":34.503,
            "month":65.038,
            "units":"kWh",
            "mprn":"REDACTED",
            "supplier":"REDACTED",
            "price":{
               "unitrate":0.04650,
               "standingcharge":0.26590
            }
         }
      },
      "power":{
         "value":0.000,
         "units":"kW"
      }
   }
}

Bonus Content

Did you know you can replicate the Energy dashboard in Lovelace, and then include your own other entities, allowing you to hide it from the sidebar and just use your Lovelace?

Find below my setup, with the only mention that I am using custom layout card. You can probably change to adapt it to your liking, but hopefully it inspired some of you.

  - title: ''
    path: energy
    icon: mdi:flash
    type: custom:grid-layout
    layout:
      grid-template-columns: 1fr 1fr 1fr
      grid-template-areas: |
        "date date date"
        "graphs graphs graphs"
        "sources sources distribution"
        "entities entities entities"
      mediaquery:
        '(max-width: 900px)':
          grid-template-columns: 100%
          grid-template-areas: |
            "date"
            "graphs"
            "sources"
            "distribution"
            "entities"
    badges: []
    cards:
      - type: energy-date-selection
        view_layout:
          grid-area: date
      - type: custom:layout-card
        layout_type: grid
        layout:
          margin: 0 -4px
          grid-template-columns: 1fr 1fr
          grid-template-rows: auto
          mediaquery:
            '(max-width: 900px)':
              grid-template-columns: 1fr
        cards:
          - type: energy-usage-graph
            title: Electricity usage
          - type: energy-gas-graph
            title: Gas usage
        view_layout:
          grid-area: graphs
      - type: energy-sources-table
        title: Sources
        view_layout:
          grid-area: sources
      - type: energy-distribution
        title: Energy distribution
        card_mod:
          style: |
            ha-card {
              height: 100%;
            }
        view_layout:
          grid-area: distribution
      - type: custom:layout-card
        layout_type: grid
        layout:
          margin: 0 -4px
          grid-template-columns: 1fr 1fr
          grid-template-rows: auto
          mediaquery:
            '(max-width: 900px)':
              grid-template-columns: 1fr
        cards:
          - type: entities
            entities:
              - entity: sensor.smart_meter_electricity_import_today
                name: Import (Today)
              - entity: sensor.smart_meter_electricity_cost_today
                name: Cost (Today)
              - entity: sensor.smart_meter_electricity_import
                name: Import
              - entity: sensor.smart_meter_electricity_import_this_week
                name: Import (This week)
              - entity: sensor.smart_meter_electricity_import_this_month
                name: Import (This month)
              - entity: sensor.smart_meter_electricity_import_unit_rate
                name: Import Unit Rate
              - entity: sensor.smart_meter_electricity_import_standing_charge
                name: Import Standing Charge
            title: Electricity
          - type: entities
            entities:
              - entity: sensor.smart_meter_gas_import_today
                name: Import (Today)
              - entity: sensor.smart_meter_gas_cost_today
                name: Cost (Today)
              - entity: sensor.smart_meter_gas_import
                name: Import
              - entity: sensor.smart_meter_gas_import_this_week
                name: Import (This week)
              - entity: sensor.smart_meter_gas_import_this_month
                name: Import (This month)
              - entity: sensor.smart_meter_gas_import_unit_rate
                name: Import Unit Rate
              - entity: sensor.smart_meter_gas_import_standing_charge
                name: Import Standing Charge
            title: Gas
        view_layout:
          grid-area: entities
11 Likes

Update above :slight_smile:

Although I currently use a combination of EM clamps and Glow cloud, I have been waiting for their non-display device in order to get local MQTT, so I really appreciate the time and effort put in to this post and have bookmarked it as my go to as and when I can get the new interface and plan to ditch the EM clamps. :+1:

You are welcome @rossk

Just to confirm, this is using the IHD (with display) and is a brand new feature. Given this information (but i have no inside knowledge) I do not think Hildebrand will launch the non-display local mqtt only device (is there any need at this point?). My understanding was that they were building that device in house, and they didn’t think they will add local mqtt to the Display version because of the size of the firmware stack. Now given that this was overcome, maybe they won’t continue with a build for a product that would have cost the end user the same, plus with the IHD you get a display for a quick “interactive” session.

Maybe I am wrong, but with the current situation, if I had to choose between local mqtt from IHD or new device, I would personally choose the IHD, cause it is classy, but also feels “old school” - e.g. parent friendly, anyone understands it, and the mqtt is just a “geek” bonus :slight_smile:

2 Likes

Good to know as well, may just order the CAD then now that it has local MQTT as that was the only reason I was hanging fire on it.

1 Like

@robertalexa
That’s awesome Robert :clap:
Many thanks for the templates and for documenting the process so clearly.
That’s exactly what I was looking for :+1:

1 Like

This is awesome - especially when I just bought the unit to realise the integration had been archived!

Ok really stupid question - when you say ‘Create the following entities in Home Assistant.’ How do I do this? Have tried creating through UI, but it doesn’t recognise the YAML code in card configuration. Do I create this in configuration.yaml?

Sorry for the silly question!

This is great work and helped me fix my older “remote” MQTT sensors. The only issue I have is that the cumulative gas reading is in kWh and not m3 therefore the current meter reading, which I record weekly in a meter app, is wrong. It could be converted but would never exactly match the live meter reading. I have to keep the remote mqtt sensor just for this reading for now, unless Hildebrand add that to their local mqtt feed.

@alphabeta279 Generally I create all my entities via the configuration.yaml, I think some of the entity types can nowadays be created via the UI, but meh.

If you do not have any other template or mqtt entities created previously, you can just copy that in as is. Otherwise, you will need to merge with your existing ones, so only copy the individual entities in your existing setup e.g.

    - name: "Smart Meter Electricity: Export"
      unique_id: "smart_meter_electricity_export"
      state_topic: "glow/REDACTED/SENSOR/electricitymeter"
      device_class: "energy"
      unit_of_measurement: "kWh"
      state_class: "total_increasing"
      value_template: "{{ value_json['electricitymeter']['energy']['export']['cumulative'] }}"
      icon: "mdi:flash"

@BertrumUK Hey Neil, unfortunately this is a limitation of the MQTT feed, I have exposed exactly what the feed makes available.

However, you can still do that, with a bit of research from your supplier bill. You could create extra template entities that convert from the local mqtt ones into m3.

The formula is m3 × Calorific Value × 1.02264 ÷ 3.6 = kWh and you can get the calorific value specific to your supply from your bill. As a proof of concept, you can try to use the Import entity value (cumulative = current meter reading), convert it to m3 and compare to the reading on your meter. Hope this helps you achieve your desired result. Happy to help if you need me

I’ve posted the request on their forum page, will give your formula a go in NR and compare it to the live readings I have.

Great work on your post BTW :grinning:

1 Like

Just updated my post in an attempt to avoid a possible issue with the Cumulative Import. Explanation can be found in the post at the top. Code is already updated.

Another update to the post fixing the device class for smart_meter_electricity_power and smart_meter_gas_power. More details in the post

Perfect - thank you, will give it a shot tonight then, should be relatively simple (apart from my lifelong mission to slap the person who invented yaml, hate the daft indents with a passion!)

I’d really like to get the IHD to take advantage of the local MQTT, however before I take the plunge I wondered whether the MQTT feed includes the running cost in £ for the day? I am on the octopus Smart EV tariff where the kwh rate changes at night, so if this isn’t included in the feed, how would I calculate the running cost? Cheers.

I am experiencing occasional (approx 1 - 2 per day) huge negative spikes in the local MQTT electricity power readings. Since I don’t have solar Jane from Hildebrand thinks the readings might be the result of a sporadic issue with my electricity meter (SMETS1). I will chase the energy supplier (ScottishPower) but I suspect that they won’t be interested unless it starts to impact their ability to remotely read the meter.

Unfortunately because of the magnitude these negative spikes are completely masking all the other readings:
Screenshot 2022-06-09 145642
Interestingly the negative spikes appear to be all the same value (-8,388.61 kW).

Naturally it would be best to resolve the spurious readings ‘at source’ but in the meantime I would appreciate any thoughts on how to avoid logging them in HA?

Hey @JohnWH

Have a look at the entities above, in particular the Import ones, and notice how I have done a template to avoid saving the value if it is == to 0.

I would suggest you do sth similar for the power entities. So if the value is less than 0 than use the previous value instead. It is a bit hacky, but it will keep you much closer to the truth than your current ituation. Here is the value_template for the power entity:

value_template: >
  {% if value_json['electricitymeter']['power']['value'] < 0 %}
    {{ states('sensor.smart_meter_electricity_power') }}
  {% else %}
    {{ value_json['electricitymeter']['power']['value'] }}
  {% endif %}

@saltinesurfer the IHD does not provide a running cost in the feed, this is something i had to calculate manually via the template entities from the unit rates, standing charge and unit total. I do not have a dual tariff, and I can’t guarantee the IHD will provide that. Best bet is to email Hildebrand, Jane is lovely and she will be able to advise. If the IHD provides extra information for people on dual tariff, then I am sure we can make it work somehow. e.g. if we know the unit price, and the time interval, we can achieve that (i think). Might actually be able to do that manually as a test by hardcoding the the unit prices. Unfortunately I am due to going away for the next 4 weeks, so I won’t be around to help.

1 Like

@robertalexa im not getting any data in HA? but im also getting an error in my energy dashboard settings

ELEC: Last Reset missing - the following entities have state class ‘measurement’ but ‘last_reset’ is missing: sensor.smart_meter_electricity_import_today

GAS: Last Reset missing - the following entities have state class ‘measurement’ but ‘last_reset’ is missing: sensor.smart_meter_gas_import_today

Are the entities that you have created been populated with values (the entities, not the Energy dashboard).

If not, start by checking that your IHD is sending data to MQTT and the topic it is doing it on. By default on the IHD the topic is glow. You can see that in the entities as well. If you have changed that, make sure to update the topics for the entities.

Also, make sure you have replaced the word REDACTED with the actual Device ID for your IHD.

Let me know how that goes.

PS: there is a tool called MQTT Explorer that you can use to check what topics and messages are received by your MQTT server. This way you can confirm seeing traffic and on what topics.

Hi @robertalexa
That’s an excellent suggestion.

I’ve substituted the code (above) into my configuration file. Minor point if anyone else uses it - the 5th line should read ‘electricitymeter’ not ‘electricity’

As a newbie (especially to templating) your help has been so invaluable - thank you very much!
Safe travels.

1 Like