DHCP broken by recent firmware update to P110

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

DHCP broken by recent firmware update to P110

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
DHCP broken by recent firmware update to P110
DHCP broken by recent firmware update to P110
2023-12-04 09:00:18
Model: Tapo P110  
Hardware Version: V1
Firmware Version: 1.3.0 Build 230905 rel 1.52200

My ten or so TAPO p110 have all stopped getting DHCP assigned static addresses after I recently allowed their firmware to update.

 

Looking around the internet there are many many posts from folk with a similar problem. It is nothing to do with my cisco 877 router since the problem is occuring across a vast range of diffenet routers.

 

This totally breaks my Home Assistant integration.

 

What has changed? Is it going to be fixed?

 

  0      
  0      
#1
Options
4 Reply
Re:DHCP broken by recent firmware update to P110
2023-12-14 11:13:06

  @ferg22 

 

Have you double-checked the DHCP settings, ensure the device address reservation is not disabled, or verified if any other devices in the network are occupying the reserved IP you've set for the smart plugs?

 

Try to delete the address reservation for one device and then create a new rule with a different IP. Monitor whether this device will switch IP address afterward.

Landscape Mode - Tapo App for PadShare Your Pet Story. Win Free Tapo Care!Smart Action 2.0 Explore and meet the next level home automation.
  0  
  0  
#3
Options
Re:DHCP broken by recent firmware update to P110
2023-12-20 11:12:29

  @ferg22 

 

Thanks for the replies.

 

The ten devices were working fine till the firmware update. Investigation revealed they were no longer getting their DHCP reserved addresses. I had made no changes to the DHCP config. The tapo devices are odd in that they had to be configured using their hardware(mac) address rather than a client identifier. Every other device I have uses client identifiers. The client identifier for these switches seems to be "P110" which, if correct, is pretty stupid.

 

Anyway I did all kinds of messing with the DHCP config trying to get the tapos to use their reserved addresses. This weekend I had another go and everyuthig just worked! No idea what broke it or what fixed it.

 

The tapo app worked fine at all times for switching the devices on and off irrespective of the DHCP assigned ip address. I wonder if it uses .local or something. However use of the reserved address is crucial for use with home assistant.

  0  
  0  
#4
Options
Re:DHCP broken by recent firmware update to P110
2023-12-29 19:10:43

  @ferg22 Had a similar issue myself. not fully resolved yet, but I just installed a pfsense router and assigned all known devices static IPs.  1 of the P110 was fine and picked up its new IP at some point.   The others just stopped working/showing offline.  I tried doing a factory reset and could get through all the way until pairing with the wifi, at which point it would fail.

 

So I did a test, whilst it was pairing, I modified the MAC address on my router for the device so that it no longer had a static and straight away it picked up an IP Address from the standard DHCP pool.

 

Tried this with another P110 and got the same result.

 

So, I have now re-introduced a static for one of them, left the other as it was and will now wait and see what happens overnight.  Failing that, will do a router reboot once everyone is out of the house over the weekend and see if that fixes it.

 

The issue is definately DHCP/static mapping related during the pairing process

  0  
  0  
#5
Options
Re:DHCP broken by recent firmware update to P110
2023-12-29 21:47:29

  @ferg22 update.  my bad. as I was configuring a new router, a device that I had reassigned to a static didnt switch over for some reason, so there was a clash of IP addresses which is why the P110 was denied the IP address it was asking for.

 

Rebooted the other device so it picked up its correct IP, and the P110 was reset and setup as expected with the now not in use IP address.

 

  1  
  1  
#6
Options