#How To Reset ZBT-2

1 messages · Page 1 of 1 (latest)

vagrant scroll
#

Hi team! I seem to be backed into a corner with the initial setup of the** ZBT-2**. The initial detection was automatic, but it stalled halfway through adding it and I waited about 10-15 minutes before stopping it and restarting HA.

Now I cannot get it added anymore. Nothing I do makes it appear in the discovered devices list, and I don't see a way to select/add it manually.

Here is what I have done:

  • Just to make sure it wasn't a ghost device, I checked the Devices list and it's not there.
  • I have reset the unit by unplugging it, holding in the reset button and plugged it back in. It does a fast yellow flashing, but then it goes to the slow blue flashing pattern (not fast-blue flash?)

Note that I do not have OpenThread Border Router or **Thread **enabled/installed yet, because those steps are later in the docs https://support.nabucasa.com/hc/en-us/articles/31347105826077-Forming-a-new-Thread-network-with-Home-Assistant-Connect-ZBT-2.

How else can I reset/restart the discoverable phase? What logs will tell me what is going on?

Thank you!

rose drift
#

if that doesn't help, you should probably contact nabu casa support.

#

make sure also to do a full restart of home assistant to reset the discovery

vagrant scroll
#

Thanks! I did try a host reboot (I'm using HA Blue) thinking it was a stuck USB process, but didnt help either. I was hoping that the FW was reinstallable (I tried flashing a 3rd party one, but that was a disaster, the model was too new)

vagrant scroll
#

Oh boy, even the firmware updater wont work. IT tries to connect, the blue light goes into a faster flash, then it craps out and I get this. I'm going to try one of my own USB cables, but the fact that the initial start to COM5 was fine gives me low hopes

image.png
#

For the Nabu Casa team looking at this from my support ticket, here's the Firmware Updater's log after it fails. Notice how it initially connects, then closes the connection. This might be also what is affecting its use back on Home Assistant Blue (I am flashing from my dev PC)?

📎 silabs_flasher.log
frail rampart
#

Did you try a different cable yet?

vagrant scroll
#

Yep, that possibility that they factory shipped cable was borked, or nearby interference was influencing it. I switched to my known working USB C cable I use for other flashing. [edit] Let me try a 3rd one, and another PC entirely

frail rampart
#

I have seen someone try to flash using windows where it failed, and then it worked on another machine with windows (and Chrome) so if that's an option along with using the toolbox it would be good to try

vagrant scroll
#

I'm loading up through my macbook pro, it detected the device manufacturer when the OS asked for perm to connect. I'm trying the site again and will give oyu an update as soon as I know more. In the meantime, what are the flashing LED codes? Copilot told me fast blue is clean start, slow blue is pairing mode, yellow is restart.

frail rampart
#

Flashing for thread, you will lose any light activity and reset button functionality. Reset for thread is done within home assistant.

#

You would need to flash for zigbee to get that back

vagrant scroll
#

I want to use it for Thread, and the fw update appears to be working on the mac. I see a bootloader recovery 3.0.1 and HA Connect ZBT-2. Then a "Change Firmware" option. Running it now

frail rampart
#

Blinking fast is probably due to holding it an an angle?

#

If you see any light activity after flashing it for thread, it will likely end faster than you would normally notice

vagrant scroll
#

I havent seen any fast flashing, just slow blue and a yellow (after I use the rest button). Now I have the option to flash the OpenThread, gonna try that

#

yep, it failed when trygin to flash for thread :/

frail rampart
#

@wide tundra are you around?

vagrant scroll
#

No variation of cord/USB port/OS seems to help. Here's what I am doing

  1. Switched from PC to macbook pro and Google Chrome (Edge & Chrome have same result, but they're both chromium)
  2. Click 'Install Firmware', COM selector popups up
  3. I select the "ZWA cu.usbmodemXXXXX" item (on PC this just says COMx)
  4. It connects and shows
    "
    Bootloader (recovery) 3.0.1
    HomeAssistant Connect ZBT-2
    Change Firmware
    "
  5. I select "Change Firmware" and it shows a list with: Zigbee (EZSP) and OpenThread (RCP)
  6. I select OpenThread
  7. PRogress bar starts at 0% and does not increase
  8. Errors out with the above debug log
frail rampart
#

I'm here from your ticket, btw @vagrant scroll
puddly might have more suggestions or questions for you (zigpy dev)

#

it is groundhog day, though.

vagrant scroll
#

I sincerely appreciate it. I'm at my wits end 😄 I tried a different device but sent it back to Amazon earlier this week and said "I should juts buy HA's dedicated device". It arrived yesterday and I was stoked... but now this 🙁

#

What might be relevant is the very first time I plugged it into the HA Blue (odroid-n2), it was detected, but failed in the same manner that we're seeing from the dedicated FW flasher.

[edit rephrased for clarity)

#

Also, I'm no stranger to Silicon Lab's sdk/devices, I've used commander many times, but I just don't have the recent experience/time to start from scratch like I used to 😎

Especially when it comes to zigbee/zwave/matter, I try to buy the most stable device and rely on your guy's awesomeness. and yeah, I was using HA in the very early days, well before Nabu Casa, running separate containers for everything, and slowly getting wife approval. Now I loooove the hardware from Nabu Casa, like the HA Blue/Green/etc because of the stability.

vagrant scroll
#

@wide tundra I need to step away form PC for the rest of the night. If I dont respond within 2 minutes, I probably wont see it until I get the email update. Please let me know all the things I need to do so I can handle it in one shot when I log on in the morning. Note: I do have USB to TTL gear and can probe the board if it needs to get to that level. Or maybe it better I ask for a replacement (this is only 1 day old)

wide tundra
#

Hey @vagrant scroll! I looked a bit closer at your logs and I'm noticing that you have the ZWA-2 bootloader. Just to confirm, is this a ZWA-2? Or is this a ZBT-2?

rose drift
#

if you're not sure, easiest way to tell them apart is by size: ZBT-2 is about 18cm/7" tall, ZWA-2 is about 31cm/12" tall.

#

(i sure hope there's not a batch of ZBT-2 out there with the ZWA-2 bootloader installed… tho that's on the radio soc bootloader not the esp32, right? so i'm not sure whether that's even possible…)

vagrant scroll
#

Hi! I'm back online (I'm in Boston). Ah, the label underneath says ZWA-2.

#

<flips desk>

This is the Z-wave one, isn't it... what a HUGE goof 😄 (OK, I just ordered the ZBT-2 from ameridroid, arrives in 2 days). I'll keep the ZWA-2 anyways, its far better than SmartThings hub's Zwave. So, back to the problem, I'll move forward with https://home-assistant.github.io/zwa2-toolbox/ to re-flash and start fresh.

vagrant scroll
#

The new tool works but fails when trying to download the release with a 403. I found the repo for it and will open an issue

  • [Edit 1] Opened https://github.com/home-assistant/zwa2-toolbox/issues/40. I determined the problem; you need to upgrade your corsproxy plan.
  • [Edit 2] Actually, I'm forking the repo and fix the code to use api.allorigins.win instead of corsproxy.io (more reliable and you guys don't have to pay for it). If it works for me, I'll open a PR.
vagrant scroll
vagrant scroll
#

Okay, @wide tundra I have an update, here's a recap so you don't need to read everything above

  1. Face palm after realizing I bought the wrong thing (immediately purchase the ZBT-2, arrives in 2 days)
  2. Got off my pity pot and went to work, but now the ZWA firmware updater is broken 🤦‍♂️.
  3. I cloned and fixed it opened PR w/ fix
  4. Installed fresh copy of firmware, HA still does not detect it
  5. Fortunately, the Z-Wave JS addon does detect the serial port, so I selected it
  6. HA still didn't autodetect, so I rebooted the host
  7. After reboot, the ZWA-2 light was a steady blue! Now the Devices page shows a Z-Wave service available.

All is good for Z-Wave, time to move stuff off SmartThings ot HA 🥳 Thank you all @frail rampart @rose drift! Next time I'm in town, dinner is on me.

GitHub
Fix CORS Proxy Problem by LanceMcCarthy · Pull Request #41 · home...

Fixed #40. The app is using a service that need to be updated to a paid plan. In this pull request, I have migrated the project to use a more modern option, api.allorigins.win instead of corsproxy....

rose drift
#

well, I'm glad you're happy with your now working ZWA-2 :) I guess this is a problem with TLA device codenames, they're sometimes hard to tell apart when you're not paying close attention…

vagrant scroll
#

Def my fault for rushing to buy it, I manually searched on Amazon. All the ZBTs are sold out, so they gave me only a single a search result for the ZWA instead. It looks liek the thing I wanted and clicked "Buy Now".

I never gave it any scrutiny due to the appearance and not knowing there was also a ZWA in the world. I usually read the specs very closely because of esp32 mishaps in the past. So, now I'll be a proud owner of both 😅

frail rampart
#

Can you fit a roll of toilet paper? ZBT-2
Paper towel? ZWA-2