The info is available in the last_period
attribute of your daily utility meter. If it’s not enough, you can create a template sensor fed by that attribute.
Hi, any update on this functionality? Thanks!
You lost me 🫣
Add this to configuration.yaml
and adjust it to your utility meter id.
template:
- sensor:
- name: "Verbruik gister"
unique_id: "yesterday_energy_usage" # Something unique, self defined
unit_of_measurement: "kWh"
state_class: measurement
device_class: energy
state: '{{ state_attr("sensor.verbruik_vandaag", "last_period") }}'
Hello,
I have an issue since monday with the water meter.
the active_water_usage sensor does not relay any informations
despite the fact that all the others sensors works well
any idea ?
thanks !
There is a lot that could go wrong, without having information about your situation/configuration.
Some ideas to think about:
- Does the HomeWizard app show the same ‘missing’ information
- Have you tried a reboot or something?
- Is there something changed since ‘Monday’?
thanks for your support,
Unfortunately, the Homewizard app does not show the active_water_usage, just the total, and value are the same as HA.
I’ve updated HA Core from 2023.3.6 to 2023.4.5 and OS to 10.0 yesterday, so yes already rebooted a lot of time.
What is the advantage to see the voltage ? What can you see or learn from it ?
Is it possible to get the date out of the “peak demand current month” ?
@Faecon
Is it possible to get the date out of the “peak demand current month” ?
Opened Add 'Last update' timestamp attributes for timed HomeWizard sensors by DCSBL · Pull Request #91837 · home-assistant/core · GitHub to allow users to do this.
But you have to create a template sensor again, so time for you to practice
Hi,
So far I have not been able to get this working.
I put this piece of .yalm in the folder configuration.yaml. But I still can’t get it to work. Can someone help me with this?
Hi, Help needed with the Homewizard P1 meter.
I noticed with one of the updates when the homewizard P1-meter loses the WiFi connection values of some sensors are filled in when there is no data or time out errors.
In the past there was no problem, but when I disconnect the P1 meter my monthly counting is doubled as soon as new data is received.
I made special month sensors with kWh and Euro, because we receive a discount every day. (every day same amount)
My configuration.yaml for the energy sensors is:
recorder:
db_url: mysql://hass:[email protected]/homeassistant?charset=utf8mb4
purge_keep_days: 365
include:
entities:
- sensor.db_size
- sensor.verbruik_vandaag_t1
- sensor.verbruik_vandaag_t2
- sensor.energy_import_t1_dagelijks
- sensor.energy_import_t2_dagelijks
- person.kees
- sensor.p1_meter_wi_fi_strength
- sensor.energy_import_total_dagelijks_eur
- sensor.import_t1_dagelijks_eur
- sensor.import_t2_dagelijks_eur
- sensor.energy_import_total_dagelijks_kwh
- sensor.energy_import_total_dagelijks_metkorting_eur
- sensor.p1_meter_total_power_import_t1
- sensor.p1_meter_total_power_import_t2
- sensor.p1_meter_total_power_import
- sensor.energy_import_maandelijks_euro
- sensor.energy_import_korting_maandelijks_euro_werkelijk
- sensor.energy_import_maandelijks_kwh_totaal
sensor:
#import electra
-
platform: template
sensors:
energy_import_t2_dagelijks_eur:
friendly_name: ‘Kosten vandaag Normaal’
value_template: “{{ ‘%0.2f’ | format ((states(‘sensor.energy_import_t2_dagelijks’)|float(0) * states(‘input_number.t2_energy_cost’)|float(0))|round(2)) }}”
unit_of_measurement: “€” -
platform: template
sensors:
energy_import_t1_dagelijks_eur:
friendly_name: ‘Kosten vandaag Dal’
value_template: “{{ ‘%0.2f’ | format ((states(‘sensor.energy_import_t1_dagelijks’)|float(0) * states(‘input_number.t1_energy_cost’)|float(0))|round(2)) }}”
unit_of_measurement: “€” -
platform: template
sensors:
energy_import_total_dagelijks_eur:
friendly_name: ‘Kosten vandaag Totaal’
value_template: “{{ ‘%0.2f’ | format ((states(‘sensor.energy_import_t2_dagelijks_eur’)|float(0) + states(‘sensor.energy_import_t1_dagelijks_eur’)|float(0))|round(2)) }}”
unit_of_measurement: “€” -
platform: template
sensors:
energy_import_total_dagelijks_metkorting_eur:
friendly_name: ‘Kosten vandaag Totaal - Korting’
value_template: “{{ ‘%0.2f’ | format ((states(‘sensor.energy_import_t2_dagelijks_eur’)|float(0) + states(‘sensor.energy_import_t1_dagelijks_eur’)|float(0) - states(‘input_number.daily_cost’)|float(0))|round(2)) }}”
unit_of_measurement: “€” -
platform: template
sensors:
energy_import_total_dagelijks_kwh:
friendly_name: ‘kWh vandaag Totaal’
value_template: “{{ ‘%0.3f’ | format ((states(‘sensor.energy_import_t1_dagelijks’)|float(0) + states(‘sensor.energy_import_t2_dagelijks’)|float(0))|round(3)) }}”
unit_of_measurement: “kWh” -
platform: template
sensors:
verbruik_vandaag_t2:
friendly_name: ‘Verbruik vandaag Normaal’
value_template: “{{ ‘%0.3f’ | format ((states(‘sensor.energy_import_t2_dagelijks’)|float(0)) |round(3)) }}”
unit_of_measurement: “kWh” -
platform: template
sensors:
verbruik_vandaag_t1:
friendly_name: ‘Verbruik vandaag Dal’
value_template: “{{ ‘%0.3f’ | format ((states(‘sensor.energy_import_t1_dagelijks’)|float(0)) |round(3)) }}”
unit_of_measurement: “kWh” -
platform: template
sensors:
day_of_month:
friendly_name: ‘Dag van de Maand’
value_template: “{{ now().day }}” -
platform: template
sensors:
energy_import_korting_deze_maand:
friendly_name: ‘Korting deze Maand’
value_template: “{{ ‘%0.2f’ | format ((states(‘input_number.daily_cost’)|float(0) * states(‘sensor.day_of_month’)|float(0)) |round(2)) }}”
unit_of_measurement: “€” -
platform: template
sensors:
energy_import_korting_maandelijks_euro_werkelijk:
friendly_name: ‘Kosten deze maand werkelijk’
value_template: “{{ ‘%0.2f’ | format ((states(‘sensor.energy_import_maandelijks_euro’)|float(0) - states(‘sensor.energy_import_korting_deze_maand’)|float(0)) |round(2)) }}”
unit_of_measurement: “€” -
platform: template
sensors:
energy_import_maandelijks_kwh_totaal:
friendly_name: ‘Verbruik deze maand’
value_template: “{{ ‘%0.3f’ | format ((states(‘sensor.energy_import_maandelijks_kwh’)|float(0)) |round(3)) }}”
unit_of_measurement: “kWh”
input_number:
t2_energy_cost:
name: Tarief Normaal
mode: box
min: 0
max: 1
step: 0.00001
unit_of_measurement: " €/kWh"
icon: mdi:currency-eur
t1_energy_cost:
name: Tarief Dal
mode: box
min: 0
max: 1
step: 0.00001
unit_of_measurement: " €/kWh"
icon: mdi:currency-eur
daily_cost:
name: Korting per dag
mode: box
min: 0
max: 2
step: 0.00001
unit_of_measurement: " €/dag"
icon: mdi:currency-eur
utility_meter:
energy_import_t2_dagelijks:
source: sensor.p1_meter_total_power_import_t2
cycle: daily
energy_import_t1_dagelijks:
source: sensor.p1_meter_total_power_import_t1
cycle: daily
energy_import_maandelijks_euro:
source: sensor.energy_import_total_dagelijks_eur
cycle: monthly
energy_import_maandelijks_kwh:
source: sensor.energy_import_total_dagelijks_kwh
cycle: monthly
Hello!
Using the P1 meter now for a while, but since a week we have solar panels and i can see in the P1 meter that we exported about 100kWh, but when i look in HA it is saying ‘disabled by intergration’ and even by reloading it keeps disabled. How can i fix this?
Export is disabled by default when export is “0” during installation.
Just hit the and then enable. And wait for a reload.
Over the weekend I’ve added a few solar panels to the roof of a little building in the garden. To keep track of all energy collected in one place, I’ve also added a KWh meter on the combined input. Total is now 4kWp. However, now the P1 and KWh meter take turns to stop communicating with HA. I’ve to disconnect power and physically remove the P1 meter from the port. Insert power and the plug back into the port or cycle the breakers for the KWh meter. After that they come back to live. At the same time, my router sees them as connected and the app works without a problem. Any ideas what’s causing this behavior? It only takes a few hours before one of them or both become unresponsive again…
Is anyone in the UK using the WiFi KwH meter in their UK consumer unit…
This is the closest that i can get for the circular gauges using circular custom card, which you could probably copy for the other ones as well.
For anyone encountering this issue, it’s something to do with the guest network. I’ve changed both the kWh meter and the P1 meter to the “regular” network and if the WiFi now goes down, both happily rejoin and everything stays working in Home Assistant. Don’t know if it’s ASUS guest network specific, and I can’t understand what’s causing it, bu this fixes it.
Hi,
Is it possible to gather historic data from the P1 meter or from HA?
Reason for my question is, that I need to switch to a new raspberry with HA installed. I can access the old one, but not able to use it much longer. However I’d like to keep the gathered information of the past 10 months (as you can imagine )
Thanks in advance.