0.4.0 breaks the integration

[rthorntn]

Hi,

I had to rollback to 0.3.0 as for the life of me I couldn't get a setup dialog.

Core 2024.10.2
Supervisor 2024.10.0
Operating System 13.1
Frontend 20241002.3

Thanks.
Richard

[gurrier]

I have been able to reproduce the issue. Leave it with me.

[gurrier]

There was an omission in manifest.json. Now rectified. Can you try again at your convenience and let me know?

[entr0py79]

I had the same issue and rolled back to 0.3.0.
I have just rolled forward to 0.4.1 and it still breaks the integration for me.

This entity is no longer being provided by the localvolts integration. If the entity is no longer in use, delete it in settings.

Core 2024.10.2
Supervisor 2024.10.0
Operating System 13.0
Frontend 20241002.3

[gurrier]

@entr0py79 did you see a setup dialog to collect the three setup variables? Could you try commenting them out from the configuration.yaml and then performing the upgrade to 0.4.1?

#  api_key: "abc123abc123abc123abc123abc123ab"
#  partner_id: "12345"
#  nmi_id: "1234567890" #Ignore trailing checksum digit on Localvolts bill and dashboard

[rthorntn]

Thanks, is it safe to upgrade now?

Do we lose any functionality if we don't?

Will the sensor stay as earningsFlexUp as I was worried it might change and break my automations?

[gurrier]

@rthorntn

Please try it.

FYI I have completely removed the integration from my Home Assistant and re-added it. A dialog pops up when I install the integration which asks for the APIkey, partnerid and NMI. The sensor for earningsFlexUp still exists, as does costsFlexup.
There is also now implemented a sensor called DataLag which is the time delay at Localvolts until the latest interval data was successfully retrieved (handy to track the timeliness of Localvolts delivering latest pricing data to their customers. Typically it is within 30 seconds).
The integration now checks every 5 seconds at the start of each 5 minutes interval until it gets the latest data and is more efficient as it gets all sensor data on that one retrieval request now.

If you can try the 0.4.1 version now, please let me know what happens. If you have any difficulties, try removing it and re-adding it.

[gurrier]

I have just rolled forward to 0.4.1 and it still breaks the integration for me.

This entity is no longer being provided by the localvolts integration. If the entity is no longer in use, delete it in settings.

@entr0py79 If it says the entity is no longer being offered by the Localvolts integration, can you go into the Home Assistant settings, then Device and Services, then Integrations to check whether Localvolts is there? If it indicates that Localvolts is providing 3 entities (as it should) then click on the entities shown to see whether they are correctly populated with values.
Please let me know so I can resolve.

[gurrier]

@entr0py79 @rthorntn Can either of you confirm that you are successfully on latest version 0.4.2?

[entr0py79]

Confirmed. Working. Wasn't added via integrations only hacs and config.yaml entry.