Things change . . . way back when, I said I was going to drop the program on my daily driver because the device is so inaccurate, but I decided, for now at least, and since I have initiated a formal complaint/inquiry, and have asked for a fair resolution, and have to wait 30 days for that, that I should let the devices continue being inaccurate, build the log up, and see if a resolution comes along.
Of course, what I would like to accomplish is to somehow establish where/why the inaccurate readings are occurring. I have half the information available, the timestamp on the log in our RightTrack account, but the other half is to establish, and show beyond a doubt, where I am at that those times.
I sense no one is going to just take our word for it, even though some of the "evidence" is so ridiculous it loses it's own credibility.
I see on the Internet that others have had problems with these devices, some problems even worse, like ruining vehicles' electrical systems, and there may be some class-actions going. The electrical system problems have to do with devices plugged into the OBD2 port, which ours are, and that "code-reading" port being intended for short-time use in a controlled environment, like a mechanic's garage. It seems like plugging something in, and leaving it, fries some systems.
I am an experienced, DIY, code reader, and never thought about that.