Has anyone had an issue adding multiple dallas temp sensors?
Every time I add a new board the old one stops reporting and I still only end up with 1 sensor...
You write "...clicking is heard..." Is that a single click or a click click click ...?
After getting the LOW signal, wait a period of time and if it's still low, send the message that there is a flame. Likewise for a HIGH signal.
Perhaps instead of a relay, an opto-isolator?
https://github.com/mysensors/MySensors/pull/1562 switches to using libgpiod instead of the earlier interface. I have not tested it myself but it looks good.
@jaydenlord Probably you do. If you leave the EN floating, electrical noise could cause it to enable or disable randomly.
Some enable pin require a HIGH, some LOW. Connect it to VCC to see if it works more consistently. If it doesn't detect, connect it to GND.
If one of these works, then the part wasn't designed to be in a default state of enable.
Let us know your results (I found this video
OSD
I'm having the same / a simular issue of temperature related readings, but at a different temperature level (for me it must be > 14 degree). I massure the dew point as well (temperature = orange, dew point = yellow). It looks to be more related to water in the air than only to temperature.
@zboblamont have you been finally been able to find a solution?
@tnick STM32F1 2019.12.8 (stm32duino) is the version that was active when the latest MySensors release was made. Later versions may or may not work; nobody would know until they tried.
