-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Espnow packet transport #5458
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?
Espnow packet transport #5458
Conversation
attempt to get links working
reverted accidental change
hopefully got the md formatting correct...
fix hugo spack attack
The deploy error is:
|
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.
Fix deploy error
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
remove #espnow
✅ Deploy Preview for esphome ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
thaks - I've changed that to docref form. |
Hi There @swoboda1337 - thankyou - I've now addressed with the latest commit |
full deploy preview is here |
this is now done. |
| Name | Type | Default | Description | | ||
|---------------------|--------------------------|---------------------|--------------------------------------------------------------------------------------------------------| | ||
| `peer_address` | MAC Address *(optional)* | `FF:FF:FF:FF:FF:FF` | MAC address to send packets to. This can be either a specific peer address for point-to-point communication, or the broadcast address `FF:FF:FF:FF:FF:FF` for broadcasting to all registered peers. | | ||
| *All other options* | — | — | From the [Packet Transport Component](#packet-transport). | |
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.
No other page uses tables like this for config variable. Please follow the existing style.
Description:
Related issue (if applicable): fixes
Pull request in esphome with YAML changes (if applicable):
Checklist:
[X ] 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.[X ] Link added in
/components/index.rst
when creating new documents for new components or cookbook.