@Kayleealyssaa delete and re-install the app fixed it for me

Kayleealyssaa wrote

Purchased a KC120 KASA HOME camera today. Once installed, push notifications on my iPhone will not work. When I go to setting in the KASA app for notifications I get an error of “Operation Failed. Please try again later.” My notification settings on my iPhone are allowed. I have tried to reset the camera, app, and made sure they are both updated. I need help tonight!!!!

@Gregren the first time I set mine up it did this too. I pressed the reset button on the camera (push camera upwards until you see reset bottom and hold for 15secs to go back to factory settings) then re add the device. It then send motion notifications) 
I don't know if it made any difference but the first time I set it up I chose to set up view points later not during set up the second time I set them up when prompted. Then when I went to settings and turned on motion detect and then went to notifications and they were automatically turned on. 

I'm running into the same situation with my KC200 camera. Fortunately I just bought it via Amazon yesterday so if I can't get it to work in two or three days I'll just return it. This trend of paperweights unless you can activate it via the Cloud is really disappointing. I can't even accept the terms of service while setting up the camera due to this issue.

Edit: figured out a solution, had to unplug the camera, sign out, sign back in, start the setup process and then plug back in the camera.

@DY20  Setting the Time zone worked for me. Many thanks 

@Gregren Is there a solution to this yet? I have uninstalled, reinstalled the app plug and plug the camera done all of the usual things. And I'm still getting the same error message. I'm using a new iPhone so I expect the problem

@Gregren  hi I set location and it finally worked!

@DY20 this worked. Thank you!!! Glad someone was able to help!

  @Carl I'm also having the same issue...

  @Cj19 

Hello CJ.  

This is an aged post and the issue in it was resolved sometime ago and was related to an AWS issue back when it was first reported.   I will be locking this post from here but please create a new thread and provide as much detail as possible so we can address this new concern.