Closed c0mputerguru closed 5 months ago
Given that you're also the owner for the home assistant integration, I'm curious on whether you'd prefer to add this, and then add the service point id as a part of the home assistant id prefix (https://github.com/home-assistant/core/blob/a385ca93bd0d5b7de4b8b20fe7cc34c006ab1aed/homeassistant/components/opower/coordinator.py#L99) or whether to bite the bullet and just use the uuid. Either will be a breaking change for folks given the name of the entity changes, but the uuid change should be the last case of it breaking.
Unfortunately I can't seem to find any documentation on the APIs to determine whether the utility account + service point id + meter type is unique enough, so the safest thing to do would be to use the uuid, but uuid's aren't very readable.
Closing since this isn't needed after https://github.com/home-assistant/core/pull/108616
I'm adding a service point id to be able to distinguish between multiple meters on a single account id. The use case is that I have 2 electric accounts when making the get customers API call; the first is consumption from the grid, and the second is my solar production. I'd like to be able to distinguish between the 2 of them, and while uuid can do it, I'd prefer to have something that is a little more human friendly. Ultimately I want to be able to pull both in as separate statistics in home assistant.
I have tested these changes on my personal account, and the Account field gets updated correctly for historical usage. I cannot test the forecasts as my provider (PSE) does not have forecasts.
All precommits have been run and pass.
My list of accounts looks like the following: