Tapo L535 Bulbs - Become Unresponsive

I have 5 Tapo L535 bulbs. Lately they one ore more become unresponsive. The only way to get them to turn on is to unscrew them and screw them back in. Any ideas?

When unscrewing and then screwing a bulb, the bulb itself forces a rejoin with your wifi router. next time this occurs, see if the device is on you wifi router device list. Also, try the Tapo phone app. If it is greyed out - it is likely this case (it will initially be greayed-out but eventually found - when you open the phone app it sends the discovery packet to see who is there.

Question: Installed via matter or the community integration

They are joined via Matter. When they are unresponsive the Tapo app shows them as OFFLINE
They are not using the Tapo integration code. I should have included that.

I find that Matter on these bulbs drops the connection all the time. If I join them from the Tapo integration they work fine.

2 Likes

Interesting. Is that everyone’s experience?

Mine also; however - disclaimer I wrote the app. Not one glitch in the last year.

2 Likes

Ready to give it a shot. Rejoined these 5 bulbs using the Tapo integration. I take it that they are child devices because the Swap Devices feature doesn't find them?

Second question: The Kasa integration required (suggested) static IP addresses and putting the address into the preferences sheet. Seems this is not required for the Tapo integration?

It is still required. If not done, the device will recover after having to ask the app to look for devices and update ip address. However, it will cause significant delays in a command execution if it occurs.

1 Like

Understood. But there's no place in the HE device sheets to add the IP, right?

The app will automatically add the IP once detected. You need to set up the DHCP reservation in your wifi Router.

The built-in Kasa app allowed putting in the IP address; however, that was only for advanced users and if all else failed. The option was listed as caution.

image