Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Translation Error: The intl string context variable "number" was not provided to the string "Search {number} entities" #20474

Closed
3 of 4 tasks
MagnusErler opened this issue Apr 8, 2024 · 0 comments · Fixed by #20491

Comments

@MagnusErler
Copy link

Checklist

  • I have updated to the latest available Home Assistant version.
  • I have cleared the cache of my browser.
  • I have tried a different browser to see if it is related to my browser.
  • I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.

Describe the issue you are experiencing

When viewing the exposed entities for assist an error in the search bar is shown:
Translation Error: The intl string context variable "number" was not provided to the string "Search {number} entities"

Screenshot from 2024-04-08 17-49-10

Describe the behavior you expected

No translation error

Steps to reproduce the issue

  1. Go to Settings -> Voice assistants -> Expose
  2. View the error in the search bar (see image)

What version of Home Assistant Core has the issue?

2024.4.2

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

Brave: Version 1.64.113 Chromium: 123.0.6312.86 (Official Build) (64-bit)

Which operating system are you using to run this browser?

Ubuntu 22.04

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant