MQTT name changes in Home Assistant 2023.8

Home Assistant changed the naming of MQTT entities in 2023.8:

Versions until 2024.2 will tolerate the old method, so this will eventually be a breaking change for us. We need to choose support for ≥2023.8 or support for <2024.2.

For now, the only effect of this change is a warning is shown in the logs:

MQTT entity name starts with the device name in your config {'name': 'Qotom CPU Core 1 Temperature', 'state_topic': 'homeassistant/sensor/Qotom_lm-sensors_coretemp-isa-0000_temp3/state', 'unique_id': 'Qotom_lm-sensors_coretemp-isa-0000_temp3', 'device_class': <SensorDeviceClass.TEMPERATURE: 'temperature'>, 'entity_category': <EntityCategory.DIAGNOSTIC: 'diagnostic'>, 'expire_after': 66, 'state_class': <SensorStateClass.MEASUREMENT: 'measurement'>, 'unit_of_measurement': '°C', 'device': {'identifiers': ['Qotom'], 'manufacturer': 'AMI Corporation', 'model': 'Aptio CRB', 'name': 'Qotom', 'sw_version': 'Debian GNU/Linux 12 (bookworm)', 'connections': []}, 'availability_mode': 'latest', 'force_update': False, 'payload_available': 'online', 'payload_not_available': 'offline', 'qos': 0, 'enabled_by_default': True, 'encoding': 'utf-8'}, this is not expected. Please correct your configuration. The device name prefix will be stripped off the entity name and becomes 'CPU Core 1 Temperature'

Given running the new names with an old Home Assistant causes stupid-ass entity names, we might want to wait a couple months before tackling this one. Once we do decide to change our naming to match the new guidelines, it should be a fairly easy change, so waiting a bit should not bite us later on.

@qwindelzorf @Z3liff thoughts? We OK with limiting this project to only supporting HomeAssistant ≥2023.8 in a couple months?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information