2024.4.2 duplicates names of devices provided by Control4 integration

[phuertay]

The problem

After upgrading to 2024.4.2, the names of entities provided via the Control4 integration get duplicated, e.g., from "Garage" to " Garage Garage".

What version of Home Assistant Core has the issue?

System Information version | core-2024.3.3 -- | -- installation_type | Home Assistant OS dev | false hassio | true docker | true user | root virtualenv | false python_version | 3.12.2 os_name | Linux os_version | 6.6.20-haos arch | x86_64 timezone | America/Denver config_dir | /config

Home Assistant Community Store

GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4978 Installed Version | 1.34.0 Stage | running Available Repositories | 1396 Downloaded Repositories | 11 HACS Data | ok

Home Assistant Cloud

logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok

Home Assistant Supervisor

host_os | Home Assistant OS 12.1 -- | -- update_channel | stable supervisor_version | supervisor-2024.04.0 agent_version | 1.6.0 docker_version | 24.0.7 disk_total | 755.2 GB disk_used | 135.0 GB healthy | true supported | true board | ova supervisor_api | ok version_api | ok installed_addons | Advanced SSH & Web Terminal (17.2.0), Frigate (0.13.2), Mosquitto broker (6.4.0), Studio Code Server (5.15.0), Music Assistant BETA (2.0.0b133), Samba share (12.3.1), MariaDB (2.6.1), OneDrive Backup (2.3.1), Double Take (1.13.1), Exadel CompreFace (1.1.0), Whisper (2.0.0)

Dashboards

dashboards | 1 -- | -- resources | 8 views | 6 mode | storage

Recorder

oldest_recorder_run | March 15, 2024 at 00:13 -- | -- current_recorder_run | April 9, 2024 at 23:38 estimated_db_size | 432.23 MiB database_engine | mysql database_version | 10.6.12

What was the last working version of Home Assistant Core?

2024.3.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Control4

Link to integration documentation on our website

https://www.home-assistant.io/integrations/control4

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

[home-assistant[bot]]

Hey there @lawtancool, mind taking a look at this issue as it has been labeled with an integration (control4) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `control4` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign control4` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

control4 documentation control4 source _{^{(message by IssueLinks)}}

[william57m]

Similar issue for me but for MQTT device since I upgraded to 2024.4 (I was previously on 2023.12 or around this date, so not sure exactly what update caused that) so it doesn't seems to be Control4 specific.

For the entities that comes from MQTT with the default name, they appeared with a double name (e.g. "Floor lamp Floor lamp" instead of "Floor lamp"). However, when I override the name it's no longer an issue.

[willigetin]

I'm having an issue where my Control4 Integration will randomly say failed to configure. So i restart the integration and after a few failed attempts it will start working and usually stay that way for a day or so and then the integration needs to be restarted once again. Anyone else having this issue?

[hautfr]

@willigetin: yes i did experience the same, and in particular nearly every time I am restarting HA I have to reload the C4 integration sometimes several times to get it working. With HA 2024.4.3 even if I do reloads, it does not work anymore. I had to uninstall 2024.4.3 to get it working again. I have a CA H250 under OS2 and some C4-SM201-Z. I hope next HA version will solve this.

[doolj]

Same problem for me. I upgraded from 2024.3.3 to 2024.5.1 and Control4 wouldn't load at all. Not even after repeated Reload attempts. Reverting back to 2024.3.3 solved the problem.

[willigetin]

I’m currently on 2024.5.1 and my C4 is up to date. I have an EA3 controller as well as a bunch of Crestron / Lutron / Control4 lighting and AV. When the integration is running it is ROCK SOLID but almost never loads correctly when HA is restarted. Would be nice if there was a watchdog service or something where you could flag certain integrations and if they fail to load have the service continue to reload until it reports back as active.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[doolj]

I upgraded to 2024.7.4 and Control4 is working great.

[m33py]

So far i'm only discovering light devices after integration. How do i discover sensors and HVAC devices as well?