As you can see in the following screen, it continuously repots back 85°C, whilst it also reports the correct values (like switching from correct to wrong all the time):
reported temp 85 degrees in case of DS1820 means that you don’t have a connection with sensor, not that it’s “freaking out”. No sensor connected will return 85. Check length of your cables → power supply to the sensor - do you have parasitic power? It can cause problems. Like tom said: power supply issues or communication issues.
I guess if you have posted logs we would have seen that the one wire bus resets after each reading and therefor starts again with the power-up temperature of 85°C
I wasn’t at home and will check everything in the evening but I don’t think it’s about the length of the cable as I use the same temerature probe on the same ESP32 for the lower temperature of the heatpump.
Maybe it is about some hardware-connection / soldering problem then.
This obviously means that you’ll loose specifically 85C. If you’re actively using this range, it’ll jump from 84.9C straight to 85.1C. Shouldn’t pose a real problem imo.
It goes back to old AVR’s, but i always wondered why manufacturers chose this stupid number for showing (not available) sensor. Way more logical would be one or other limit end, or even “out of the range” number, say, 200 degrees…
I use this sensor for central heating system with pellets, sp 85 degrees is a number which can happen…
There is a simple, undocumented, way to discriminate between the power-up 85 °C-reading and a genuine temperature reading of 85 °C in DS18B20 of Family A [5]: <byte 6> of the scratchpad register. If it is 0x0c, then the 85 °C-reading is a power-up reading, otherwise it is a true temperature measurement.
Might be challenging for users to integrate this into esphome but if a feature request is raised maybe it can end up in the official component which would then could automatically discard this “power-up” readings