So, a little packet sniffing sheds some light…
Sense works with the KP115s and the HS300s quite differently.
For the KP115s, Sense sends a single link local broadcast packet (109 bytes) requesting both system info and power measurements. All KP115s respond with their current system and power values. The response packets are surprisingly large (760+ bytes) due to inclusion of complete system information (~85% of the packet).
For the HS300, Sense sends a sends a point-to-point packet (183 bytes) requesting both complete system information and power information for each individual socket on each HS300. Each response packets is quite large (1087+ bytes) because complete system information is included in each response. The repeat of complete system information (937+ bytes) in each request/reply cycle is obviously very inefficient.
As a result, @JustinAtSense, I would like to make two enhancement requests:
-
Please allow individual plugs on the HS300 to be disabled in Sense. No reason to query plugs that are not being used.
-
Please optimize queries for the HS300. No reason to ask for six copies of complete system information every two seconds. One copy will do.
