Skip to content

Remove redundant 'loxone' prefix from device names#488

Closed
jmartasek wants to merge 1 commit into
JoDehli:masterfrom
jmartasek:fix/remove-loxone-device-name-prefix
Closed

Remove redundant 'loxone' prefix from device names#488
jmartasek wants to merge 1 commit into
JoDehli:masterfrom
jmartasek:fix/remove-loxone-device-name-prefix

Conversation

@jmartasek

@jmartasek jmartasek commented Jun 20, 2026

Copy link
Copy Markdown
Contributor

Question / Discussion

I noticed that all Loxone devices in HA get a "loxone" prefix in their display name (e.g., "loxone Kitchen Light" instead of just "Kitchen Light"). This comes from helpers.py:get_or_create_device():

"name": f"{DOMAIN} {device_name}",

Is there a specific reason for this? The manufacturer field is already set to "Loxone", and HA shows the integration attribution in the UI, so the prefix seems redundant and adds noise to the device list.

This PR removes the prefix. When I tested locally, all active devices got renamed automatically on next HA load — no manual intervention needed, no broken automations (entity_ids are unaffected since they come from the entity's own name, not the device name).

Changes

One-line change: device name uses device_name directly instead of f"{DOMAIN} {device_name}".

Observations from testing

  • All existing devices got their display names updated immediately (HA updates device registry names, unlike entity_ids which are locked)
  • Entity IDs unchanged
  • Manufacturer still shows "Loxone" in device info

🤖 Generated with Claude Code

The manufacturer field already identifies these as Loxone devices.
The prefix just added noise to device names in the HA UI.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@JoDehli

JoDehli commented Jun 28, 2026

Copy link
Copy Markdown
Owner

I merged it manually. Hope we will not get a lot of issues. I think I made it on purpose but I can not remember why.

@JoDehli JoDehli closed this Jun 28, 2026
@jmartasek jmartasek deleted the fix/remove-loxone-device-name-prefix branch July 2, 2026 23:06
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 this pull request may close these issues.

2 participants