Hostname in my DHCP server is not updated

ESPHome
1

I trying to understand why the hostname of my ESPHome device is not updated in my routers DHCP list. Yes I have a simple TP-Link Router…

The hostname shown in the DHCP server is test-tuya (a name I created a while ago). I have rebooted the router and rebooted the ESPHome device.

I can adress the device using the name defined in the config file (biltema1.local) but why isn’t it reflected in the router.

My ESP config file looks like below:

esphome:
  friendly_name: biltema1_friendly
  name: "biltema1"
  name_add_mac_suffix: False

bk72xx:
  board: generic-bk7231t-qfn32-tuya

logger:

web_server:

captive_portal:

mdns:

api:
  password: ""

ota:
  password: ""
wifi:
  # ...
  #manual_ip:
    # Set this to the IP of the ESP
    #static_ip: 192.168.0.147
    # Set this to the IP address of the router. Often ends with .1
    #gateway: 192.168.0.1
    # The subnet of the network. 255.255.255.0 works for most home networks.
    #subnet: 255.255.255.0
  #use_address: biltema1.local
  ssid: !secret wifi_ssid
  password: !secret wifi_password
  ap:

button:
  - platform: restart
    name: Restart
2

biltema.local is a mdns address

3

Yes but shouldn’t my DHCP server pick up the new hostname

4

I suspect there is some caching going on - associating the original hostname with the mac address.

What dhcp server?

5

TP-Link Archer AX50 v1.0

I also reduced lease-time to 1 minuted but same result

6

Yes but what dhcp software does it have?

7

No clue what TP link are using for this specific model

8

Any option in the TP Link to delete clients from the DHCP-List and/or DHCP reservations? The router might remember the device using the MAC

9

Haven’t found anything like that. I have done a SW reboot and a HW reboot. DHCP request looks ok.
Probably this is a just another fault in the Router FW that I need to live with

  TIME: 2023-11-04 13:51:30.658
    IP: 0.0.0.0 (fc:67:1f:fc:93:c3) > 255.255.255.255 (ff:ff:ff:ff:ff:ff)
    OP: 1 (BOOTPREQUEST)
 HTYPE: 1 (Ethernet)
  HLEN: 6
  HOPS: 0
   XID: 6954af37
  SECS: 0
 FLAGS: 0
CIADDR: 0.0.0.0
YIADDR: 0.0.0.0
SIADDR: 0.0.0.0
GIADDR: 0.0.0.0
CHADDR: fc:67:1f:fc:93:c3:00:00:00:00:00:00:00:00:00:00
 SNAME: .
 FNAME: .
OPTION:  53 (  1) DHCP message type         3 (DHCPREQUEST)
OPTION:  57 (  2) Maximum DHCP message size 1500
OPTION:  50 (  4) Request IP address        192.168.0.147
OPTION:  54 (  4) Server identifier         192.168.0.1
OPTION:  55 (  4) Parameter Request List      1 (Subnet mask)
					      3 (Routers)
					     28 (Broadcast address)
					      6 (DNS server)
					    
OPTION:  12 (  8) Host name                 biltema1
10

I found out what the problem is. TP-Link has in their Routes implemented this having a possibility to define a Device Name. If no Device name is specified it uses the device host name. But once defining a device name it’s not possible to revert back. I have reported this to TP-Link and they will bring it up with the engineering team