Closed helmarw closed 4 years ago
probably to to with sensors.getTempC(0) it results into reboot loop with my ESP32, when I changed it to sensors.getTempCByIndex(0) it wasnt crashing anymore...
I did not extensively test the ESP32 code so it isn't surprising there are some subtle differences :)
On Sun, Oct 27, 2019 at 8:27 AM helmarw notifications@github.com wrote:
probably to to with sensors.getTempC(0) it results into reboot loop with my ESP32, when I changed it to sensors.getTempCByIndex(0) it wasnt crashing anymore...
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/dragondaud/myClock/issues/15?email_source=notifications&email_token=AGM5GPSEGYGHXCTO4RUQTO3QQWJNBA5CNFSM4JFB6MLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECK7UAQ#issuecomment-546699778, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGM5GPSRHNOVQE2MDSTOABDQQWJNBANCNFSM4JFB6MLA .
-- david denney dragondaud AT gmail DOT com 719-821-8900
i don't think its an issue with the ESP32 code, its related to the Dallaslibraries, maybe you used an old one ?! for getTempC(Sensoradress) you will need the hex address of the sensor not just the "index" that's where getTempCByIndex(0) comes is, that's handy when there is only one sensor attached, no need to find out its address first, first index is always 0 ...
cant find the cause for that, will dig deeper once I got a second EPS32 for testing