-
-
Notifications
You must be signed in to change notification settings - Fork 2k
esp32_camera: Remove remaining references to i2c_pins-option from examples #5115
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
esp32_camera: Remove remaining references to i2c_pins-option from examples #5115
Conversation
WalkthroughThe ESP32 camera component documentation was updated to replace deprecated inline I²C pin configuration with an explicit Changes
Suggested labels
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
✅ Deploy Preview for esphome ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
8cc6a99
to
9d6673b
Compare
9d6673b
to
cee252d
Compare
cee252d
to
8d5f966
Compare
…mples - Remove deprecated configuration option - Rework example for Freenove ESP32-S3-DevKitC-1 to use new `frame_buffer_location: PSRAM` option instead of external component
8d5f966
to
b7b6f4c
Compare
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.
Please add the entry to the configuration variables list =)
@jesserockz wrote:
I've added a minimal documentation to the next branch: Maybe @MichaKersloot can add some details on when to use? :) |
I think it's only when the board doesn't have psram |
Okay, but why then export this as option? Just detect that there's no psram and use dram in this case... or am I missing something? |
No you do not miss something. To me it looks like there is some detection for PSRAM implemented somewhere (there is a log entry at boot for that). But somehow it does not work for all boards, in my case the TTGO T-journal. So an option to override this was needed for me. There could be a better fix at a lower level, but that is way beyond my capabilities and this option at least makes the esp32_camera module useable for me now. I tried to find the original discussion that leaded to this fix, but was unable to find it. |
Yeah I did a lot of fixing in the esp32-camera library in the last couple of days, I'll just have a look why it may fail. I think I spotted the detection somewhere. Can I mention you for testing with hardware? Because my hardware all got PSRAM. |
Let's suspend the PR for this time. |
I'll be on holydays for a few weeks, so testing would not be possible for a while. Further the camera is in use, so switching between Home Assistent and current master releases of ESPHome is not that easy for me. That's the reason why my patch only applies to official releases and not to the current master. Postponing this fix would mean ESPHome would not be useable for a couple of boards without my unofficial fix for the time being. |
Hey @MichaKersloot I'm not postponing a fix, I just think it should be automatic instead of a user decision. I'll have a look if there's a detection and maybe it's just broken in the esp32-camera lib, when I'm home. I'm on the go right now. If that's not possible, it's maybe possible to do this in ESPHome itself. |
Hmm.. i've read my previous comment and I see it looks a bit grumpy. Sorry! Thank you for your time and effort to fix this. I'll try to make some time next week for this. |
No worries! Enjoy your free time and just let me know if you got really the head and mind free to look at this. :) I'll just mention you on everything I'll find about that topic. |
@jesserockz alright, after reading the esp32-camera lib source code on that matter: If we don't specify anything, the default would be PSRAM and there's no detection on steering this decision, not "auto" mode, no fallback. So I was misremembering things - sorry. So my suggestion would be to implement this setting like it's currently proposed, and then add in the future a third value, |
I'll resubmit this changes for |
Description:
Small fix for the examples in ESP32_Camera to all show the new
i2c:
-block +i2c_id:
option in ESP32_Camera, instead of the now undocumentedi2c_pins:
option.Related issue (if applicable): discussed in #9601
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
/components/index.rst
when creating new documents for new components or cookbook.