Open Mithras opened 3 weeks ago
It's incorrect for years: https://github.com/home-assistant/core/commit/d37a3cded059d0cde95eb5826ebf42a0e03f97dd but something has changed that now calling service with mismatched data type is throwing an error.
in services.yaml target is defined as object selector. That should accept both list and dictionary as far as I can see. not sure why it's not working then and what changed suddenly
I've been looking into websocket_api and telegram_bot components but can't seem to find a change that would trigger such an error
The problem
https://github.com/home-assistant/core/blob/dev/homeassistant/components/telegram_bot/services.yaml#L17 specifies
target
asobject
which is incorrect as expected value is actually an int or an array of ints.What version of Home Assistant Core has the issue?
2024.10.3
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
telegram_bot
Link to integration documentation on our website
https://www.home-assistant.io/integrations/telegram_bot/
Diagnostics information
AppDeemon app:
Result:
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response