No history for specific entity

1

Hi everyone,
I've installed smart meter devices which measures voltage, power, and current, via tuya integration. In the dashboard I'm getting values for all entities of the device:

image
image763×582 32.4 KB

Historic values are there for voltage and power but not for current.

image
image2445×730 43.1 KB

image
image2430×735 32.8 KB

I've queryed the DB directly but the result was an empty set.

What could cause this beahvior? Is this an integration issue? How would i debug this to find the roout cause?

Thanks!

2

Please tell us how you did this.
This is the official Docs about this. [1] [2]

Also How to help us help you - or How to ask a good question

  1. History - Home Assistant ↩ī¸Ž

  2. Recorder - Home Assistant ↩ī¸Ž

3

Fair enough. :wink:

Goal: Display historical data of the entity sensor.3_phase_wifi_smart_meter_phase_c_current.
Reason: The circuit is shutting down repeatetly, and I hope to see according data.
What I did so far:
I queried the DB (SQLite Web Add-on) for another entity of the same device (voltage):

SELECT
  datetime(st.start_ts, 'unixepoch', 'localtime') AS time,
  sm.statistic_id,
  st.mean,
  st.min,
  st.max,
  st.state
FROM statistics st
JOIN statistics_meta sm ON st.metadata_id = sm.id
WHERE sm.statistic_id = 'sensor.3_phase_wifi_smart_meter_phase_c_voltage'
ORDER BY st.start_ts DESC
LIMIT 1000;

the result set was as expected (snippet):slight_smile:

image
image1996×558 134 KB
.

The same query for a different entity (current) of the same device:

SELECT
  datetime(st.start_ts, 'unixepoch', 'localtime') AS time,
  sm.statistic_id,
  st.mean,
  st.min,
  st.max,
  st.state
FROM statistics st
JOIN statistics_meta sm ON st.metadata_id = sm.id
WHERE sm.statistic_id = 'sensor.3_phase_wifi_smart_meter_phase_c_current'
ORDER BY st.start_ts DESC
LIMIT 1000;

has an empty result set. I'm wondering why.

Here are all sensors, provided by the device:

image
image510×938 23.6 KB

All of them have history data, but the

  • Phase A current
  • Phase B current
  • Phase C current

entities

I'm running HA on a Synology VM:

  • Installation methodHome Assistant OS
  • Core2026.4.4
  • Supervisor2026.05.1
  • Operating System17.2
  • Frontend20260325.8
    approx. 330 devices, 2300 entities
4

I suggest trying with the HA built-in tools rather that trying to forensically determine how the database is designed and making conclusions off of that.

I did give you a couple of links that tell you how to make sure data is in the database and how to see it.

5

@Sir_Goodenough, I don't understand, what you want more from me.

As you can see from the first screenshots I've send, I used as a first step History to retrieve the values and was wondering why they are not showing up. Next step was accessing the DB with SQLite Web since Recorder is suggesting

[...] The default, and recommended, database engine is SQLite which does not require any configuration. The database is stored in your Home Assistant configuration directory (’/config/’) and is named home-assistant_v2.db . For details on the database structure, including available tables and columns, see the Database documentation. [...]

While I understand the requirement for a structured question and the necessary research, which I did, throwing two links for standard documentation over the fence is not really help. If you don't want or can help - fair enough.

I can say, having HA since 2021 heavily in production, I have a fair understanding what's going on under the hood. But I'm probably still scratching the surface. Hence, my request for support from the people who know what's going on in depth.

Thanks,
Damos

6

OK, so these entities are the only ones with an issue you are saying.

  • Make sure these are not excluded in some way using History integration.
  • Make sure all these are enabled in the Device screen, and not hidden.
  • Sometimes if they show up as diagnostic here it can change stuff. Might have to use customize to change that but not certain.
  • Look at the entities in Open your Home Assistant instance and show your state developer tools. and see if it all looks OK.
  • You could use the UI tools under the gear for the entity to try different attributes for the data.
  • Sometimes restarting HA or rebooting the host can clear up transient things, so don't rule that out.
7

Will do, @Sir_Goodenough!

1 Like
8

@Sir_Goodenough, thanks for your support. The reason was an awkward exclusion in the recorder settings. Sorry for the hassle.

Best -
Damos

1 Like