search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.54k stars 30.72k forks source link

TP-Link P110 going offline/online repeatedly #122129

Closed drchanas closed 3 months ago

drchanas commented 3 months ago

The problem

I have a mix of TP-Link HS110, P110 and some Shellys. The last 2-3 days (that I noticed) the P110s started going offline/online or staying offline with a "Failed to setup. Check the logs". Reloading the integration sometimes works. Network connectivity should be no issue. One of the devices is right next to the access point at 30cm line of sight. Also Shellys and HS110s have no such problem. This has been working fine for months with no changes in networking/access point placement of firmware/settings. Also pinging the devices with WinMTR show no packets loss or excessive latency. I tried the LED on/off + restart workaround that is for the P100s with no result. In all cases the TAPO app on my mobile has no issues at all. Eg. I have been blinking the LED over Wi-Fi and 4G all the time that HASS was having issues.

What version of Home Assistant Core has the issue?

core-2024.7.2

What was the last working version of Home Assistant Core?

No response

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

config_entry-tplink-d649eec1d84e7c60c31b856ded13a967.json reducted.log home-assistant_tplink_2024-07-18T09-43-38.870Z.zip

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Reducted.log has some error messages i think might have something to do with it.
I attached a debug log also.

Additional information

No response

home-assistant[bot] commented 3 months 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)

hansgoed commented 3 months ago

I was about to report the same for my P115 devices. Yesterday reloading the addon fixed it for me, but today they stopped working completely.

drchanas commented 3 months ago

There seems to be no firmware change lately either. If build reflects the date it should be a 2023 version. P110 - Firmware: 1.3.0 Build 230905 Rel.152200

DawidPietrykowski commented 3 months ago

Having the same problems, here's my log from the setup:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 586, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/tplink/__init__.py", line 165, in async_setup_entry
    device: Device = await Device.connect(config=config)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/kasa/device.py", line 233, in connect
    return await connect(host=host, config=config)  # type: ignore[arg-type]
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/kasa/device_factory.py", line 71, in connect
    return await _connect(config, protocol)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/kasa/device_factory.py", line 110, in _connect
    await device.update()
  File "/usr/local/lib/python3.12/site-packages/kasa/smart/smartdevice.py", line 156, in update
    await self._negotiate()
  File "/usr/local/lib/python3.12/site-packages/kasa/smart/smartdevice.py", line 132, in _negotiate
    resp = await self.protocol.query(initial_query)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/kasa/smartprotocol.py", line 68, in query
    return await self._query(request, retry_count)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/kasa/smartprotocol.py", line 73, in _query
    return await self._execute_query(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/kasa/smartprotocol.py", line 202, in _execute_query
    return await self._execute_multiple_query(request, retry_count)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/kasa/smartprotocol.py", line 145, in _execute_multiple_query
    response_step = await self._transport.send(smart_request)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/kasa/klaptransport.py", line 356, in send
    decrypted_response = self._encryption_session.decrypt(response_data)
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/kasa/klaptransport.py", line 491, in decrypt
    dp = decryptor.update(msg[32:]) + decryptor.finalize()
                                      ^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/cryptography/hazmat/primitives/ciphers/base.py", line 184, in finalize
    data = self._ctx.finalize()
           ^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/cryptography/hazmat/backends/openssl/ciphers.py", line 223, in finalize
    raise ValueError(
ValueError: The length of the provided data is not a multiple of the block length.

Also from the second plug that managed to connect I'm getting logs like these:

2024-07-18 16:07:15.925 WARNING (MainThread) [homeassistant.components.tplink.entity] Unable to read data for <DeviceType.Plug at x.x.x.x - Tapo P110-1 (P110)> switch.server_tapo_p110_1_auto_update_enabled: get_latest_fw for Firmware (error_code=UNSPECIFIC_ERROR)
 'result': {'responses': [{'error_code': 0,
                           'method': 'get_current_power',
                           'result': {'current_power': 55}},
                          {'error_code': -1001, 'method': 'get_latest_fw'},
                          {'error_code': 0,
                           'method': 'get_auto_update_info',
                           'result': {'enable': True,
                                      'random_range': 120,
                                      'time': 180}},
                          {'error_code': 0,
                           'method': 'get_led_info',
                           'result': {'led_rule': 'always',
                                      'led_status': True,
                                      'night_mode': {'end_time': 286,
                                                     'night_mode_type': 'sunrise_sunset',
                                                     'start_time': 1260,
                                                     'sunrise_offset': 0,
                                                     'sunset_offset': 0}}},
                          {'error_code': 0,
                           'method': 'get_device_time',
                           'result': {'region': 'x',
                                      'time_diff': 60,
                                      'timestamp': 1721311635}}]}}
andrewptw commented 3 months ago

Same for me, it only affects Tapo plugs not Kasa.

dphotograph commented 3 months ago

Here for me the same i have a similiar Problem. Some of my Tapo Plugs are repeatingly going Offline/Online 5 of 14 Devices are doing this.

i noticed it since Yesterday (can it have to do with the last Core Update?)

Core: 2024.7.2 Supervisor: 2024.06.2 Operating System: 12.4 Frontend: 20240710.0

Logger: homeassistant.components.tplink.coordinator Quelle: helpers/update_coordinator.py:312 Integration: TP-Link Smart Home (Dokumentation, Probleme) Erstmals aufgetreten: 17. Juli 2024 um 21:59:54 (85505 Vorkommnisse) Zuletzt protokolliert: 16:18:54

Unexpected error fetching 192.168.5.197 data Unexpected error fetching 192.168.8.158 data Unexpected error fetching 192.168.9.240 data Unexpected error fetching 192.168.10.143 data Unexpected error fetching 192.168.5.87 data Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 312, in _async_refresh self.data = await self._async_update_data() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/tplink/coordinator.py", line 49, in _async_update_data await self.device.update(update_children=False) File "/usr/local/lib/python3.12/site-packages/kasa/smart/smartdevice.py", line 165, in update self._last_update = resp = await self.protocol.query(req) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/kasa/smartprotocol.py", line 68, in query return await self._query(request, retry_count) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/kasa/smartprotocol.py", line 73, in _query return await self._execute_query( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/kasa/smartprotocol.py", line 202, in _execute_query return await self._execute_multiple_query(request, retry_count) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/kasa/smartprotocol.py", line 145, in _execute_multiple_query response_step = await self._transport.send(smart_request) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/kasa/klaptransport.py", line 356, in send decrypted_response = self._encryption_session.decrypt(response_data) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/kasa/klaptransport.py", line 491, in decrypt dp = decryptor.update(msg[32:]) + decryptor.finalize() ^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/cryptography/hazmat/primitives/ciphers/base.py", line 184, in finalize data = self._ctx.finalize() ^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/cryptography/hazmat/backends/openssl/ciphers.py", line 223, in finalize raise ValueError( ValueError: The length of the provided data is not a multiple of the block length.

sdb9696 commented 3 months ago

This has been caused by tplink throttling their cloud service due to the HA integration querying too often for the latest firmware. HA 2024.7.3 should be released tomorrow which should fix this issue.

drchanas commented 3 months ago

Aren't TP-Link plugs supposed to work in local mode too?

sdb9696 commented 3 months ago

They mostly do except not for this particular feature (checking latest firmware). Some users have reported that if you stop them accessing the internet it fixes the issue, although I haven't fully confirmed that myself.

drchanas commented 3 months ago

I just tried blocking them on my firewall. Things break. The TAPO app goes crazy and works with delays. Counters for current and todays power are a hit/miss. Maybe it's a cloud first - lan second method of connecting. I'll wait for the fix. Should have gone full Shelly...

jove01 commented 3 months ago

All my Tapo switches are Not working. `Logger: homeassistant.config_entries Quelle: config_entries.py:586 Erstmals aufgetreten: 17:11:54 (7 Vorkommnisse) Zuletzt protokolliert: 17:11:55

Error setting up entry Nubert P115 for tplink Error setting up entry TP Lenovo Tab HA P110 for tplink Error setting up entry Sky P110 for tplink Error setting up entry TP Stecker-PV P115 for tplink Error setting up entry Trockner P110 for tplink Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 586, in async_setup result = await component.async_setup_entry(hass, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/tplink/init.py", line 165, in async_setup_entry device: Device = await Device.connect(config=config) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/kasa/device.py", line 233, in connect return await connect(host=host, config=config) # type: ignore[arg-type] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/kasa/device_factory.py", line 71, in connect return await _connect(config, protocol) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/kasa/device_factory.py", line 110, in _connect await device.update() File "/usr/local/lib/python3.12/site-packages/kasa/smart/smartdevice.py", line 156, in update await self._negotiate() File "/usr/local/lib/python3.12/site-packages/kasa/smart/smartdevice.py", line 132, in _negotiate resp = await self.protocol.query(initial_query) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/kasa/smartprotocol.py", line 68, in query return await self._query(request, retry_count) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/kasa/smartprotocol.py", line 73, in _query return await self._execute_query( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/kasa/smartprotocol.py", line 202, in _execute_query return await self._execute_multiple_query(request, retry_count) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/kasa/smartprotocol.py", line 145, in _execute_multiple_query response_step = await self._transport.send(smart_request) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/kasa/klaptransport.py", line 356, in send decrypted_response = self._encryption_session.decrypt(response_data) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/kasa/klaptransport.py", line 491, in decrypt dp = decryptor.update(msg[32:]) + decryptor.finalize() ^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/cryptography/hazmat/primitives/ciphers/base.py", line 184, in finalize data = self._ctx.finalize() ^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/cryptography/hazmat/backends/openssl/ciphers.py", line 223, in finalize raise ValueError( ValueError: The length of the provided data is not a multiple of the block length.`

MihaiKrieger commented 3 months ago

I have the exact same problem with Tapo L900 LED Bands. The issue started yesterday and it matches the description in this thread. The sad part is, I thought the these products were working 100% locally :(.

Logger: homeassistant.components.tplink.coordinator
Source: helpers/update_coordinator.py:344
integration: TP-Link Smart Home (documentation, issues)
First occurred: 17 July 2024 at 13:00:48 (17 occurrences)
Last logged: 17:55:43

Error fetching 192.168.0.21 data: ('Device connection error: 192.168.0.21: Cannot connect to host 192.168.0.21:80 ssl:default [Network unreachable]', ClientConnectorError(ConnectionKey(host='192.168.0.21', port=80, is_ssl=False, ssl=True, proxy=None, proxy_auth=None, proxy_headers_hash=4620280071607537732), OSError(101, 'Network unreachable')))
Error fetching 192.168.0.190 data: Unable to connect to the device: 192.168.0.190:9999: [Errno 113] Connect call failed ('192.168.0.190', 9999)
Error fetching 192.168.0.190 data: Unable to connect to the device: 192.168.0.190:9999:
Error fetching 192.168.0.21 data: ('Unable to query the device: 192.168.0.21: Session is closed', RuntimeError('Session is closed'))
Error fetching 192.168.0.21 data: ("Unable to query the device: 192.168.0.21: 0, message='', url=URL('http://192.168.0.21:80/app/request?seq=-1053090951')", ClientResponseError(RequestInfo(url=URL('http://192.168.0.21:80/app/request?seq=-1053090951'), method='POST', headers=<CIMultiDictProxy('Host': '192.168.0.21', 'User-Agent': 'HomeAssistant/2024.7.0 aiohttp/3.9.5 Python/3.12', 'Accept': '*/*', 'Accept-Encoding': 'gzip, deflate, br', 'Cookie': 'TP_SESSIONID=E127AAC3634F27E40B8EA0E2CA3A26E1', 'Content-Length': '432', 'Content-Type': 'application/octet-stream')>, real_url=URL('http://192.168.0.21:80/app/request?seq=-1053090951')), ()))
supermimai commented 3 months ago

same here, my Tapo P110 plugs aren't responding in home assistant, while it works with a windows monitoring app I m using in the same time https://www.obviousidea.com/windows-software/tapopanel/ so that's strange a third party works but not home assistant ( same plug, same date ) I see I m not alone, so I wait for an update of home assistant, as I m not sure if I can delete and fix it with another way.

jove01 commented 3 months ago

In Addition to my Post before. One of my Tapo ist a charger in EVCC. So EVCC stops working and I can't load my car in this way.

zqnikals commented 3 months ago

same issue.

hooonza commented 3 months ago

The same issue, all my Tapo P110 and P100 do not respond to HA. One of P100 does not work with official app too.

s55ma commented 3 months ago

Same problem. Some are not working with Tapo android app, until you unplug them from power and plug again. Works for a while, then goes offline in app again. Devices are connected to wifi all the time and are pingable. So network is not the reason, Tplink cloud is doing something funky.

RoadkillUK commented 3 months ago

I have to add my 2 P110's on here, on and off every 5 seconds. This could be life or death, one is the kettle! ;)

Below is my Unavailable Entities Sensor.

image

dphotograph commented 3 months ago

This has been caused by tplink throttling their cloud service due to the HA integration querying too often for the latest firmware. HA 2024.7.3 should be released tomorrow which should fix this issue.

i think this is a good hint for what this issue is, because my Alexa also cant reach the Plugs in question.

in the TAPO App is it only a slightly strange behavior, short time Offline but back online in a short time.

found also a Forum post about this in the TAPO Forum. (https://community.tp-link.com/en/smart-home/forum/topic/676312)

ronyoung commented 3 months ago

What is it about cloud dependency and home assistant am I missing? I thought the TP link devices would operate locally but obviously that is not true. What happens if my Internet goes out? Will my TP link devices still operate with home assistant? Or will they go up and down like an old man's socks every time HA goes to the Internet looking for hardware updates?

Urdicalion commented 3 months ago

Is it possible to modify the integration and leave the choice on this update request which is causing the bug?

thisistotallyshaun commented 3 months ago

I am having the same problem - though only with a Tapo plug, a P110. My older Kasa HS110 plugs seem to be working fine.

I can't get the P110 online at all, regardless of restarting/reloading the integration.

Same error as others above but I'll put it here anyway:

Logger: homeassistant.config_entries
Source: config_entries.py:586
First occurred: 08:54:23 (2 occurrences)
Last logged: 09:10:50
Error setting up entry Downstairs Heater Plug P110 for tplink

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 586, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/tplink/__init__.py", line 165, in async_setup_entry
    device: Device = await Device.connect(config=config)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/kasa/device.py", line 233, in connect
    return await connect(host=host, config=config)  # type: ignore[arg-type]
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/kasa/device_factory.py", line 71, in connect
    return await _connect(config, protocol)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/kasa/device_factory.py", line 110, in _connect
    await device.update()
  File "/usr/local/lib/python3.12/site-packages/kasa/smart/smartdevice.py", line 156, in update
    await self._negotiate()
  File "/usr/local/lib/python3.12/site-packages/kasa/smart/smartdevice.py", line 132, in _negotiate
    resp = await self.protocol.query(initial_query)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/kasa/smartprotocol.py", line 68, in query
    return await self._query(request, retry_count)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/kasa/smartprotocol.py", line 73, in _query
    return await self._execute_query(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/kasa/smartprotocol.py", line 202, in _execute_query
    return await self._execute_multiple_query(request, retry_count)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/kasa/smartprotocol.py", line 145, in _execute_multiple_query
    response_step = await self._transport.send(smart_request)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/kasa/klaptransport.py", line 356, in send
    decrypted_response = self._encryption_session.decrypt(response_data)
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/kasa/klaptransport.py", line 491, in decrypt
    dp = decryptor.update(msg[32:]) + decryptor.finalize()
                                      ^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/cryptography/hazmat/primitives/ciphers/base.py", line 184, in finalize
    data = self._ctx.finalize()
           ^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/cryptography/hazmat/backends/openssl/ciphers.py", line 223, in finalize
    raise ValueError(
ValueError: The length of the provided data is not a multiple of the block length.
exnewbie3 commented 3 months ago

I am having the same issue with my 3x Tapo P110 switches... in addition 6x of my GU-10 Tapo Bulbs (L610) are also behaving strangely and become un-responsive but then come back online after some time.

Not sure if this is related

boby51 commented 3 months ago

I am having same problem with P100

goncalorijo commented 3 months ago

Same problem with a bunch of P110 and P100. Already described it here: https://github.com/home-assistant/core/issues/122083

jonrbloom commented 3 months ago

I agree with @Urdicalion that it would be nice to have a checkbox to disable fw polling, and remove the internet dependency completely. I am happy to use the tapo app for this.

Good to know there's a fix rippling through though. Thanks for fixing it so quickly.

MihaiKrieger commented 3 months ago

They mostly do except not for this particular feature (checking latest firmware). Some users have reported that if you stop them accessing the internet it fixes the issue, although I haven't fully confirmed that myself.

Blocked external access from the router for all my Tapo L900 LED bands. They stop working completely. The devices are also offline in the Tapo app, which worries me, because that bypasses HA. Could it be that my account was banned due to too many querries from HA?

On the other hand, it would be nice to be able to opt out of FW update checks and have the devices function fully locally. I understand that cloud dependent feature may be present, but if technically possible, would be nice to disable them.

nicola-spreafico commented 3 months ago

Is this the same issue? https://github.com/home-assistant/core/issues/122090

Jugom commented 3 months ago

oh thank goodness it's not just me. I was starting to get scared and just unplugged my devices from it to check if it was a general power grid issue. on my tp 110, additionally to the constant on/off switching I also see many of the sensors are unavailable, like the consumption ones.

Oddly and luckily enough, when the toggle happens (this one I have on my PC), my second monitor doesn't notice it and remains on, but the laptop does pop up the "using battery/connected to power" notification"

LaurentiuAndrei commented 3 months ago

Same issue here with P110 plugs. They randomlly "broke" today.

alyusuph commented 3 months ago

Same problem with me. One of the plugs is just four meters away from the router, when and if they happen to work the wifi signal shows to be good enough

Ollijung commented 3 months ago

Same problem here with four P100 plugs.

Strangely I have this issue since I setup a fresh HAOS on a generic x86-64 machine. Before I run HAOS in a virtualbox on a windows machine and the tapo plugs were running flawlessly. But maybe it's just a coincidence .

mplessing commented 3 months ago

Same here, yesterday my P110 plugs stopped working. Logs are exactly same as above.

JohnMurphy474 commented 3 months ago

Having problems with all Tapo WIFI devices (bulbs and plugs - P110, L510, L530) going offline. Any idea when the core will be updated 2024.7.3 ??

MihaiKrieger commented 3 months ago

Having problems with all Tapo WIFI devices (bulbs and plugs - P110, L510, L530) going offline. Any idea when the core will be updated 2024.7.3 ??

Expected today evening, but we don't know for certain

JohnMurphy474 commented 3 months ago

@MihaiKrieger - Any workaround if the release is late? I've a house full of automations that are now "broken".

MihaiKrieger commented 3 months ago

@MihaiKrieger - Any workaround if the release is late? I've a house full of automations that are now "broken".

Nope, none that i know of or can confirm. Mine are also broken

Hanzwurscht commented 3 months ago

Every hour briefly there, so nothing can be controlled Tapo

Ollijung commented 3 months ago

So guys.

I just removed the tp-link integration coming with HA and I installed the Tapo Controller integration from HACS.

https://github.com/petretiandrea/home-assistant-tapo-p100

I do not want to promise too much right now, but I think the "unavailable"-issue is gone now.

kylroy1 commented 3 months ago

@JohnMurphy474 yes, look this other issue: https://github.com/home-assistant/core/issues/122090

Edit: that thread is a bit long so here is the summary (you can go there for the screenshots)

what worked for me to bring the power and energy sensors back was:

  1. block the socket internet access
  2. remove the socket from the Tapo app (not need to remove them in HA)
  3. add the socket back into the Tapo app (no need to reset them from the button)

  4. reload the socket in HA from the integration (see my post above, the reload button is somewhat hard to find in the UI)

    after doing that all should be back to normal.

nicola-spreafico commented 3 months ago

@JohnMurphy474 yes, look this other issue: #122090

Edit: that thread is a bit long so here is the summary (you can go there for the screenshots)

what worked for me to bring the power and energy sensors back was:

  1. block the socket internet access
  2. remove the socket from the Tapo app (not need to remove them in HA)
  3. add the socket back into the Tapo app (no need to reset them from the button)
  4. reload the socket in HA from the integration (see my post above, the reload button is somewhat hard to find in the UI)

after doing that all should be back to normal.

I confirm that with this procedure also worked for me

jove01 commented 3 months ago

So guys.

I just removed the tp-link integration coming with HA and I installed the Tapo Controller integration from HACS.

https://github.com/petretiandrea/home-assistant-tapo-p100

I do not want to promise too much right now, but I think the "unavailable"-issue is gone now.

For testing I added 1 device to the HACS-Integration: It works there!

josefseger commented 3 months ago

I have the same problems and logs as DawidPietrykowski. Tried the custom integration as jove01. It works for 3pcs P110 and 3pcs P100.

sdb9696 commented 3 months ago

Home assistant core 2024.7.3 has just been released and should fix the issues that have occurred over the last few days due to tplink throttling their cloud services. After upgrading I would recommend power cycling any devices that are having issues as they get themselves into a bad state after encountering the throttling.

LaurentiuAndrei commented 3 months ago

Can confirm that the 2024.7.3 update fixed it after physically unplugging and then replugging the smart plugs, then reloading the device in the tp-link HA interface.

JohnMurphy474 commented 3 months ago

The core update seems to have worked for me. Will power cycle the devices to be sure they are fresh, although all seem ok. Time will tell.

hooonza commented 3 months ago

The core update doesn't fix a P110 issue. For me, the Tapo Controller integration from HACS seems to be a solution, thank you 👍🏻

So guys. I just removed the tp-link integration coming with HA and I installed the Tapo Controller integration from HACS. https://github.com/petretiandrea/home-assistant-tapo-p100 I do not want to promise too much right now, but I think the "unavailable"-issue is gone now. https://github.com/home-assistant/core/issues/122129#issuecomment-2239337645

jove01 commented 3 months ago

The new Version works. Thank you

MihaiKrieger commented 3 months ago

The new version works. For me, i had to power cycle the device while disabled in HA, and when I re enabled them after the reconnection, they snapped online. Tested with 3 L900 led strips

perdimia commented 3 months ago

Ok so ha core update and a power cycle brought all my plugs back, but now none of them are showing any power consumption data, and I have 6 plugs, all with the same fault