Discovered entities with a name that starts with the device name

[IceBotYT]

Home Assistant Version?

2023.8.0b1 - 2023.8.0

Add-On or Self Hosted?

HA Supervised (Add-On)

Weatherflow2MQTT version?

3.1.6

What happened?

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.

https://developers.home-assistant.io/blog/2023-057-21-change-naming-mqtt-entities/

List of affected entities:

• sensor.tempest_st_********_humidity
• sensor.tempest_st_********_zambretti_number
• sensor.tempest_st_********_wet_bulb_temperature
• sensor.tempest_st_********_pressure_trend
• sensor.tempest_st_********_zambretti_text
• sensor.tempest_st_********_uv_index
• sensor.tempest_st_********_lightning_distance
• sensor.tempest_st_********_illuminance
• sensor.tempest_st_********_lightning_count_3_hours
• sensor.tempest_st_********_wind_speed
• sensor.tempest_st_********_fog_probability
• sensor.tempest_st_********_voltage
• sensor.tempest_st_********_air_density
• sensor.tempest_st_********_rain_intensity
• etc.

Relevant log output

No response

[alvinchen1]

Also the Repair in 2023.8.0 (no longer in beta) says "This stops working in version 2024.2.0. Please address before upgrading." So have 6 months to resolve/repair before functionality is lost.

[marc-gist]

gota love-hate HA :(

[alvinchen1]

Looks like an official WeatherFlow Integration is inbound shortly. Just got merged. From the looks of it, will support Local Push

home-assistant/core@dev...jeeftor:core:weatherflow

[TopBanana123]

Is this fixed? Because I just updated HA and Weatherflow Addon and the error went away

[craigwitter]

No, homeassistant removed the error as it was causing a lot of unnecessary confusion.

…

On Sat, Sep 2, 2023, 5:32 PM TopBanana123 ***@***.***> wrote: Is this fixed? Because I just updated HA and the error went away — Reply to this email directly, view it on GitHub <#230 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADDNYGYRJLYKBVHIG3MDOQTXYOQU7ANCNFSM6AAAAAA27552ME> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[frederickjh]

@briis will this be fixed in the "HA official WeatherFlow Integration" when it comes out? I am guessing you are focusing your efforts there for the time being.

[TopBanana123]

Question for anyone, as I'm a little confused as I've not been keeping up to date with this issue and HA in general. There is this addon, now there is the official integration and per the release notes in the latest update, there is briis/weatherflow_forecast

Is this add-on (briis/hass-weatherflow2mqtt) going to be supported going forward? Do I need to migrate to the briis/weatherflow_forecast or Official Intergration?

Will this issue (mqtt devive name) be fixed in the current version if we just stay where we are?

[baylanger]

@TopBanana123 If you have a question in regards to hass-weatherflow2mqtt , open an issue in that repo or go in HA forums and you'll find a thread where you could also ask your questions.

In the future, please try not to hijack an issue for yours. It makes noise, perhaps not you but some here are probably receiving 100+ emails per day from github and I'm one of them.

[TopBanana123]

Filter your emails better.

[TopBanana123]

Where am I hijacking anything? Read the post and you'll see my question relating to this very problem.

[briis]

@TopBanana123

Will this issue (mqtt devive name) be fixed in the current version if we just stay where we are?

I will fix this issue, as soon as I have time. Thanks for letting me know.