Numeric state .. 00:02:00 cannot be processed as a number. But no time in automation

Configuration
1

Logbook shows the above warning, 2000 times .
I cannot find the origin of the error.

The automation is one of the most run automation I have: The light control of the ‘eethoek’, where I pass all day going in-/outside.
Therefore I have 2 RF PIR detectors(NodeRed mqtt), 2 zigbee PIRs, and a zigbee ‘human’ microwave detector and 2 zigbee lumi detectors, controlling 3 tuya spotlights.
The automation uses several timers and scripts.

Warning:

Eerst voorgekomen: 14 juni 2025 om 12:42:34 (2063 gebeurtenissen)
Laatst gelogd: 12:06:41

Error in 'De Enige Eethoek timer automation, 10m' trigger: In 'numeric_state' condition: entity timer.eethoek_timer_30 state '0:04:00' cannot be processed as a number
Error in 'De Enige Eethoek timer automation, 10m' trigger: In 'numeric_state' condition: entity timer.eethoek_timer_30 state '0:02:00' cannot be processed as a number
Error in 'websocket_api' trigger: In 'numeric_state' condition: entity timer.eethoek_timer_30 state '0:04:00' cannot be processed as a number

Automation:

d: '1705931657483'
alias: De Enige Eethoek timer automation, 10m
description: ''
triggers:
  - entity_id:
      - timer.eethoek_timer_30
    attribute: remaining
    to: '55'
    id: minuut
    trigger: state
  - topic: home/node/cmnd/eethoek
    payload: 'on'
    id: eethoek on
    trigger: mqtt
    enabled: false
  - topic: home/node/cmnd/eethoek
    payload: 'off'
    id: eethoek off
    trigger: mqtt
    enabled: false
  - type: motion
    device_id: 060a775422d3420df5b2910039e927a9
    entity_id: a6bc7b0539d0ca35a12838620e5cb450
    domain: binary_sensor
    id: eethoek on
    trigger: device
    enabled: true
  - entity_id:
      - timer.eethoek_timer_30
    to: idle
    id: eethoek off
    trigger: state
    enabled: false
  - entity_id:
      - timer.eethoek_timer_30
    to: idle
    from: null
    for:
      hours: 0
      minutes: 0
      seconds: 6
    id: eethoek off
    trigger: state
  - type: motion
    device_id: 001e5c2528a16c947e3908ae81419e91
    entity_id: 62c7a7dc1c4301112cb942c4bfc644cd
    domain: binary_sensor
    id: eethoek on
    trigger: device
  - topic: home/RF/cmnd/pir6
    payload: 'on'
    id: eethoek on
    alias: pir 6 on
    trigger: mqtt
    enabled: true
  - alias: pir 10 on
    topic: home/RF/cmnd/pir10
    payload: 'on'
    id: eethoek on
    trigger: mqtt
    enabled: true
  - trigger: state
    entity_id:
      - light.eethoek_1
    to: 'on'
    id: aangezet
    for:
      hours: 0
      minutes: 0
      seconds: 20
  - trigger: state
    entity_id:
      - light.eethoek_2
    to: 'on'
    id: aangezet
    for:
      hours: 0
      minutes: 0
      seconds: 25
  - trigger: state
    entity_id:
      - light.eethoek_3
    to: 'on'
    id: aangezet
    for:
      hours: 0
      minutes: 0
      seconds: 30
  - trigger: numeric_state
    entity_id:
      - timer.eethoek_timer_30
    attribute: remaining
    below: 59
    id: minuut
  - trigger: state
    entity_id:
      - input_boolean.manuuit_eethoek
    to: 'off'
    from: 'on'
    for:
      hours: 0
      minutes: 0
      seconds: 10
    id: aangezet
  - type: occupied
    device_id: 55f407ca96dc777a7192b1ed3e1106eb
    entity_id: b8f1fd9975ba7f222b1e5d6cccc2e7b7
    domain: binary_sensor
    trigger: device
    id: Humandetect
    alias: ZbmwPir Human detected
conditions: []
actions:
  - choose:
      - conditions:
          - condition: trigger
            id:
              - aangezet
          - condition: not
            conditions:
              - condition: state
                entity_id: timer.eethoek_timer_30
                state: active
            alias: als timer niet actief
          - condition: or
            conditions:
              - condition: device
                type: is_on
                device_id: ee939c997a2841d5410531809675c463
                entity_id: a9fbdfa4be41f7ef399f8f3444b85d6a
                domain: light
              - condition: device
                type: is_on
                device_id: 10a97eb0b56988c4623f7038c36e8606
                entity_id: 1ecb96150826c628415e38993152efcb
                domain: light
              - condition: device
                type: is_on
                device_id: db24262f5e3061bc1463ae4a4345b1b5
                entity_id: c4bf88b6ac8a0eba02b337bb3c05699f
                domain: light
            alias: Als er een van de lampn aan is(en/of)
          - condition: state
            entity_id: input_boolean.manuuit_eethoek
            state: 'off'
        sequence:
          - action: timer.start
            metadata: {}
            data: {}
            target:
              entity_id: timer.eethoek_timer_30
      - conditions:
          - condition: trigger
            id:
              - eethoek on
        sequence:
          - data:
              duration: '240'
            target:
              entity_id: timer.eethoek_timer_30
            action: timer.start
          - if:
              - condition: or
                conditions:
                  - condition: device
                    type: is_off
                    device_id: ee939c997a2841d5410531809675c463
                    entity_id: a9fbdfa4be41f7ef399f8f3444b85d6a
                    domain: light
                  - condition: device
                    type: is_off
                    device_id: 10a97eb0b56988c4623f7038c36e8606
                    entity_id: 1ecb96150826c628415e38993152efcb
                    domain: light
                  - condition: device
                    type: is_off
                    device_id: db24262f5e3061bc1463ae4a4345b1b5
                    entity_id: c4bf88b6ac8a0eba02b337bb3c05699f
                    domain: light
            then:
              - data: {}
                action: script.eethoek_aan_2
            alias: als er een lamp niet aan, doe die aan
      - conditions:
          - condition: trigger
            id:
              - eethoek off
        sequence:
          - data: {}
            action: script.eethoek_aan
          - action: timer.start
            metadata: {}
            data: {}
            target:
              entity_id: timer.eethoek_uit_tijd
      - conditions:
          - condition: trigger
            id:
              - minuut
        sequence:
          - alias: >-
              Als geen human detected in laatste 10 minuten, zet lampen 1 voor 1
              uit
            if:
              - condition: not
                conditions:
                  - condition: state
                    entity_id: timer.humandetected
                    state: active
            then:
              - action: light.turn_off
                metadata: {}
                data: {}
                target:
                  entity_id: light.eethoek_3
              - delay:
                  hours: 0
                  minutes: 0
                  seconds: 30
                  milliseconds: 0
              - if:
                  - condition: device
                    type: is_off
                    device_id: db24262f5e3061bc1463ae4a4345b1b5
                    entity_id: c4bf88b6ac8a0eba02b337bb3c05699f
                    domain: light
                then:
                  - type: turn_off
                    device_id: 10a97eb0b56988c4623f7038c36e8606
                    entity_id: 1ecb96150826c628415e38993152efcb
                    domain: light
                else:
                  - stop: beweging na eeth3 uit
              - delay:
                  hours: 0
                  minutes: 0
                  seconds: 30
                  milliseconds: 0
              - if:
                  - condition: device
                    type: is_off
                    device_id: 10a97eb0b56988c4623f7038c36e8606
                    entity_id: 1ecb96150826c628415e38993152efcb
                    domain: light
                then:
                  - type: turn_off
                    device_id: ee939c997a2841d5410531809675c463
                    entity_id: a9fbdfa4be41f7ef399f8f3444b85d6a
                    domain: light
                else:
                  - stop: beweging na 2 uit
        alias: 'timer <1min: lamp3 uit, <30:lamp2'
      - conditions:
          - condition: trigger
            id:
              - Humandetect
        sequence:
          - action: timer.start
            metadata: {}
            data: {}
            target:
              entity_id:
                - timer.humandetected
mode: parallel
max: 5

NodeRed handles all RF codes by comparing the mqtt codes to a list and returning a MQTT like ‘pir6 ON’ and a few seconds later "pir6 OFF’

2

I’m very confused about the yaml.
But perhaps it’s all a misunderstanding. Timers shouldn’t be used with state triggers.
They use events.

3

I do not use a lot of yaml, it confuses me. The automation is made with the UI.
Besides… I never use timer.finished or similar ‘events’ because they fail to trigger anything. I use the moment the timer switches to idle.

4

Ok…
What are you trying to do.
I really don’t understand it all.
As said you should remove these that use state triggers where events exist.

  - entity_id:
      - timer.eethoek_timer_30
    to: idle
    from: null
    for:
      hours: 0
      minutes: 0
      seconds: 6
    id: eethoek off
    trigger: state

and catching the moment the attribute is 55 might work, but not like this.

  - entity_id:
      - timer.eethoek_timer_30
    attribute: remaining
    to: '55'
    id: minuut
    trigger: state

If anything then it should be 0:00:55
But I’m not sure that works either.

6

I’m looking into scripts now. The timer default has a time of 0:20:00 but the timer is started always at 0:04:00 .
It is actually in this automation, triggered by a light to come on. (capturing also manual control). The ‘240’ mentioned.

7

Try using the developer tools instead.
The UI shows beautified values

8

I took out the ‘240’ in timer duration and got rid of one warning. However… the 240 seems to have been translated well to 0:04:00 .
Now one remaining: What is the websocket.api??

Logger: homeassistant.components.homeassistant.triggers.numeric_state
Bron: components/homeassistant/triggers/numeric_state.py:149
integratie: Home Assistant Core Integration (documentatie, problemen)
Eerst voorgekomen: 12:44:28 (6 gebeurtenissen)
Laatst gelogd: 13:06:04

Error initializing 'websocket_api' trigger: In 'numeric_state' condition: entity timer.eethoek_timer_30 state '0:04:00' cannot be processed as a number
Error initializing 'De Enige Eethoek timer automation, 10m' trigger: In 'numeric_state' condition: entity timer.eethoek_timer_30 state '0:04:00' cannot be processed as a number

(cleared log 10 minutes ago)

Changed default timer delay to 0:10:00.

Logger: homeassistant.components.homeassistant.triggers.numeric_state
Bron: components/homeassistant/triggers/numeric_state.py:202
integratie: Home Assistant Core Integration (documentatie, problemen)
Eerst voorgekomen: 12:36:22 (56 gebeurtenissen)
Laatst gelogd: 13:12:50

Error in 'websocket_api' trigger: In 'numeric_state' condition: entity timer.eethoek_timer_30 state '0:10:00' cannot be processed as a number
Error in 'De Enige Eethoek timer automation, 10m' trigger: In 'numeric_state' condition: entity timer.eethoek_timer_30 state '0:10:00' cannot be processed as a number
Error in 'De Enige Eethoek timer automation, 10m' trigger: In 'numeric_state' condition: entity timer.eethoek_timer_30 state '0:02:00' cannot be processed as a number
Error in 'De Enige Eethoek timer automation, 10m' trigger: In 'numeric_state' condition: entity timer.eethoek_timer_30 state '0:04:00' cannot be processed as a number
Error in 'websocket_api' trigger: In 'numeric_state' condition: entity timer.eethoek_timer_30 state '0:04:00' cannot be processed as a number

dev tools:

timer.eethoek_timer_30
eethoek timer 30
active	duration: 0:04:00
editable: true
finishes_at: 2025-06-16T11:22:06+00:00
remaining: 0:04:00
restore: true
icon: mdi:table-chair
friendly_name: eethoek timer 30
9

After restart HA, the error warning happened only once at the start.
I guess …Problem solved.

the only remaining warning is python related, which is not mine to solve.

Logger: py.warnings
Bron: components/cast/__init__.py:7
Eerst voorgekomen: 13:20:39 (1 gebeurtenis)
Laatst gelogd: 13:20:39

/usr/local/lib/python3.13/site-packages/google/__init__.py:2: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81. __import__('pkg_resources').declare_namespace(__name__)
10 
Data attribute	Optional	Description
entity_id	no	Name of the entity to take action, e.g., timer.timer0.
duration	no	Duration in seconds or 00:00:00 to add or subtract from the running timer.

as it says, both should work

source: Events

11

I don’t know where you are getting that text from.

EDIT is that from the action timer.start?
That isn’t the same as triggers and conditions.

12

Action timer.change

13

I see what you mean. The event is to set a duration, not to trigger something because of what timer.duration is currently at.

the kicker here is that de Dutch translation of the attribute uses a timer.resterend (which translates back to timer.whatsLeftOfit )

the dutch ui attributes :    and english translations
Duur                                Durations
Resterend                       Whats left of it
Eindigt om                       Finishes at
Herstellen                        Recover

attributes are not documented

14

And that is the main reason why I have most of my softwares in English.
I don’t want translations making it harder for me.

Anyways…
Did 0:00:55 work? If not then you might need a template that splits and makes it to seconds.

15

just to avoid time notation issues I use ‘55’ seconds , and that works.
However in previous years I was using different issues (HA OS works best for me) like Ubuntu with HA or HA in a container. Not in all of those did attributes work. Also sometime the attribute disappeared after an update.