Network restore and PAN ID #144

zyberwoof · 2022-03-07T17:18:48Z

zyberwoof
Mar 7, 2022

I'm currently trying to troubleshoot an issue getting Zigbee2MQTT to start. I've reflashed the firmware on my tube-zb-gw-cc2652p2-v2. Before reflashing, I did a network backup using this tool.

I can see in the JSON of the backup values for pan_id and extended_pan_id. However, when I run the network_restore I've noticed that the console shows different values for the PAN ID and Extended PAN ID from what is in the JSON backup. For example, my JSON shows the pan_id being 1a62.

Is this expected behavior?

python3 -m zigpy_znp.tools.network_restore socket://192.168.3.193:6638 -i network_backup.json
2022-03-07 11:44:30.036 megamind zigpy_znp.zigbee.application INFO Forming a new network
2022-03-07 11:45:14.951 megamind zigpy.device INFO [0x0000] Requesting 'Node Descriptor'
2022-03-07 11:45:14.988 megamind zigpy.device INFO [0x0000] Got Node Descriptor: NodeDescriptor(logical_type=<LogicalType.Coordinator: 0>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_ba
nd=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress|RxOnWhenIdle|MainsPowered|FullFunctionDevice|AlternatePanCoordinator: 143>, manufacturer_code=0, maximum_buffer_size=80, maximum_incoming_transfe
r_size=160, server_mask=11265, maximum_outgoing_transfer_size=160, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=True, *is_coordinator=True, *is_end_device=False, *is_fu
ll_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=False, *is_security_capable=False)
2022-03-07 11:45:14.989 megamind zigpy.device INFO [0x0000] Discovering endpoints
2022-03-07 11:45:15.018 megamind zigpy.device INFO [0x0000] Discovered endpoints: [2, 1]
2022-03-07 11:45:15.018 megamind zigpy.device INFO [0x0000] Initializing endpoints [<Endpoint id=2 in=[] out=[] status=<Status.NEW: 0>>, <Endpoint id=1 in=[] out=[] status=<Status.NEW: 0>>]
2022-03-07 11:45:15.019 megamind zigpy.endpoint INFO [0x0000:2] Discovering endpoint information
2022-03-07 11:45:15.052 megamind zigpy.endpoint INFO [0x0000:2] Discovered endpoint information: SizePrefixedSimpleDescriptor(endpoint=2, profile=49246, device_type=2080, device_version=0, input_clusters=[0], output_clusters=[])
2022-03-07 11:45:15.053 megamind zigpy.endpoint INFO [0x0000:1] Discovering endpoint information
2022-03-07 11:45:15.085 megamind zigpy.endpoint INFO [0x0000:1] Discovered endpoint information: SizePrefixedSimpleDescriptor(endpoint=1, profile=260, device_type=1024, device_version=0, input_clusters=[0, 25], output_clusters=[1280, 1282])
2022-03-07 11:45:15.085 megamind zigpy.device INFO [0x0000] Already have model and manufacturer info
2022-03-07 11:45:15.085 megamind zigpy.device INFO [0x0000] Discovered basic device information for <ZNPCoordinator model='CC1352/CC2652, Z-Stack 3.30+ (build 20211217)' manuf='Texas Instruments' nwk=0x0000 ieee=00:12:4b:00:25:90:08:ff is_initialized=True>
2022-03-07 11:45:15.085 megamind zigpy_znp.zigbee.application INFO Network settings
2022-03-07 11:45:15.086 megamind zigpy_znp.zigbee.application INFO   Model: CC1352/CC2652, Z-Stack 3.30+ (build 20211217)
2022-03-07 11:45:15.086 megamind zigpy_znp.zigbee.application INFO   Z-Stack version: 3.3
2022-03-07 11:45:15.086 megamind zigpy_znp.zigbee.application INFO   Z-Stack build id: 20211217
2022-03-07 11:45:15.086 megamind zigpy_znp.zigbee.application INFO   Max concurrent requests: 16
2022-03-07 11:45:15.086 megamind zigpy_znp.zigbee.application INFO   Channel: 15
2022-03-07 11:45:15.086 megamind zigpy_znp.zigbee.application INFO   PAN ID: 0xEFB4
2022-03-07 11:45:15.086 megamind zigpy_znp.zigbee.application INFO   Extended PAN ID: 07:15:60:c8:8a:cd:81:4b
2022-03-07 11:45:15.087 megamind zigpy_znp.zigbee.application INFO   Device IEEE: 00:12:4b:00:25:90:08:ff
2022-03-07 11:45:15.087 megamind zigpy_znp.zigbee.application INFO   Device NWK: 0x0000
2022-03-07 11:45:15.087 megamind zigpy_znp.zigbee.application INFO Permitting joins for 0 seconds

Answered by zyberwoof

Mar 8, 2022

Success! Thanks for the help @puddly.

For anyone who comes across the same issue, my commands for Linux were below. Replace the IP information with your own.

# My steps working with the tube-zb-gw-cc2652p2-v2 and Z2M
virtualenv -p python3.8 --clear venv 
source venv/bin/activate

pip install https://github.com/puddly/zigpy/tarball/puddly/new-radio-settings-api https://github.com/puddly/zigpy-cli/tarball/puddly/zigpy-radio-api https://github.com/puddly/zigpy-znp/tarball/puddly/new-radio-settings-api https://github.com/puddly/zigpy-deconz/tarball/puddly/new-radio-api https://github.com/puddly/bellows/tarball/puddly/zigpy-radio-api

# If the below command fails, try repeating it a few times.…

View full answer

puddly · 2022-03-07T18:04:44Z

puddly
Mar 7, 2022
Maintainer

For consistency, zigpy-znp forms a temporary network with completely random settings before replacing that network's settings with your expected ones.

I agree that printing the temporary settings is a little confusing and this will be fixed by #97

2 replies

puddly Mar 7, 2022
Maintainer

The current stable release of zigpy-znp also does not write all of the settings that Zigbee2MQTT expects (nothing that affects network operation) so Z2M will re-form your network from its own backup when you try using again with your adapter.

Use zigpy/zigpy-cli#2 to do the backup/restore to get Z2M to use the adapter as-is.

More concretely:

Restore the existing backup you took with zigpy-znp using zigpy_znp.tools.network_restore, to ensure that the stick is in a consistent state and matches the way it was before you took the backup.
Set up the venv for zigpy-cli and install it with the instructions in Implement new zigpy radio API #97.
Back up your stick again with the new zigpy cli.
Restore that backup to the stick with the new zigpy cli. The stick will now be compatible with Z2M.

zyberwoof Mar 8, 2022
Author

@puddly Just an FYI. When I'd run the backup command from my answer, it would fail about half of the time. By the end, I tried running the command back to back a few times. Below is the error that I'd get on the failures:

Traceback (most recent call last):
  File "/home/zyberwoof/venv/lib/python3.8/site-packages/zigpy_znp/api.py", line 950, in request
    response = await response_future
asyncio.exceptions.CancelledError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/zyberwoof/venv/bin/zigpy", line 8, in <module>
    sys.exit(cli())
  File "/home/zyberwoof/venv/lib/python3.8/site-packages/click/core.py", line 1128, in __call__
    return self.main(*args, **kwargs)
  File "/home/zyberwoof/venv/lib/python3.8/site-packages/click/core.py", line 1053, in main
    rv = self.invoke(ctx)
  File "/home/zyberwoof/venv/lib/python3.8/site-packages/click/core.py", line 1659, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/zyberwoof/venv/lib/python3.8/site-packages/click/core.py", line 1659, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/zyberwoof/venv/lib/python3.8/site-packages/click/core.py", line 1395, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/zyberwoof/venv/lib/python3.8/site-packages/click/core.py", line 754, in invoke
    return __callback(*args, **kwargs)
  File "/home/zyberwoof/venv/lib/python3.8/site-packages/click/decorators.py", line 38, in new_func
    return f(get_current_context().obj, *args, **kwargs)
  File "/home/zyberwoof/venv/lib/python3.8/site-packages/zigpy_cli/cli.py", line 19, in inner
    return loop.run_until_complete(cmd(*args, **kwargs))
  File "/usr/lib/python3.8/asyncio/base_events.py", line 616, in run_until_complete
    return future.result()
  File "/home/zyberwoof/venv/lib/python3.8/site-packages/zigpy_cli/radio.py", line 91, in backup
    await app.load_network_info(load_devices=True)
  File "/home/zyberwoof/venv/lib/python3.8/site-packages/zigpy_znp/zigbee/application.py", line 148, in load_network_info
    await self._znp.load_network_info(load_devices=load_devices)
  File "/home/zyberwoof/venv/lib/python3.8/site-packages/zigpy_znp/api.py", line 200, in load_network_info
    for dev in await security.read_devices(self, tclk_seed=tclk_seed):
  File "/home/zyberwoof/venv/lib/python3.8/site-packages/zigpy_znp/znp/security.py", line 259, in read_devices
    addr_mgr = await read_addr_manager_entries(znp)
  File "/home/zyberwoof/venv/lib/python3.8/site-packages/zigpy_znp/znp/security.py", line 158, in read_addr_manager_entries
    entries = [
  File "/home/zyberwoof/venv/lib/python3.8/site-packages/zigpy_znp/znp/security.py", line 158, in <listcomp>
    entries = [
  File "/home/zyberwoof/venv/lib/python3.8/site-packages/zigpy_znp/nvram.py", line 401, in read_table
    yield await self.read(
  File "/home/zyberwoof/venv/lib/python3.8/site-packages/zigpy_znp/nvram.py", line 329, in read
    read_rsp = await self.znp.request(
  File "/home/zyberwoof/venv/lib/python3.8/site-packages/zigpy_znp/api.py", line 950, in request
    response = await response_future
  File "/home/zyberwoof/venv/lib/python3.8/site-packages/async_timeout/__init__.py", line 129, in __aexit__
    self._do_exit(exc_type)
  File "/home/zyberwoof/venv/lib/python3.8/site-packages/async_timeout/__init__.py", line 212, in _do_exit
    raise asyncio.TimeoutError
asyncio.exceptions.TimeoutError

@puddly Lastly, a tip for when suggesting people test newer builds. I got tripped up for a while because older pip packages were installed in my virtualenv. Eventually I realized the issue. A suggestion would be to specify the "--clear" argument. I believe doing this removes the possibility of someone using the wrong build. An example would be virtualenv -p python3.8 --clear venv

Thanks again!

zyberwoof · 2022-03-08T18:47:40Z

zyberwoof
Mar 8, 2022
Author

Success! Thanks for the help @puddly.

For anyone who comes across the same issue, my commands for Linux were below. Replace the IP information with your own.

# My steps working with the tube-zb-gw-cc2652p2-v2 and Z2M
virtualenv -p python3.8 --clear venv 
source venv/bin/activate

pip install https://github.com/puddly/zigpy/tarball/puddly/new-radio-settings-api https://github.com/puddly/zigpy-cli/tarball/puddly/zigpy-radio-api https://github.com/puddly/zigpy-znp/tarball/puddly/new-radio-settings-api https://github.com/puddly/zigpy-deconz/tarball/puddly/new-radio-api https://github.com/puddly/bellows/tarball/puddly/zigpy-radio-api

# If the below command fails, try repeating it a few times.  I was able to run
# the same command repeatedly and have it complete successfully half of the time.
zigpy radio znp socket://192.168.10.10:6638 backup "zigpy-backup.json"
zigpy radio znp socket://192.168.10.10:6638 restore "zigpy-backup.json"

deactivate

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Network restore and PAN ID #144

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 2 comments 2 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

Network restore and PAN ID #144

zyberwoof Mar 7, 2022

Replies: 2 comments · 2 replies

puddly Mar 7, 2022 Maintainer

puddly Mar 7, 2022 Maintainer

zyberwoof Mar 8, 2022 Author

zyberwoof Mar 8, 2022 Author

zyberwoof
Mar 7, 2022

Replies: 2 comments 2 replies

puddly
Mar 7, 2022
Maintainer

puddly Mar 7, 2022
Maintainer

zyberwoof Mar 8, 2022
Author

zyberwoof
Mar 8, 2022
Author