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

Tasmota 2023.9.0 now show device name and frendly name from tasmota devices #100089

Closed
kodiakastu opened this issue Sep 11, 2023 · 1 comment · Fixed by #100129
Closed

Tasmota 2023.9.0 now show device name and frendly name from tasmota devices #100089

kodiakastu opened this issue Sep 11, 2023 · 1 comment · Fixed by #100129

Comments

@kodiakastu
Copy link

The problem

Before 2023.9.0 Tasmota devices would show only friendly names. Now they show both device name and friendly name. I've seen some issue floating around but none opened here.

Would it be possible to have a mechanism to truncate one or the other name if they're identical ?

What version of Home Assistant Core has the issue?

2023.9.0

What was the last working version of Home Assistant Core?

2023.8.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Tasmota

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

@thecode thecode mentioned this issue Sep 11, 2023
20 tasks
@kodiakastu
Copy link
Author

Also found my issue is about this PR #98636 to conform to HA standards.

Went the rabbit hole to find this discussion home-assistant/architecture/discussions/957.

As far as I understand, #100129 wont solve the issue with devices that have multiple endpoints ( like a smart power strip with individually controlled sockets). Please correct me if I'm wrong.

This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant