mirror of
https://github.com/Koenkk/zigbee2mqtt.git
synced 2026-07-02 01:51:38 +00:00
Added information on how to flash firmware without re-pairing (#1045)
* Added information on how to flash firmware without re-pairing * Fixed typos and added `permit_join` info * Update index.md
This commit is contained in:
@@ -3,7 +3,7 @@ The CC2531 USB stick needs to be flashed with a custom firmware.
|
||||
|
||||
*NOTE 1: The following instructions assume you have a CC Debugger. In case you don't, see [Alternative firmware flashing methods](../information/alternative_flashing_methods.md).*
|
||||
|
||||
*NOTE 2: When you have already flashed the stick and paired devices to it, reflashing it requires to re-pair all your devices!*
|
||||
*NOTE 2: When you have already flashed the stick and paired devices to it, reflashing it requires to re-pair all your devices! You can try to avoid this (see: [Flashing without re-pairing](../information/flashing_without_re-pairing.md))*
|
||||
|
||||
## Windows
|
||||
1. Install [SmartRF Flash programmer](http://www.ti.com/tool/FLASH-PROGRAMMER) (**NOT V2**). This software is free but requires a Texas Instruments account in order to download.
|
||||
|
||||
@@ -45,3 +45,4 @@ Welcome to the Zigbee2mqtt documentation!
|
||||
* [CC sniffer devices](information/cc_sniffer_devices.md)
|
||||
* [Alternative flashing methods](information/alternative_flashing_methods.md)
|
||||
* [Running Zigbee2mqtt in Virtual Environment](information/virtual_environment.md)
|
||||
* [Flashing without re-pairing](information/flashing_without_re-pairing.md)
|
||||
@@ -0,0 +1,23 @@
|
||||
# Flashing without re-pairing
|
||||
|
||||
## Why do I need to re-pair?
|
||||
Flashing firmware usually requires re-pairing of all connected [routers](zigbee_network.md#Router).
|
||||
If you remove the coordinator from the network, the remaining routers (e.g. bulbs) can still communicate with each other and they still form a zigbee network.
|
||||
If you now flash the coordinator and try to bring it back to the network, it will use its old `pan_id` incremented by one.
|
||||
So if you used the default `pan_id: 0x1a62` your coordinator will now use `pan_id: 0x1a63`.
|
||||
This will result in a new PAN (personal area network) with no connection to the old one.
|
||||
|
||||
This means that you have to follow the instructions on how to [pair a device](../getting_started/pairing_devices.md) again for every router that was connected to the coordinator.
|
||||
|
||||
## How to avoid re-pairing
|
||||
You can try to avoid this by bringing your coordinator out of range from your other network devices. There are multiple options to achieve this:
|
||||
|
||||
* Shield the coordinator with tinfoil
|
||||
* Take the coordinator physically out of range (e.g. drive to a nice place with your coordinator)
|
||||
* Cut the power of all connected routers
|
||||
|
||||
Once you are outside the network range you can [flash the coordinator with the new firmware](../getting_started/flashing_the_cc2531.md) and start zigbee2mqtt.
|
||||
After zigbee2mqtt started successfully, you can shutdown zigbee2mqtt and bring the coordinator back in network range.
|
||||
|
||||
Your coordinator should now use the old `pan_id` and therefore be in the same PAN as before.
|
||||
You need to set `permit_join: true` and wait a few minutes to let your devices reconnect.
|
||||
Reference in New Issue
Block a user