v2.0.1: Entity update error when _0d expires

[genem2]

I could use some direction on this:
Home-Assistant: 2023.5.3 (container)
Wundergroundpws: v2.0.1

I reverted my HA back to 2022.4.6 and verified that my WU Sensors matched the documentation:
> API after 3:00pm Local Apparent Time. The affected sensors will return as "Today Expired" with a value of "—" when this condition is met.

entity: sensor.kcasanjo1654_forecast_temperature_0d
Friendly Name: Forecast Temperature Today Expired
State: —
unit_of_measurement: 
attribution: Data provided by the WUnderground weather service
device_class: temperature
icon: mdi:thermometer
friendly_name: Forecast Temperature Today Expired

But on 2023.5.3, all is fine until 15:00, when my log is bombarded with:

2023-05-15 16:02:49.128 ERROR (MainThread) [homeassistant.components.sensor] Error adding entities for domain sensor with platform wundergroundpws
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/sensor/__init__.py", line 579, in state
    numerical_value = int(value)
ValueError: invalid literal for int() with base 10: '—'

At this time, and until _0d returns the following day, the entity state (developer-tools/state or from a template render) remains as the previous numeric value, and friendly_name remains as Forecast Temperature Today. (Makes sense I guess, given the entity update failed.) If I restart HA, it reports as state:unavailable friendly_name:Forecast Temperature Today Expired.

So, would this be a custom_component issue, or something for HA?
Many thanks...

[genem2]

Well, it appears HA doesn't want Strings returned for these type of sensors:
ValueError: Sensor sensor.kcasanjo1654_forecast_temperature_0d has device class temperature, state class None unit and suggested precision None thus indicating it has a numeric value; however, it has the non-numeric value: — (<class 'str'>)

I don't know the proper way to resolve this, but as a temporary workaround:
I replaced all instances of else str('—'),
with: else int(0),
in my local custom_components\wundergroundpws\wupws_forecast_sensors.py file.

I guess this should be moved out of Discussions to Issues?

[cytech]

its already a known issue
at this point it is just a warning and goes away after a cycle until the next time HA is restarted

[genem2]

Apologies - can't believe I missed it...
FWIW: I'm not seeing it go away; it's 25 lines in the log every 5 min from 15:00-03:00.
Anyway, my workaround holds me until #169 is resolved. Tnx

[clau-bucur]

@cytech I've opened a bug ticket on this: https://github.com/cytech/Home-Assistant-wundergroundpws/issues/173
For me at least seems not to be a warning and it's persistent between restarts to the point that the _0d sensors got disabled and are now unavailable:

[cytech]

issue fixed in v2.0.2