Fix WDT reset during dallas search algorithm

[wysiwyng]

What does this implement/fix?

Fixes a WDT reset bootloop caused by the dallas sensor search algorithm never terminating for certain combinations of found sensor IDs. This fix was implemented by cross-checking against Paul Stoffregen's OneWire Arduino library.

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Other

Related issue or feature (if applicable): fixes esphome/issues#3107

Test Environment

• ESP32
• ESP32 IDF
• ESP8266

Checklist:

• The code change is tested and works locally.
• Tests have been added to verify that the new code works (under tests/ folder).

[OttoWinter]

Something must be wrong with the family variable (or it's intentionally not used). I can't find any place it's value is read from. We should figure out why it's there in the first place.

[wysiwyng]

Looking at Maxim's documentation for onewire search at https://www.maximintegrated.com/en/design/technical-documents/app-notes/1/187.html, it seems that LastFamilyDiscrepancy is only used for "advanced" search modes, in this case skipping entire device families during discovery.

[OttoWinter]

Thanks! In that case we should just remove the member variable and its assignments

[jesserockz]

Should have read above comments first...haha

[AlexValery13]

My project stopped because I found this issue:
esphome/issues#3107

How I can testing patch?

[OttoWinter]

Thanks, @wysiwyng !