I keep getting strange Log errors. Since I am new to HA, I am not sure if these errors are common WiFi connection errors or if they are caused by TP-Link devices having problems staying connected to WiFi. Here is an example of the type of error messages I receive:
integration: TP-Link Smart Home (documentation, issues)
First occurred: 1:26:36 PM (3 occurrences)
Last logged: 1:29:40 PM
Error fetching 192.168.1.195 data: Unable to communicate with the device update: Timeout after 5 seconds sending request to the device 192.168.1.195:9999:
Error fetching 192.168.1.190 data: Unable to communicate with the device update: get_device_info not found in {‘get_device_info’: <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, ‘get_device_usage’: <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>} for device 192.168.1.190
Error fetching 192.168.1.191 data: Unable to communicate with the device update: get_device_info not found in {‘get_device_time’: <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, ‘get_device_info’: <SmartErrorCode.INTERNAL_QUERY_ERROR: -100001>, ‘get_device_usage’: {‘time_usage’: {‘today’: 25, ‘past7’: 888, ‘past30’: 4087}, ‘power_usage’: {‘today’: 0, ‘past7’: 97, ‘past30’: 435}, ‘saved_power’: {‘today’: 25, ‘past7’: 791, ‘past30’: 3652}}} for device 192.168.1.191
I am suspecting it is TP-Link devices causing havoc since my other WiFi devices do not seem to generate HA Core errors like these.
Also I should probably mention, that these TP-Link devices periodically become unavailable (according to the Logbook) but seem to be working fine in my automations and dashboard. Matter of fact, I would not even realize they were having problems if I did not look in the Logbook area and the Home Assistant Core Logs area.
Update:
I replaced the KASA/TP-Link bulbs (3 of them) with Zigbee bulbs (ThirdReality), and I replaced two of the TP-Link plugs (HS105) with Zigbee plugs. The error messages being received on the Home Assistant Core Logs have been dramatically reduced. Granted, I still do not know if the above errors were caused by the devices being WiFi or because of the brand TP-Link. Only conclusion I can come to currently is that the errors are reduced significantly when I removed the TP-Link items.
I still have quite a few WiFi devices as well as WiFi TP-Link devices. I noticed that the EP10 plugs (KASA plug that does not report power usage) report quite a few less errors to the Core Logs than the HS105 plugs (does report power usage). This has prompted me to start developing a recommended device list as well as a “Devices to avoid” list. The KASA/TP-Link L530 Bulbs and the HS105 plugs are definitely on the “Devices to avoid” list.
Are you by chance blocking them from the Internet? I know there are some Kasa/TP Link products that will restart every 15 or 20 minutes if they can’t phone home.
Even though I probably should be firewalling them and blocking the internet, I am not doing that. I have 16 more TP-Link devices that are NOT having any problems or continuously throwing errors. Number 1 problem child was the L530 bulbs which would throw an error almost every 15 minutes. Next was the HS105 plugs that would throw an error at least once an hour. I replaced both with Zigbee devices.
I would definitely like to hear if there are users out there that have the L530 bulb and are NOT getting any HA Core errors. That would mean I have a WiFi problem or a bad batch of bulbs.
As I implied earlier in this thread, I was NOT having any automation problems or dashboard implementation problems that were apparent with these devices. The only reason I knew they were having issues is because I went to the Logbook and noticed they would randomly go offline for a couple of seconds and then when I looked at the HA Core Logs, I noticed they were throwing errors.
I am trying to learn how to catch (and correct) errors early with devices so that I build a “rock solid” smart home. This is a GREAT part of HA that it gives you an opportunity to see these potential weak links in your system so that you can replace or fix it. When I was just using the ALEXA automations (routines in that environment), it never gave me an indication that a device was failing or possibly giving problems. No telling how many times a routine had failed during the years I used that environment that could of been prevented/fixed if I would of had been using HA instead.
For what it’s worth, I’ve had two Kasa HS105 (non power monitoring) for almost 6 years, and they have been pretty reliable, with the exception that maybe twice they have lost their mind and I have to reset them. Mine aren’t allowed to access the internet.
While it is possible they are failing, often if you have several devices with WiFi problems, it may be worth taking a look at your WiFi network/coverage. ISP router wifi is notoriously bad — I upgraded to an Omada 600-series AP and now have over 70 wifi devices in HA alone.
It is not that they are failing, not reliable, or even that I have to reset them. They HAVE been reliable and I have never had to reset them. I am trying to circumvent any problems in the future, by evaluating my devices using HA to determine where there may be a weak link.
In the case with the KASA HS105’s, I have never had a failure from them to operate during an automation or voice command. However when I look in the logs file for the HA Core, and I look in the HA Logbook area; I see that the HA Core is reporting multiple error messages from the HS105’s (see my first post above for an example) and the Logbook is also showing the HS105’s becoming unavailable for several seconds.
By replacing the HS105’s and the KASA L530 lightbulbs with Zigbee plugs and bulbs, I have eliminated the Core and Logbook errors. I am hoping that this preemptive move has made my HA network stronger and prevented future problems that may have been caused by the errors reported. On the other hand, I may have wasted my money replacing the KASA/TP-Link devices with Zigbee ones since the errors and unavailable issues may have never actually caused me a problem in the future.
So do not take this thread to imply that the HS105 plugs are not right for you or anyone else who has bought them. You may never get an error (even though you did say you had to reset at times) that will mess up your automations. What I am informing HA users about is that on my network, I have identified multiple HA flagged errors associated with the KASA/TP-Link brand that may possibly be a cause of future Smart Home issues. I eliminated those HA errors and Unavailability issues. Hopefully, my efforts have made my HA network a much stronger and reliable one by doing so. I will never know if I did make my HA network stronger unless another HA user has problems associated with the KASA/TP-Link errors and fixes them by doing the same thing I did.
I do not have a solution to the problem, but I also have a H105 with exactly the same message:
Error fetching 192.168.1.185 data: Unable to communicate with the device update: Timeout after 5 seconds sending request to the device 192.168.1.185:9999
I have total of 3 H105 and this is the only one causing this error.
I have yet to find out why is this one device causing the issue.
