-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
[xiaomi_miscale] Add support for S400 #4801
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. |
3819684 to
869463b
Compare
|
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. |
|
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. |
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.
Pull request overview
This PR adds documentation for the Xiaomi Body Composition Scale S400 (MJTZC01YM) to the xiaomi_miscale component. The S400 model supports additional features compared to existing models, including encrypted BLE advertisements, dual-frequency impedance measurement, heart rate monitoring, and multi-user profiles.
Key Changes:
- Added S400-specific configuration section with encryption requirements
- Documented new sensor types (impedance_low, heart_rate, timestamp, profile_id)
- Added multi-user configuration example for S400
Signed-off-by: zry98 <dev@zry.io>
Description:
Add support for Xiaomi Body Composition Scale S400 (MJTZC01YM) to the component
xiaomi_miscale.Pull request in esphome with YAML changes (if applicable):
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
/components/index.rstwhen creating new documents for new components or cookbook.