M-R
(M R)
April 16, 2024, 8:12am
1
Hello everyone,
I have been looking for this problem for days, but can’t find any clues to solve it.
After updating to 2024.4.1, my automation displays the following message in the trace timeline:
Translation error: The intl string context variable “reason” was not provided to the string “Stopped for unknown reason {reason} at {time} (runtime: {executiontime} seconds)”
I have not changed anything in the automation and it worked before without any problems.
Any hints or tips on what I can do?
Many thanks in advance.
M-R
(M R)
April 19, 2024, 1:34pm
3
Hello @Sir_Goodenough .
Thanks for your message.
The YAML is the following:
alias: Licht Wohnzimmer
description: ""
trigger:
- platform: device
device_id: 18b234665cafd58dca7803bef7f50dfe
domain: bosch_shc
type: PRESS_LONG
subtype: LOWER_BUTTON
id: lange
- platform: device
device_id: 18b234665cafd58dca7803bef7f50dfe
domain: bosch_shc
type: PRESS_SHORT
subtype: LOWER_BUTTON
id: kurz
condition: []
action:
- choose:
- conditions:
- condition: trigger
id: kurz
- condition: state
entity_id: light.lichter_wohnzimmer
state: "off"
sequence:
- service: light.turn_on
data:
brightness_pct: 30
transition: 10
kelvin: 2700
target:
entity_id: light.lichter_wohnzimmer
- choose:
- conditions:
- condition: device
device_id: f8a48aa83df7e787c5a8d61ae07cbadf
domain: media_player
entity_id: media_player.samsung_q95t
type: is_off
sequence:
- device_id: 0b07d9e5a6423c359a70e5b6800bfb4a
domain: select
entity_id: 754c86a08006a8b0cab082e454596586
type: select_option
option: Warm Weiß
- device_id: 228cf8ad3966f44ba24a781853eca0f3
domain: select
entity_id: 2cbde699c42aa9b0ce3bb8a6873ca1a7
type: select_option
option: Warm Weiß
- conditions:
- condition: device
device_id: f8a48aa83df7e787c5a8d61ae07cbadf
domain: media_player
entity_id: media_player.samsung_q95t
type: is_on
- condition: device
device_id: f791d35281808bb0068a9d2e54d732d8
domain: device_tracker
entity_id: da548a9ee21c3ef27de30e47a2a97e7e
type: is_home
sequence:
- device_id: 0b07d9e5a6423c359a70e5b6800bfb4a
domain: select
entity_id: 754c86a08006a8b0cab082e454596586
type: select_option
option: "Christmas "
- device_id: 228cf8ad3966f44ba24a781853eca0f3
domain: select
entity_id: 2cbde699c42aa9b0ce3bb8a6873ca1a7
type: select_option
option: Christmas
- conditions:
- condition: device
device_id: f8a48aa83df7e787c5a8d61ae07cbadf
domain: media_player
entity_id: media_player.samsung_q95t
type: is_on
- condition: device
device_id: f791d35281808bb0068a9d2e54d732d8
domain: device_tracker
entity_id: da548a9ee21c3ef27de30e47a2a97e7e
type: is_not_home
sequence:
- device_id: 0b07d9e5a6423c359a70e5b6800bfb4a
domain: select
entity_id: 754c86a08006a8b0cab082e454596586
type: select_option
option: Mirko
- device_id: 228cf8ad3966f44ba24a781853eca0f3
domain: select
entity_id: 2cbde699c42aa9b0ce3bb8a6873ca1a7
type: select_option
option: Mirko
- conditions:
- condition: trigger
id: kurz
- condition: state
entity_id: light.lichter_wohnzimmer
state: "on"
sequence:
- service: light.turn_off
data:
transition: 10
target:
entity_id: light.lichter_wohnzimmer
- conditions:
- condition: trigger
id: lange
- condition: or
conditions:
- condition: device
device_id: 4d31d44d64d569969eed31c5a15ba0a3
domain: alarm_control_panel
entity_id: alarm_control_panel.intrusion_detection_system
type: is_armed_home
- condition: device
device_id: 4d31d44d64d569969eed31c5a15ba0a3
domain: alarm_control_panel
entity_id: alarm_control_panel.intrusion_detection_system
type: is_armed_away
- condition: device
device_id: 4d31d44d64d569969eed31c5a15ba0a3
domain: alarm_control_panel
entity_id: alarm_control_panel.intrusion_detection_system
type: is_triggered
sequence:
- device_id: 4d31d44d64d569969eed31c5a15ba0a3
domain: alarm_control_panel
entity_id: alarm_control_panel.intrusion_detection_system
type: disarm
- delay:
hours: 0
minutes: 0
seconds: 3
milliseconds: 0
- service: automation.trigger
data:
skip_condition: false
target:
entity_id: automation.rollladen_morgens_hoch
mode: single
Regards
You are using all device triggers which are not user friendly and are very hard for me to diagnose. I don’t see a problem, though.
The error is not talking about the automation at all, just complaining about a language problem when trying to provide an error message I think. Clear the core log then run it again, see if there is another error.
Did you look at the trace and see what is working and what isn’t. That will be your best bet to fixing this. And sending me pictures of the trace is not going to help me. Also look at what it thinks the variables are in the automation when it runs, and check that the variables are what you think they are supposed to be.
M-R
(M R)
April 19, 2024, 8:04pm
5
I have now created a new automation and tested it. When I configure the trigger with device, the button press is recognized. But the error appears.
If I configure the trigger as a changing entity, the automation works.
If I press the switch too many times in succession, the Home Assistant crashes. It’s all very strange.
I will test further.
Thank you for your input.
So found another user posting this on Discord.
Discord .
The suggestion was for them to open a core issue for the problem. I would suggest you look to see if there was one opened. That Discord post was posted April 9.
If you don’t see one you should open an issue in frontend. Provide all the info you can including your default language settings and an automation that shows the problem, the error message, and pics of the trace and history if you can.
Reporting issues - Home Assistant .
Issues · home-assistant/frontend · GitHub .
(Edited to Frontend instead of core)
karwosts
(karwosts)
April 19, 2024, 8:43pm
7
This should be the frontend fix for this error string:
home-assistant:dev
← karwosts:fix_stopped_unknown_reason
opened 08:37PM - 19 Apr 24 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Proposed change
Fix error: `Translation Error: The intl string context variable "reason" was not provided to the string "Stopped because of unknown reason {reason} at {time} (runtime: {executiontime} seconds)"`
## Type of change
<!--
What type of change does your PR introduce to the Home Assistant frontend?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [x] Bugfix (non-breaking change which fixes an issue)
- [ ] New feature (thank you!)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Example configuration
<!--
Supplying a configuration snippet, makes it easier for a maintainer to test
your PR.
-->
```yaml
```
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue or discussion:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [ ] The code change is tested and works locally.
- [ ] There is no commented out code in this PR.
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
<!--
Thank you for contributing <3
-->
[docs-repository]: https://github.com/home-assistant/home-assistant.io
1 Like