search

ldotlopez / ha-ideenergy

ideenergy integration for home-assistant
GNU General Public License v3.0
73 stars 13 forks source link

I-DE logs in correctly, but data does not show up in energy dashboard (had corruputed database) #55

Closed hartmood closed 10 months ago

hartmood commented 11 months ago

Since the 4th of October, my energy dashboard and the I-DE consumption have not worked anymore. Probably, this has been caused by an update on the beta channel that corrupted my SQLite database. Multiple re-installations of SQLite, MariaDB, and I-DE did not bring back data to the energy dashboard. The energy dashboard is empty, and both relevant sensors show the data from the 4th. I can see that the I-DE energy plugin logs in correctly, but data needs to be written to the correct tables.

Describe the bug Data should show up as it did before the corrupt database.

To Reproduce I have deleted and reinstalled databases (Sqlite, MariaDB) or I-DE and have yet to return the energy board data successfully.

Environment Raspi 4 - no docker Home Assistant 2023.10.2 Supervisor 2023.10.0 Operating System 10.5 Frontend 20231005.0 - latest

Expected behavior Data written into the energy dashboard

Logs 2023-10-13 09:54:19.720 INFO (MainThread) [ideenergy] : '215315583' contract selected 2023-10-13 09:54:19.720 INFO (MainThread) [ideenergy] : successful authentication 2023-10-13 09:58:50.476 INFO (MainThread) [ideenergy] : '215315583' contract selected 2023-10-13 09:58:50.477 INFO (MainThread) [ideenergy] : successful authentication

Zsoltt-dom commented 10 months ago

Same here, no data is being shown. And it complains about a database error.

hartmood commented 10 months ago

In my case, the SQLite database was corrupted. All data is gone, unfortunately. Although I could set up a new database, I-DE still doesn’t work. Maybe I-DE was the cause of the troubles?

ldotlopez commented 10 months ago

Hi,

I didn't have enough information to check where the problem is.

I'm running myself the latest version both from Home Assistant and this integration without issues.

If you still can reproduce the bug enable debug with the '-v' switch from hass or adding this lines in the configuration and post the logs.

logger:
  default: warning
  logs:
    ideenergy: warning
    custom_components.ideenergy.datacoordinator: debug
    custom_components.ideenergy.sensor: debug
    custom_components.ideenergy.updates: debug
    custom_components.ideenergy.fixes: debug
    custom_components.ideenergy: debug
    homeassistant_historical_sensor: debug
hartmood commented 10 months ago

Hi,

I didn't have enough information to check where the problem is.

I'm running myself the latest version both from Home Assistant and this integration without issues.

If you still can reproduce the bug enable debug with the '-v' switch from hass or adding this lines in the configuration and post the logs.

logger:
  default: warning
  logs:
    ideenergy: warning
    custom_components.ideenergy.datacoordinator: debug
    custom_components.ideenergy.sensor: debug
    custom_components.ideenergy.updates: debug
    custom_components.ideenergy.fixes: debug
    custom_components.ideenergy: debug
    homeassistant_historical_sensor: debug
2023-10-18 16:29:26.615 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Request update for datasets: MEASURE
2023-10-18 16:29:26.616 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for MEASURE: update window is closed
2023-10-18 16:29:26.616 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Finished fetching b@xxxx.xxx/215315555 coordinator data in 0.001 seconds (success: True)
2023-10-18 16:33:56.616 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Request update for datasets: MEASURE
2023-10-18 16:33:56.616 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for MEASURE: update window is closed
2023-10-18 16:33:56.617 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Finished fetching b@xxxx.xxx/215315555 coordinator data in 0.001 seconds (success: True)
2023-10-18 16:38:26.616 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Request update for datasets: MEASURE
2023-10-18 16:38:26.617 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update denied for MEASURE: update window is closed
2023-10-18 16:38:26.617 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Finished fetching b@xxxx.xxx/215315555 coordinator data in 0.001 seconds (success: True)2023-10-18 18:45:33.895 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Finished fetching b@xxxx.xxx/215315555 coordinator data in 0.001 seconds (success: True)
2023-10-18 18:50:03.894 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Request update for datasets: MEASURE
2023-10-18 18:50:03.894 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for MEASURE
2023-10-18 18:50:05.119 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update error for MEASURE: Internal Server Error (500)
2023-10-18 18:50:05.119 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Finished fetching b@xxxx.xxx/215315555 coordinator data in 1.226 seconds (success: True)
hartmood commented 10 months ago

@ldotlopez Any idea?

hartmood commented 10 months ago 
2023-10-23 16:56:41.428 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Request update for datasets: MEASURE
2023-10-23 16:56:41.428 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update allowed for MEASURE
2023-10-23 16:56:41.708 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] update error for MEASURE: command error from API (CommandError({'success': 'false', 'message': 'Se ha producido un error en la aplicación'}))
2023-10-23 16:56:41.708 DEBUG (MainThread) [custom_components.ideenergy.datacoordinator] Finished fetching b@bube.net/215315583 coordinator data in 0.281 seconds (success: True)
hartmood commented 10 months ago

I have completely deleted the plugin and re-installed it. After trying to set up the integration, I received an authentication error. But I can log into the portal with the credentials. And they worked before. The profile shows as advanced. As the author mentioned, his setup still works: might there be an issue with the API?

hartmood commented 10 months ago

Iberdrola had an error, at least for me, for the last four weeks, plus my corrupted SQLite database. I checked this morning, and now I am back.