#zbt-1 not connecting even after flashing the right name

8 messages · Page 1 of 1 (latest)

whole kettle
#

I installed the current version of Home Assistant a few hours ago (in a virtualenv) and connected up my recently-purchased ZBT-1.

Unfortunately, despite initially detecting something, when asked whether I wanted to use the device as Zigbee or Thread, and my choosing Zigbee, I was then given an error.

I found documentation saying that some people had been successful using cp210x-cfg so I cloned the repo and compiled the binary. I did see some warning messages:

cp210x-cfg# make
cc -std=c11 -O2 -pipe -Wall -Wextra -D_POSIX_C_SOURCE=2 -c src/main.c -o build/main.o
src/main.c: In function ‘cp2102n_set_serial’:
src/main.c:452:8: warning: ‘encode_descriptor_string’ accessing 256 bytes in a region of size 130 [-Wstringop-overflow=]
452 | if (!encode_descriptor_string ((uint8_t*) &cfg->serDesc, name))
...
src/main.c: In function ‘cp2102n_set_manuf’:
src/main.c:467:8: warning: ‘encode_descriptor_string’ accessing 256 bytes in a region of size 131 [-Wstringop-overflow=]
467 | if (!encode_descriptor_string ((uint8_t*) &cfg->mfrDesc, name))
src/main.c:467:8: note: referencing argument 1 of type ‘uint8_t[256]’ {aka ‘unsigned char[256]’}
src/main.c:393:13: note: in a call to function ‘encode_descriptor_string’
393 | static bool encode_descriptor_string (uint8_t out[256], const char *str)
cc build/main.o -lusb-1.0 -o cp210x-cfg

After this, I ran it as described, and it showed the following output:

./cp210x-cfg -N 'SkyConnect v1.0' -C 'Nabu Casa'

ID 10c4:ea60 @ bus 003, dev 047: SkyConnect v1.0
Model: CP2102N QFN24
Vendor ID: 10c4
Product ID: ea60
Name: SkyConnect v1.0
Manufacturer: Nabu Casa
Serial: c450e130a3dced11b692ef2d62c613ac
Use internal serial: 1
ret: 678
IMPORTANT: Device needs to be replugged for some changes to take effect!

but despite trying a few times, I did not get any further when HA detected the USB; the same error as above kept reappearing.

#

@leaden oxide
Ping

leaden oxide
#

How are you running Home Assistant?

#

Actually, you say virtualenv. Does your user have permission to communicate with serial ports?

#

@whole kettle I would also re-run the command, ./cp210x-cfg -N 'Home Assistant Connect ZBT-1' -C 'Nabu Casa'. Your device is being detected properly.

whole kettle
#

It could be a permissions issue. I created the home assistant account and the virtualenv is owned by that user, and systemd is running hacs as that user. But I didn't add that user to any groups, which could well be the problem. I'll give that a try and follow up with the result

#

Well that was easy. I added the user to the dialout group, rebooted and it is now working. Thanks for the tip! It'd be nice to add a hint to try this to the HA error message.

leaden oxide
#

I tried with the bottom part 😄