New MQTT entity name warning in HA 2023.8.0

[nwf]

Before submitting this form

• [X] I have checked that there hasn't been a similar issue submitted in the past

• [X] I have updated the issue title to something relevant and clear to understand the bug I'm facing

Description of the bug

I just upgraded HA to 2023.8.0 and it's warning me:

Discovered entities with a name that starts with the device name

This stops working in version 2024.2.0. Please address before upgrading.

Some MQTT entities have an entity name that starts with the device name.  This
is not expected. To avoid a duplicate name the device name prefix is stripped
of the entity name as a work-a-round. Please inform the maintainer of the
software application that supplies the affected entities to fix this issue.

List of affected entities:

  sensor.qolsys_panel_last_error

It's entirely possible that this is something in my configuration rather than a bug per se, but in that case it'd be nice to have a warning that's a little closer to the bad setting?

Expected behavior

Operation without warnings would be nice. :)

DEBUG logs

I don't believe these are relevant, but am happy to provide if I'm wrong.

Additional context

No response

[XaF]

Hello! Thanks for the report!

According to the following threads, this is unrelated to qolsysgw and can be safely ignored:

• https://community.home-assistant.io/t/mqtt-entity-naming-change/598534/2
• https://community.home-assistant.io/t/psa-mqtt-name-changes-in-2023-8/598099

[nwf]

I don't understand how this can be unrelated to qolsysgw, though I understand that it is safe to ignore right now. Is the sensor.qolsys_panel_last_error name not determined by qolsysgw (that is, is something other than qolsysgw the warning text's "software application that supplies the affected entities")?

[wozz]

@XaF I think you misunderstood those threads. This should be a really simple fix - can we get it merged so that these warnings go away?

[nwf]

Be advised that HA 2023.8.4 has merged a change that removes the Repair notification, but the underlying issue potentially remains.

[XaF]

Finally got to fix the end-to-end tests after this change. @wozz, will run the tests on your patch to get this merged.

[XaF]

Thanks everyone! This is now live in 1.5.0.