actions input_number increment and decrement do not function anymore after upgrade to HA core 2026.8.0

[Cimpel]

The problem

the action action: input_number.decrement
target:
entity_id: input_number.xyz gives an error "Actie input_number/increment kon niet worden uitgevoerd. 'InputNumber' object has no attribute '_step'

It used to work in 2026.7.x

What version of Home Assistant Core has the issue?

2026.8.0

What was the last working version of Home Assistant Core?

2026.7.0

What type of installation are you running?

Home Assistant OS

Integration causing the issue

it's a yaml template

Link to integration documentation on our website

No response

Diagnostics information

Logger: homeassistant.helpers.script.websocket_api_script
Bron: helpers/script.py:573
Eerst voorgekomen: 15:20:33 (1 gebeurtenis)
Laatst gelogd: 15:20:33

websocket_api script: Error executing script. Unexpected error for call_service at pos 1: 'InputNumber' object has no attribute '_step'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 573, in _async_step
await getattr(self, handler)()
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1081, in _async_step_call_service
response_data = await self._async_run_long_action(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...<9 lines>...
)
^
File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 683, in _async_run_long_action
return await long_task
^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 2961, in async_call
response_data = await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/core.py", line 3004, in _execute_service
return await target(service_call)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 906, in entity_service_call
response_data = await _async_handle_entity_calls(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...<5 lines>...
)
^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 785, in _async_handle_entity_calls
single_result = await entity.async_request_call(_with_context(entity, coro))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1710, in async_request_call
return await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 780, in _with_context
return await coro
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 864, in _handle_single_entity_call
result = await task
^^^^^^^^^^
File "/config/custom_components/spook/ectoplasms/input_number/services/increment.py", line 37, in async_handle_service
amount = call.data.get("amount", entity._step) # noqa: SLF001
^^^^^^^^^^^^
AttributeError: 'InputNumber' object has no attribute '_step'. Did you mean: 'step'?

Example YAML snippet

type: custom:button-card
layout: grid
styles:
  card:
    - padding: 0 8px 0 8px
    - height: 48px
    - background: dark
    - box-shadow: none
    - padding-right: 24px
    - background-color: '#2b2b2b'
    - border-radius: 8px
  grid:
    - grid-template-columns: auto 1fr 32px 40px 32px
    - grid-template-areas: '"label spacer minus value plus"'
    - column-gap: 4px
    - align-items: center
custom_fields:
  label:
    card:
      type: custom:button-card
      name: PV Limiter Offset (W)
      styles:
        card:
          - background: dark
          - height: 24px
          - padding: 4px 8px
          - border-radius: 6px
          - background-color: '#2b2b2b'
          - border: none
          - margin-left: 8px
        name:
          - color: white
          - font-size: 14px
  spacer:
    card:
      type: custom:button-card
      styles:
        card:
          - background: dark
          - box-shadow: none
          - background-color: '#2b2b2b'
          - border: none
  minus:
    card:
      type: custom:button-card
      name: −
      tap_action:
        action: call-service
        service: input_number.decrement
        service_data:
          entity_id: input_number.pv_limiter_offset
      styles:
        card:
          - width: 32px
          - height: 32px
          - background-color: '#2b2b2b'
          - border-radius: 4px
        name:
          - color: white
          - font-size: 20px
  value:
    card:
      type: custom:button-card
      entity: input_number.pv_limiter_offset
      show_state: true
      show_name: false
      show_icon: false
      styles:
        card:
          - width: 40px
          - height: 32px
          - background: dark
          - background-color: '#2b2b2b'
          - border: none
        state:
          - color: white
          - font-size: 12px
          - text-align: center
  plus:
    card:
      type: custom:button-card
      name: +
      tap_action:
        action: call-service
        service: input_number.increment
        service_data:
          entity_id: input_number.pv_limiter_offset
      styles:
        card:
          - width: 32px
          - height: 32px
          - background-color: '#2b2b2b'
          - border-radius: 4px
        name:
          - color: white
          - font-size: 20px

Anything in the logs that might be useful for us?

Additional information

No response

[jmcruvellier]

Same error since 2026.8.0 upgrade.
This automation worked before and for more than 2 years:

And now failing with same error:

[mbo18]

Do you have spook integration? If yes disable it

[jmcruvellier]

Do you have spook integration? If yes disable it

Yes, and I do confirm that by disabling Spook it is working again!
Thanks for the tip 😉

[Cimpel]

Disabling Spook did the trick. Spook update required?! Op vr 7 aug 2026 om 19:55 schreef mbo18 ***@***.***>:

…

*mbo18* left a comment (home-assistant/core#178467) <#178467 (comment)> Do you have spook integration? If yes disable it — Reply to this email directly, view it on GitHub <#178467?email_source=notifications&email_token=BJDX73257KZTGZ3FGSWY3ZT5IYJYZA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMRSGAZTMNJWG4YKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-5220365670>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BJDX7342WFNN5IZBI4DIVB35IYJYZAVCNFSNUABEKJSXA33TNF2G64TZHMYTEOBYHA4TSMZ3JFZXG5LFHM2TAOJQGYZDEOBRHGQXMAQ> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/BJDX73Y6KM7ZH6KJR6J2BU35IYJYZA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMRSGAZTMNJWG4YKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/BJDX73YVAY424QDFNFJI7RD5IYJYZA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMRSGAZTMNJWG4YKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

[jmcruvellier]

Disabling Spook did the trick. Spook update required?!

Op vr 7 aug 2026 om 19:55 schreef mbo18 @.***>:

mbo18 left a comment (#178467)
#178467 (comment)

Do you have spook integration? If yes disable it

—
Reply to this email directly, view it on GitHub
#178467,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJDX7342WFNN5IZBI4DIVB35IYJYZAVCNFSNUABEKJSXA33TNF2G64TZHMYTEOBYHA4TSMZ3JFZXG5LFHM2TAOJQGYZDEOBRHGQXMAQ
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
https://github.com/notifications/mobile/ios/BJDX73Y6KM7ZH6KJR6J2BU35IYJYZA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMRSGAZTMNJWG4YKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG
and Android
https://github.com/notifications/mobile/android/BJDX73YVAY424QDFNFJI7RD5IYJYZA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMRSGAZTMNJWG4YKM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA.
Download it today!
You are receiving this because you authored the thread.Message ID:
@.***>

Yes there is already an issue raised on Spook integration repo, don't know when it will be fixed

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (input_number) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of input_number can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign input_number Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the issue.

_{^{(message by CodeOwnersMention)}}

---

@Cimpel Thanks for reporting this issue!

Before we dive in, please make sure this isn't a duplicate by searching through existing issues. Also check recently closed issues, as your problem might already be fixed but not yet released.

https://github.com/home-assistant/core/issues?q=%20label%3A%22integration%3A%20input_number%22%20
_{^{(message by IssueContext)}}

---

input_number documentation
input_number source
_{^{(message by IssueLinks)}}

[mib1185]

as proofed by many users, the cause is the custom integration spook and corresponding issue report is already open here.
As this is an issue caused by a custom component, which is not maintained by the Home Assistant project, I'm going to close this issue report.
thx 👍