I’ve had a few light switches tracking their energy use for a year or two without issue. About 3 weeks ago I added an Emporia Vue flashed with ESPHome to do whole-home energy monitoring along with several circuits. This worked great in the energy dashboard for a few days, but then all of my energy reports started showing 0, even the light switches that had been working for a long time.
I went to my history dashboard to prove to myself that I’m still collecting data reliably, but it seems I’m getting way fewer data points than I thought I was. So my issue is likely related to this. Any idea how to fix this?
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service mariadb-pre: starting
[09:06:42] INFO: Using existing mariadb
s6-rc: info: service mariadb-pre successfully started
s6-rc: info: service mariadb-core: starting
s6-rc: info: service mariadb-core successfully started
s6-rc: info: service mariadb-post: starting
[09:06:42] INFO: Starting MariaDB
2023-10-10 9:06:42 0 [Note] Starting MariaDB 10.6.12-MariaDB source revision 4c79e15cc3716f69c044d4287ad2160da8101cdc as process 66
2023-10-10 9:06:42 0 [Note] mysqld: Aria engine: starting recovery
tables to flush: 2 1 0
(0.0 seconds);
2023-10-10 9:06:42 0 [Note] mysqld: Aria engine: recovery done
2023-10-10 9:06:42 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-10-10 9:06:42 0 [Note] InnoDB: Number of pools: 1
2023-10-10 9:06:42 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2023-10-10 9:06:42 0 [Note] mysqld: O_TMPFILE is not supported on /var/tmp (disabling future attempts)
2023-10-10 9:06:42 0 [Note] InnoDB: Using Linux native AIO
2023-10-10 9:06:42 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
2023-10-10 9:06:42 0 [Note] InnoDB: Completed initialization of buffer pool
2023-10-10 9:06:42 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=621618896939,621621884509
2023-10-10 9:06:42 0 [Note] InnoDB: Starting final batch to recover 3426 pages from redo log.
2023-10-10 9:06:43 0 [Note] InnoDB: 128 rollback segments are active.
2023-10-10 9:06:43 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"
2023-10-10 9:06:43 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2023-10-10 9:06:43 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-10-10 9:06:43 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2023-10-10 9:06:43 0 [Note] InnoDB: 10.6.12 started; log sequence number 621623347956; transaction id 22675730
2023-10-10 9:06:43 0 [Note] InnoDB: Loading buffer pool(s) from /data/databases/ib_buffer_pool
2023-10-10 9:06:43 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-10-10 9:06:43 0 [Note] Server socket created on IP: '0.0.0.0'.
2023-10-10 9:06:43 0 [Note] Server socket created on IP: '::'.
2023-10-10 9:06:43 0 [Note] InnoDB: Buffer pool(s) load completed at 231010 9:06:43
2023-10-10 9:06:43 0 [Note] mysqld: ready for connections.
Version: '10.6.12-MariaDB' socket: '/run/mysqld/mysqld.sock' port: 3306 MariaDB Server
[09:06:43] INFO: MariaDB started
[09:06:43] INFO: Check data integrity and fix corruptions
mysql.column_stats OK
mysql.columns_priv OK
mysql.db OK
mysql.event OK
mysql.func OK
mysql.global_priv OK
mysql.gtid_slave_pos OK
mysql.help_category OK
mysql.help_keyword OK
mysql.help_relation OK
mysql.help_topic OK
mysql.index_stats OK
mysql.innodb_index_stats OK
mysql.innodb_table_stats OK
mysql.plugin OK
mysql.proc OK
mysql.procs_priv OK
mysql.proxies_priv OK
mysql.roles_mapping OK
mysql.servers OK
mysql.table_stats OK
mysql.tables_priv OK
mysql.time_zone OK
mysql.time_zone_leap_second OK
mysql.time_zone_name OK
mysql.time_zone_transition OK
mysql.time_zone_transition_type OK
mysql.transaction_registry OK
homeassistant.event_data OK
homeassistant.event_types OK
homeassistant.events OK
homeassistant.recorder_runs OK
homeassistant.schema_changes OK
homeassistant.state_attributes OK
homeassistant.states OK
homeassistant.states_meta OK
homeassistant.statistics OK
homeassistant.statistics_meta OK
homeassistant.statistics_runs OK
homeassistant.statistics_short_term OK
sys.sys_config OK
[09:06:43] INFO: Ensuring internal database upgrades are performed
[09:06:43] INFO: Ensure databases exists
[09:06:44] INFO: Create database homeassistant
[09:06:44] INFO: Ensure users exists and are updated
[09:06:44] INFO: Update user homeassistant
[09:06:44] INFO: Init/Update rights
[09:06:44] INFO: Granting all privileges to homeassistant on homeassistant
[09:06:44] INFO: Sending service information to Home Assistant
s6-rc: info: service mariadb-post successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
I’ve checked the history from zigbee, z-wave, and esphome entities and they are all affected.
Well, I’m not really sure what is going on, but I am now seeing granular history from about 9 am (prior to me posting my issue) and there is data in my energy dashboard again. The new server has only been online since some time overnight when it finished importing its backup, so maybe something about the new install fixed it and it just needed some time to shake things loose? I’ll consider it fixed for now. If it comes back, I’ll post here again.
