@th255,

This is definitely strange. The button and the hub will communicate using a sub-ghz frequency, which should provide better range and reduced interference compared to Wi-Fi.

The RSSI is concerningly low, with a -123dB usually meaning that the device is essentially unable to connect. Looking at my S200D, which is two rooms away from its connected hub, shows an RSSI of -52

With the devices being that close, I suppose that the button could technically fall in a deadzone of the sub-ghz signal, but it is rare.

Do you have the hub and button setup in a place where electrical interference could be a factor? Such as being on top of a router or surrounded by other wireless devices?

Have you attempted to reset and re-add the device to the hub?

  @th255,

The RSSI only appears while interacting with the device makes sense, as the device sleeps often and is reliant on its wake-up function to achieve its battery life. I want to say that the device stays awake for only about 15 seconds after interacting with it.

The experience that you are having is not representative of what we expect. I have 4 of these smart buttons in my own home and haven't seen similar. My own network is over 140 devices strong at this point and the sub-g devices have not seen any adverse consequences or issues with connection strength.

Lastly, the sub-g frequency is generally more resilient than other types of communication, including Wi-Fi. I only asked to check for interference in case there is something out of the ordinary, and to try to narrow down any external causes. 

For the original behavior though:

• I would be inclined to believe it may be an issue with your hub, especially if it occurs across multiple buttons and removing/readding does not help.
• Or even the Tapo app may not be reporting it correctly and being the result of something else entirely.
• Commands are being sent, but the device does not respond so it receives two of the same command.

I believe that hub-based smart actions are attempted to run at a local (on your network) level, before falling back to a cloud version. Perhaps there is something occurring with the lights that is preventing it from properly or responsively reporting 'Yes I did what you did and turned on' before that fallback command is sent, such as having two routers on your network.