-
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
Not found the Dallas sensors after uprade to ESPHOME v2022.3 #3153
Comments
I'm also using the dallas sensors with Esphome 2022.3 and it seems to be working fine. Don't see anything weird in your config. |
I have same issues. after updating firmware, my ESP lost all dallas sensors |
For some reason my esphomes with dallas sensors can not connect to the wifi anymore unless they have a high signal strength. Before the update the connection was rock-solid however. I'm assuming it is somehow related (although I wouldn't know how). |
I'm also having this same issue, was working fine before updating, afterwards sensors are showing bad checksum constantly, weirdly another esp8266 with d18b20 sensors connected to it is working perfectly, same setup on both, both running most up to date firmware etc. |
I am also having the same issue. I am using GPIO00 on an ESP-01 board. Worked fine until updating to 2022.3.0. Four sensors connected to bus, none are found now.
Edit: After rolling back to 2022.2.6, everything is working again. |
This is not new...
https://discord.com/channels/429907082951524364/943861928177045534 |
Same here using ESP32 with some Dallas on GPIO14 after 2022.3.0 no more Sensor found. Switching back to 2022.2.6 resolves the issue. |
So after trying several things I took a new wemos D1 mini and flashed the exact same file on to it that the old one had, plugged it into the circuit and turned it on, all sensors working again, I deleted the unit from home assistant, restarted home assistant and added the new unit back into esphome and everything is working again. |
I am change pins and found dallas:
Only Pin 0 works fine, others not works... [22:29:26][C][dallas.sensor:075]: DallasComponent: |
I too have had the 'No sensors found' since updating to 2022.3. The 5 ds18b20 were reading reliably until the update. I have since rolled back the version for now, and normal service has been resumed. |
Try with |
I just tried this with 5 dallas sensors on GPIO14 and it works fine for me on the latest dev branch and beta |
This comment was marked as outdated.
This comment was marked as outdated.
My solution was to decrease the pullup resistor as 4.7K was not anymore sufficient with the improved timing in PR #3181 and my sensors are 20-30m away |
I am having the same issue with my sonoff basic and temperature sensor after upgrading. Any potential fixes in a future release? |
To restate, the problem caused by version 2022.3.1 is that only sensors on one Dallas 1-Wire bus are recognized; a second bus is ignored. I am using two buses (pins), one per sensor. Why? Because my wires are so long that the ESP cannot drive multiple sensors per my experience and Dallas's recommendation. |
Did you try to adjust pullup resistors as described above? |
Not yet becasue it's not very accessible. After proving my configuration in a breadboard, I soldered the 4.7K pull-up resistors and ESD protection diodes between the ESP and an I/O terminal block on a perf board for robust, permanent installation where it worked fine until the 2022.3.1 firmware update. GPIO13 1-Wire bus now fails to recognize a sensor whereas 1-Wire bus on GPIO12 still works even when connecting the sensor wire from GPIO13. I'm in the process of building up an ESP breadboard to conduct many experiments with the assignment and number of GPIO pins for Dallas 1-Wire temperature sensors and pull-up resistors to understand what is happening. I'll post the results here. I didn't expect that a firmware update would require hardware modification. |
I had connected an oscilloscope and there you saw that it take some nanoseconds to pull up the signal with a 4k7 resistor. The pull up resistor was to big and therefore the signal was not immediately (without delay) pulled up. (Sorry I don‘t have saved the screenshots) As written in the docs you need to change the resistor when you have long wires. Older firmwares were more tolerant if the signal had some “noise”, but at the end we all used the wrong pull up resistor. |
That's a very clear explanation thank you. A trick related to wiring: if using CAT cables (twisted pairs) for 1-wire or I2C never use a twisted pair for data and ground. Capacitance accumulates over the long cable. For I2C I use SDA and GND with one twisted pair and SCL and VCC on another one, that allows for lengths over 6m. 1-wire similarly, I use GND and VCC on a pair, and data on another independent wire, that allows for 40m distances safely. |
edenhaus, your explanation of this as a timing issue gave me the confidence that modifying my circuit board was the solution, not merely another possible thing to try. Indeed my addition of a Zener diode and MOV for ESD/surge protection to make this a robust installation added too much capacitance to work with your corrected serial bus timing. Removing these protection devices fixed the issue. I'm interested in anybody's experience with and view on the need for and implementation of I/O protecion on long sensor wires connected to a microcontroller. My HA system is more than a hobby, it seriously runs my house. |
My 40 meters cable with a Dallas sensor on its end runs mostly under the yard ground in a plastic pipe, no special protection added, it's been like that for 3 years now, zero issues. Worked with Tasmota for 2.5 years, and moved to ESPHome 6 months ago. |
Hi, quite noob question but which pull up to use with the dallas 3m long? I had 4,7k but suddenly it shows me no sensor found (after working perfectly over month now). |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Try something lower. |
Kind of silly of changing code so stuff that worked no longer works and say its a feature that it doesnt and now everyone needs to change hardware to make something work that worked without changes. Very very annoying and disappointing. |
Hello, |
For me this is the second time that my ESP drops all Dallas sensors after an update, first it happened at the 2022.03 update, now it happened at the 2022.12 update. Both times it was solved by getting a smaller resistor. I started with a 4.7k, then I switched to 3.3, now its 2.2. Thats the only way i could solve the issue both times. |
i got this problem with 23023.4 |
Hi, After adding one i hab no issues since then. hope this helps |
The problem
Not available the Dallas sensors after uprade to ESPHOME v2022.3
Which version of ESPHome has the issue?
2022.3
What type of installation are you using?
Home Assistant Add-on
Which version of Home Assistant has the issue?
2022.3.5
What platform are you using?
ESP8266
Board
sonoff basic
Component causing the issue
dallas
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
Works with version 2022.2.6.
The text was updated successfully, but these errors were encountered: