I recently had a WiFi router change at my home. I had to change the wifi settings so I tried, but I think there may be some other problem with my Heatermeter now.
When I connect an Ethernet cable between my PC and the Heatermeter, I get 2 different results, depending on what cable I use. I've removed these cables from other working PCs in the house, so they should be OK.
one cable does nothing when I connect to my PC and the heatermeter. In the network properties, my Windows 10 PC doesn't see that there's anything connected to the Ethernet port (I usually use WiFi and have not had anything plugged into this port in a long time).
Another cable makes my heatermeter red and yellow lights flash on and off as soon as it's connected to both devices.
Now, my heatermeter will read 16F when it's powered up and no probes connected, but when I connect a pit probe, it jumps up to 600+ degrees F. I was hoping that I just had a corrupted SD card and was going to re-image it, but I'm not sure now.
I'm not sure how I should troubleshoot these symptoms.
It's a 4.2 version that has been working for the last couple years just fine. I've never had to do anything to the software or hardware on it - it's been rock-solid....until now.
When I connect an Ethernet cable between my PC and the Heatermeter, I get 2 different results, depending on what cable I use. I've removed these cables from other working PCs in the house, so they should be OK.
one cable does nothing when I connect to my PC and the heatermeter. In the network properties, my Windows 10 PC doesn't see that there's anything connected to the Ethernet port (I usually use WiFi and have not had anything plugged into this port in a long time).
Another cable makes my heatermeter red and yellow lights flash on and off as soon as it's connected to both devices.
Now, my heatermeter will read 16F when it's powered up and no probes connected, but when I connect a pit probe, it jumps up to 600+ degrees F. I was hoping that I just had a corrupted SD card and was going to re-image it, but I'm not sure now.
I'm not sure how I should troubleshoot these symptoms.
It's a 4.2 version that has been working for the last couple years just fine. I've never had to do anything to the software or hardware on it - it's been rock-solid....until now.