Backup of HUSBZB-1 not working #90

jds11111 · 2021-10-24T15:03:20Z

jds11111
Oct 24, 2021

EDIT: Everything seems to be working now, so let me put the steps in one place, in case anyone else could use the information. Some of this is already in the docs, which should be read, and this is for a supervised install using HassOS, switching from HUSBZB-1 to the Sonoff Zigbee 3.0 Dongle Plus. The new radio was already flashed with the latest firmware (in my case using cc2538-bsl.py). Thanks to @tube0013, @puddly and @MattWestb for help with the steps.

Disable ZHA integration, by Configuration->Integrations, click on the three dots for the ZHA integration, and choose "Disable"
SSH into the HA machine, and open a shell in the home assistant docker container:

docker exec -it homeassistant bash

Inside this shell, install bellows:

pip install zigpy-znp 'git+https://github.com/puddly/bellows@puddly/open-coordinator-backup'

Download the configuration of the old radio, HUSBZB-1, which in my case was located here:

bellows -d /dev/serial/by-id/usb-Silicon_Labs_HubZ_Smart_Home_Controller_C13017E9-if01-port0 backup > backup.json

Upload the configuration to the new Sonoff Zigbee 3.0 Dongle Plus, which immediately started finding nodes:

python -m zigpy_znp.tools.network_restore /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_0eccdc73c793eb11b26c1b4f3d98b6d1-if00-port0 -i backup.json
2021-10-24 12:28:47.931 homeassistant zigpy_znp.zigbee.application INFO Forming a new network
2021-10-24 12:29:06.806 homeassistant zigpy_znp.zigbee.application INFO Permitting joins for 0 seconds
2021-10-24 12:29:06.967 homeassistant zigpy.device INFO [0x0000] Requesting 'Node Descriptor'
2021-10-24 12:29:06.986 homeassistant 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_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress|RxOnWhenIdle|MainsPowered|FullFunctionDevice|AlternatePanCoordinator: 143>, manufacturer_code=0, maximum_buffer_size=80, maximum_incoming_transfer_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_full_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=False, *is_security_capable=False)
2021-10-24 12:29:06.988 homeassistant zigpy.device INFO [0x0000] Discovering endpoints
2021-10-24 12:29:07.000 homeassistant zigpy.device INFO [0x0000] Discovered endpoints: [2, 1]
...

Finally, to get HA to recognize the new radio, exit the docker shell with ctrl-d, and then navigate to the configuration file: cd /config/.storage. Make a copy of the configuration: cp core.config_entries core.config_entries_backup. Then edit it, using nano in my case: nano core.config_entries. Find the settings for ZHA (ctrl-w ZHA, return in nano), and make four changes: a) change "data.radio_type" to "znp", b) change "title" to something appropriate for your new radio, like "Sonoff Zigbee 3.0 Dongle Plus", c) change "data.device.path" to wherever your new radio is located (which you can find from Supervisor->System, and Hardware inside the three dots under Host), and d) change "data.device.baudrate" to "115200".
Reboot your HA computer. If you screwed up that config file, you might need to SSH back into the machine and restore your backup to get HA to start up after reboot, or you can try editing the config file to find your mistake.

That found my radio and saved my network settings. I did notice that all my Aqara remotes of the b1acn01 type were offline. However, putting the appropriate router or coordinator in "Adding Device" mode, and then holding the reset button on the Aqara, made it online again. All the other devices are working.

Original Post:

I (tried to) follow the instructions on home assistant to back up the coordinator: disable zigbee, ssh into machine, shell in docker. Then used the suggested command, and got the following errors:

~ $ docker exec -it homeassistant bash
bash-5.1# python -m zigpy_znp.tools.network_backup /dev/serial/by-id/usb-Silicon_Labs_HubZ_Smart_Home_Controller_C13017E9-if01-port0 -o network_backup.json
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/api.py", line 395, in request
    response = await response_future
asyncio.exceptions.CancelledError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.9/runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/local/lib/python3.9/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/tools/network_backup.py", line 104, in <module>
    asyncio.run(main(sys.argv[1:]))  # pragma: no cover
  File "/usr/local/lib/python3.9/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/usr/local/lib/python3.9/asyncio/base_events.py", line 642, in run_until_complete
    return future.result()
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/tools/network_backup.py", line 95, in main
    await znp.connect()
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/api.py", line 116, in connect
    self.capabilities = (await self.request(c.SYS.Ping.Req())).Capabilities
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/api.py", line 395, in request
    response = await response_future
  File "/usr/local/lib/python3.9/site-packages/async_timeout/__init__.py", line 55, in __aexit__
    self._do_exit(exc_type)
  File "/usr/local/lib/python3.9/site-packages/async_timeout/__init__.py", line 92, in _do_exit
    raise asyncio.TimeoutError
asyncio.exceptions.TimeoutError

Looks to me like it does not find the dongle, but I double checked the id of the device. Also tried rebooting the HA machine after disabling the coordinator. As a check I also tried downloading from the new Sonoff Zigbee 3.0 Dongle Plus, but received the same error.

Answered by tube0013

Oct 24, 2021

You need to use bellows to back up a SiLabs radio.

Puddy has a build that will create a compatible network backup:

pip install zigpy-znp 'git+https://github.com/puddly/bellows@puddly/open-coordinator-backup'

Backup;
bellows backup -d /dev/serial/.... > backup.json

Restore to new TI stick:
python -m zigpy_znp.tools.network_restore /dev/... -i /path/to/backup.json

View full answer

tube0013 · 2021-10-24T15:42:12Z

tube0013
Oct 24, 2021

You need to use bellows to back up a SiLabs radio.

Puddy has a build that will create a compatible network backup:

pip install zigpy-znp 'git+https://github.com/puddly/bellows@puddly/open-coordinator-backup'

Backup;
bellows backup -d /dev/serial/.... > backup.json

Restore to new TI stick:
python -m zigpy_znp.tools.network_restore /dev/... -i /path/to/backup.json

0 replies

jds11111 · 2021-10-24T16:14:25Z

jds11111
Oct 24, 2021
Author

Thanks. I think that there is something wrong with the order of your Backup command ("backup" should follow the device), but there was still an error. Maybe I should try to do it from a linux box, instead from inside a docker container. Anyway, apparently this is not the place to discuss backing up the SiLabs dongle. Thanks for the pointers!

0 replies

puddly · 2021-10-24T17:25:40Z

puddly
Oct 24, 2021
Maintainer

If you're doing a backup to migrate coordinators, this is as good a place as any to discuss. What's the error you receive? Did you disable the ZHA component before running any of these commands so that ZHA isn't concurrently using the serial port?

0 replies

jds11111 · 2021-10-24T17:42:58Z

jds11111
Oct 24, 2021
Author

Of course, that was it! I forgot that I re-enabled the dongle. I disabled it and then this command created a reasonable-looking json file:

bash-5.1# bellows -d /dev/serial/by-id/usb-Silicon_Labs_HubZ_Smart_Home_Controller_C13017E9-if01-port0 backup > backup.json

Then, I moved it to the new radio, and it looks like it worked:

bash-5.1# python -m zigpy_znp.tools.network_restore /dev/serial/by-id/usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_0eccdc73c793eb11b26c1b4f3d98b6d1-if00-port0 -i backup.json
2021-10-24 12:28:47.931 homeassistant zigpy_znp.zigbee.application INFO Forming a new network
2021-10-24 12:29:06.806 homeassistant zigpy_znp.zigbee.application INFO Permitting joins for 0 seconds
2021-10-24 12:29:06.967 homeassistant zigpy.device INFO [0x0000] Requesting 'Node Descriptor'
2021-10-24 12:29:06.986 homeassistant 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_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress|RxOnWhenIdle|MainsPowered|FullFunctionDevice|AlternatePanCoordinator: 143>, manufacturer_code=0, maximum_buffer_size=80, maximum_incoming_transfer_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_full_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=False, *is_security_capable=False)
2021-10-24 12:29:06.988 homeassistant zigpy.device INFO [0x0000] Discovering endpoints
2021-10-24 12:29:07.000 homeassistant zigpy.device INFO [0x0000] Discovered endpoints: [2, 1]
2021-10-24 12:29:07.001 homeassistant zigpy.device INFO [0x0000] Initializing endpoints [<Endpoint id=2 in=[] out=[] status=<Status.NEW: 0>>, <Endpoint id=1 in=[] out=[] status=<Status.NEW: 0>>]
2021-10-24 12:29:07.002 homeassistant zigpy.endpoint INFO [0x0000:2] Discovering endpoint information

plus more successful-looking lines. Many thanks @puddly and @tube0013 for your help!

Does anyone happen to know the best way to get HA to recognize the new radio? Maybe not deleting and reinstalling the integration?

1 reply

tube0013 Oct 24, 2021

You can edit the .storage/config_entities and find the zha entry

Change the path tot he device and ezsp to znp.

Be very careful and mistakes in the JSON will cause HA to fail to start.

jds11111 · 2021-10-24T17:54:32Z

jds11111
Oct 24, 2021
Author

Oh, that makes me nervous. Maybe I could make a backup of /config/.storage/core.config_entries, so that if I screw it up, then I could SSH into the machine and restore my backup and reboot?

2 replies

tube0013 Oct 24, 2021

Yes, backup will work 😉

jds11111 Oct 24, 2021
Author

Hmmm. HA started OK, but it throws an error trying to use the radio:

Logger: homeassistant.components.zha.core.gateway
Source: components/zha/core/gateway.py:152
Integration: Zigbee Home Automation (documentation, issues)
First occurred: 1:04:47 PM (2 occurrences)
Last logged: 1:05:50 PM

Couldn't start ZNP = Texas Instruments Z-Stack ZNP protocol: CC253x, CC26x2, CC13x2 coordinator
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/api.py", line 395, in request
    response = await response_future
asyncio.exceptions.CancelledError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 152, in async_initialize
    self.application_controller = await app_controller_cls.new(
  File "/usr/local/lib/python3.9/site-packages/zigpy/application.py", line 69, in new
    await app.startup(auto_form)
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/zigbee/application.py", line 196, in startup
    return await self._startup(
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/zigbee/application.py", line 209, in _startup
    await znp.connect()
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/api.py", line 116, in connect
    self.capabilities = (await self.request(c.SYS.Ping.Req())).Capabilities
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/api.py", line 395, in request
    response = await response_future
  File "/usr/local/lib/python3.9/site-packages/async_timeout/__init__.py", line 55, in __aexit__
    self._do_exit(exc_type)
  File "/usr/local/lib/python3.9/site-packages/async_timeout/__init__.py", line 92, in _do_exit
    raise asyncio.TimeoutError
asyncio.exceptions.TimeoutError

I assume that the baud rate is still 57600.

MattWestb · 2021-10-24T18:24:33Z

MattWestb
Oct 24, 2021

TI = 115200 and Software Flow Control.

2 replies

jds11111 Oct 24, 2021
Author

Changing the baud rate to 115200 fixed it. I suppose it is just out of curiosity, but is there an entry in the JSON file for software flow control? It is working now anyway. Many thanks @MattWestb, @puddly and @tube0013 . I will let it run for a few days to see how well the new radio works.

MattWestb Oct 24, 2021

I think its not needed then its the default in the config of ZHA.

You can also flashing the HUSBZB with 115200 firmware and its working OK (it was the old standard with 57600) if you like, but is practice no difference in the real world if not having on very large crowded network.

Great that you was getting it working doing the backup and restore of your system.

One trick if you need stopping ZHA for "occupying" the com port and need using the HA container for doing things like backup and restore is changing the comport config as you was doing with coordinator type to one not working comport and HA cant loading ZHA on restart and you can using the HA container and using the real device comport in the docker CLI :-))

jds11111 · 2021-10-25T16:08:45Z

jds11111
Oct 25, 2021
Author

Thanks all, for the help. I have edited my post to give all the necessary steps in one place. I did not see a way to change the flag from "unanswered" to "answered".

1 reply

MattWestb Oct 25, 2021

I think you is only having it on the first post to one answer and not on replay to one replay and not in the original posting.

Daniel-dev22 · 2021-10-27T23:22:53Z

Daniel-dev22
Oct 27, 2021

Where does the downloaded configuration save in case it was needed?

43 replies

Daniel-dev22 Dec 1, 2021

After jumping through hoops it finally is working. It was not starting again and I disabled then re-enabled.

A bunch of the Ikea buttons appear to be functional now. The network appears more responsive for sure as well.

MattWestb Dec 1, 2021

You can read the sw_build_id (id: 0x4000) on the basic cluster then waking the remote up and you is getting the current version of them.
If you dont like losing the binding you shall deactivating the IKEA OTS updates.

Daniel-dev22 Dec 1, 2021

One of them is

Firmware: 0x22010631

MattWestb Dec 1, 2021

2.2.010 is the last good with working group binding for the E1743 :-))
For the 5 button its 2.3.015.

If you like keeping the good working binding don't activating IKEA OTA.

If you like updating them but not to the lates bad one you can doing it with local OTA files but i don't recommend it for you then you have enough problems getting your system working stabile and shall not doing all things at the same time.

Daniel-dev22 Dec 1, 2021

@puddly Thank you for the help in getting it to work.
If it helps I did log the first 2 hours roughly of zha zigpy and I am uploading it here.
ZHA and Zigpy log

jds11111 · 2021-12-01T17:03:47Z

jds11111
Dec 1, 2021
Author

My own instructions are not working for updating core.config_entries. I had problems with my dongle, which I fixed, and wanted to move back to it. However, after I update this file, home assistant overwrites it with the old dongle information again. Does anyone know what detail I am stupidly missing, to avoid HA overwriting?

I think that I found the answer: first shut down the core ha core stop, then edit the file, finally restart the core: ha core start. That prevents the overwrite, but it is still not starting up correctly:

Logger: zigpy.application
Source: /usr/local/lib/python3.9/site-packages/zigpy/application.py:73
First occurred: 11:37:18 AM (3 occurrences)
Last logged: 11:38:28 AM

Couldn't start application

Followed by:

Logger: homeassistant.components.zha.core.gateway
Source: components/zha/core/gateway.py:152
Integration: Zigbee Home Automation (documentation, issues)
First occurred: 11:37:18 AM (3 occurrences)
Last logged: 11:38:28 AM

Couldn't start ZNP = Texas Instruments Z-Stack ZNP protocol: CC253x, CC26x2, CC13x2 coordinator
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/api.py", line 395, in request
    response = await response_future
asyncio.exceptions.CancelledError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 152, in async_initialize
    self.application_controller = await app_controller_cls.new(
  File "/usr/local/lib/python3.9/site-packages/zigpy/application.py", line 69, in new
    await app.startup(auto_form)
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/zigbee/application.py", line 196, in startup
    return await self._startup(
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/zigbee/application.py", line 209, in _startup
    await znp.connect()
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/api.py", line 119, in connect
    await self.nvram.determine_alignment()
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/nvram.py", line 35, in determine_alignment
    value = await self.osal_read(nvids.OsalNvIds.NWKKEY, item_type=t.Bytes)
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/nvram.py", line 170, in osal_read
    length = (await self.znp.request(c.SYS.OSALNVLength.Req(Id=nv_id))).ItemLen
  File "/usr/local/lib/python3.9/site-packages/zigpy_znp/api.py", line 395, in request
    response = await response_future
  File "/usr/local/lib/python3.9/site-packages/async_timeout/__init__.py", line 55, in __aexit__
    self._do_exit(exc_type)
  File "/usr/local/lib/python3.9/site-packages/async_timeout/__init__.py", line 92, in _do_exit
    raise asyncio.TimeoutError
asyncio.exceptions.TimeoutError

32 replies

puddly Dec 5, 2021
Maintainer

Would I need to reboot core for this or just reload zha?

You'd need to restart HA.

And do you think this will fix the pairing issues?

Probably not, you're the first to report issues like this.

How are you permitting joins? Are you clicking the blue "Add Device" button or going to a specific router and clicking "Add devices via this device"? Can you post the relevant chunk of your home-assistant.log file from when you permit joins?

Daniel-dev22 Dec 5, 2021

I am clicking both add device and going to a specific router and clicking add devices via this device and neither works. On the zha pairing screen when it says "show logs" I can see the router successfully received the request to accept new devices. The stick if I press the "add devices" shows unlike the nortek that shows it is permitting join requests.

I will post a relevant log some time today or tomorrow as I have to re-enable them I turned them off to avoid having a massive log file and I will try the dev

pypi:
  - zigpy_znp==0.6.3
  - zigpy==0.42.0

Daniel-dev22 Dec 6, 2021

Updating the coordinator firmware to the latest November developer firmware and updating to 0.6.3 at the same time appears to have fixed the ability to add devices. I was able to pair 2 devices that previously were not pairing. Time will tell as to whether it also solves the battery drainage issue on the Ikea buttons.

Daniel-dev22 Dec 8, 2021

@MattWestb the batteries are still being drained on a few. I enabled the ota updates but it keeps saying updates are not available when there has to be as it was never updated.

5 button remote firmware: Firmware: 0x23014631
Dimmer button firmware for most devices: Firmware: 0x22010631
One dimmer has this firmware that I repaired this morning: Firmware: 0x22008631

  zigpy_config:
    ota:
      ikea_provider: true

MattWestb Dec 8, 2021

I think you need triggering OTA requests from the device then its one sleeping one.
From the wiki for IKEA device:

Or for IKEA devices, you can go Config > Integrations > ZHA > Device > OTA Cluster > image_notify command to ask them to check in.

and pressing one button on the device so its waking up and can receiving the request then you is clicking "issue zigbee command".

Do only one or 2 device at the same time for not stressing the network and if the device is not working OK after the update deleting it and repairing it then its have getting / losing cluster that needs being red from the device.

jds11111 · 2021-12-10T04:05:11Z

jds11111
Dec 10, 2021
Author

I have discovered the strangest problem. There is an unknown device that has joined my network as a coordinator, and started taking it over. I think that it is the old HUSBZB dongle. It is still connected to run the Zwave network. Is there a way to make it stop. I assume that it has something to do with using the backup and restore, so that it still contains the network info.
EDIT: I am pretty sure that this rogue coordinator was causing lots of problems. Paired devices would move to use it as a router, but then all messages would just die there. I think it was also secretly pairing devices, which made them impossible to pair on the real network. Anyway, I found a way to remove it using zha.remove: https://www.home-assistant.io/integrations/zha/#service-zharemove

0 replies

balcanuc · 2022-02-17T15:56:30Z

balcanuc
Feb 17, 2022

Current Status: This approach is not working anymore. Follow the instructions on zigpy/zigpy-cli#2. Note that in order to follow the steps described on new link you need to have access to a linux system with git, python3 and gcc. Because I have my HA deployed using hassio, I had to get an ubuntu-docker image running along with the one from terminal. See instructions on my post on zigpy/zigpy-cli#2 for the commands I've used to build the zigpy. On a second thought, I think that using a separated docker instance from the homeassistant one is a better solution as it minimize the risk to break the home-assistant installation.

Here is my initial post.

Unfortunately the recipe is not working anymore. It fails when the command to install zigpy-znp is run.

When I run command below
pip install zigpy-znp 'git+https://github.com/puddly/bellows@puddly/open-coordinator-backup'

I get output below. I think is related to a dependency reference but I'm not a python expert, so I might be wrong.

bash-5.1# pip install zigpy-znp 'git+https://github.com/puddly/bellows@puddly/open-coordinator-backup'
Collecting git+https://github.com/puddly/bellows@puddly/open-coordinator-backup
  Cloning https://github.com/puddly/bellows (to revision puddly/open-coordinator-backup) to /tmp/pip-req-build-86ee7k1s
    ERROR: Command errored out with exit status 1:
     command: /usr/local/bin/python -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-req-build-86ee7k1s/setup.py'"'"'; __file__='"'"'/tmp/pip-req-build-86ee7k1s/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-pip-egg-info-agkl8k_w
         cwd: /tmp/pip-req-build-86ee7k1s/
    Complete output (28 lines):
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-req-build-86ee7k1s/setup.py", line 3, in <module>
        raise RuntimeError(
    RuntimeError:









    #######################################################################################
    This branch is obsolete!  Please test https://github.com/zigpy/zigpy-cli/pull/2 instead
    #######################################################################################











    ----------------------------------------
ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.

4 replies

julianjwong Apr 6, 2022

@puddly I too am getting stuck when trying to run the install command as per the comment above. Any suggestions?

puddly Apr 6, 2022
Maintainer

Where are you getting stuck?

julianjwong Apr 6, 2022

@puddly when running this command it fails

pip install zigpy-znp 'git+https://github.com/puddly/bellows@puddly/open-coordinator-backup'

The error message is

This branch is obsolete! Please test zigpy/zigpy-cli#2 instead

puddly Apr 6, 2022
Maintainer

Indeed. Did you follow the link and run that code instead?

julianjwong · 2022-04-06T21:24:01Z

julianjwong
Apr 6, 2022

Ah let me try that out and get back to you. Sorry for my noobness ☺️

…

On Thu, 7 Apr 2022, 7:19 am puddly, ***@***.***> wrote: Indeed. Did you follow the link and run that code instead? — Reply to this email directly, view it on GitHub <#90 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHW2LSKRWVYJ7ONKY2GAS43VDX5XTANCNFSM5GTVZAJA> . You are receiving this because you commented.Message ID: ***@***.***>

0 replies

Backup of HUSBZB-1 not working #90

Original Post:

Replies: 12 comments · 85 replies

jds11111 Oct 24, 2021 Author

puddly Oct 24, 2021 Maintainer

jds11111 Oct 24, 2021 Author

jds11111 Oct 24, 2021 Author

jds11111 Oct 24, 2021 Author

jds11111 Oct 24, 2021 Author

jds11111 Oct 25, 2021 Author

jds11111 Dec 1, 2021 Author

puddly Dec 5, 2021 Maintainer

jds11111 Dec 10, 2021 Author

puddly Apr 6, 2022 Maintainer

puddly Apr 6, 2022 Maintainer

Replies: 12 comments 85 replies

jds11111
Oct 24, 2021
Author

puddly
Oct 24, 2021
Maintainer

jds11111
Oct 24, 2021
Author

jds11111
Oct 24, 2021
Author

jds11111 Oct 24, 2021
Author

jds11111 Oct 24, 2021
Author

jds11111
Oct 25, 2021
Author

jds11111
Dec 1, 2021
Author

puddly Dec 5, 2021
Maintainer

jds11111
Dec 10, 2021
Author

puddly Apr 6, 2022
Maintainer

puddly Apr 6, 2022
Maintainer