Statistics Import Stops Working after Renaming Statistics Entity

[realk1ko]

I've had some issues during the setup the past few days as I assumed that the created sensor entities can be renamed. That doesn't seem to be the case however.

Steps to reproduce:

• Setup integration and let it import historic data
• Rename the statistics entity
• Wait until new data is available and the integration imports it

Result:

• The new data is imported via the original entity id (sensor.<zaehlpunkt_id>_statistics) and is shown as orphaned in the statistics dashboard
• The renamed entity shows a negative consumption for the day after the last historic usage data entry

[maia]

Probably related: If you have a "Spitzname" in https://smartmeter-web.wienernetze.at/#/anlagedaten, when installing the integration the created sensors will be named by this "Spitzname". But another part of the integration uses a hardcoded name for the sensor sensor.{zaehlpunktnummer}_statistics, without looking up the "real" name. So whenever you rename your sensor or it is created with a name and not a zaehlpunktnummer, you will run into issues until the other part of the integration does not assume the sensor name is always sensor.{zaehlpunktnummer}_statistics. @DarwinsBuddy I believe I mentioned this to you some weeks ago, but I didn't create an issue back then, so here it is. :)

As for the negative consumption, I'm also seeing this issue, but currently I do not have renamed sensors, so it might be unrelated. See #217.

[DarwinsBuddy]

@reox already suspected potential issues with this labeled name as he implemented the statistical import. I guess it has more value to have a consistent name than a mirrored label from WienerNetze. Especially when you can create a label yourself within HA.

I'll remove this functionality in the next release