Z-wave error: has unit of measure and device class enum

OldSurferDude · October 2, 2026, 3:51am

I’m getting this ominous error message in the core logs:

ValueError: sensor: sensor.outdoor_motion_sensor_manual_motion_re_trigger_time_setting has a unit of measurement and thus indicating it has a numeric value, it has the non-numeric device class: enum
The yaml from Settings–>Tools–>States

restored: true
options:
  - 5 seconds (Test mode)
device_class: enum
friendly_name: Currant House Outdoor Motion Sensor Manual Motion Re-Trigger Time Setting
supported_features: 0
unit_of_measurement: seconds

This was automatically created when I added the device.
Any idea what the problem is?

petro · October 3, 2026, 10:57am

Yeah, it has a unit_of_measurement when it shouldn’t have that.

Your entity is coming through as a zwave list sensor

github.com/home-assistant/core

homeassistant/components/zwave_js/sensor.py

0a96db3c4


      
                          f"Failed to reset meters on node {node} endpoint {endpoint}: {err}"
                      ) from err
                  LOGGER.debug(
                      "Meters on node %s endpoint %s reset with the following options: %s",
                      node,
                      endpoint,
                      options,
                  )
          
          
          class ZWaveListSensor(ZwaveSensor):
              """Representation of a Z-Wave Numeric sensor with multiple states."""
          
              def __init__(
                  self,
                  config_entry: ZwaveJSConfigEntry,
                  driver: Driver,
                  info: ZwaveDiscoveryInfo,
                  entity_description: SensorEntityDescription,
                  unit_of_measurement: str | None = None,
              ) -> None:

Which does not set unit_of_measurement at any point. If you have the option in the UI to remove or change the unit of measurement, change it to None.

OldSurferDude · October 5, 2026, 4:37am

I deleted it, disconnected it from z-wave, factory reset, restarted HA, restarted the virtual machine and otherwise spent a couple of hours thrashing. Eventually I got it connected again.