@xpanmanx 

Might be best to swap the problem KL130s with one that does work to verify if the issue follows the bulb or stays with the socket it was originally installed in.

If the issue follows the bulb, I would reach out to support regarding the remaining bulb as there could be an issue with it.

@Tony - thanks. Neither KL130 would work. My OP describes my troubleshooting process, I was quite thorough.

That KL125 fired right up. Although I will say, briefly, that the KL125 coloration is a little different than the KL130. Not much, but it's noticible.

I've sent both KL130s back to Amazon with a note that they were defective. I don't know if they'll get binned or sent back to you guys for dissection, but that's the end of that chapter.

I have to try one of TP-Link's lightstrips soon  ;)

@xpanmanx  I am having the exact same situation as you have described. I have 4 KL130s (3x v1 and 1x v2) and 2 of them (at separate times) have decided to go belly up. One of them is v1, one v2 I was getting the same pings for 2 seconds and then non-responsive for about 30 seconds. The bulb also blinks off every 37 seconds. I've reset the bulbs multiple times across multiple sockets and the setup process never completes. It hangs on different phases of the setup. It is no more than 8 feet from my access point in which it shares with a couple other devices.  One of the other devices, mostly TP-Link wall switches, have any issues. 
 

@TP-Link @tony what are our next steps?

@jlboggsCO - I wonder if they're being bricked by a firmware download.

@xpanmanx I don't think so, I haven't done any firmware updates since I got them. I actually got the v1 working last night, so now I just have a v2 that's jacked. Turns out I'm 1 day shy of the return window Amazon is handling the return and replacement.  I've tried resetting it a couple more times with no luck.  

@jlboggsCO, I feel like the firmware updates are automatic.

@xpanmanx so here's a fun twist. I got a replacement KL130 v2 from Amazon today and it's doing the exact same thing. Meanwhile my 3 KL130 v1 bulbs are fine. 
 

I'm going to take a deep(er) dive in to troubleshooting this. I do have a very busy network (60+ devices, many hardwired, many wireless across multiple access points). I need to isolate it and see if it's my network configuration or truly the bulb(s).

@jlboggsCO Exactly my symptoms here. All KL130 v1 running strong. Two new KL130 v2 no go (as described in my OP). New KL125 working fine.

My network is similarly sized to yours, with different SSIDs depending on the device (to help me apply throttling to the kids when they act out, lol) but no VLAN segmentation between compute and IOT.

@xpanmanx do you run your own DNS and/or DHCP server?  I hooked up an old router running ddwrt and setup a basic network with DHCP and using 8.8.8.8 for the DNS server.  I paired the bulb with this network and magically everything works fine!  So I have, unfortunately, narrowed this down to something on my network.  I did recently move my DNS/DHCP (PiHole controlling both) from one server to another.  I disabled all blocking on my DNS server and this did not help.  I'm going to keep playing around with the settings to figure out if it's the DNS side or DHCP side that's making things freak out.

@jlboggsCO I'm running pfSense for DHCP/DNS/VPN/NAT/firewall etc. I also run pfBlockerNG-devel, so there's some DNS blackholing taking place. I use a NAT to force any outbound DNS query to my router. And, I use OpenDNS (Umbrella free) for p*rn filtering so my local firewall doesn't have to bear the brunt of processing sooooo many domains into a blocklist. It can be pretty restrictive, but the logging is great and I can work around anything which can be seen.

That said, I have a group/rule that will allow specific devices to directly query Google's name servers. I tried the KL130s there, also, without luck.