I'm running Core 2026.5.4, Frontend 20260429.4, on a Home Assistant Docker Container...
When asking the Claude conversation agent to set a timer or do anything with a delay (e.g. "turn off the desktop in 2 minutes"), it responds with "This device is not able to start timers" rather than attempting the action.
This looks like the same issue reported in #160565. The HassStartTimer and HassDecreaseTimer tools generate JSON schemas with anyOf at the top level, which the Anthropic API rejects with a 400 error. The timer tools end up silently unavailable.
The bug was first reported against 2026.1.0. Still seeing it on 2026.5.4. Has anyone managed to fix this or found a workaround?
Here are some of my thoughts (which may not be entirely accurate/up-to-date):
I came across a fix for the anyOf issue you referred to, but this particular fix was for the open router CA which also seems to have the same anyOf problem. After taking a look at the current HA claude integration code, I see the same fix there, so I don't think the anyOf schema is a problem now.
Looking at OpenAI CA logs, I see that HA has added text to the prompt and the prompt contains the sentence: This device is not able to start timers. My guess is that the same has been done for anthropic CA.
Having said the above, I'm not sure how this would work anyway, as HA core doesn't support dynamic timer creation. The VAPE however does support dynamic timer creation and local sentence intent processing that keys off of "timer" knows to use the VAPE for this; So as far as I can tell, using the VAPE (or similar satellite) is the only way to use timers in the pipeline.