-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Update dallas_temp.md #5847
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
base: current
Are you sure you want to change the base?
Update dallas_temp.md #5847
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -46,6 +46,11 @@ | |||||
|
|
||||||
| - All other options from [Sensor](/components/sensor). | ||||||
|
|
||||||
| ### Byte Order of the Address | ||||||
| EspHome (most recent version 2026-January) - uses reversed order of the bytes, compared to the Arduino IDE. That means, if you have an address for a sensor via the Arduino IDE that says 0x2870F5E0161301C7 - then you have to use 0xc7011316e0f57028 in EspHome. The bytes are pairwise ordered in reverse. The Arduino IDE version ends in the above example with c7 - the EspHome version the same address starts with c7. - The other pairs accordingly. The arduino IDE is LSB‑first. While EspHome is MSB‑first. | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why is there an esphome version mentioned at all? It has always done it this way. |
||||||
|
|
||||||
| If you don't have the addresses, use index instead of addresses for the first run. EspHome will print the addresses on the log at first use with index. After that, try with addresses, if you want. | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If you don't have the addresses, then just run it without any sensors configured. It will always print the detected addresses in the log. |
||||||
|
|
||||||
| ### See Also | ||||||
|
|
||||||
| - [Arduino DallasTemperature library](https://github.com/milesburton/Arduino-Temperature-Control-Library) | ||||||
|
|
||||||
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a blank line before the heading.
The linting check requires headings to be surrounded by blank lines. Add a blank line between line 48 and the heading.
🔎 Proposed fix
- All other options from [Sensor](/components/sensor). ~ ### Byte Order of the Address🧰 Tools
🪛 GitHub Check: Lint
[failure] 49-49:
Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "### Byte Order of the Address"]
🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pls fix
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ximex, I'll fix the linting issue by adding a blank line after the heading.Task: Fix markdown linting issue
💡 For code changes across multiple files, use
@coderabbitaiplan in an issue comment