Ethernet DHCP hostname intermittently advertised as tasmota after upgrade to WLED 16.x

[alex-gh]

What happened?

After upgrading from WLED 0.15 to 16.0.1, one of my WLED devices using Ethernet intermittently advertises the hostname "tasmota" via DHCP instead of its configured WLED hostname.

This does not happen on another WLED device using Wi-Fi.

The result is that OPNsense registers the device as "tasmota" in local DNS, which breaks bookmarks and other hostname-based access to the device.

To Reproduce Bug

• Run WLED 16.0.1 on an ESP32 device using Ethernet.
• Configure a hostname for the WLED device.
• Use DHCP and observe the hostname supplied by the device to the DHCP server.

Expected Behavior

The reported to DHCP server hostname being the one from "mDNS address" setting.

Install Method

Binary from WLED.me

What version of WLED?

WLED 16.0.1 (2606300) "ESP32_Ethernet" (Processor: ESP32-D0WD-V3)

Which microcontroller/board are you seeing the problem on?

ESP32 with ethernet

Relevant log/trace output

Anything else?

I don't know if it is relevant, but the problem happens with the Olimex ESP32-POE.
It does not appear to be the intentional behavior from #5542 since the hostname changed to "tasmota" instead of "wled-abcd".

Code of Conduct

• I agree to follow this project's Code of Conduct