Explain about ESP32-S3-BOX-3 sensors #4458
Conversation
And the fact they go unavailable with the currently available firmware, so people have more information to buy the device more consciously.
WalkthroughThe changes in this pull request primarily involve modifications to the Changes
Possibly related PRs
Suggested labels
Suggested reviewers
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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 (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (1)
projects/installer.html (1)
233-240: LGTM! Clear and helpful warning about firmware limitations.The warning message effectively communicates the firmware limitations and provides a clear recommendation for potential buyers. The text is well-structured and aligns perfectly with the PR objectives of preventing misunderstandings about device capabilities.
Minor suggestion: Consider adding a brief mention that these sensors work with the factory firmware, as mentioned in the PR description, to provide complete context.
<p> Also, keep in mind that <u>the currently available firmware does not support - any of the sensors from the additional dock</u>. Thus, unless you want + any of the sensors from the additional dock</u> (though they work with factory firmware). Thus, unless you want to tinker yourself with the device, it's recommended to buy the 3B variant, which does not come with the blue dock that has temperature/humidity/radar sensors and the IR emitter/receiver. It also does not include the adapter bracket and breadboard, which would be exclusive to custom-made projects. </p>
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (1)
projects/installer.html(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
projects/installer.html (1)
Pattern **: - Do not generate or add any sequence diagrams
✅ Deploy Preview for esphome ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
And the fact they go unavailable with the currently available firmware, so people have more information to buy the device more consciously.
Description:
Long story short, there are two versions of the device available, and the "default" one (both in stores and in promos images) is the blue one, which is a bit more expensive and comes with extra parts that become useless with the currently available firmware. The device has all sensors working with the factory software, but once you install the wakeword assistant, they do not show on HA, given they're probably not implemented.
Interested users must be aware of this, so there's no chance they'll buy the extra parts thinking they'll get an assistant with sensors included. Or that, at least, they buy knowing it could be added... someday.
Related issue (if applicable): This issue got mentioned here (home-assistant/home-assistant.io#35299 (comment)) a month ago, but it's not directly related.
Pull request in esphome with YAML changes (if applicable): none
Checklist:
I am merging into
nextbecause this is new documentation that has a matching pull-request in esphome as linked above.or
I am merging into
currentbecause 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.rstwhen creating new documents for new components or cookbook.