Thank you for your feedback.
I will start with your third point:
That is a essentially part of this request, so part of the FR.
I would argue that your first and second point are the same. Tasmota stock does not track area.
However, it is not true that a firmware change is needed. I can make an FR there, but honestly, it is not needed.
Just create a simple rule that publishes the property
suggested_area and the area value. Done.
No need for firmware changes.
For everybody using Node-RED: just subscribe to the topic and add the msg property. Done.
So the Tasmota firmware already offers everything you need except a GUI setting.
The problem is that the Tasmota integration cannot handle any additional information. So the
suggested_area support, which is one of the key features in MQTT discovery’s linking to devices, would not be processed.
Personally I would not mind aligning the Tasmota interpretations with those of MQTT, so all parameters supported in MQTT are supported by the Tasmota integration.
But I feel my chances are better if I focus on the basics and ask for just one addition
As you mention the new naming guidelines, I have to admit that I was extremly suprised to see those. They really do mess up all devices.
I do not know the reason for this change, but a friendly_name is almost always a unique identifier by itself. Forcing device name into the friendly or entity_id is a surprising and, in my very personal view, very unfortunate step.
Making that optional would have been far more user friendly.
Fyi, I made a change request for the Tasmota integration for this new approach a week or two ago, when I thought it was a bug