I’ve also had multiple problems with HS110 wireless connection, despite very strong network service. I only have three of them (none plugged in at the moment), but each has taken multiple tries, and one required calls to support. The others I got tweaked into operation by following suggestions on the HS110 support site(s).
Haven’t tried any of the other monitoring device options. I plan to permanently tie one of my H110’S to my refrigerator (major task moving it out in limited space, etc), one for the office (14 devices, none detected by Sense), and one for the entertainment center (6 boxes, none detected by Sense). Then I think I’ll stop…costs add up with little incremental value.
Still wish there was a 220v HS110 like device suitable for wiring into the 220v circuits for my well, geothermal, stove/oven, etc. That I would invest in. I’ve pretty much given up on Sense device detection after more than two years.
@andy
The first HS110 I purchased also has had WiFi trouble from day one. Mine have been range issues and in order to use that one I first had to setup extension cords coming 50ft closer to the Router and anoo50ft back to the device. I then purchased a T PLink range extender plug. Funny huh, buy a $35 extender to use a $16 plug. So my first HS110 cost almost $50.
I can say that although being half duplex and slowing things down, it works fine for its purpose. I have all my smart plugs on the reange extender so it’s a network inside a network of its own. The range on this thing is even better than my DSL WiFi router surprisingly.
I wanted to do some testing with my new Wemo tonight and when I went to start the testing I noticed that my “test plug” wasn’t showing up on the Sense app and was showing as off instead of on so I went in and disabled Network listening and restarted the app and sure enough my Wemo plugged popped up and is reporting accurately now.
If you’re having issues with smart plugs going offline (and subsequently are able to fix it by resetting Network Listening) please write into Support. We’re tracking the problem and could use some more data from your end.
I ended up completely resetting the plug and by first turning off Sense integration then starting fresh in Kasa. Three or four days now without a problem