Since updating to 2023.2.0 I’m getting a heap of these on restart before my modbus returns actual values:
Sensor sensor.iammeter_3_modbus_exportgrid_sum has device class energy, state class total_increasing and unit kWh thus indicating it has a numeric value; however, it has the non-numeric value: unavailable (<class 'str'>); Please update your configuration if your entity is manually configured, otherwise create a bug report
Once it all loads and a numeric value appears it is fine.
I test for “unavailable” in subsequent filter entities based on the underlying modbus entities (i.e. I WANT it to be “unavailable” if it is not there, as I test for that) - so am I right in thinking I can ignore the errors?
This is my modbus definition for the sensor noted in the error above:
- name: Iammeter_3_modbus_ExportGrid_SUM
unique_id: 2452716747647
slave: 1
address: 36
input_type: holding
unit_of_measurement: kWh
device_class: energy
state_class: total_increasing
count: 2
scale: 0.00125
offset: 0
precision: 2
data_type: uint32