Roll back the changed procedure for unique entity id’s

Checklist

• I have filled out the template to the best of my ability.
• This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
• This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.

In the latest release all entity id’s are changed/renaned with an ipadress prefix. It ruiend my setup because the old sensors got unavailable. I als do not see the use of it. If the user want it the he can do it with the prefix. Why force this change.
Please roll back this change i now had to go back to a backup to get my system running again. And future updates are not possible anymore.
Also the consequents of this change the sensor is imho not easy recognisable.
Let the user decide what prefix to use.

Describe the solution you'd like

Roll back the change, via the prefix the user can decide what he wants

Describe alternatives you've considered

Roll back this change.

Additional context

.

[effinamon]

I've also had issues with this release related to the entity ID's, though I'm not sure roll back is the answer.

After updating my automations and parsing in Telegraf also failed due to the new entity ids. I tried renaming them, but it was not possible to update entity_id's in the UI any longer.

I had to go back to the previous release for now as my data parser in part are based on he entity_id.

I think roll back the change of forcing the ip-adres prefix is the correct solution. The user can decide if he want to have the ip-adres prefix. Because a prefix can entered manualy in the previous release. That was working fine. So the need for this change is not there. Let the user decide which prefix he want to use. If he want the ip-adress prefix he can enter it.
Also if the ip-address of the device is changed then there is again a problem with the existing entity id’s. As i see it the change regarding to entity id’s only generate problems and confusion.
And imho with the ip-address prefix i do not find the sensors more recognisable.