[SOLVED] Z-Wave JS: Charting thermometer states? (Idle/Heat)

Hi,

I have MH7H wall thermostats - all works fine in HAOS (the integration communicates via websockets).

Some entities were automatically created:

  • climate.water_electrical_heating_thermostat_2
  • sensor.water_electrical_heating_thermostat_air_temperature_2
  • sensor.water_electrical_heating_thermostat_humidity_2
  • and some others (firmware, node status, …)

But I do not understand, how to access historical data for hvac_action (idle/heat) for charting purposes.

In Developer Tools // States I can see all the attributes of climate.water_electrical_heating_thermostat_2 entity:

hvac_modes:
  - 'off'
  - heat
min_temp: 7
max_temp: 35
preset_modes:
  - none
  - Energy heat
  - Away
current_temperature: 21.8
temperature: null
current_humidity: 53
hvac_action: idle
preset_mode: none
friendly_name: Bedroom - Thermostat
supported_features: 17

In Z-Wave JS, I can see the property named like [3-66-0-state] Operating state

Do I have to create a new entity manually? How?

When I check the “device” history, the hvac_action (aka Bedroom - Thermostat heating) is displayed for the past:

I am confused…

Tried Discord for help:

you want to create a sensor using the statistics platform. It isn’t specific to z-wave, so there is likely a better channel. Statistics - Home Assistant

and

In the past some platforms, climate in particular I think, use attributes for non-primary functionality, and not as separate entities. Temp/humidity are the obvious exceptions. If you think it’s worthwhile that the operating mode/state should be a separate entity, then put the discussion in
devs_zwave , or submit a PR and maybe it will be accepted. I think there’s been movement towards that design lately, but I’m not the authoritative source. For example, fan mode was added as a separate entity. Otherwise, a template entity is the best approach today.