Hello,
I realised that I’m getting tons of this type of error all connected to
Tplink switches
2018-12-27 17:06:15 WARNING (SyncWorker_16) [homeassistant.components.switch.tplink] Could not read state for lucine_casa: Communication error
2018-12-27 17:08:16 WARNING (SyncWorker_9) [homeassistant.components.switch.tplink] Could not read state for lavatrice: Communication error
2018-12-27 17:08:21 WARNING (SyncWorker_15) [homeassistant.components.switch.tplink] Could not read state for lucine_casa: Communication error
2018-12-27 17:09:47 WARNING (SyncWorker_13) [homeassistant.components.switch.tplink] Could not read state for lavatrice: Communication error
2018-12-27 17:10:23 WARNING (SyncWorker_11) [homeassistant.components.switch.tplink] Could not read state for lucine_casa: Communication error
2018-12-27 17:11:46 WARNING (SyncWorker_17) [homeassistant.components.switch.tplink] Could not read state for lucine_casa: Communication error
2018-12-27 17:11:46 WARNING (SyncWorker_14) [homeassistant.components.switch.tplink] Could not read state for lavatrice: Communication error
2018-12-27 17:14:57 WARNING (SyncWorker_4) [homeassistant.components.switch.tplink] Could not read state for lucine_casa: Communication error
2018-12-27 17:15:02 WARNING (SyncWorker_10) [homeassistant.components.switch.tplink] Could not read state for lavatrice: Communication error
2018-12-27 17:16:34 WARNING (SyncWorker_6) [homeassistant.components.switch.tplink] Could not read state for lavatrice: Communication error
2018-12-27 17:16:39 WARNING (SyncWorker_3) [homeassistant.components.switch.tplink] Could not read state for lucine_casa: Communication error
2018-12-27 17:17:58 WARNING (SyncWorker_16) [homeassistant.components.switch.tplink] Could not read state for lucine_casa: Communication error
2018-12-27 17:17:58 WARNING (SyncWorker_12) [homeassistant.components.switch.tplink] Could not read state for lavatrice: Communication error
2018-12-27 17:20:07 WARNING (SyncWorker_11) [homeassistant.components.switch.tplink] Could not read state for lavatrice: Communication error
2018-12-27 17:21:09 WARNING (SyncWorker_10) [homeassistant.components.switch.tplink] Could not read state for lavatrice: Communication error
2018-12-27 17:21:40 WARNING (SyncWorker_15) [homeassistant.components.switch.tplink] Could not read state for lucine_casa: Communication error
2018-12-27 17:22:11 WARNING (SyncWorker_9) [homeassistant.components.switch.tplink] Could not read state for lavatrice: Communication error
2018-12-27 17:24:10 WARNING (SyncWorker_18) [homeassistant.components.switch.tplink] Could not read state for lucine_casa: Communication error
2018-12-27 17:24:10 WARNING (SyncWorker_3) [homeassistant.components.switch.tplink] Could not read state for lavatrice: Communication error
2018-12-27 17:25:48 WARNING (SyncWorker_5) [homeassistant.components.switch.tplink] Could not read state for lucine_casa: Communication error
2018-12-27 17:26:25 WARNING (SyncWorker_16) [homeassistant.components.switch.tplink] Could not read state for lavatrice: Communication error
2018-12-27 17:27:22 WARNING (SyncWorker_19) [homeassistant.components.switch.tplink] Could not read state for lavatrice: Communication error
2018-12-27 17:27:51 WARNING (SyncWorker_6) [homeassistant.components.switch.tplink] Could not read state for lucine_casa: Communication error
2018-12-27 17:33:01 WARNING (SyncWorker_14) [homeassistant.components.switch.tplink] Could not read state for lucine_casa: Communication error
2018-12-27 17:34:02 WARNING (SyncWorker_19) [homeassistant.components.switch.tplink] Could not read state for lavatrice: Communication error
2018-12-27 17:34:07 WARNING (SyncWorker_6) [homeassistant.components.switch.tplink] Could not read state for lucine_casa: Communication error
Is there something I can do to debug this?
Is it something known?
This error appears both on a HS110 and HS100.
Usually that means that the device is not powered on or is having problems talking to your network. I get this on my TP Link switches from time to time, and have to ‘reboot’ them.
Just a note for the records:
I power-ccled one of mine switches.
I still get errors from both.
Moreover, I never loss a ping from any device while I got errors in HA.
In Logbook do they switched to “unavailable” frequently? I found an answer to change the channel on your 2.4ghz WiFi and that worked for me. I just did it last night too.
@mauog You have to change the channel on your 2.4ghz WiFi in your router settings. It’s probably set to auto, so try channel 1 or 12 first. If those don’t work try the others. If you have a hue hub or any other zigbee devices move them as far from your router as is practical.
Sorry for my late answer @TravelinMax, I took some days off…
I have some Fortigate APs and I can control channels quite fine. My APs are transmitting on channels 1, 6 and 11 on 2.4 GHz.
I would try some fine tuning but If the TP-Link device had any problem I would expect some loss packet while pinging it.
I’ll keep it monitored…
At the moment the Kasa app tells that the signal strength is about -62 dBm
Thank You
I’ve use TP-Link switches, and plugs since somewhere around version .48(I think). I do not consistently have any issues with them. They randomly (without regard to HA versions) will go offline and require a reboot.
I found there is a network problem in my Pi.
When I start the HA container it starts losing packet.
It losses about 20% of the packet. That explain the TP-Link problem I suppose.
Unfortunately I cannot figure out why that happens.
im also facing this issue by my tp-link switches and struggle in any solutions. Changing the wifi channel does not have any effect but i figured out that are some difference by the models.
I have 5 tplink switches and 2 of them working excellent without any disconnections and the other 3 of them are more offline than online.
The different you can see by the kasa app is the hardware-version. the switches without trouble have hardware version 1.0 and the troublemakers version 2.0. could anyone confirm this theory?
And maybee have anyone solved this issue?
Have to share another possible solution. Had this problem aswell and tried every single thing in here that people had shared. Almost gave up. By accident i found my solution.
Got in my mind to remove the nmap_tracker component from configuration.yaml and did so and cleared the known_devices list (unrelated to this issue)
Restarted hass and to my surprise and going for 1 hour now. Every single device is working as they should. Not a single error. I have 8 of these HS100 and not once have they stayed cleared from errors this long.
I’ve started having this issue too when I updated to 0.90.1 and similarly with 0.90.2
I don’t recall what version I was using previously, but I had delayed updating for some time.
After playing around with some things, I’ve got it back to where it was before.
First, a few things changed in the suggested yaml format. The suggested yaml in the docs went from:
switch:
- platform: tplink
host: 192.168.10.102
to now something like
tplink:
switch:
- host: 192.168.10.102
That seems to be necessary. If you go to the docs here they suggest you can turn off discovery for those of us who know the ip addresses of our switches.
Clearly there’s a whole lot here that needs some love. I’m guessing it’s the discovery. I haven’t had time to dig into the code underneath and my python is rusty, but I might have to if this isn’t fixed soon.
I’d really like to control my lights from the HA. As you likely know, Kasa doesn’t have a desktop app.
I have one bulb that keeps becoming unavailable all the time, but it’s also inaccessible from the Kasa app. It just keeps dropping connection. It’s a problem with my bulb for sure because there’s a Kasa switch sitting 2 feet away from bulb and it never drops.
yes i agree troy, by placing the tplink switch in the configuration with your host address works great. Also for the bulbs i would do the same thing with your bridge in your configuration for example phillips hue. theres an option for allow unreachable which might help. i always see bridge issues upon a reboot, for some reason, everytime.
Hi, wanted to revive the thread to see if there is a new issue with the latest upgrade of HA and TPLink.
I have had the TPLink integration for about a year now, and never had an issue with it. I updated HA to the latest:
I can see the and control the switches from the Kasa app on my phone.
I have other devices on the same network as the Kasa switches which are all accessible from HA, so not a network issue.
Both switches and outlets are not visible, and any kind of switch. So it is not a device type issue either.
I restarted HA, and nothing helped.
I reloaded the integration, and did not ix the issue.
I went ahead and deleted the integration and when I went to re-install it, it says there are no devices detected. I have no idea where to look now.
