LB100 association issues
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
LB100 association issues
Model :
Hardware Version :
Firmware Version :
ISP :
I have two LB100 bulbs. Last night our utility power went off at 8:45 PM and went back on at 9:55. I have the bulbs set to turn on at sunset and turn off at sunrise. Late this morning I noticed that both bulbs were on. I opened the Android Kasa app to try to turn the bulbs off. When I tapped on their icons I got a toast message that told me I could control the bulbs when the phone was connected to my home internet. I closed Kasa and opened up a WiFi analyzer and could see that both bulbs were broadcasting their SSID. I power cycled one bulb and it did not associate with my access point (APO.) I had to go through the setup process to get the bulbs both back on my WiFi LAN. That process itself is fraught with problems. The app seems not capable of setting up more than one bulb at a time. It even has a place where if communication with the bulb fails, you cannot exit the screen except by going to Android Settings and forcing a stop. Here are specific problems that should be addressed.
[*]The bulb should wait longer following power up to associate with the AP. Some APs take longer to power up and broadcast their SSID.
[*]If the bulb cannot associate with the AP on power up, it should at the least do so following the next power up. It is clear that once it fails, it gives up forever and requires the homeowner to go through the setup process again. A better solution would be to watch for the associated SSID when it goes into setup mode (if the radio supports this.)
[*]If (during setup) the bulb is power cycled when Kasa is on the screen that allows the user to choose to reset the device settings, the next screen will fail and there is no escape (except going to settings to kill the app.) Yes, I know it is not normal to power cycle the bulb at this point in the process. I did so because earlier I was presented with two SSIDs and was not able to get the device configured so I turned one off. Unfortunately the one I turned off was the one I was in the process of configuring.
[*]Provide an option for the Kasa app to reconfigure 'lost' devices. All the information is known and the light bulbs are already broadcasting their SSID. It's ridiculous that the homeowner has to go through the setup process for each device.
Both bulbs are H/W version 1.0. One is at F/W 1.2.1 and the other at 1.4.3. The one that is at 1.2.1 occasionally does not turn off in the morning.
I hope these issues can be addressed. I generally like the TP-Link IOT devices but this keeps me from considering any additional bulbs. I have a couple outlets and they do not have this problem.
Thanks!
Hardware Version :
Firmware Version :
ISP :
I have two LB100 bulbs. Last night our utility power went off at 8:45 PM and went back on at 9:55. I have the bulbs set to turn on at sunset and turn off at sunrise. Late this morning I noticed that both bulbs were on. I opened the Android Kasa app to try to turn the bulbs off. When I tapped on their icons I got a toast message that told me I could control the bulbs when the phone was connected to my home internet. I closed Kasa and opened up a WiFi analyzer and could see that both bulbs were broadcasting their SSID. I power cycled one bulb and it did not associate with my access point (APO.) I had to go through the setup process to get the bulbs both back on my WiFi LAN. That process itself is fraught with problems. The app seems not capable of setting up more than one bulb at a time. It even has a place where if communication with the bulb fails, you cannot exit the screen except by going to Android Settings and forcing a stop. Here are specific problems that should be addressed.
[*]The bulb should wait longer following power up to associate with the AP. Some APs take longer to power up and broadcast their SSID.
[*]If the bulb cannot associate with the AP on power up, it should at the least do so following the next power up. It is clear that once it fails, it gives up forever and requires the homeowner to go through the setup process again. A better solution would be to watch for the associated SSID when it goes into setup mode (if the radio supports this.)
[*]If (during setup) the bulb is power cycled when Kasa is on the screen that allows the user to choose to reset the device settings, the next screen will fail and there is no escape (except going to settings to kill the app.) Yes, I know it is not normal to power cycle the bulb at this point in the process. I did so because earlier I was presented with two SSIDs and was not able to get the device configured so I turned one off. Unfortunately the one I turned off was the one I was in the process of configuring.
[*]Provide an option for the Kasa app to reconfigure 'lost' devices. All the information is known and the light bulbs are already broadcasting their SSID. It's ridiculous that the homeowner has to go through the setup process for each device.
Both bulbs are H/W version 1.0. One is at F/W 1.2.1 and the other at 1.4.3. The one that is at 1.2.1 occasionally does not turn off in the morning.
I hope these issues can be addressed. I generally like the TP-Link IOT devices but this keeps me from considering any additional bulbs. I have a couple outlets and they do not have this problem.
Thanks!