The slightly interesting part of this is, I have a PINE64 with an i2c temp/humidity sensor, being monitored/logged over SNMP. The temp sensor is sitting on the receiver and you can easily correlate when the receiver is on or off by the readings.
Well, you can pretty much see when things started to go haywire. (don't mind the bumpiness toward the right, the older data is averaged.)
The extra sucky part, is that on top of the receiver dying, when I went to wake my workstation up, the USB connector finally gave up the ghost. It's my nice mechanical keyboard with hall-effect switches, too. I'm think gonna have to attempt soldering a new USB port.
Well, thank the gods of the Wired, the receiver appears to magically work, again. Maybe it was the extended temperature? Never did that before. There's only one way to find out...
You can see on the far right where I unplugged gally (the pine64) and the receiver, and then the sliver on the far right shows things back to normal... at least, thermally.
Open instance in the spirit of netizenship. Cyberpunk leaning, tech-forward, available to the public; I provide a lot of services that no one but me really uses, just 'cause. https://drastical.net/
So, the receiver is dead.
The slightly interesting part of this is, I have a PINE64 with an i2c temp/humidity sensor, being monitored/logged over SNMP. The temp sensor is sitting on the receiver and you can easily correlate when the receiver is on or off by the readings.
Well, you can pretty much see when things started to go haywire.
(don't mind the bumpiness toward the right, the older data is averaged.)