-
### The problem
For utility_meter with multiple tariffs unit_of_measurement is set only for the first defined tariff in table statistics_meta, which causes following errors:
Logger: homeassistant.co…
-
La dernière version de Home Assistant a maintenant une section Énergie et malheureusement, smart energy meter n'y apparait pas. Selon HA, il faut spécifier quelques metadata au sensor pour quil soit r…
-
Hello and congratulations for your work.
I'm using Wibeee and the entity providing power is a sensor.
When installing the component, I can select the provider and tarif (in my case Galp Simples) but…
-
This model is used in a number of places:
https://sustainablewebdesign.org/calculating-digital-emissions/
There's a bit more research needed for what I was referring to as the Green Byte Model i…
-
**Synopsis:**
Upon searching and viewing a single consumption metering point in a Graphical User Interface (GUI), the Charges domain must be able to provide required charge links data to fulfill any m…
-
This decision proposal contains a recommendation for the candidate URIs and end points for Generic Tariff Data. This proposal has been developed with the aid of AER and DELWP.
The decision proposal…
-
### The problem
Hi there,
I've been struggling with this for almot quite some time now, I guess I need some help!
The issue itself it's pretty straight forward, on each reboot or reconnection o…
-
The decision proposal for Tailored Tariff data payloads is attached below:
[Decision Proposal 115 - Tailored Tariff Data Payloads.pdf](https://github.com/ConsumerDataStandardsAustralia/standards/file…
-
**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 o…
-
This decision proposal contains a recommendation for the candidate URIs and end points for Usage Data. This proposal has been developed with the aid of AEMO.
The decision proposal is embedded belo…