-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
Inkplate 6 support for ESPHome #1283
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
Conversation
Inkplate 6 is e-paper display based on ESP32. This commit adds support for integrating Inkplate 6 into the ESPHome. Find more info here: inkplate.io
Attempt to fix formatting errors
@glmnet @OttoWinter Any advice on what to do with the |
Co-authored-by: Jesse Hills <3060199+jesserockz@users.noreply.github.com>
Co-authored-by: Jesse Hills <3060199+jesserockz@users.noreply.github.com>
cv.Required(CONF_SPV_PIN): pins.gpio_output_pin_schema, | ||
cv.Required(CONF_VCOM_PIN): pins.gpio_output_pin_schema, | ||
cv.Required(CONF_WAKEUP_PIN): pins.gpio_output_pin_schema, | ||
cv.Optional(CONF_CL_PIN, default=0): pins.internal_gpio_output_pin_schema, |
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.
Why are there default values here?
Also these config options don't appear to be documented in the docs (which they should)
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.
The defaults are there because you cant change the hardwired pins for the Inkplate, which then saves on adding more yaml config. Can be removed if too much though?
|
||
this->buffer_ = (uint8_t *) ps_malloc(buffer_size); | ||
if (this->buffer_ == nullptr) { | ||
ESP_LOGE(TAG, "Could not allocate buffer for display!"); |
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.
If allocation fails, shouldn't we return from this method?
Ignore some lint errors Only allow on ESP32
Lint errors etc
Update the codeowners file
Phef, finally, very nice! Thanks on your assistance, Jesse. |
* Add Inkplate 6 support Inkplate 6 is e-paper display based on ESP32. This commit adds support for integrating Inkplate 6 into the ESPHome. Find more info here: inkplate.io * Greyscale working * Update inkplate.h * Fix formatting * Formatting * Update esphome/components/inkplate6/display.py Co-authored-by: Jesse Hills <3060199+jesserockz@users.noreply.github.com> * Update esphome/components/inkplate6/display.py Co-authored-by: Jesse Hills <3060199+jesserockz@users.noreply.github.com> * Fix some lint errors Ignore some lint errors Only allow on ESP32 * Update the codeowners file Co-authored-by: Jesse Hills <3060199+jesserockz@users.noreply.github.com>
* Add Inkplate 6 support Inkplate 6 is e-paper display based on ESP32. This commit adds support for integrating Inkplate 6 into the ESPHome. Find more info here: inkplate.io * Greyscale working * Update inkplate.h * Fix formatting * Formatting * Update esphome/components/inkplate6/display.py Co-authored-by: Jesse Hills <3060199+jesserockz@users.noreply.github.com> * Update esphome/components/inkplate6/display.py Co-authored-by: Jesse Hills <3060199+jesserockz@users.noreply.github.com> * Fix some lint errors Ignore some lint errors Only allow on ESP32 * Update the codeowners file Co-authored-by: Jesse Hills <3060199+jesserockz@users.noreply.github.com>
Description: Inkplate 6 is e-paper ESP32 based display. This PR enables its usage with ESPHome.
Related issue (if applicable): fixes
**Pull request in esphome-docs with documentation (if applicable): esphome/esphome-docs#778
Checklist:
tests/
folder).If user exposed functionality or configuration variables are added/changed: