Chart/overlay labels are hardcoded "Topic #" using MqttBrokerSensor

[jerrylewisbh]

Every chart/overlay slot for an MqttBrokerSensor renders as "Topic 1" to "Topic 10" in mqttBrokerSensor.py:19-30.

The configured topic (A_PIN_1...) can be a human-readable label, but there's no way to surface it, we need to users keep a side cheatsheet to know which "Topic N" is which.

[aaronwmorris]

Because of the way the labels are read for sensors, the only way to update them for the MQTT sensor is to edit the code.

https://github.com/aaronwmorris/indi-allsky/blob/main/indi_allsky/devices/sensors/mqttBrokerSensor.py#L20

[jerrylewisbh]

Makes sense. Submitted a PR (#2906 ) with a possible solution. I am using that on my instance where I have dozens of external sensors for weather and micro-climate research.

I am relying on the ESPHome / Home Assistant convention: "/sensor//state" that might not be true for everyone. We could include it in the documentation. It wouldn't crash or anything, just fall back to the original labels.

Let me know what you think.