v3.0.0 - New major release for HA 2023.9.x

[alexdelprete]

This version was in the works since a couple of months, it isn't fully tested yet, but the problems introduced by HA 2023.9.x and pymodbus 3.5 forced me to push it sooner than I wanted to. This release seems to be working fine with HA 2023.9.x.

The code has mostly been refactored using DataUpdateCoordinator, etc. and many other things under the hood. It should perform better, I hope. :)

Enjoy and let me know in case of problems.

---

This discussion was created from the release v3.0.0 - New major release for HA 2023.9.x.

[dexmorgan8888]

This update creates a new device which mirrors the existing one. Because of this, all entities under the one no longer function. The entity ids under the new device is now named with xxx_2 suffix, eg: solar_ac_current_2
This causes downstream sensors such to fail as helpers sensors with Riemann sum integral utility meter calculation.
Anyway to elegantly fix this? if not, I will be forced to revisit all my downstream sensors.
Thanks

[alexdelprete]

What version were you using previously? It shouldn't create a new device. The unique I'd is the inverter serial, so it should be the same.

[usrpend]

Same problem here. I was using v2.6.5. If I disable the old devices, this also rises one more issue: the old sensors stats are not showing in Energy panel anymore.

[alexdelprete]

You shouldn't have 2 devices because the unique_id remains the same.

can you please open .storage/core.device_registry file in the editor and look for abb_powerone_pvi_sunspec. Be careful not to modify anything...it's a critical HA file.

You should find only one instance, like this one:

      {
        "area_id": null,
        "config_entries": [
          "54dcc9b0ac601ef0a7d78ebcd861cc76"
        ],
        "configuration_url": null,
        "connections": [],
        "disabled_by": "config_entry",
        "entry_type": null,
        "hw_version": null,
        "id": "935c4542399356b8c2b7293120faf791",
        "identifiers": [
          [
            "abb_powerone_pvi_sunspec",
            "077909-3G82-3112"
          ]
        ],
        "manufacturer": "Power-One",
        "model": "PVI-10.0-OUTD",
        "name_by_user": null,
        "name": "ABB VSN300",
        "sw_version": "C008",
        "via_device_id": null
      },

The identifiers are unique, because I used the s/n of the inverter, so a duplication isn't possible.

In .storage/core.entity_registry you can look for the sensors, and you will see that the unique_id starts with the s/n of the device, and that config_entry_id and device_id match the ones of the device (it's how sensor entities are associated to the device).

      {
        "aliases": [],
        "area_id": null,
        "capabilities": null,
        "config_entry_id": "54dcc9b0ac601ef0a7d78ebcd861cc76",
        "device_class": null,
        "device_id": "935c4542399356b8c2b7293120faf791",
        "disabled_by": "config_entry",
        "entity_category": null,
        "entity_id": "sensor.abb_vsn300_manufacturer",
        "hidden_by": null,
        "icon": null,
        "id": "24010e2479d6848bbcfb79b210e39760",
        "has_entity_name": true,
        "name": null,
        "options": {
          "conversation": {
            "should_expose": false
          }
        },
        "original_device_class": null,
        "original_icon": "mdi:information-outline",
        "original_name": "Manufacturer",
        "platform": "abb_powerone_pvi_sunspec",
        "supported_features": 0,
        "translation_key": null,
        "unique_id": "077909-3G82-3112_comm_manufact",
        "unit_of_measurement": null
      },

Please let me know what you and @dexmorgan8888 find in those files.

Thanks.

[dexmorgan8888]

I upgraded from v2.6.6 or v2.6.5

In the core.device_registry, there are 2 instances of abb:

   {
    "area_id": null,
    "config_entries": [
      "f6ab50a9ada5b7aa61317b10e07d5fbc",
      "37900e16beb740da63e3f070624f810a",
      "f7d3846e5ace4101016f403e6e98d3fb",
      "93cb36a6a3282fb88e9a0ab24d54ae51"
    ],
    "configuration_url": null,
    "connections": [],
    "disabled_by": null,
    "entry_type": null,
    "hw_version": null,
    "id": "69f20b7764386cbe8f675fa73295afa1",
    "identifiers": [
      [
        "abb_powerone_pvi_sunspec",
        "Solar"
      ]
    ],
    "manufacturer": "FIMER\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000",
    "model": "PVI-12.5-OUTD-I",
    "name_by_user": null,
    "name": "Solar",
    "sw_version": "2149C\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000",
    "via_device_id": null
  },

and

  {
    "area_id": null,
    "config_entries": [
      "f6ab50a9ada5b7aa61317b10e07d5fbc"
    ],
    "configuration_url": null,
    "connections": [],
    "disabled_by": null,
    "entry_type": null,
    "hw_version": null,
    "id": "2cfe4cc90e533d1d12038d5f8b11bcec",
    "identifiers": [
      [
        "abb_powerone_pvi_sunspec",
        "22241081703Q019902000F"
      ]
    ],
    "manufacturer": "FIMER",
    "model": "PVI-12.5-OUTD-I",
    "name_by_user": null,
    "name": "Solar",
    "sw_version": "2149C",
    "via_device_id": null
  },

In core.entity_registry, there are 2 groups. I guess each group correspond to each device. Each group has around 20-30 entities. here are example of each group:

  {
    "aliases": [],
    "area_id": null,
    "capabilities": null,
    "config_entry_id": "f6ab50a9ada5b7aa61317b10e07d5fbc",
    "device_class": null,
    "device_id": "69f20b7764386cbe8f675fa73295afa1",
    "disabled_by": null,
    "entity_category": null,
    "entity_id": "sensor.solar_manufacturer",
    "hidden_by": null,
    "icon": null,
    "id": "7007db5f296ed2f80871fd1b6a37c562",
    "has_entity_name": false,
    "name": null,
    "options": {
      "conversation": {
        "should_expose": false
      }
    },
    "original_device_class": null,
    "original_icon": "mdi:information-outline",
    "original_name": "Solar (Manufacturer)",
    "platform": "abb_powerone_pvi_sunspec",
    "supported_features": 0,
    "translation_key": null,
    "unique_id": "Solar_comm_manufact",
    "unit_of_measurement": null
  },

and

  {
    "aliases": [],
    "area_id": null,
    "capabilities": null,
    "config_entry_id": "f6ab50a9ada5b7aa61317b10e07d5fbc",
    "device_class": null,
    "device_id": "2cfe4cc90e533d1d12038d5f8b11bcec",
    "disabled_by": null,
    "entity_category": null,
    "entity_id": "sensor.solar_manufacturer_2",
    "hidden_by": null,
    "icon": null,
    "id": "d53863266e94d520205735551eda6561",
    "has_entity_name": true,
    "name": null,
    "options": {
      "conversation": {
        "should_expose": false
      }
    },
    "original_device_class": null,
    "original_icon": "mdi:information-outline",
    "original_name": "Manufacturer",
    "platform": "abb_powerone_pvi_sunspec",
    "supported_features": 0,
    "translation_key": null,
    "unique_id": "22241081703Q019902000F_comm_manufact",
    "unit_of_measurement": null
  },

Thanks for following up

[alexdelprete]

The device with "id": "69f20b7764386cbe8f675fa73295afa1" is an old one, created with early releases of the component, you can see that from the indentifier, that doesn't contain the s/n but the device name:

    "identifiers": [
      [
        "abb_powerone_pvi_sunspec",
        "Solar"
      ]
    ],

I would suggest to clean up things by deleting both devices and readding the inverter from scratch. That means you will lose the history of sensors though.

Or you can just delete the old device and the associated sensors.

Regarding the energy integration, you will simply have to add to it the energy sensors used.

[dexmorgan8888]

Ouch.... Was afraid you would say that
But still, thanks!

[alexdelprete]

Ouch.... Was afraid you would say that But still, thanks!

That change (the s/n as device_id and unique_id of entities) has been introduced several versions ago, so you had 2 devices since a long time. I remember writing a note about this, in case it happened.

I think what happened is that you were using an older version (before that change), and now that you upgraded to latest, it created the new device.

Actually, there's a way to not lose history: you need to point the "old" sensors to the new device, but you need to change several things for each sensor and it's not a clean solution.