#If the web flasher doesn't work, ZHA isn

1 messages · Page 1 of 1 (latest)

jaunty sphinx
#

Thats the one I flashed but it doesn't work either

jaunty sphinx
#

no

#

I also flashed the router firmware as a test and the console logs stuff but with the coordinator one it doesn't output anything, just "{~"

jagged crypt
#

It won't until you actually communicate with it

jaunty sphinx
#

But even then the web flasher doesnt detect it

#

with whatever firmware i tried

jagged crypt
#

What browser are you using?

jaunty sphinx
#

Chrome

#

it works great with esp web tools for serial connection

jagged crypt
#

The serial port isn't in use by other tools, right?

jaunty sphinx
#

i also tried restarting windows but its not used by anything afaik

jagged crypt
#

Do you have a Linux environment that isn't inside of a VM?

jaunty sphinx
#

I could use a raspberry pi

jagged crypt
#

If you have one running, you can just directly use the firmware flasher:

wget 'https://github.com/darkxst/silabs-firmware-builder/raw/main/firmware_builds/zbdonglee/ncp-uart-hw-v7.4.3.0-zbdonglee-115200.gbl'
pip install universal-silabs-flasher zigpy-cli
universal-silabs-flasher -vvv --device /dev/serial/by-id/... flash --firmware *.gbl --force
jaunty sphinx
#

thx I'll give it a try

jaunty sphinx
#

okay it's flashed now but the web flasher still cant connect

#

let's see if HA can detect it

#

It's still confusing that the USB Device id is 10c4:ea60 and not 1A86:55D4

#

10c4:ea60 is not the ZBDongle-E EFR32MG21 one but the ZBDongle-P afaik

#

And HA still fails to setup with: Failed to probe the usb device

jagged crypt
jaunty sphinx
#

just plugging in

jagged crypt
#

Can you post the flasher verbose logging output?

jaunty sphinx
jagged crypt
#

The flasher effectively uses ZHA to communicate with the stick to get it into its bootloader. If it can do that, the stick is 100% functional so whatever issue you're having inside of HA OS is USB passthrough.

#

What about the beginning?

#

That would indicate if the stick is actually functional or if it's stuck in the bootloader

jaunty sphinx
#

Unfortunately it's cut due to windows terminal buffer size

#

it starts at uploading 3%

jagged crypt
#

In that case, get rid of --force

jaunty sphinx
#

but it entered the bootloader

jagged crypt
#

It should say that the firmware version you're trying to install is already running

jaunty sphinx
#

okay lets see

#
2024-08-23 18:57:07.827 raspberrypi bellows.ash DEBUG Sending data  444121a9fe2a04284a7e
2024-08-23 18:57:07.836 raspberrypi bellows.ash DEBUG Received data 4541a1a9fe2a15b559944d21a9553806d87e
2024-08-23 18:57:07.836 raspberrypi bellows.ash DEBUG Received frame DataFrame(frm_num=4, re_tx=0, ack_num=5, ezsp_frame=b'\x03\x80\x01\xaa\x00\x00\x07\x00\x00\x07\x04\x03\x00\xaa')
2024-08-23 18:57:07.837 raspberrypi bellows.ash DEBUG Sending frame AckFrame(res=0, ncp_ready=0, ack_num=5) + FLAG
2024-08-23 18:57:07.838 raspberrypi bellows.ash DEBUG Sending data  8520dd7e
2024-08-23 18:57:07.838 raspberrypi bellows.ezsp.protocol DEBUG Received command getValue: {'status': <EzspStatus.SUCCESS: 0>, 'value': b'\x00\x00\x07\x04\x03\x00\xaa'}
2024-08-23 18:57:07.839 raspberrypi bellows.ash DEBUG Changing ACK timeout from 0.96 to 0.85
2024-08-23 18:57:07.841 raspberrypi bellows.uart DEBUG Connection lost: None
2024-08-23 18:57:07.842 raspberrypi bellows.uart DEBUG Closed serial connection
2024-08-23 18:57:07.942 raspberrypi universal_silabs_flasher.flasher INFO Detected ApplicationType.EZSP, version '7.4.3.0 build 0' (7.4.3.0.0) at 115200 baudrate (bootloader baudrate None)
2024-08-23 18:57:07.942 raspberrypi universal_silabs_flasher.flash INFO Firmware version '7.4.3.0 build 0' (7.4.3.0.0) is flashed, not re-installing
#

seems to be good

jagged crypt
#

Right, so the stick works and the firmware that's expected to be running is running

#

So it's unfortunately a passthrough issue

jaunty sphinx
#

but I'm using a SkyConnect as well without any issues

#

same configuration

#

is it better to passthrough a full port instead of a single device?

jagged crypt
#

I'm not too sure, I assume the full port would prevent the hypervisor from being too smart

#

10c4:ea60 is a SiLabs CP2102(N) chip, same as the SkyConnect

jaunty sphinx
#

I'm trying to reboot the entire system, maybe that might help

#

or just running HA on the pi with the stick to try if it works

jagged crypt
#

The flasher and ZHA use the exact same library to communicate with the stick

jaunty sphinx
#

But I wonder why it's detected by HA and the ZHA Integration

jagged crypt
#

Discovery uses just the USB info which is separate from the serial port device

#

USB passthrough often passes through the USB info but the actual serial port isn't functional

jaunty sphinx
#

I found a thread where they suggested to install linux-modules-extra-5.15.0-30-generic on the vm to make the stick work

#

however thats not possible on HA OS

jagged crypt
#

The stick is 100% compatible with HA OS running on bare metal, the serial drivers are part of the Kernel

#

And HA OS is very up-to-date with kernel releases, they're on 6.6.31, 5.51.0 would be ancient 😄

jaunty sphinx
#
usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_56f54acc8ee7ed1194fb646262c613ac-if00-port0```
#

that's on the HA Cli

jagged crypt
#

Yeah, that's normal and generated from the USB descriptors

#

But just the USB descriptors, nothing else

jaunty sphinx
#

mhh so I guess there is no solution

jagged crypt
#

What hypervisor and OS are you using?

#

Is this running from Windows?

jaunty sphinx
#

Proxmox Virtual Environment 8.1.3

#

And HA OS Generic X86

jagged crypt
#

Have you tried passing through the whole port instead of just the specific USB device?

jaunty sphinx
#

yea but unfortunately no difference

jagged crypt
#

It's a common issue with Proxmox, I'm not too sure why some serial chips work with it and some don't

jaunty sphinx
#

Would it be possible to provide the serial connection via tcp?

#

connecting the dongle to the host and providing the connection via tcp serial

jagged crypt
#

Sure, socket://... is a valid serial port path for ZHA

jaunty sphinx
#

Okay that works now using ser2net on the Host