@pfps,

I believe that it is being caused by the device not being connected to the internet/ being able to reach the TP-Link server, but I will have to make sure. I would assume that the check is simply failing because it is may be attempting to ping an outside server to verify its connectivity, rather than the gateway its connected to.

I will pass the feedback along, however I have a feeling that this is an intended function for users who connect the device to their Kasa app, as the normal rules still apply about schedules and such operating until they become out of sync.

If you temporarily unblock the internet access of the device, does the light change?

If you only set the device up via your matter controller and not through the Kasa app, is the light also red?

  @pfps,

You would need to delete the device from within the kasa app, however, you may want to perform a factory reset and only use the setup of your matter controller.

After speaking with my team, however, this sounds as though the red light is the 'intended' behavior as it cannot be controlled via the matter protocol, and follows the LED follows the Wi-Fi setup process. When using the Matter protocol, the Red Light is an indicator that the device is not connected to the internet, rather than the device not being able to connect to the Wi-Fi.

There is an option in the Kasa App to disable the LED indicator entirely, which is likely the best course of action so that you do not need to look at the red light all of the time.

As a side note, while Matter is a local-based protocol, it is still recommended to have the device's cloud connection available for use, since certain features, such as firmware updates, are often not delivered via matter.