Device Data Contamination
Device activity is not normalized correctly within the App/Site database(s) for New Gold SE.
Ex. 1: 20 minutes prior to my wife coming home, I had an Alarm for Abnormal Upload. It said it was for another device, but when I read it, it contaminated itself and changed to my wife's mobile device when she returned within Wi-Fi range as I was reading the Alarm and a New Device Alarm entry was created.
Ex. 2: I have smart lights. These lights are by Hubspace. Their traffic is normally very minimal. Think 5-10 KB/hr for status updates with the control module. Looking at both Alarms and the Dashboard, Hubspace devices accounted for 1.2 GB of bandwidth download and upload, which isn't what happened at all.
Both of these occurrences would be remediated with proper database normalization, primary keys, and referencing of a hash of the device's MAC, hostname, and whatever other attributes the developer wishes.
Highly recommend the developers review this post for vital feedback on the performance of the products.
Box Version: 1.978 (c419cef5)
App Version: 1.61.88 (1740)
Let me know if you need additional feedback or information. Thank you so much!
Ken Rogers Jr.
-
I found the answer to the "why" for Ex 2. Turns out, a few devices, including an iPad and multiple Hubspace lights, we're randomizing their MACs, coincidentally picking up identical addresses starting with "No Vendor" DEEC5C OUI. I thought that was interesting. Turning off the iPad features resulted in breaking out into the appropriate device segregations.
I do not have an answer for Ex 1.
Please sign in to leave a comment.
Comments
4 comments