@Уэйн-ТП  

Thank you for your response and your willingness to assist me with this issue.

Regarding your questions:

Yes, I have tested the local control, and unfortunately, the devices do not respond to commands either when connected to the home WiFi network or remotely via other WiFi networks or cellular data. The issue persists regardless of the network type.

The model of my router is Keenetic Voyager Pro (Model Index: KN-3510), which serves as the root router. Clients are connected directly to it. Band Steering is disabled, and the 2.4GHz band is allocated to a separate SSID specifically dedicated to IoT devices. Additionally, the HomePod (the HomeKit controller) is also connected to this SSID.

I currently own three Tapo P300 devices, totaling nine sockets (3x3). One of the devices ceased to connect to HomeKit, so I had to relocate it to an environment where it can function without HomeKit through the native Tapo app. The behavior of the new device is consistent with the two previous ones, exhibiting the same issues as described in my initial message. The problematic device, which is not connected to HomeKit, now works fine through the native app without any glitches.

I would like to bring to your attention that a similar issue was observed with the Wi-Fi device Xiaomi Mi Bedside Lamp 2. After adding it to HomeKit, it would stop being recognized in both the native app and HomeKit after a few days. However, similar to the Tapo P300, the device maintained its connection to Wi-Fi and continued to consume some traffic. This problem was eventually resolved with a firmware update last year.

Two days ago, during a routine audit of devices, I realized that Beamforming and IGMP were still enabled for the 2.4GHz band. I have since disabled these features and will monitor how it affects the situation.

  @Wayne-TP 

After disabling Beamforming and IGMP, I noticed a significant improvement in device availability. They seem to respond more reliably in both the native Tapo app and Apple HomeKit.

It is worth noting that this improvement is unlikely to coincide with a firmware update to version 1.0.15. The devices were updated automatically on February 5, as evidenced by traffic consumption statistics, but the problems still remained.

When the devices were unavailable from the native app and HomeKit, they were still among the connected devices on the router, but I didn't ping their IP addresses from the network.

In the near future, I will try to restore IGMP and Beamforming and monitor the dynamics.