-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Temperature gets "stuck" or skips values #61
Comments
Got my TEMPer 1.4 and after a few polls it gets stuck at 22.7, even after rebooting it reports 22.7. I need to unplug it and wait a minute. |
@endolith If #59 (comment) is correct then we should expect increments of 0.125°C as that would be the reported resultion. The "preferring" of some temperature I cannot explain, sorry. My guess would be an issue with the sensor or the way it works. This driver does not seem to be a likely cause. |
@cooljimy84 Your device (or this driver) reporting the same value over and over is likely a USB problem. We have had problems with the USB interactions initiated by this driver leading to "stuck" or resetting TEMPer devices. The root cause seems to be that we don't know for sure what we are doing in that regard. There are several different device revisions and the original source of the USB intercation was a more-or-less unmaintained C source. We have (or at least I have) no clear idea what exactly happens inside each TEMPer when this driver does its job. You could try to look in old issues for likely sources. But I guess we cannot help here, as it stands. sorry! |
So I've had this for years and it's always had this problem, but your "Reported working devices" includes this VID/PID? So maybe there's a bug that's been fixed that you know about?
Here are the USB descriptors:
and here is the log from several years:
As you can see, it goes up and down with the seasons, but avoids certain temperature ranges and gets "stuck" at certain temperatures. If I do
diff(unique(data))
, though, it seems like it actually has 0.0625 °C resolution across the entire range:It just strongly prefers certain temperatures over others. I don't know if this is a bug in the hardware, firmware, or software that reads it, but I'm posting here in case you know. It's been logging using cba5bf4 since that date. If you know this has nothing to do with your software, feel free to close it.
The text was updated successfully, but these errors were encountered: