Config flow strings.json not working

amattas · December 17, 2022, 5:55pm

I’m working on a custom component and I’m having an issue with the labels showing up in my Config Flow.

I have added a strings.json file and a copy of it in translations/en.json but they’re still not showing up.

Are there any other gotchas to look for?

amattas · December 18, 2022, 2:32am

So for anyone else that has hit this - I figured out the answer and filed a bug on this. Currently if your directory name isn’t the same as your domain name, the translations code ignores your translations/en.json and strings.json files.

UpDryTwist · March 26, 2023, 5:46pm

Thank you! This was driving me nuts, and just couldn’t figure it out until I found your post. Hope the defect gets fixed, as this is very non-intuitive.

amattas · March 26, 2023, 6:01pm

Unfortunately they closed my bug last week as “Not Planned”

kdkavanagh · April 15, 2023, 4:34am

Thank you! Wasted 2hrs trying to solve this before stumbling on this issue

mateine · July 17, 2023, 7:52pm

Can you share the link to your issue? A warning in the logs would have saved me many hours

amattas · July 18, 2023, 1:34pm

github.com/home-assistant/core

Translation Files Silently Ignored

opened 09:01PM - 17 Dec 22 UTC

closed 09:06PM - 24 Mar 23 UTC

amattas

stale

### The problem Currently, labels won't appear on the forms if you have a custo…m component with a config flow that doesn't use the same directory name as its domain. This is due to helpers/translation.py checking to see if the names don't match and then returning silently without logging. This was difficult to hunt down without going to the source code and seems like unexpected behavior. ### What version of Home Assistant Core has the issue? core-2022.12.6 ### What was the last working version of Home Assistant Core? _No response_ ### What type of installation are you running? Home Assistant Core ### Integration causing the issue helpers/translation.py ### Link to integration documentation on our website _No response_ ### Diagnostics information _No response_ ### Example YAML snippet _No response_ ### Anything in the logs that might be useful for us? _No response_ ### Additional information _No response_

gjohansson · July 27, 2023, 2:39pm

I would think it’s pretty well mentioned the directory name needs to be same as your domain.

amattas · July 27, 2023, 3:15pm

But here is the thing, everything else works except for this if the directory name doesn’t match the domain. If that is a requirement, it should block loading the integration for the error.

jameson_uk · December 4, 2023, 4:09pm

I guess this isn’t going to change and I understand why it forces you to name your directory the same as your domain but the fact it fails silently is really frustrating.

Thank you for saving me from going crazy. Will see if it least this can be added to the docs (Better visibility that custom integration directory must be the same name as DOMAIN · Issue #30144 · home-assistant/home-assistant.io · GitHub)