You implied 'your' product was the only viable method for acquiring temps, and suggested that diy routes using nodemcu's were fraught with errors due to untested software and counterfeit ds18b20s.
I stated (not suggested, stated) this wasn't true. I also pointed out that to achieve 100m runs, your product requires an additional purchase of.... Well... Not sure what really. Because the link just said to "contact us".
I (correctly) concluded that your product was too expensive for me, for what it was, and wished you luck.
I never once claimed I'd soldered trusted pair cables on a 100m run.
And yet now you return to the thread 3 months down the line to add a misplaced insult, claiming I'm misinformed, lying and "paid" (????) for posting my factual opinions?
Hilarious to see one of the resident (questionable) ambassadors has continued with their classic behaviour of attempting to add some weight to your post too.
"I also pointed out that to achieve 100m runs, your product requires an additional purchase of.... Well... Not sure what really. Because the link just said to "contact us"."
What really? The wired pobe, really, my friend. A 100 meters wire with a digital probe, it requires. Even 4 of them.
Good luck connecting 4 x 100 meter wires with sensors to your ESP8266.
I see you’ve chosen to focus on tone rather than the engineering constraints I highlighted. Let’s address the technical substance, since that is what actually matters for users planning reliable installations.
You stated that my concerns about DIY 1-Wire implementations over long distances were misplaced. Let's correct that record for anyone reading this thread in the future.
The DS18B20 protocol relies on strict timing constraints (microseconds). On a 100-meter run of unshielded or even shielded twisted pair (like Cat5e), the cable capacitance becomes a critical factor. It acts as a low-pass filter, rounding off the sharp edges of the digital signal.
Signal Integrity: Without active pull-up management or dedicated bus drivers (which a bare NodeMCU/ESP8266 does not have on its GPIO pins), the signal degradation over 100m often results in CRC errors or '85.0' phantom readings.
Voltage Drop: While manageable for power, the voltage drop on the data line combined with ground potential differences over 100m can push logic levels into undefined states.
Reflections: At 100m, transmission line effects (reflections) begin to matter if impedance isn't matched, further corrupting data packets.
The product I mentioned (tempSensorDIN) solves these specific physical layer problems with hardware designed for industrial cable lengths (galvanic isolation, active bus driving, noise filtering). That is why I compared it to a DIY solution—not to say DIY is impossible, but to say that simply soldering wires to an ESP and hoping for the best over 100m is engineering gambling, not a reliable deployment strategy.
You are free to build whatever you like. My role here is to offer robust solutions for those who value reliability over tinkering.
I won’t address the ad hominem remarks ('crayon', 'kids') as they speak for themselves. I stand by the technical facts
I don't think he was - I think the "Ambassador" shade was directed at @marktheknife's earlier comment, months ago - Which does seem a bit far-reaching in historical commentary.
That all said - Bonus points for the puerile word usage - That's my new word for the day! - Also, as the tenor of this thread slides downhill - It may be headed for a lounge topic, as with some of the flagged posts, I'm not really clear what shade is being thrown where..
An ambassador "liking" a post, dripping in errors and flamebait.
I'm not going to bother responding to the latest drivel the OP, because it's more of the same tripe and I'm tired of explaining myself. 100% in the right here, so... All out of fucks.
This topic went way off the rails today after a period of inactivity. Please start another thread if you’d like to discuss the device described in the OP.
