-
-
Notifications
You must be signed in to change notification settings - Fork 2k
add docs for dlms_meter component #4536
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: next
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for esphome ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
components/sensor/dlms_meter.rst
Outdated
|
||
# Example configuration entry for generic grid operator | ||
uart: | ||
rx_pin: GPIO4 # change this to the pin where you connected the mbus adapter board |
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.
Use the correct RX pin from ESP32 and give a hint that the user had to check what is the correct pin
See: SimonFischer04/esphome#1 (comment)
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 changed the pin now to gpio33 and added a hint.
But what do you mean by "correct" pin?
As far as I understand https://www.esphome.io/components/uart, i can use almost any pin on an esp32.
I don't see any difference in supported pin modes between gpio4 and gpio33 either.
components/sensor/dlms_meter.rst
Outdated
|
||
# Sample configuration entry for netznow | ||
uart: | ||
rx_pin: GPIO4 # change this to the pin where you connected the mbus adapter board |
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.
Use the correct RX pin from ESP32 and give a hint that the user had to check what is the correct pin
See: SimonFischer04/esphome#1 (comment)
There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. Thank you for your contributions. |
@SimonFischer04 pls fix merge conflict |
@ximex sorry for the delay, |
Description:
Related issue (if applicable): fixes
Pull request in esphome with YAML changes (if applicable): esphome/esphome#8009
Checklist:
I am merging into
next
because this is new documentation that has a matching pull-request in esphome as linked above.or
I am merging into
current
because this is a fix, change and/or adjustment in the current documentation and is not for a new component or feature.Link added in
/index.rst
when creating new documents for new components or cookbook.