TP-Link Casa keeps changing my IP address of my devices to 192.168.0.1, which obviously is incorrect.

[bobloadmire]

The problem

my devices will go offline randomly and HA shows in the integrations "Retrying setup: Unable to connect to the device: 192.168.0.1: [Errno 111] Connect call failed ('192.168.0.1', 9999)" which is wrong, because the device has a regular assigned IP that isn't my router. The devices work fine within the TP Link casa app. the only way to fix it is to removed the device and wait for HA to auto discover the device. If I add manually immediately and use discovery, it will find the device, but say its located at 192.168.0.1. It will add it successfully but immediately go into an offline state, giving the error above. If I wait for HA to discover the device and suggest it, it works fine, for a few days and then goes offline, giving the error above.

What version of Home Assistant Core has the issue?

core-2023.4.6

What was the last working version of Home Assistant Core?

unknown prior to 2023.4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

TP-Link Casa

Link to integration documentation on our website

https://www.home-assistant.io/integrations/tplink

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Retrying setup: Unable to connect to the device: 192.168.0.1: [Errno 111] Connect call failed ('192.168.0.1', 9999)

Logger: homeassistant.components.tplink.coordinator
Source: helpers/update_coordinator.py:193
Integration: TP-Link Kasa Smart (documentation, issues)
First occurred: April 25, 2023 at 2:52:11 PM (2 occurrences)
Last logged: April 25, 2023 at 2:54:17 PM

Error fetching 192.168.0.29 data: Unable to connect to the device: 192.168.0.29:
Error fetching 192.168.0.50 data: Unable to connect to the device: 192.168.0.50:

Additional information

No response

[home-assistant[bot]]

Hey there @rytilahti, @thegardenmonkey, mind taking a look at this issue as it has been labeled with an integration (tplink) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `tplink` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign tplink` Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

tplink documentation tplink source _{^{(message by IssueLinks)}}

[bdraco]

You like have a rouge dhcp server on your network

https://en.wikipedia.org/wiki/Rogue_DHCP

[bobloadmire]

I don't know how that would be possible on my network, home assistant is really the only thing that is capable of doing that, I don't use ad guard home or anything like that.

[bobloadmire]

ok I don't see any DHCP Offer packets in wireshark on my network other than from my router 192.168.0.1. I do see the TP-Link devices making DHCP Requests though. But oddly they still function fine as well in the Kasa app

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.