Thread: migrate to a new adapter#42007
Conversation
✅ Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Pull request overview
This pull request adds documentation for migrating an existing Thread network to a new adapter. The new section provides step-by-step instructions for users who want to switch their Thread adapter hardware while maintaining their existing Thread network configuration.
Key changes
- Added a new section "Migrating a Thread network to a new adapter" with prerequisites and step-by-step migration instructions
- Documented the process of configuring a new Thread adapter through the OpenThread Border Router add-on
- Clarified that Thread network credentials are managed by Home Assistant, not stored on the adapter hardware
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
| - on a Home Assistant Green, where Home Assistant OS is preinstalled | ||
| - On a Home Assistant Yellow or on a Raspberry Pi |
There was a problem hiding this comment.
First "on" is lower-case, second "On" is upper-case, for some reason.
Everything else starts with upper-case, so that's probably the right fix:
| - on a Home Assistant Green, where Home Assistant OS is preinstalled | |
| - On a Home Assistant Yellow or on a Raspberry Pi | |
| - On a Home Assistant Green, where Home Assistant OS is preinstalled | |
| - On a Home Assistant Yellow or on a Raspberry Pi |
There was a problem hiding this comment.
All of these suggestions are fixed with:
| - If you can't find the baudrate, contact the manufacturer's support. | ||
| - If you're feeling lucky, try `460800`. |
There was a problem hiding this comment.
nit: I think we can suggest users to try the de facto default for RCP firmware of 460800 before mentioning manufacturer support.
| - If you can't find the baudrate, contact the manufacturer's support. | |
| - If you're feeling lucky, try `460800`. | |
| - If you can't find the baudrate, try `460800` or contact the manufacturer's support. |
| - **Save** your changes. | ||
| - **Troubleshooting**: | ||
| - Check the logs. | ||
| - If the add-on crashes or fails to communicate with the Thread integration: Disable the **Hardware flow control** option and try again. |
There was a problem hiding this comment.
Let's use "Toggle" for the hardware flow control.
If it was on, it should be turned off. If it was off, it can be turned on.
| - If the add-on crashes or fails to communicate with the Thread integration: Disable the **Hardware flow control** option and try again. | |
| - If the add-on crashes or fails to communicate with the Thread integration: Toggle the **Hardware flow control** option and try again. |
There was a problem hiding this comment.
We may also be able to mention this should be set per the manufacturer's documentation, similar to the baudrate.
But we can still keep it in the troubleshooting section here, since it doesn't hurt to just toggle it on/off if it doesn't work initially.
| 6. Go to {% my integrations title="**Settings** > **Devices & services**" %}, select the **Thread** integration. | ||
| - Select the cogwheel {% icon "mdi:cog-outline" %}. | ||
| - **Result**: You should now see that the Thread network is still there. | ||
| - **Troubleshooting**: If you don't see the network there, go back to the add-on configuration and adjust your settings, if needed and try again. |
There was a problem hiding this comment.
nit: If we have a comma before the "if needed" part, we should also add one after it.
| - **Troubleshooting**: If you don't see the network there, go back to the add-on configuration and adjust your settings, if needed and try again. | |
| - **Troubleshooting**: If you don't see the network there, go back to the add-on configuration and adjust your settings, if needed, and try again. |
or remove it completely:
| - **Troubleshooting**: If you don't see the network there, go back to the add-on configuration and adjust your settings, if needed and try again. | |
| - **Troubleshooting**: If you don't see the network there, go back to the add-on configuration and adjust your settings if needed and try again. |
Proposed change
Migrate Thread to a new adapter
https://deploy-preview-42007--home-assistant-docs.netlify.app/integrations/thread/#migrating-a-thread-network-to-a-new-adapter
Type of change
currentbranch).currentbranch).nextbranch).nextbranch).Additional information
Checklist
currentbranch.nextbranch.