Some P100 devices stopped working after they initially worked

DarthSonic commented 1 week ago

The problem

Plugs worked when initially added integration in 2024.7.0. But they stopped working shortly after that. 2024.7.1 did not change anything.

Devices working as expected in Tapo App on Android.

What version of Home Assistant Core has the issue?

core-2024.7.1

What was the last working version of Home Assistant Core?

core-2024.7.0

What type of installation are you running?

Home Assistant OS

Integration causing the issue

TP-Link Smart Home

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?

No response

Additional information

No response

home-assistant[bot] commented 1 week ago

Hey there @rytilahti, @bdraco, @sdb9696, 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. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

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

DarthSonic commented 1 week ago

Here the diagnostic log: home-assistant_tplink_2024-07-05T19-41-16.820Z.zip

spongerobinson commented 1 week ago

Having problems here too but only with 2 specific devices. Happy to provide logs if they help, but not sure which ones to grab.

Had same problem with same two plugs on 2024.7, downgrading resolved it.

Edit: Just rolled back to 2024.6.4 and problem is gone instantly.

Clutch57 commented 1 week ago

Same problem with p100 plugs.

Eisbaer2 commented 1 week ago

Same here

sdb9696 commented 1 week ago

Hi @DarthSonic. Could you try powering the affected devices off and on again and if that does not work check they are on the latest firmware? The P100s are quite temperamental and difficult to debug.

If that doesn't work would you be ok to help by testing out with the python-kasa library command line tool that this integration relies on?

Also could you give us the hardware and firmware versions reported in the TAPO app under Device Info?

mrbeller commented 1 week ago

Same for me regarding Tapo P115 smart plugs. I have 1 out of 10 not working. The system indicate is would be deactivated, but activating doesn't help. I removed the device and added it again, but no change... config_entry-tplink-01J23K84S9C5AEEHBZH0K7G7AN.json

edit: Switching on and off done many times ;-)

DarthSonic commented 1 week ago

Hi @DarthSonic. Could you try powering the affected devices off and on again and if that does not work check they are on the latest firmware? The P100s are quite temperamental and difficult to debug.

If that doesn't work would you be ok to help by testing out with the python-kasa library command line tool that this integration relies on?

Also could you give us the hardware and firmware versions reported in the TAPO app under Device Info?

I plugged them off for 10 seconds and back in. Now they are recognized. I will wait some time and report if they stay active and still are recognized by integration.

Should have done that before. But the simplest solution is not always the one you are thinking about first 😇

DarthSonic commented 1 week ago

Okay. Still issues. Devices itselfs is found but entities are unavailable:

DarthSonic commented 1 week ago

Firmware is newest on every device. I do not know python-kasa library command line tool. Have to check that out but need PC for that. I do not have access to a PC until Monday.

mrbeller commented 1 week ago

Meantime I found out that the naming of the sensors was mixed up. Don't know what this caused... After redoing the entity for the specific device it came back working. No issue anymore.

sdb9696 commented 1 week ago

@DarthSonic can you do a reload of one of the affected devices and post the logs?

Clutch57 commented 1 week ago

I have three P100's, eventually you can't even ping them until you power cycle them. When I can't ping them, I see arp requests that are never answered.

The button for turning on/off the smart plug at the device quits functioning. Started with the 2024.07 updates.
All my L530 devices are working fine.

sdb9696 commented 1 week ago

I have three P100's, eventually you can't even ping them until you power cycle them. When I can't ping them, I see arp requests that are never answered.

The button for turning on/off the smart plug at the device quits functioning. Started with the 2024.07 updates. All my L530 devices are working fine.

@Clutch57 could you please open a new issue for your problem and include some diagnostics and logs. It’s difficult to follow multiple problems on the one thread.

DarthSonic commented 1 week ago

@DarthSonic can you do a reload of one of the affected devices and post the logs?

Meanwhile init on the same three P100 failed again. I will power cycle them later again and see for the logs. @sdb9696 Which logs exactly do you need?

sdb9696 commented 1 week ago

The core logs

DarthSonic commented 1 week ago

The core logs

After reloading, the device is not initialized with the above red error message. In core logs there are no related entries. All I could find is this, but it was some hours before the reload:

Logger: homeassistant.helpers.service
Quelle: helpers/service.py:301
Erstmals aufgetreten: 5. Juli 2024 um 22:03:13 (41 Vorkommnisse)
Zuletzt protokolliert: 18:58:02

Referenced entities switch.steckdose_kuche_katzenbrunnen are missing or not currently available
Referenced entities switch.1000dbfa68_1 are missing or not currently available

additionally there is this entry (but seems to be another issue):

Logger: homeassistant.components.tplink.entity
Quelle: components/tplink/entity.py:207
Integration: TP-Link Smart Home (Dokumentation, Probleme)
Erstmals aufgetreten: 5. Juli 2024 um 23:46:13 (8 Vorkommnisse)
Zuletzt protokolliert: 05:42:37

Unable to read data for <DeviceType.Plug at 192.168.229.184 - Steckdose Sat Multiswitch (P110)> switch.steckdose_sat_multiswitch_automatisches_update_aktiviert: get_latest_fw for Firmware (error_code=UNSPECIFIC_ERROR)
Unable to read data for <DeviceType.Plug at 192.168.229.192 - Steckdose Heizungsraum (P100)> switch.steckdose_heizungsraum_automatisches_update_aktiviert: get_latest_fw for Firmware (error_code=UNSPECIFIC_ERROR)
Unable to read data for <DeviceType.Plug at 192.168.229.170 - Steckdose Katzenbrunnen Az (P100)> switch.steckdose_katzenbrunnen_az_automatisches_update_aktiviert: get_latest_fw for Firmware (error_code=UNSPECIFIC_ERROR)
Unable to read data for <DeviceType.Plug at 192.168.229.136 - Steckdose Rechner (P110)> switch.steckdose_rechner_automatisches_update_aktiviert: get_latest_fw for Firmware (error_code=UNSPECIFIC_ERROR)
Unable to read data for <DeviceType.Hub at 192.168.229.85 - Tapo Smart Hub (H100)> switch.tapo_smart_hub_automatisches_update_aktiviert: get_latest_fw for Firmware (error_code=UNSPECIFIC_ERROR)

DarthSonic commented 1 week ago

What I am wondering is, how many entities or which entities should have been created by Tp Link Smart Home integration for a P100 ? Why I am asking is, I had some custom integration installed some time ago (until this stopped working) and maybe there is some interference because of some leftovers of this integration?

Currently I can see these 13 entities:

DarthSonic commented 1 week ago

If that doesn't work would you be ok to help by testing out with the python-kasa library command line tool that this integration relies on?

Unfortunately, I am having trouble running that library under windows. I do not get it to work.

sdb9696 commented 1 week ago

These are the entities I have for my P100:

You may very well be seeing some unavailable entities from previous integration for the same device. I would say that if you are seeing something close to the list I pasted from the device page, and you can turn the the device off and on, then you are ok now.

DarthSonic commented 1 week ago

Unfortunately I cannot turn it on and off as either the device is not initializing and if ALL the entities are not available.

sdb9696 commented 1 week ago

Can you paste another screenshot of the device page or the integration page? You're definitely running 2024.7.1?

DarthSonic commented 1 week ago

Can you paste another screenshot of the device page or the integration page? You're definitely running 2024.7.1?

DarthSonic commented 1 week ago

There are two more plugs looking fine in integrating but are not available also:

sdb9696 commented 1 week ago

Some of those red entities look like they were created from another integration. For the one that is failed Cannot connect to host 192.168.229.101 I think you should delete it, power cycle the device, then try to rediscover it from the integration. Also check the ip address of it in the TAPO app is the same beforehand.

DarthSonic commented 6 days ago

I think you should delete it, power cycle the device, then try to rediscover it from the integration. Also check the ip address of it in the TAPO app is the same beforehand.

Okay. I removed all the devices with failure, power cycled them, checked that all related entites where removed and added them to integration by IP again. For now they are working. I will keep an eye on this, as after the first setup of the integration everything worked also (but I never power cycled the devices).

DarthSonic commented 6 days ago

@sdb9696 the entities of the P100 plugs all gone unavailable again after some time.

sdb9696 commented 6 days ago

@sdb9696 the entities of the P100 plugs all gone unavailable again after some time.

Could you upload the logs from the time when they went unavailable?

DarthSonic commented 6 days ago

@sdb9696 the entities of the P100 plugs all gone unavailable again after some time.

Could you upload the logs from the time when they went unavailable?

I cannot see with reference to that or at the time of that in log of Home Assistant Core.

sdb9696 commented 6 days ago

Can you enable debug logging from the device integration page and restart. It's the "core" logs we're looking for.

DarthSonic commented 6 days ago

This is "tapo" related in the core log. All before 13:00:00 is before power cycle and re-adding plugs:

I will enable debug logging and restart HA.

sdb9696 commented 6 days ago

It looks like you are running the custom tapo integration at the same time as the tplink one. Can you disable that and also upload the diagnostics download from the integration page.

DarthSonic commented 6 days ago

After restart P100s are not initialized still no log entries:

It is a tapo integration for cameras only. It does not query plugs: https://github.com/JurajNyiri/HomeAssistant-Tapo-Control

DarthSonic commented 6 days ago

Tapo Debug Log:

home-assistant_tplink_2024-07-08T15-23-50.204Z.log.zip

sdb9696 commented 6 days ago

You can see in the log that the tapo integration is enabled as well as the tapo_control:

2024-07-08 17:10:00.567 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tapo_control which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-07-08 17:10:00.582 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tapo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant

You should definitely disable it while we're troubleshooting.

Log is very helpful thanks. I can see the P100 ending .90 with hardware version 1.20 and firmware 1.5.5 has an error but I don't see errors with other devices. Can you screenshot device pages for the devices with issues and let me know the last number of the ips?

DarthSonic commented 6 days ago

IPs are: 192.168.229.72 192.168.229.75 192.168.229.101

There are three more P100 that work perfectly with the exact same firmware version as these unavailable ones.

I cannot disable the custome HACS integration. I have to remove it, but then my whole configuration for my cameras and security system is broken. The HACS integration completely works locally without TP Link cloud account.

sdb9696 commented 6 days ago

There are no timeout errors in the logs for those devices. Did you maybe download the log before they started to error?

w.r.t the HACS integration I'm not suggesting to disable the tapo_control one, just the tapo one. The tapo one is not for cameras, it's for P100 etc.

DarthSonic commented 6 days ago

There are no timeout errors in the logs for those devices. Did you maybe download the log before they started to error?

w.r.t the HACS integration I'm not suggesting to disable the tapo_control one, just the tapo one. The tapo one is not for cameras, it's for P100 etc.

No. I am a 1000% sure it was after the re-add and reboot of HA.

Ah! I found that "Tapo Controller" in HACS integrations. I now removed it and rebooted HA. I do not need that integration anymore. Sorry for that misunderstanding.

Still the same three devices are not working.

sdb9696 commented 6 days ago

Do they still say timeout error? Can you upload a fresh log since the reboot?

DarthSonic commented 6 days ago

I can see this after the latest reboot:

Logger: kasa.smart.smartchilddevice
Quelle: components/tplink/climate.py:53
Erstmals aufgetreten: 18:25:54 (2 Vorkommnisse)
Zuletzt protokolliert: 18:25:54

Unknown child device type, please open issue

Also, for some brief time there was a "JSON ENCODE ERROR" or similar on initialization of one of the devices. But before I could make a screenshot it was initializing again.

DarthSonic commented 6 days ago

sdb9696 commented 6 days ago

Are you on discord? Maybe we should connect there so we can try out a fix we're working on for another issue that may work here

DarthSonic commented 6 days ago

Are you on discord? Maybe we should connect there so we can try out a fix we're working on for another issue that may work here

Yes I am.

sdb9696 commented 6 days ago

Ping me there, sdb9696

sdb9696 commented 5 days ago

@home-assistant rename Some P100 devices stopped working after they initially worked

sdb9696 commented 4 days ago

@DarthSonic I believe we have a fix for this issue if you are still having it. If you want to test it out (and have it working for you until it's released) you can reach out to me on discord, my handle is sdb9696.

sdb9696 commented 3 days ago

So this issue will be fixed in the next HA release scheduled for tomorrow.

One of the underlying causes was due to a bug in the P100 firmware causing it to crash when HA reads the state the Led switch after several times (usually crashes after 40 mins). It seems this particular cause can actually be fixed by simply going into the device in the Tapo app and changing the "Led status" from Auto to Off, then back again, and power cycling.

Many thanks to @Clutch57 for all the help with testing the fix over the last few days! :muscle: :rocket:

home-assistant / core