Welcome to Incremental Social! Learn more about this project here!
Check out lemmyverse to find more communities to join from here!

@codechimp@mastodon.online cover
@codechimp@mastodon.online avatar

codechimp

@codechimp@mastodon.online

Live in Ipswich, Suffolk in the UK, mainly work from home but occasionally in London.
I’m an IT architect by day but I don’t post about work stuff.
In my free time, in no particular order I am interested in #HomeAssistant #HomeAutomation #3dPrinting #iosDev #macOS #lego #food #cooking #diy #gardening

This profile is from a federated server and may be incomplete. Browse more on the original instance.

paul , to homeassistant
@paul@crashloop.social avatar

Hi,
I recently had some issue regarding some custom integration: The resource (sensor) names were localised / translated.

This created first some confusion, later some effort to get some other custom-card working.

Example:
sensor.CHARGERNAME_dynamic_circuit_limit --> sensor.CHARGERNAME_dynamisches_stromkreislimit

Is there a general rule for (integration-) developers to localise resource/sensor names?

What is yr idea?

@homeassistant @homeassistant @homeassistant @homeassistant

codechimp ,
@codechimp@mastodon.online avatar

@paul @homeassistant @homeassistant @homeassistant @homeassistant For entity ids I stick to english with the entity name being translated since the ids are used in code which is english.
I did make the mistake of translating them to start with but got flack from people who couldn’t make common templates etc. much like you’ve experienced.
I’ve not seen official guidance either way but core integrations seem to not translate them.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • incremental_games
  • meta
  • All magazines