szupi-ipuzs
commented
5 months ago I don't know much about mdns and I don't know if this is related, but comparing different esphome implementations of MDNSComponent, there's one thing different with libretiny: lack of the loop() method, which other implementations seem to use to call update() periodically. And the loop method is missing because it wasn't enabled for cases when USE_LIBRETINY is defined:
class MDNSComponent : public Component {
public:
void setup() override;
void dump_config() override;
#if (defined(USE_ESP8266) || defined(USE_RP2040)) && defined(USE_ARDUINO)
void loop() override;
#endif@kuba2k2 Is this by design or was simply forgotten? Could this be related to @chrwei observerations ?
kuba2k2
chrwei
Cossid
I'm using a bk7231n cb2s based device with esphome and had already opened an issue there https://github.com/esphome/issues/issues/5435 but it seems the issue is in libretiny's mDNS
to summarize the issue linked, when esphome adds a TXT record that is longer than 44 characters, that record, and any TXT records added after that, do not show up in the mDNS packet. They do show up in the esphome logs, so it's somewhere in how libretiny's mDNS handles the
MDNS.addServiceTxt(service_type, proto, record.key.c_str(), record.value.c_str());call.I've looked at the code and I don't see anything obvious that would cause this, but my C++ skills are basic.
The same yaml works on esp8266, so it's not a non-printable character, I even retyped the line to be sure. I did attempt to compare the esp8266mDNS code, but it's too different to make a useful comparison.