-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dallas temperature sensor not found after upgrade to ESPHome 2024.5.0 #5803
Comments
Have you tried/can you try https://github.com/persuader72/esphome-components ? |
I have the same issue, annoying 🤨 |
I don’t think this is related. I have a Dallas soldered to a gpio on esp32. |
Not solved with ESPHome 2024.5.1 nor with ESPHome 2024.5.2 |
I had this issue and I switched the GPIO pin I was using and that seemed to fix the issue. |
I’m using GPIO pin 21. |
I’m using GPIO23 now. |
After some playing around, nothing with the board I have and ESPHome version 2024.5.3 worked. My code now looks like: external_components:
dallasng:
sensor:
|
Thanks for sharing, this works for me as well |
I updated to 2024.5.3 and now my temperature sensors also stopped working. |
Thanks, this worked for me too! |
thank you - thank you. crazy that i had to dig so far to find the answer and that esphome has not been able to address for this ESP board? |
Maybe you can test the new one_wire component that will replace the original dallas component esphome/esphome#6860 |
wow that is a fresh PR - thanks for letting me know - it works here! |
The problem
Dallas temperature sensor was normally working normally with ESPHome 2024.4.x version. I have only one sensor connected. After upgrade to ESPHome 2024.5.0, sensor is not found.
Which version of ESPHome has the issue?
2024.5.0
What type of installation are you using?
Home Assistant Add-on
Which version of Home Assistant has the issue?
2024.5.3
What platform are you using?
ESP32
Board
WeMos WROOM
Component causing the issue
dallas temperature sensor
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: