home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
69.26k stars 28.47k forks source link

HomeWizard gas values/sensors not available anymore #117557

Closed vincentvdb1987 closed 5 days ago

vincentvdb1987 commented 2 weeks ago

The problem

Few days ago my digital gas and electricity devices were replaced with new onces since the previous stopped communicating. Since then I don't get the GAS information anymore from my HomeWizard P1 meter. I tried removing the integration, restarted HA and add again but still the same. I also restarted the P1 meter multiple times. The gas values are still available in the diagnostics file but I don't have any sensor available in HA. Previously the integration showed 3 devices (P1 electricity, Gas, Water), now only P1 and water.

What version of Home Assistant Core has the issue?

2024.5.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

HomeWizard

Link to integration documentation on our website

No response

Diagnostics information

config_entry-homewizard-faeaed9652a01d5fe687706c2b3b051d (2).json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

The gas values are still available in the diagnostics file

Additional information

No response

home-assistant[bot] commented 2 weeks ago

Hey there @dcsbl, mind taking a look at this issue as it has been labeled with an integration (homewizard) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `homewizard` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign homewizard` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


homewizard documentation homewizard source (message by IssueLinks)

vincentvdb1987 commented 2 weeks ago

I see that also the "P1 meter energy import" and "P1 meter energy export" is not working the same as the "sensor.p1_meter_total_energy_export" and "sensor.p1_meter_total_energy_import" I had before... The Energy dashboard is showing completely wrong information with these 2 new sensors. :(

Willem-Dekker commented 2 weeks ago

@vincentvdb1987 check if can reach your meters local api on <ip-of-meter>/api. If you can not try unplugging the meter and plugging it back in and check again. This fixed it for me just now.

vincentvdb1987 commented 1 week ago

I can reach it without issue and get this info: { "product_name": "P1 meter", "product_type": "HWE-P1", "serial": "xxxxxx", "firmware_version": "4.19", "api_version": "v1" }

The P1 meter is also available in HA but I only get electricity and water values, no gas information

DCSBL commented 1 week ago

@Willem-Dekker, I think you issue is https://github.com/home-assistant/core/issues/87432


@vincentvdb1987, can you see if you still have some old entities alive in your instance? Maybe you can (backup and) remove those. I suspect we do not handle unique ID's + migration properly (introduced in https://github.com/home-assistant/core/pull/100684)

vincentvdb1987 commented 1 week ago

@DCSBL thanks for the reply. I checked and indeed some old entities were available, I deleted them and reloaded the integration but still no luck. Anything else I should do?

DCSBL commented 1 week ago

Oh, I've just checked your diagnostic file. I see two things that may be concerning;

  1. I cannot see your gas meter listed, only your watermeter. This may be the root of your problem → Your supplier fkd up and did not connect your gasmeter properly.
  2. I do not like the unique \u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 string, this should be something more readable.

If you have discord, can you message me privately with the result of http://<ip_address>/api/v1/telegram. Or feel free to redact some data and paste it here.

vincentvdb1987 commented 1 week ago

I had the same thought that they fkd up but in the diagnostics file I see this: "total_gas_m3": 0.053, "gas_timestamp": "2024-05-16T12:57:37", "gas_unique_id": "REDACTED",

So it looks to me like there is something available? Also when I use the HomeWizard app I see both electricity and gas usage without issues.

I am not using discord so I paste the info here, no idea if there is anything sensitive? :-D

/FLU5\253967035_D

0-0:96.1.4(50221) 1-0:94.32.1(400) 0-0:96.1.1(xxxxx) 0-0:96.1.2() 0-0:1.0.0(240521162426S) 1-0:1.8.1(000025.929kWh) 1-0:1.8.2(000026.332kWh) 1-0:2.8.1(000056.838kWh) 1-0:2.8.2(000028.696kWh) 0-0:96.14.0(0001) 1-0:1.4.0(00.168kW) 1-0:1.6.0(240520200000S)(03.819kW) 0-0:98.1.0(1)(1-0:1.6.0)(1-0:1.6.0)(240301000000W)(240201000000W)(00.000kW) 1-0:1.7.0(00.250kW) 1-0:2.7.0(00.000kW) 1-0:21.7.0(00.609kW) 1-0:41.7.0(00.234kW) 1-0:61.7.0(00.000kW) 1-0:22.7.0(00.000kW) 1-0:42.7.0(00.000kW) 1-0:62.7.0(00.593kW) 1-0:32.7.0(235.3V) 1-0:52.7.0(236.7V) 1-0:72.7.0(237.2V) 1-0:31.7.0(002.64A) 1-0:51.7.0(001.14A) 1-0:71.7.0(002.71A) 0-0:96.3.10(1) 0-0:17.0.0(99.999kW) 1-0:31.4.0(999.99A) 0-1:96.3.10(0) 0-2:96.3.10(0) 0-3:96.3.10(0) 0-4:96.3.10(0) 0-0:96.13.0() 0-1:24.1.0(003) 0-1:96.1.1(xxxxxx) 0-1:96.1.2(000000000000000000) 0-1:24.4.0(1) 0-1:24.2.3(xxxxxx) 0-2:24.1.0(007) 0-2:96.1.1(3853455430303130303535303633) 0-2:96.1.2(000000000000000000) 0-2:24.2.1(240521161900S)(00003.336m3) !7B4D

DCSBL commented 1 week ago

Your gasmeter and watermeter both have the EAN 000000000000000000, this should not happen. I am not sure if this is something new or something your installed messed up. I have not seen this before.

Because we use this value as unique_id in Home Assistant, it will conflict as both IDs are the same.

So we have to figure out if this is something we could/should fix is to determine if this is new behaviour from Fluvius or just one installer that had pressed the wrong button or something. Can you get in contact with Fluvius? Just send them the telegram and tell them 0-1:96.1.2 should contain something unique.

vincentvdb1987 commented 1 week ago

I called with Fluvius, apparently they have some issues "in transition" where a lot of EAN numbers got locked, that's why I get all 0. They are working on but it can take some months :-| Gonna contact water supplier and check if they can change the 0's, if so, then the gas is the only one with 0's and it should work again, correct?

DCSBL commented 1 week ago

Okay, bummer! Having one that is unique should do the trick indeed. (Maybe you have to remove the 'old' 000-watermeter first.)

It may be possible to add something to fix this issue (temporary) as this may cause issues with more customers in the near-future. We may create an unique_id based on the smart meter EAN + 'It is a gasmeter', that combo is pretty unique in most cases 🤞. I will ping the core developers to join the discussion.

vincentvdb1987 commented 1 week ago

That would be indeed a good workaround since I don't believe that the water-people are smart enough to program a serial number in that thing :-s Support is not the best thing on these smart-devices unfortunately. Thanks for the effort, would be nice to get it working again like that!

EAN+'it is a gasmeter' should indeed be unique in most households, unless in apartment or business buildings with multiple devices where the owner wants to control everything :-)

DCSBL commented 1 week ago

Proposed a fix in https://github.com/home-assistant/core/pull/117940

vincentvdb1987 commented 1 week ago

Nice! Thanks a lot!!! I am always willing to install the fix and test it, if you can guide me through the installation :-)

DCSBL commented 5 days ago

@vincentvdb1987 as beta week is coming close I think it is the best to wait for that. Otherwise you have to set up a development environment.

Besides this, can we add you to a firmware beta? We have developed a fix which should solve this issue. If so please fill in this form and I will add your P1 Meter to the beta channel.