-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TP-Link Deco Not reporting to HA that a device is on the network #276
Comments
I have the same issue, but clearly it's a deco issue and this integration can't fix it. The NMAP and Ping integrations are more reliable anyway in sensing Home/Away, but this one is still indispensable for sensing much more data. |
Did TP Link send you the fie to fix the issue and if they did, did it work? If it worked can you advise me on exactly what file to ask for and who you contacted please? Thanks for all your help. Have a great New Year. |
I didn't install it, and opted to wait for an update that'd fix it automatically. That was a false hope, as the device received two or three updates that didn't fix nothing. I would send you the update file they sent me, but you most probably have a different device. Contact them via: https://community.tp-link.com/ |
I received a TP link update today for Home Assistant and it did not fix it. Thanks for all your help. I appreciate it. |
So I shouldn't bother installing it either. Thanks for saving me that time. |
My issue is different. My Deco devices report the info it had when it first started and does change that, no even with a reload. Even the Deco app reports the same info. The only way to get around that is a restart of the Deco network. |
That is good to know. Mine just goes unavailable continually and will never change states after that. I have to reload integration continually with an automation. Then if that doesn’t work, then I have to restart home assistance. Then if that doesn’t work, then I have to reboot the TP-Link unit itself. |
Here is the latest error logs. Hope you can shed some light on this. This error originated from a custom integration. Logger: custom_components.tplink_deco.coordinator Unexpected error fetching tplink_deco-decos data During handling of the above exception, another exception occurred: Traceback (most recent call last): The above exception was the direct cause of the following exception: Traceback (most recent call last): |
Problem
Not reporting to HA that a device is on the network. It is always not_home on my devices. I do know that TP-Link did an update on there app.
TP-Link Deco Version
3.6.0
Router Model
Deco X55
Debugging Information
not_home
icon: mdi:lan-disconnect
friendly_name: iPhone Mike
source_type: router
ip: 192.168.68.106
mac: 8E-18-51-37-67-12
connection_type: band2_4
device_type: client
interface: main
down_kilobytes_per_s: 0
up_kilobytes_per_s: 0
deco_device: Entryway
deco_mac: 9C-53-22-CC-34-48
The text was updated successfully, but these errors were encountered: