@Teviot 

Remote control option was removed awhile ago.

Do you have the latest App on the phone?

Try deleting the App, then install using the same account info.

Then reset and reconnect the LB120

Yes, I had the latest version of the app, I just installed today BUT I removed and re-downloaded. I also reset and reconnected. As before all works fine with Kasa in the house but is not discovered with Alexa. The remote control option is very much present and still fails. TP-Link claims it is required to work with Alexa which is why I purchased it in the first place.

@Teviot 

 

Try this, factory default the bulb by turning the switch off and on five times. After the fifth time it should blink three times indicating the reset went through.

 

Now download this upgrade utility: https://static.tp-link.com/2019/201912/20191212/Upgrade%20Instruction.zip

 

Extract the file and run the .exe file (need a Windows computer), connect your computer to the smart bulb, then select scan on the utility. It should find the bulb where you can update the firmware.

 

There should also be instructions inside the zip file as well.

 

Once that is done try to add the bulb again to Kasa.

@Tony 

The firmware tool worked and I am now at V1.8.11

After re-adding the scheduling in the Kasa app now works, before it flashed an error that it could not sync.

 

Still I can't enable the Remote Control, it still flashes the message "failed" cloud send cmd failed"

Alexa still can't find the device because the requred Remote Control will not enable.

 

Thanks for the help

 

@Teviot 

 

When you mentioned the firewall and DNS, did that involve disabling the firewall in the router and also changing the DNS to 8.8.8.8?

 

What you can also try in the router is to reserve an IP address for the bulb that is outside of your DHCP pool. What can cause the error is either the bulb having an IP conflict with another device or it may be bound to another account. 

 

If reserving the IP does not help I would recommend reaching out to: kasa.support@tp-link.com

 

They should be able to check on the back end what may be happening.

@Teviot 

 

When you mentioned the firewall and DNS, did that involve disabling the firewall in the router and also changing the DNS to 8.8.8.8?

 

What you can also try in the router is to reserve an IP address for the bulb that is outside of your DHCP pool. What can cause the error is either the bulb having an IP conflict with another device or it may be bound to another account. 

 

If reserving the IP does not help I would recommend reaching out to: kasa.support@tp-link.com

 

They should be able to check on the back end what may be happening.

@Tony 

Yes, when I disabled the firewall I also used changed the DNS.

I have the bulb on an address outside the DBCP pool on a reserved IP.

 

Will email kasa.support@tp-link.com and hope for the best.

Thanks!

 

@Teviot 

Changed the DNS to cloudfair (1.1.1.1 / 1.0.0.1) and now all is happy!

No other changes helped.

Thanks