Timing Issue with IP connectivity during Boot after Home power outage
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Recently we have had several storms which reeulted in a home power outage.
After power is restored the HS200 and HS210 switches no longer respond to Alexa or Google home.
I have a Google NEST router and this showed the devices online further the Kasa app on my Android phone can communicate with the switches ok.
I assume the Kasa app is using the MAC address as this app does not work when outside the house.
The problem can be easily remedied by using the reboot button on each switch, however this scenario would seem to indicate a timing issue with obtaiining an IP address from the local NEST router during the period when the house power is restoreed.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hello @alan2857
May I know do you own a Google Nest Mesh system with extenders? If Kasa device does not reconnect to router or Internet after power restoration:
1. make sure Kasa switches have strong signal at its location:
Kasa app-> Device Settings-> tap name of the device ->signal strength ( tap on the Wi-Fi icon to see the value of the dBm/RSSI)
(-40- 70dBm is good to average, less than -70dBm is relatively poor : relocate device or router to get stronger signal)
2. If you own a Mesh system or AP+ extender, force kasa device to the closest AP or extender nodes (if router allows)
For a test, try to turn Mesh off for smart devices only and see if that makes any difference
Can you also help confirm some details here to help locate the issue:
- After power restoration, how about the Wi-Fi Led on the switches, it is Red/ Flashing Green/ Solid Green?
- Model of Google Nest router (double-check on router sticker)
- Can you control kasa device remotely when phone is Not connect to home Wi-Fi. i.e. phone is on LTE mobile data or non-local Wi-Fi, or does the device show local only?
- Copy Link
- Report Inappropriate Content
Yes the Kasa HS 200 & HS 210 are on a Google Mesh System Model number H2D
When everything is working normally and my Android phone is not on WiFi I can use the Kasa app to connect to the light switches over an LTE network. However when the failure occured the Kasa app could not connect to the switches over LTE.
Please note this is a general failure off all switches when the power outage is restored several of the switches are located within a few feet o the base router so WiFi signal is not an issue.
I did try rebooting the mesh network after the failure was noted and this did not make a difference, the only solution that worked was to press the restart button on each switch.
Also note if you reboot the Google mesh network when the HS switches are working OK the switches come back online OK. However after the failure mode rebooting the Google NEST WiFi does not bring the switches back online.
Note I have played with the curcuit breakers to shut off power and the HS devices boot okay.
The symptoms I describe would seem to point to the power up boot sequence in the HS switches, when the house power is restored after an area outage I suspect that power is not restored smoothly and there is significant fluctuatrions in voltage for a short period before stabilization you probably don't see this with just flipping the curcuit breakers.
Note the switch LED's are all white when the the problem occurs, also the Google NESTsoftware reports the Kasa switches as being on the WiFi network (but they are not contactable via IP).
Based on the way configuration of the Kasa switches work I would have to conclude the switches have some NV RAM for storing network information. I suspect that the switches may be retaining the old IP address prior to the power failure,
During the boot sequence when the whole house has power restored if there is some error condition that results in failure to obtain a new lease on an IP address I suspect that the switch is defaulting to using stored IP address.
I'm an ex software engineer and have had to debug driver and firmware code in the past; here is a thought to comsider.
If the firmware code responds to interrupts then the power fluctations occuring when the house power outage is restored may be causing a 2nd interrupt while still processing the 1st interrupt. If the firmware coder did not account for this condition then its possible that this may the the root cause of the error .
- Copy Link
- Report Inappropriate Content
Hello @alan2857 really appreciated for your insights and more detailed information about this case. It does not seem to the issue on IP release if switches could still be controlled locally. This may require some further debug, I escalated your case and our engineers will help investigate further, hope we could sort this out together.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 372
Replies: 3
Voters 0
No one has voted for it yet.