jnxxx / homeassistant-dabblerdk_powermeterreader Goto Github PK

This custom integration uses deprecated DEVICE_CLASS_* constants in its codebase.

The DEVICE_CLASS_* constants have been deprecated and replaced in Home Assistant Core 2021.12 (over a year ago). I would highly suggest updating/migrating this integration to the new enums.

For example, for the device classes supported by the sensor platform, there is now a SensorDeviceClass enum. So if a sensor previously used the DEVICE_CLASS_ENERGY constant, it should now use SensorDeviceClass.ENERGY. Other platforms (like binary_sensor, and number) provide similar enumerations for their supported device classes.

The migration thus only consists of replacing constants with an enumeration member and is, therefore, very low impact and should be fairly straightforward.

If I can help resolve any questions regarding this change or migration, feel free to ask or respond to this issue. I'm happy to help!

Kindest regards,

../Frenck

Hvis jeg starter opladningen af min el bil samtidig med at opvaskemaskinen kører stopper integrationen.

Bilen tager i gennemsnit 4-5 timer at oplade, opvaskeren kører omkring 1.5time. - starter begge omkring kl. 00:30

L1 current stiger fra ca. 1A til ca. 26A indenfor 20min

Integrationen stopper med at give målinger, også selv om begge dele forlængst er stoppet.
Som jeg læser dit indlæg hos dabbler, burde den ignorere den høje måling i en time inden den acceptere den, det virker som det ikke sker.

Modul firmware: [NES MEP, version: Dec 23 2022 11:07:41]

Hvis integrationen genindlæses, virker det igen indtil næste gang bilen skal lades.

Fra HA log:

Logger: custom_components.dabblerdk_powermeterreader.meter.meter
Source: custom_components/dabblerdk_powermeterreader/meter/meter.py:49
Integration: Dabbler.dk reader for Echelon/NES smart power meter (documentation, issues)
First occurred: 00.37.21 (97 occurrences)
Last logged: 08.37.21

Fwd_Act_Wh changed too much (23441), sticking to previous values
Fwd_Act_Wh changed too much (23453), sticking to previous values
Fwd_Act_Wh changed too much (23466), sticking to previous values
Fwd_Act_Wh changed too much (23478), sticking to previous values
Fwd_Act_Wh changed too much (23485), sticking to previous values

Hi there my issue is that "Echelon energy consumption" is showing just fine on a entities card but not an the HA Energy dashboard. I can find the entity in the dropdown under "Configure grid consumption" but no values are shown on the dashboard.

Echelon integration installed via hacs v1.0.4

Spring is around the corner and then it will be time to look at the automation for charging the electrical cars when there is surplus energy.

The integration proveides the returned power but it would be easier to use the returned current if it can be read from the echelon. Otherwise i'll have to calculate it from power and voltage.

I plan on adjustning the dynamic_charge_limit on my easee home charger on a timer with the surplus current. Something along the line of

If (sensor.echelon_l1_current_returned >0){ currentP1 +=sensor.echelon_l1_current_returned;}
else if (sensor.echelon_l1_current>0) { currentP1 +=sensor.echelon_l1_current;}

or maybe also including the actual current state_inCurrentT so i just set the max to the current current plus the export (so i won't continue to inccrease the limit on phase if it is one of the others that are actually limiting it,

If the echelon does not provide the data i will have to make an automation that just look at the from grid without knowing how much is exported to the grid.

Or would it be better to wait for the upgraded MEP interface with MQTT ?

Denne fejl kommer konstant i Home assistant, og sensoren opdatere ikke som forventet. Den er konstant med få opdateringer til værdien en gang i mellem. Jeg har genstartet HA flere gange, deraf at den "kun" er vist en gang :-)

Det virker til at MEP modulet har god forbindelse på 2.4 GHz båndet.. Ihvertfald det er hvad min unifi dream router fortæller mig :-)

Kan jeg frembringe andre logs på companion integrationen, som kan bringe mig tættere på noget brugbart?

`This error originated from a custom integration.

Logger: custom_components.dabblerdk_powermeterreader.meter.meter
Source: custom_components/dabblerdk_powermeterreader/meter/meter.py:49
Integration: Dabbler.dk reader for Echelon/NES smart power meter (documentation, issues)
First occurred: 17:53:25 (1 occurrences)
Last logged: 17:53:25

Requesting meter values failed: Cannot connect to host 192.168.1.82:80 ssl:default [Connect call failed ('192.168.1.82', 80)]`

When sun is shining and solar panels are producing power and the amount of power consumed is lower than produced aka power returned to grid, then the MEP readings stop to work and the integration triggers a problem.

The sensor values gets stuck at the previous reading until the integration is reloaded.
The only suspicious Warning I could find in the logs are lines starting like:

L1_Fwd_W + L2_Fwd_W + L3_Fwd_W does not equal Fwd_W (499 != 142), sticking to previous values
...
L1_Fwd_W + L2_Fwd_W + L3_Fwd_W does not equal Fwd_W (502 != 142), sticking to previous values

As a workaround I had to create an automation that triggers a reload of the integration whenever the problem binary sensor switched to active to get the problem cleared and at least a fresh reading.

alias: echelon reload
description: ""
trigger:
  - platform: state
    entity_id:
      - binary_sensor.echelon_mep_problem
    to: "on"
condition: []
action:
  - service: homeassistant.reload_config_entry
    data: {}
    target:
      device_id: <device = Echelon>
mode: single

Are there any data evaluation checks in place that probably do not consider this use case?
The Integration works great as long no power is returned to the grid.

Have just installed/configured HW from dabbler, and integrated your stuff in HA.
I just have 1 question.
How to get your "Energy dashboard" in HA as shown in your Readme.

Suddenly 2025 is all over us and we cannot have this fine integration stop working.

Logger: homeassistant.const
Kilde: helpers/deprecation.py:205
Første forekomst: 10.54.51 (4 forekomster)
Senest logget: 10.54.51

ELECTRIC_POTENTIAL_VOLT was used from dabblerdk_powermeterreader, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfElectricPotential.VOLT instead, please create a bug report at https://github.com/jnxxx/homeassistant-dabblerdk_powermeterreader/issues
ELECTRIC_CURRENT_AMPERE was used from dabblerdk_powermeterreader, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfElectricCurrent.AMPERE instead, please create a bug report at https://github.com/jnxxx/homeassistant-dabblerdk_powermeterreader/issues
POWER_WATT was used from dabblerdk_powermeterreader, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfPower.WATT instead, please create a bug report at https://github.com/jnxxx/homeassistant-dabblerdk_powermeterreader/issues
FREQUENCY_HERTZ was used from dabblerdk_powermeterreader, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfFrequency.HERTZ instead, please create a bug report at https://github.com/jnxxx/homeassistant-dabblerdk_powermeterreader/issues

Hi Jan
I updated to the new version and get error.
Can you please help with some advise for me.
BR Jan O Petersen

Anyone know what the default login name is on the web interface? I only remembered the password I typed in, and did not change the username

This looks really promising for Echelon users, but -

Where to buy the MEB hardware?
You are referring to dabbler.dk site, but I can't seem to find any way to buy the hardware

I have the MEP board running since early afternoon and the integration in HA a bit later.

The MEB dashboard is updating nicely on the ESP

but the [sensor.echelon_energy_consumption] stopped updating after a couple of hours (the rest of the sensors was still updating)

I.e Power

I restarted HA and then it is updating again.