garo_wallbox icon indicating copy to clipboard operation
garo_wallbox copied to clipboard

After update missing the readout from power meter

Open molcam opened this issue 1 year ago • 27 comments

Hi!

I have recently updated to latest version (2024.9.5) and I have now lost the sensors for the power meters and the currents on each phase (laster på varje fas). Additionally, the state of the senor when toggling from set mode = "On" to "Off" or vice versa has become extremely slow and states "Not available for charging" instead of previous "on" or "off". It takes 5-10 seconds before the state is updated. Any work around this?

molcam avatar Oct 02 '24 18:10 molcam

@molcam Hi, are there any logs? There could be something interfering with the connection.

sockless-coding avatar Oct 06 '24 09:10 sockless-coding

Hi! The following is stated for the Phase 1 to 3 - GARO meter Phase 1 current - "This entity is no longer being provided by the garo_wallbox integration. If the entity is no longer in use, delete it in settings." From the logg: 2024-10-16 19:36:56.569 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration garo_wallbox 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 2024-10-16 19:37:00.574 DEBUG (MainThread) [custom_components.garo_wallbox.coordinator] Finished fetching Garo Device Coordinator data in 0.028 seconds (success: True) 2024-10-16 19:37:00.597 DEBUG (MainThread) [custom_components.garo_wallbox.coordinator] Fetched 0 schemas 2024-10-16 19:37:00.884 DEBUG (MainThread) [custom_components.garo_wallbox.coordinator] Finished fetching Garo Meter Coordinator data in 0.287 seconds (success: True) 2024-10-16 19:37:03.816 DEBUG (MainThread) [custom_components.garo_wallbox.sensor] Updated schedule entries: 0 2024-10-16 19:37:14.390 DEBUG (MainThread) [custom_components.garo_wallbox.coordinator] Finished fetching Garo Meter Coordinator data in 0.389 seconds (success: True) 2024-10-16 19:37:24.388 DEBUG (MainThread) [custom_components.garo_wallbox.coordinator] Finished fetching Garo Meter Coordinator data in 0.392 seconds (success: True) 2024-10-16 19:37:34.124 DEBUG (MainThread) [custom_components.garo_wallbox.coordinator] Finished fetching Garo Device Coordinator data in 0.041 seconds (success: True) 2024-10-16 19:37:44.565 DEBUG (MainThread) [custom_components.garo_wallbox.coordinator] Finished fetching Garo Meter Coordinator data in 0.568 seconds (success: True) 2024-10-16 19:37:54.403 DEBUG (MainThread) [custom_components.garo_wallbox.coordinator] Finished fetching Garo Meter Coordinator data in 0.405 seconds (success: True)

molcam avatar Oct 16 '24 17:10 molcam

I also miss Power meter in "W" very much. I downgraded to 1.0.9 to get it back.

markuska00 avatar Oct 16 '24 18:10 markuska00

@markuska00 what firmware are you running on the garo?

sockless-coding avatar Oct 16 '24 18:10 sockless-coding

Mjukvaruversion 1.3.7 (according to local site it is the latest). For some reason the charger integration has become very slow (can take up to a minute before the updated integration shows its status. Also the Power meter dose not work...). I can see the Power meter on the local website, so the info is there - just not transfered to the HA integration - Lastbalanseringsmätare 2: XXYYZZ Mätarställning: 87568.3kWh Fas 1 ström/effekt: 1.4A/0kW Fas 2 ström/effekt: 1.5A/0kW Fas 3 ström/effekt: 1.6A/0kW

molcam avatar Oct 16 '24 18:10 molcam

@markuska00 what firmware are you running on the garo?

I'm running firmware 1.3.7

markuska00 avatar Oct 16 '24 18:10 markuska00

1.3.7 is the latest... 1.0.9 is old and doesn't have support for the power meter. The 2024.x.x should provide a device for it, please enable debug logging for the integration.

sockless-coding avatar Oct 16 '24 20:10 sockless-coding

I first attach trend on the Power meter with the old version 1.0.9 And then with the new 2024.9.5 The resolution on the new version is too bad. Would like the same resolution as on version 1.0.9

Skärmklippgarogamla Skärmklippgaroladdarenya

markuska00 avatar Oct 17 '24 13:10 markuska00

Most of the time the power meter items show 0 kW. Skärmklippgaro

markuska00 avatar Oct 17 '24 13:10 markuska00

Are you running a fork of 1.0.9? Since that version does not have any Meter support. Still need those debug logs, and info about what meter you have.

sockless-coding avatar Oct 17 '24 18:10 sockless-coding

Are you running a fork of 1.0.9? Since that version does not have any Meter support. Still need those debug logs, and info about what meter you have.

The signals that I campare. 1.0.9 : sensor.XXXX_meter_power

2024.9.5: sensor.energy_meter_XXXX_power_consumption

I use the Power meter in my automations. To get it working I'm back on 1.0.9 and unfortunately can't give you for debug 2024.9.5 right now.

markuska00 avatar Oct 17 '24 18:10 markuska00

Could my problem be that in 1.0.9 you calculate the power from ampere? In the new version you use power from the power meter? Maybe my powermeter do not support that Screenshot_20241017-204302_Chrome

markuska00 avatar Oct 17 '24 18:10 markuska00

Hi!

I have at least found my issue and that is that the name of the Powermeter has changed in the new integration - Now it is called "Energy meter (110020U) Power consumption phase L1" or L2 or L3 and is a new device in the updated integration. However, I now have the same issue as Markuska00. The energy readings are 0.0 kw for all three phases. The integration is still super slow though...

molcam avatar Oct 17 '24 19:10 molcam

Version 1.0.9 only had the Charging Power sensor, and that is still available. Regarding "slow" the update interval can be changed: image

sockless-coding avatar Oct 17 '24 19:10 sockless-coding

The official v1.0.9 only registered the following sensors:

    async_add_entities([
        GaroMainSensor(device),
        GaroSensor(device, 'Status', 'status'),
        GaroSensor(device, "Charging Current", 'current_charging_current', 'A'),
        GaroSensor(device, "Charging Power", 'current_charging_power', 'W'),
        GaroSensor(device, "Phases", 'nr_of_phases'),
        GaroSensor(device, "Current Limit", 'current_limit', 'A'),
        GaroSensor(device, "Pilot Level", 'pilot_level', 'A'),
        GaroSensor(device, "Session Energy", 'acc_session_energy', "Wh"),
        GaroSensor(device, "Total Energy", 'latest_reading', "Wh"),
        GaroSensor(device, "Total Energy (kWh)", 'latest_reading_k', "kWh"),
        GaroSensor(device, "Temperature", 'current_temperature', TEMP_CELSIUS),
        ])

https://github.com/sockless-coding/garo_wallbox/blob/v1.0.9/custom_components/garo_wallbox/sensor.py No meter_power sensor

sockless-coding avatar Oct 17 '24 19:10 sockless-coding

I have this

    GaroMainSensor(device),
    GaroSensor(device, 'Status', 'status'),
    GaroSensor(device, "Charging Current", 'current_charging_current', 'A'),
    GaroSensor(device, "Charging Power", 'current_charging_power', 'W'),
    GaroSensor(device, "Phases", 'nr_of_phases'),
    GaroSensor(device, "Current Limit", 'current_limit', 'A'),
    GaroSensor(device, "Pilot Level", 'pilot_level', 'A'),
    GaroSensor(device, "Session Energy", 'acc_session_energy', "Wh"),
    GaroSensor(device, "Total Energy", 'latest_reading', "Wh"),
    GaroSensor(device, "Total Energy (kWh)", 'latest_reading_k', "kWh"),
    GaroSensor(device, "Temperature", 'current_temperature', TEMP_CELSIUS),
]

if device.meter:
    sensors.extend([
        GaroSensor(device.meter, "Total Energy", 'acc_energy_k', 'kWh'),
        GaroSensor(device.meter, "Power", 'power', 'W'),
        GaroSensor(device.meter, "Phase 1 current", 'phase1_current', 'A'),
        GaroSensor(device.meter, "Phase 2 current", 'phase2_current', 'A'),
        GaroSensor(device.meter, "Phase 3 current", 'phase3_current', 'A')
    ])

markuska00 avatar Oct 17 '24 19:10 markuska00

@markuska00 then you are running a fork... would be interesting to know what call that fork is using to get a more detailed power reading since the 3 calls I looked at meterinfo/EXTERNAL, meterinfo/CENTRAL100, meterinfo/CENTRAL101 only provide kW power readings as far as I can tell (I don't have a Meter hooked up to the charger directly)

sockless-coding avatar Oct 17 '24 20:10 sockless-coding

Weird. I don't have the knowledge to change anything myself. Can't remember as it is from 2021 or 2022

markuska00 avatar Oct 17 '24 20:10 markuska00

Could you provide the 1.0.9 files you are running?

sockless-coding avatar Oct 17 '24 20:10 sockless-coding

I found it on github. https://github.com/joek-makewave/garo_wallbox/blob/load_balancer/custom_components/garo_wallbox/sensor.py

I was not aware that it was not the original sorry

markuska00 avatar Oct 17 '24 20:10 markuska00

That version is not using the Power value from the Meter instead it's using a fixed value for the voltage (230V) and calculating the power from the current values so it's just an estimated Power reading... Don't know why Garo doesn't provide a better reading.

Using a constant like 230 isn't that exact... i.e. I rarely see 230V image But I guess I could add a "calculated power" sensor

sockless-coding avatar Oct 17 '24 20:10 sockless-coding

Hej, I have downloaded the integration via HACS (2024.9.5). When I setup the integration, I get error message ”Unexpected error creating device”. I have a Garo entity compact charging box. Anyone who knows what could be wrong and what to do about it?

davidgbg86 avatar Oct 18 '24 14:10 davidgbg86

@davidgbg86 Garo Entity devices rely on the cloud and isn't supported by this integration.

sockless-coding avatar Oct 18 '24 15:10 sockless-coding

I've added some controls to the Meter devices: image It's now possible to set meter power sensors to use calculated values and a "Mains voltage"

When it comes to kW / W this can be toggled on the sensors: image

I might be able to release this later today, I have to consolidate a pull request first.

sockless-coding avatar Oct 18 '24 15:10 sockless-coding

Version 2024.10.0 has been released

sockless-coding avatar Oct 18 '24 16:10 sockless-coding

@davidgbg86 Garo Entity devices rely on the cloud and isn't supported by this integration.

Thanks for your reply. Is there support planned for the future or are there technical limitations that do not allow support?

davidgbg86 avatar Oct 19 '24 19:10 davidgbg86

@davidgbg86 the only limitation is that I don't have access to an Entity device.

sockless-coding avatar Oct 19 '24 21:10 sockless-coding