Home Assistant integration for energy consumption data from UK SMETS (Smart) meters using the Hildebrand Glow API.

Aniket

Last update: Dec 30, 2022

Related tags

Hardware energy gas home-assistant smart-meter electricity uk smartmeter energy-consumption electricity-consumption glow smart-meters smets smets2 hildebrand

Overview

Hildebrand Glow (DCC) Integration

Home Assistant integration for energy consumption data from UK SMETS (Smart) meters using the Hildebrand Glow API.

This integration works without requiring a consumer device provided by Hildebrand Glow and can work with your existing smart meter. You'll need to set up your smart meter for free in the Bright app on Android or iOS. This will only work when using the Data Communications Company (DCC) backend, which all SMETS 2 meters and some SMETS 1 meters do (more information). Once you can see your data in the app, you are good to go.

The data provided will be delayed by around 30 minutes. To get real-time consumption data, you can buy Hildebrand Glow hardware. Although this integration will work with their hardware, you should use the MQTT version here to get real-time consumption data.

This integration will currently emit one sensor for the daily usage of each detected smart meter.

Installation

Automated installation through HACS

You can install this component through HACS and receive automatic updates.

After installing HACS, visit the HACS Integrations pane and add https://github.com/HandyHat/ha-hildebrandglow-dcc as an Integration by following these instructions. You'll then be able to install it through the Integrations pane.

Manual installation

Copy the custom_components/hildebrandglow_dcc/ directory and all of its files to your config/custom_components directory. You'll then need to restart Home Assistant for it to detect the new integration.

Configuration

Visit the Integrations section within Home Assistant's Configuration panel and click the Add button in the bottom right corner. After searching for "Hildebrand Glow", you'll be asked for your Glow credentials.

Once you've authenticated, the integration will automatically set up a sensor for each of the smart meters on your account.

Debugging

To debug the integration, add the following to your configuration.yaml

logger:
  default: warning
  logs:
    custom_components.hildebrandglow_dcc: debug

Development

To begin, it is recommended to create a virtual environment to install dependencies:

python -m venv dev-venv
. dev-venv\Scripts\activate

You can then install the dependencies that will allow you to develop: pip3 install -r requirements-dev.txt

This will install homeassistant, autopep8, isort and pylint.

Code Style

This project makes use of isort, pylint and autopep8 to enforce a consistent code style across the codebase.

Credits

Thanks to the original project from which this project is forked, and to this python library for helping me troubleshoot.

Comments

list index out of range error

Describe the bug

2021-10-26 14:31:07 ERROR (MainThread) [custom_components.hildebrandglow_dcc.sensor] Key Error - plan (list index out of range): ({'status': 'OK', 'name': 'gas consumption', 're
sourceTypeId': '08ab415f-d851-423f-adf4-c2b1e0529e27', 'resourceId': 'b1f5af6e-3507-453c-ab8f-66ff9606b7de', 'data': [], 'classifier': 'gas.consumption'})
2021-10-26 14:31:08 ERROR (MainThread) [custom_components.hildebrandglow_dcc.sensor] Lookup Error - plan (list index out of range): ({'status': 'OK', 'name': 'gas consumption',
'resourceTypeId': '08ab415f-d851-423f-adf4-c2b1e0529e27', 'resourceId': 'b1f5af6e-3507-453c-ab8f-66ff9606b7de', 'data': [], 'classifier': 'gas.consumption'})

To Reproduce only added in my bright iOS details (im a british gas customer with a smart elec/gas/monitor all DCC with no glow hub)

Expected behaviour not sure?

Screenshots If applicable, add screenshots to help explain your problem.

Version LATEST - v0.5.0 and HA core-2021.10.6

Debug log Enable debug logging by following the instructions here TO FOLLOW

Additional context i think this error is because british gas have goofed up my gas tariff, so its showing in HA AND the bright iOS app as NO TRARIFF and its not calculating the cost either

bug

opened by si458 27

fix home assistant complaining GBP/kWH is an invalid currency
Description

fix home assistant complaining GBP/kWH is an invalid currency

Motivation and Context

How Has This Been Tested?

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)

[ ] New feature (non-breaking change which adds functionality)

[ ] Breaking change (fix or feature that would cause existing functionality to change)
opened by si458 24

Entities not available

Describe the bug all my entities are showing as unavailable however all data is available in the app - I've readded the integration and was able to login without issue however the problem remains.

To Reproduce Steps to reproduce the behaviour:

setup integration

Expected behaviour entities should be available

Screenshots

Version 6.0 2022.6.7

Debug log

2022-06-28 08:54:58 DEBUG (SyncWorker_2) [custom_components.hildebrandglow_dcc.glow] get 1: (https://api.glowmarkt.com/api/v0-1/resource)
2022-06-28 08:56:55 DEBUG (SyncWorker_7) [custom_components.hildebrandglow_dcc.glow] Post 1: (https://api.glowmarkt.com/api/v0-1/auth)
2022-06-28 08:56:55 DEBUG (SyncWorker_7) [custom_components.hildebrandglow_dcc.glow] Invalid data: {'valid': False}
2022-06-28 08:57:02 DEBUG (SyncWorker_8) [custom_components.hildebrandglow_dcc.glow] Post 1: (https://api.glowmarkt.com/api/v0-1/auth)
2022-06-28 08:57:02 DEBUG (SyncWorker_2) [custom_components.hildebrandglow_dcc.glow] get 1: (https://api.glowmarkt.com/api/v0-1/resource)

bug

opened by tungmeister 22

No longer working?

Describe the bug The integration seems to no longer be connecting to the Glow API to retrieve data - it just errors in the HA log file.

Is it just me?

Version Glow - v0.5.0 HA - 2022.2.0 and 2021.12.x

Debug log Debug logging enabled, but no additional error messages shown other than:

2022-02-03 09:42:38 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hildebrandglow_dcc which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-02-03 09:43:13 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform hildebrandglow_dcc is taking over 10 seconds.
2022-02-03 09:49:51 WARNING (SyncWorker_1) [custom_components.hildebrandglow_dcc.glow] Error connecting to Glow ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2022-02-03 09:49:51 WARNING (SyncWorker_9) [custom_components.hildebrandglow_dcc.glow] Error connecting to Glow ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2022-02-03 09:49:51 WARNING (SyncWorker_5) [custom_components.hildebrandglow_dcc.glow] Error connecting to Glow ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2022-02-03 09:49:51 WARNING (SyncWorker_6) [custom_components.hildebrandglow_dcc.glow] Error connecting to Glow ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2022-02-03 09:49:51 WARNING (SyncWorker_8) [custom_components.hildebrandglow_dcc.glow] Error connecting to Glow ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))

bug

opened by derekoharrow 22

1000s of DNS lookups to api.glowmarkt.com

I use Pi-hole (see https://pi-hole.net/) on my LAN to filter out excessive internet adverts and also as my DHCP & DNS lookup server.

Sometime after installing this integration, I noticed many 1000's of DNS lookups to api.glowmarkt.com in my Pi-hole dashboard. There are 30+ lookups every 1second.

To see these lookups, you would need to setup Pi-hole or some other network device to receive & forward DNS queries. I have attached a screenshot.

Surely 30+ DNS lookups every 1 second is unnecessary and presumably not good for LAN, ISP or Hildebrand servers!?

Home Assistant v2021.10.6 Hildebrand Glow (DCC) integration v0.5.0

bug

opened by smithbill17 22
Stopped pulling data from Glow after switch to GMT

Describe the bug After the switch to GMT, the sensors have stopping pulling data from the Glow API, showing a data value of "0"

To Reproduce Run the integration in the GMT timezone (UTC offset = 0)

Expected behaviour Should retrieve data

Version 5.0

Debug log Logs who the Glow API call fails.
bug

opened by ColinRobbins 18
Keep getting Error in Logs

This is a constant error i get on every reboot of HA.

Version | core-2021.12.9 -- | -- Installation Type | Home Assistant OS Development | false Supervisor | true Docker | true User | root Virtual Environment | false Python Version | 3.9.7 Operating System Family | Linux Operating System Version | 5.10.88 CPU Architecture | x86_64 Timezone | Europe/London
Glow API data error (Electric Tariff Rate): (list index out of range) 09:48:31 – (ERROR) Hildebrand Glow (DCC) (custom integration) - message first occurred at 09:48:31 and shows up 2 times Glow API data error (Electric Tariff Standing): (list index out of range) 09:46:31 – (ERROR) Hildebrand Glow (DCC) (custom integration) - message first occurred at 09:46:31 and shows up 2 times bug

opened by thorrrr 17
Energy Data no longer showing after 10 Oct after latest update

The problem Energy Data no longer showing after 10 Oct after latest update. I could see it yesterday but after update 2022.10.3 it is missing and nothing is recording today? Home Assistant 2022.10.3 Supervisor 2022.10.0 Operating System 9.0 Frontend 20221010.0 - latest

What version of Home Assistant Core has the issue? 2022.10.3

What was the last working version of Home Assistant Core? 2022.10.2

What type of installation are you running? Home Assistant Supervised

Debug log Enable debug logging by following the instructions here

Additional context Add any other context about the problem here. This error originated from a custom integration.

Logger: custom_components.hildebrandglow_dcc.glow Source: custom_components/hildebrandglow_dcc/glow.py:194 Integration: Hildebrand Glow (DCC) (documentation, issues) First occurred: 08:35:57 (1 occurrences) Last logged: 08:35:57

Glow response status code: 500 (https://api.glowmarkt.com/api/v0-1/resource/0328f32a-09c1-4769-8ffa-889d9313f86b/tariff)

Logger: homeassistant.helpers.entity Source: helpers/entity.py:515 First occurred: 08:35:55 (3 occurrences) Last logged: 09:00:55

Update of sensor.gas_tariff_standing is taking over 10 seconds Update of sensor.electric_tariff_standing is taking over 10 seconds
bug

opened by thorrrr 16

Update sensor to only query Glow API shortly after 0 and 30 mins past the hour

This is to address Glow's concerns referenced in https://github.com/HandyHat/ha-hildebrandglow-dcc/issues/126

There's probably a better way to do this, but it seems to work. I'm new to HA development so finding my feet a little.

This does cause HA to complain that the sensor update is taking over 10s, but doesn't seem to be a problem

Feb 08 18:30:00 HA 62d3ea2a38d1[1066]: 2022-02-08 18:30:00 DEBUG (MainThread) [custom_components.hildebrandglow_dcc.sensor] Update time, sleeping 22 before talking to API
Feb 08 18:30:00 HA 62d3ea2a38d1[1066]: 2022-02-08 18:30:00 DEBUG (MainThread) [custom_components.hildebrandglow_dcc.sensor] Update time, sleeping 30 before talking to API
Feb 08 18:30:00 HA 62d3ea2a38d1[1066]: 2022-02-08 18:30:00 DEBUG (MainThread) [custom_components.hildebrandglow_dcc.sensor] Update time, sleeping 77 before talking to API
Feb 08 18:30:00 HA 62d3ea2a38d1[1066]: 2022-02-08 18:30:00 DEBUG (MainThread) [custom_components.hildebrandglow_dcc.sensor] Update time, sleeping 2 before talking to API
Feb 08 18:30:00 HA 62d3ea2a38d1[1066]: 2022-02-08 18:30:00 DEBUG (MainThread) [custom_components.hildebrandglow_dcc.sensor] Update time, sleeping 7 before talking to API
Feb 08 18:30:00 HA 62d3ea2a38d1[1066]: 2022-02-08 18:30:00 DEBUG (MainThread) [custom_components.hildebrandglow_dcc.sensor] Update time, sleeping 15 before talking to API
Feb 08 18:30:00 HA 62d3ea2a38d1[1066]: 2022-02-08 18:30:00 DEBUG (MainThread) [custom_components.hildebrandglow_dcc.sensor] Update time, sleeping 21 before talking to API
Feb 08 18:30:00 HA 62d3ea2a38d1[1066]: 2022-02-08 18:30:00 DEBUG (MainThread) [custom_components.hildebrandglow_dcc.sensor] Update time, sleeping 39 before talking to API
Feb 08 18:30:02 HA 62d3ea2a38d1[1066]: 2022-02-08 18:30:02 DEBUG (SyncWorker_1) [custom_components.hildebrandglow_dcc.glow] get 2: (https://api.glowmarkt.com/api/v0-1/resource/XXXX/readings?from=2022-02-08T00:00:00&to=2022-02-08T23:59:59&period=P1D&offset=0&function=sum)
Feb 08 18:30:07 HA 62d3ea2a38d1[1066]: 2022-02-08 18:30:07 DEBUG (SyncWorker_0) [custom_components.hildebrandglow_dcc.glow] get 2: (https://api.glowmarkt.com/api/v0-1/resource/XXXX/readings?from=2022-01-01T00:00:00&to=2022-02-08T23:59:59&period=P1Y&offset=0&function=sum)
Feb 08 18:30:10 HA 62d3ea2a38d1[1066]: 2022-02-08 18:30:10 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.gas_consumption_today is taking over 10 seconds
Feb 08 18:30:10 HA 62d3ea2a38d1[1066]: 2022-02-08 18:30:10 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.gas_consumption_year is taking over 10 seconds
Feb 08 18:30:10 HA 62d3ea2a38d1[1066]: 2022-02-08 18:30:10 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.gas_tariff_standing is taking over 10 seconds
Feb 08 18:30:10 HA 62d3ea2a38d1[1066]: 2022-02-08 18:30:10 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.electric_tariff_standing is taking over 10 seconds
Feb 08 18:30:10 HA 62d3ea2a38d1[1066]: 2022-02-08 18:30:10 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.gas_cost_today is taking over 10 seconds
Feb 08 18:30:10 HA 62d3ea2a38d1[1066]: 2022-02-08 18:30:10 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.electric_cost_today is taking over 10 seconds
Feb 08 18:30:15 HA 62d3ea2a38d1[1066]: 2022-02-08 18:30:15 DEBUG (SyncWorker_0) [custom_components.hildebrandglow_dcc.glow] get 2: (https://api.glowmarkt.com/api/v0-1/resource/XXXX/tariff)
Feb 08 18:30:21 HA 62d3ea2a38d1[1066]: 2022-02-08 18:30:21 DEBUG (SyncWorker_0) [custom_components.hildebrandglow_dcc.glow] get 2: (https://api.glowmarkt.com/api/v0-1/resource/XXXX/readings?from=2022-02-08T00:00:00&to=2022-02-08T23:59:59&period=P1D&offset=0&function=sum)
Feb 08 18:30:22 HA 62d3ea2a38d1[1066]: 2022-02-08 18:30:22 DEBUG (SyncWorker_5) [custom_components.hildebrandglow_dcc.glow] get 2: (https://api.glowmarkt.com/api/v0-1/resource/XXXX/readings?from=2022-02-08T00:00:00&to=2022-02-08T23:59:59&period=P1D&offset=0&function=sum)
Feb 08 18:30:30 HA 62d3ea2a38d1[1066]: 2022-02-08 18:30:30 DEBUG (SyncWorker_6) [custom_components.hildebrandglow_dcc.glow] get 2: (https://api.glowmarkt.com/api/v0-1/resource/XXXX/readings?from=2022-01-01T00:00:00&to=2022-02-08T23:59:59&period=P1Y&offset=0&function=sum)

opened by jackyaz 16

Data @ 11pm-12am is lost every night

Each night at the end of the day, the accumulating value of kWh consumed is reset to zero and begins increasing again for the next day from after midnight. This value (for electricity) is sensor.electric_consumption_today

However, if you use a HistoryGraph (see attached image) to graph sensor.electric_consumption_today it's apparent that there is no data from 11pm until 12.30am every night (the consumption data is zero for at least 1.5hrs). This means that there is at least 1.5hrs of consumption not being accounted for every night.

Expected behaviour would be for consumption data to continue until 12.00am when it would reset to 0kWh and begin accumulating again from 12.01am.

HomeAssistant v2021.10.6 Hildebrand Glow (DCC) integration v0.3.3

bug

opened by smithbill17 16
Yearly sensors unavailable as of 7/12

I noticed yesterday yearly elec and gas sensors were unavailable. Rebooted HA and I got one reading however checked again this morning and sensors showing as unavailable again. All others still reading. Just yearly sensors seem to be the problem.

opened by tmh88 15
State class for tariff standing & rate sensors are not set
Describe the bug

HA statistics page reports that the state class of the following entities are not supported:

DCC Sourced smart electricity meter Standing charge (sensor.electric_tariff_standing)

DCC Sourced smart electricity meter Rate (sensor.electric_tariff_rate)

DCC Sourced smart gas meter Standing charge (sensor.gas_tariff_standing)

DCC Sourced smart gas meter Rate (sensor.gas_tariff_rate)

To Reproduce

Go to Developer Tools > Statistics /developer-tools/statistics

See error.

Expected behaviour HA to report no issues.

Screenshots

Version 1.0.2
bug
opened by markcocker 2
Pull through historical data

Related to #188

It seems that it is now possible to backfill data in home assistant, according to the comments in this thread. This would be really useful and could help with occasional gaps in the data caused by connectivity problems.
enhancement

opened by potchin 1
Handle Reauthentication through Home Asssistant

I changed my password on the Bright app. How do I update the integration's configuration to match?

If I delete the integration from my HA and re-add it using the new password credentials, will it lose past data, or cause new data to be disconnected from old data?

It would be handy to be able to change credentials easily without disrupting data storage.
enhancement

opened by caliston 3

Releases(v1.0.2)

v1.0.2(Jan 3, 2023)
What's Changed

Improved error handling to ensure the integration works even if there is no tariff data (#285)

If you are upgrading from before v1.0.0, please ensure you read the breaking changes!

Full Changelog: https://github.com/HandyHat/ha-hildebrandglow-dcc/compare/v1.0.1...v1.0.2
Source code(tar.gz)
Source code(zip)
v1.0.1(Jan 2, 2023)
What's Changed

A fix to ensure gas data is fully collected for the previous day

~Improved error handling to ensure the integration works even if there is no tariff data (#285)~

If you are upgrading from before v1.0.0, please ensure you read the breaking changes!

Full Changelog: https://github.com/HandyHat/ha-hildebrandglow-dcc/compare/v1.0.0...v1.0.1
Source code(tar.gz)
Source code(zip)
v1.0.0(Jan 1, 2023)

This release is a total rewrite of the entire integration to follow Home Assistant best practices, switch to using a library, implement some of the ideas in https://github.com/HandyHat/ha-hildebrandglow-dcc/discussions/191 to reduce strain on Hildebrand's servers and improve the stability of the integration dramatically.

Breaking Changes

The yearly sensors have been removed. Please use the daily sensors in the energy dashboard, as these now contain the missing 30 minutes at the end of each day.

The minimum version of Home Assistant needed is now 2022.12.0

Other changes

The standing charge and rate sensors are now disabled by default for new installations as they are used less commonly and many suppliers neglect to provide the data. If you do not use these sensors, please disable them to help reduce load on the API.

Thanks

With many thanks to the Hildebrand Glow team and the contributors to pyglowmarkt, which this integration is now using.

Full Changelog: https://github.com/HandyHat/ha-hildebrandglow-dcc/compare/v0.6.0...v1.0.0
Source code(tar.gz)
Source code(zip)
v0.6.0(Mar 28, 2022)
This release reworks the integration to only poll the API at a few minutes past :00 and :30 past each hour, with a random extra interval built in to ensure the servers are not hit at once. It is strongly recommended to update to this version to prevent issues like in #136.

Other changes:

Improve error handling when tariff data is unavailable (#80)

Unset device class for rate sensors (#77)

Full Changelog: https://github.com/HandyHat/ha-hildebrandglow-dcc/compare/v0.5.2...v0.6.0

With thanks to @si458, @ColinRobbins, @jackyaz, the team at Hildebrand Glow and the entire community for helping out!
Source code(tar.gz)
Source code(zip)
v0.5.2(Nov 13, 2021)

Quick release to fix (#70) the authentication bug (#69) introduced in #64
Source code(tar.gz)
Source code(zip)
v0.5.1(Nov 8, 2021)
Thanks to @ColinRobbins, various bugs have been fixed and this integration has been improved!

Fixed fetching data after DST change (#58 fixes #57)

Error handling when there is no tariff data available has been improved (#54 fixes #52)

Units for the standing charge have been corrected (#54 fixes #53)

As well as this, #64 changes requests to create a session, reducing DNS lookups (#55) and making the integration more efficient.
Source code(tar.gz)
Source code(zip)
v0.5.0(Oct 26, 2021)
Thanks to the efforts of @ColinRobbins , @totalitarian and @Lee-BS-AMS, many issues have been closed:

The documentation and issue links have been fixed (#37 closes #27)

Cost and tariff sensors have been added (#46 closes #31 and #24)

The integration now correctly handles invalid authentication (#46 closes #43 and #14)

BST is no longer hardcoded (#46)

Cumulative sensors have been added (#49 closes #25 and #45)

As well as this, Home Assistant 2021.10.01 supports using kWh in the gas section of energy management, so using m3 is no longer required 🎉
Source code(tar.gz)
Source code(zip)
v0.3.3(Sep 1, 2021)
This release updates the state class in line with changes in Home Assistant 2021.9.0! Please make sure you are on 2021.9.0 before updating.

Changes:

Change state class from measurement to total_increasing

Remove last_reset value and pytz, which was only used to calculate last_reset

Source code(tar.gz)
Source code(zip)
v0.3.2(Aug 19, 2021)
The name, domain and repository of this project has changed

No longer prompt for application ID

Handle bad response codes (should hopefully stop sensors becoming unavailable at midnight)

Change device and entity names

Clean up code

Source code(tar.gz)
Source code(zip)
v0.2.0(Aug 19, 2021)

Initial Release of the DCC version
Source code(tar.gz)
Source code(zip)

Owner

Aniket

GitHub

Smart EQ connect - Custom Integration for Home Assistant

Smart EQ Connect platform as a Custom Component for Home Assistant.

2 Jan 4, 2022

emhass: Energy Management for Home Assistant

emhass EMHASS: Energy Management for Home Assistant Context This module was conceived as an energy management optimization tool for residential electr

70 Dec 24, 2022

Home Assistant custom component to help ev-chargers stay below peak hourly energy levels.

Peaqev ev-charging Peaqev ev-charging is an attempt of charging an ev without breaching a preset monthly max-peak energy level. In order for this inte

35 Dec 24, 2022

Water quality integration for Home Assistant with data provided by Budapest FVM

Water Quality FVM (Budapest, HU) custom integration for Home Assistant This custom component integrates water quality information provided by Budapest

3 Dec 23, 2021

Universal Xiaomi MIoT integration for Home Assistant

Xiaomi MIoT Raw 简体中文 | English MIoT 协议是小米智能家居从 2018 年起推行的智能设备通信协议规范，此后凡是可接入米家的设备均通过此协议进行通信。此插件按照 MIoT 协议规范与设备通信，实现对设备的状态读取及控制。

1.9k Jan 2, 2023

Home Assistant custom integration for e-distribución

e-Distribución is an energy distribution company that covers most of South Spain area. If you live in this area, you probably are able to register into their website to get some information about your power demand, energy consumption, or even cycle billing (in terms of consumptions).

17 Sep 7, 2022

Resmed_myair_sensors - This is a Home Assistant custom component to pull daily CPAP data from ResMed's myAir service using an undocumented API

resmed_myair This component will set up the following platforms. Platform Description sensor Show info from the myAir API. Installation Using the tool

17 Dec 29, 2022

Provide Unifi device info via api to Home Assistant that will give ap sensors

Unifi AP Device info Provide Unifi device info via api to Home Assistant that will give ap sensors

12 Jan 7, 2023

Historic weather - Home Assistant custom component for accessing historic weather data

Historic Weather for Home Assistant (CC) 2022 by Andreas Frisch github@fraxinas.

1 Jan 10, 2022

Home Assistant integration for energy consumption data from UK SMETS (Smart) meters using the Hildebrand Glow API.

Related tags

Overview

Hildebrand Glow (DCC) Integration

Installation

Automated installation through HACS

Manual installation

Configuration

Debugging

Development

Code Style

Credits

Comments

Description

Motivation and Context

How Has This Been Tested?

Types of changes

Releases(v1.0.2)

v1.0.2(Jan 3, 2023)

What's Changed

v1.0.1(Jan 2, 2023)

What's Changed

v1.0.0(Jan 1, 2023)

Breaking Changes

Other changes

Thanks

v0.6.0(Mar 28, 2022)

Other changes:

v0.5.2(Nov 13, 2021)

v0.5.1(Nov 8, 2021)

v0.5.0(Oct 26, 2021)

v0.3.3(Sep 1, 2021)

v0.3.2(Aug 19, 2021)

v0.2.0(Aug 19, 2021)

Owner

Aniket

Smart EQ connect - Custom Integration for Home Assistant

emhass: Energy Management for Home Assistant

Home Assistant custom component to help ev-chargers stay below peak hourly energy levels.

Water quality integration for Home Assistant with data provided by Budapest FVM

Universal Xiaomi MIoT integration for Home Assistant

Home Assistant custom integration for e-distribución

Home Assistant custom integration for Yi cameras: yi-hack-MStar, yi-hack-Allwinner and yi-hack-Allwinner-v2

Electrolux Pure i9 robot vacuum integration for Home Assistant.

A Home Assistant integration for Solaredge inverters

Nordpool_diff custom integration for Home Assistant

OPNsense integration with Home Assistant

Component for deep integration LedFx from Home Assistant.

Aqara Camera G3 integration for Home Assistant

Sleep As Android integration for Home Assistant

Skykettle ha - Redmond SkyKettle integration for Home Assistant

Ha-rpi gpio - Home Assistant Raspberry Pi GPIO Integration

Resmed_myair_sensors - This is a Home Assistant custom component to pull daily CPAP data from ResMed's myAir service using an undocumented API

Provide Unifi device info via api to Home Assistant that will give ap sensors

Historic weather - Home Assistant custom component for accessing historic weather data