Skip to content

Conversation

@tomaszduda23
Copy link
Contributor

@tomaszduda23 tomaszduda23 commented Dec 7, 2025

Description:

Related issue (if applicable): fixes

Pull request in esphome with YAML changes (if applicable):

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.

New Component Images

If you are adding a new component to ESPHome, you can automatically generate a standardized black and white component name image for the documentation.

To generate a component image:

  1. Comment on this pull request with the following command, replacing COMPONENT_NAME with your component name in UPPER_CASE format with underscores (e.g., BME280, SHT3X, DALLAS_TEMP):

    @esphomebot generate image COMPONENT_NAME
    
  2. The ESPHome bot will respond with a downloadable ZIP file containing the SVG image.

  3. Extract the SVG file and place it in the images/ folder of this repository.

  4. Use the image in your component's index table entry in /components/index.rst.

Example: For a component called "DHT22 Temperature Sensor", use:

@esphomebot generate image DHT22

@netlify
Copy link

netlify bot commented Dec 7, 2025

Deploy Preview for esphome ready!

Name Link
🔨 Latest commit 9fec3e5
🔍 Latest deploy log https://app.netlify.com/projects/esphome/deploys/6935552a763ecf00087e01a1
😎 Deploy Preview https://deploy-preview-5740--esphome.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify
Copy link

netlify bot commented Dec 7, 2025

Deploy Preview for esphome ready!

Name Link
🔨 Latest commit 953b5b5
🔍 Latest deploy log https://app.netlify.com/projects/esphome/deploys/6935c64302295b00085a3cfb
😎 Deploy Preview https://deploy-preview-5740--esphome.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

image: system-update.svg
---

The nRF52 platform supports firmware updates via Over-the-Air (OTA) mechanisms. The **only supported bootloader** for OTA updates is **MCUboot**.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we improve the documentation on what we need around MCUboot? Most of what I read suggests that we only need slot0 partition but I suspect we need at least two slots for MCUBoot? My nice!nano nRF52 currently has an Adarfruit boot loader and I'm not certain what is required.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Best if you could open a PR with redaction of the doc. Push to this branch or just open new PR. I can link it to main PR. nrf52 doc could be improved in few places but I have no much time to think about it.

In the nut shell you need:

  1. flash firmware using SWD e.g. by stlink https://esphome.io/components/nrf52/#flashing-with-mcuboot
  2. From that moment you can flash new firmware using serial, cdc serial or ble

By default it use slot0 and slot1. https://docs.nordicsemi.com/bundle/ncs-latest/page/mcuboot/readme-zephyr.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants