Open screenagerbe opened 4 months ago
Got the same - will try the workaround and let you know how I get on.
Sorry about this. This was my fault. It's fixed in https://github.com/nathanmarlor/foxess_em/pull/356.
You can also fix this without removing and re-added, by sshing into your HA and editing config/.storage/core.config_entries
Search for the foxess_em section and change:
"version": 1 to "version": 2
You'll need to restart HA for this to take effect. You still need to reconfigure the integration either via the UI or you can add a line in the file above
"fox_api_key": "
making sure to observe JSON rules about trailing commas.
Try v1.9.1 please :)
Will do ;)
On Mon, 4 Mar 2024 at 15:01, Nathan Marlor @.***> wrote:
Try v1.9.1 please :)
— Reply to this email directly, view it on GitHub https://github.com/nathanmarlor/foxess_em/issues/354#issuecomment-1976781293, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE5PC2FPQJX6P5YFOQYFZ23YWSEDXAVCNFSM6AAAAABECJVF42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZWG44DCMRZGM . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Version of the custom_component
1.9.0
Configuration
Describe the bug
After upgrading from version 1.8.0 and restarting HA the integration would not load. It said Migration Failed on the integrations page and all values had status
unknown
. Solcast was also down.In the HA logs I saw this "Warning"
Workaround