Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AEOTEC USB Zwave module not creating /dev/ttyACM0 #3027

Closed
markcarline opened this issue Jun 27, 2019 · 87 comments

Comments

@markcarline
Copy link

commented Jun 27, 2019

When i connect one of these:

https://www.amazon.co.uk/Aeotec-Z-Stick-Z-Wave-create-gateway/dp/B00YETCNOE

I normally get this device:

/dev/ttyACM0

which is used for serial comms to zwave home automation via home assistant.

Connecting it to the Pi4 + Buster i see no such device, infact when i connect via lsusb i see no change before / after connecting.

Any ideas?

@pelwell

This comment has been minimized.

Copy link
Contributor

commented Jun 27, 2019

Do you get the same lack of results in the USB2 and USB3 ports?

@markcarline

This comment has been minimized.

Copy link
Author

commented Jun 27, 2019

Yes. I tried both usb2 and usb3 and I'm using a genuine pi 4 for power supply.

@pelwell

This comment has been minimized.

Copy link
Contributor

commented Jun 27, 2019

Are there any relevant messages in the kernel log? Unplug the device, sudo dmesg -C (to clear out the old messages), plug it in, wait a moment, then dmesg > usb.txt.

@markcarline

This comment has been minimized.

Copy link
Author

commented Jun 27, 2019

Hmm - i tried a fresh install of buster and got this:

[ 398.804524] usb 1-1.1: new full-speed USB device number 4 using xhci_hcd
[ 398.941260] usb 1-1.1: New USB device found, idVendor=0658, idProduct=0200, bcdDevice= 0.00
[ 398.941278] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 399.010369] cdc_acm 1-1.1:1.0: ttyACM0: USB ACM device
[ 399.012948] usbcore: registered new interface driver cdc_acm
[ 399.012958] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters

and i see /dev/ttyACM0

something is odd about my original install, when i try it on that install i get nothing appearing.

Let me reinstall HA over the weekend and i'll report back.

Thanks!

@pelwell

This comment has been minimized.

Copy link
Contributor

commented Jun 27, 2019

"HA"?

@markcarline

This comment has been minimized.

Copy link
Author

commented Jun 27, 2019

HA - Home Assistant. It uses zwave via the serial port /dev/ttyACM0

@markcarline

This comment has been minimized.

Copy link
Author

commented Jun 27, 2019

ok so.... i tried my "fresh" install and i can't recreate that message above. Seems very temperamental. I wonder if its power related.

@pelwell

This comment has been minimized.

Copy link
Contributor

commented Jun 27, 2019

Hmm - it could be power related, but I would expect some kind of response to a device insertion, not nothing.

@markcarline

This comment has been minimized.

Copy link
Author

commented Jun 27, 2019

Hmm - I tried the MicroSD card which wouldnt work on the Pi4 on my Pi3B+ and works flawlessly, plugged in + out + in + out....

81.081896] usb 1-1.3: new full-speed USB device number 6 using dwc_otg
[ 81.215187] usb 1-1.3: New USB device found, idVendor=0658, idProduct=0200, bcdDevice= 0.00
[ 81.215205] usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 81.289184] cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device
[ 81.290193] usbcore: registered new interface driver cdc_acm
[ 81.290201] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 95.383586] usb 1-1.3: USB disconnect, device number 6
[ 102.641555] usb 1-1.3: new full-speed USB device number 7 using dwc_otg
[ 102.774812] usb 1-1.3: New USB device found, idVendor=0658, idProduct=0200, bcdDevice= 0.00
[ 102.774830] usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 102.775964] cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device
[ 110.231628] usb 1-1.3: USB disconnect, device number 7
[ 115.331396] usb 1-1.3: new full-speed USB device number 8 using dwc_otg
[ 115.464944] usb 1-1.3: New USB device found, idVendor=0658, idProduct=0200, bcdDevice= 0.00
[ 115.464962] usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 115.466096] cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device

@markcarline

This comment has been minimized.

Copy link
Author

commented Jun 28, 2019

I thought I would check with aeotec as to the certification of the pi4 am I mentioned to check if a module is loaded, they said:


​We have tested using RPi V3 in this case, but we have not yet tested RPi 4. One item to absolutely make sure is that the cdc acm module is installed from the Linux kernel which is required to actuate as a ttyACM0 device. I'll look into acquiring a RPi V4 to see if i can find any issues here.

Cheers,
Chris Cheng
Field Application Engineer
Aeotec Inc.
www.Aeotec.com

I'm going to test more over the weekend, any ideas about the module they mentioned?

@pelwell

This comment has been minimized.

Copy link
Contributor

commented Jun 28, 2019

The module is in Raspbian images - see your kernel logs above.

Can you try connecting via a powered hub?

@markcarline

This comment has been minimized.

Copy link
Author

commented Jun 28, 2019

I currently only have the official raspberry pi 4 power supply, can you recommend a powered hub? I'll buy one. Thanks!

@pelwell

This comment has been minimized.

Copy link
Contributor

commented Jun 28, 2019

I wasn't expecting you to buy one, especially since I don't know if power is the cause of the problem, but the general rule of thumb round here is that Amazon Basics cables and adapters are safe bets.

@bieniu

This comment has been minimized.

Copy link

commented Jun 28, 2019

I had exactly same issue on RPi 3B after upgrade kernel to version raspberrypi-kernel_1.20181112-1 (November 4). Downgrade kernel fixed the issue. I haven't updated the kernel since then.

@markcarline

This comment has been minimized.

Copy link
Author

commented Jun 28, 2019

I had exactly same issue on RPi 3B after upgrade kernel to version raspberrypi-kernel_1.20181112-1 (November 4). Downgrade kernel fixed the issue. I haven't updated the kernel since then.

interesting but but i am guessing i can't do that with the PI4?

@bieniu

This comment has been minimized.

Copy link

commented Jun 28, 2019

interesting but but i am guessing i can't do that with the PI4?

I think not.

@markcarline

This comment has been minimized.

Copy link
Author

commented Jun 28, 2019

so... I found something interesting. If i connect it to one of the USB 2 ports (i tried all four actually) i get nothing in the dmesg logs.

but then when i connect a four port hub (that could be powered - but isnt) i see these:

[ 1269.486927] usb 1-1.4: new high-speed USB device number 15 using xhci_hcd
[ 1269.617433] usb 1-1.4: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.11
[ 1269.617448] usb 1-1.4: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 1269.617461] usb 1-1.4: Product: USB 2.0 Hub
[ 1269.618998] hub 1-1.4:1.0: USB hub found
[ 1269.619082] hub 1-1.4:1.0: 4 ports detected
[ 1270.046942] usb 1-1.4.1: new high-speed USB device number 16 using xhci_hcd
[ 1270.277312] usb 1-1.4.1: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.11
[ 1270.277327] usb 1-1.4.1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 1270.277340] usb 1-1.4.1: Product: USB 2.0 Hub
[ 1270.278633] hub 1-1.4.1:1.0: USB hub found
[ 1270.278720] hub 1-1.4.1:1.0: 4 ports detected

then when i connect the Aeotec USB stick to one of the back two USB ports I then see:

[ 1329.418219] usb 1-1.4.1.1: new full-speed USB device number 17 using xhci_hcd
[ 1329.654873] usb 1-1.4.1.1: New USB device found, idVendor=0658, idProduct=0200, bcdDevice= 0.00
[ 1329.654890] usb 1-1.4.1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1329.657705] cdc_acm 1-1.4.1.1:1.0: ttyACM0: USB ACM device

It now works 100% of the time.

odd

So your suggestion of using a hub @pelwell you might be onto something.

@pelwell

This comment has been minimized.

Copy link
Contributor

commented Jun 28, 2019

I think the Pi budget will stretch to one of these - I'll get one on order.

@markcarline

This comment has been minimized.

Copy link
Author

commented Jun 28, 2019

ok cool - I'm sure its something simple but from what i've read about this stick a few people have reported that updated BIOS on NUC PCs has fixed similar issues so maybe this is firmware related.

i remember seeing something similat with the pi2s back in the day and @ghollingworth i think helped fix it - some kind of timing issue with usb (I sent my hub in and they put it into some kind of usb tool.

anyway - i'm up and running with ZWave, Home Assistant and a super cool Pi4 now 💯 :)

@markcarline

This comment has been minimized.

Copy link
Author

commented Jul 3, 2019

By the way I happend to notice this article which talked about new firmware changes to the USB chip, could this issue be fixed as part of those changes?....

https://www.tomshardware.com/news/raspberry-pi-4-firmware-update-tested,39791.html

@pelwell

This comment has been minimized.

Copy link
Contributor

commented Jul 3, 2019

I'm expecting the ZWave module to arrive any day now so I'll be able to try the new firmware, but I wouldn't expect it to fix this issue. Plus, the power saving features are causing problems with some devices. However, that mainly seems to affect high throughput to SSDs, etc., and it is possible to revert to the original version, so feel free to try for yourself: https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=243500&p=1490467#p1490467

@daaaaan

This comment has been minimized.

Copy link

commented Jul 3, 2019

I can confirm the new firmware doesn't help the issue.

Mine exhibits the same behaviour as above, tho don't have a hub to test.

@P33M

This comment has been minimized.

Copy link
Contributor

commented Jul 3, 2019

Looking at some USB analyzer traces, the zwave module doesn't even signal a USB attach event. On a VLI expansion card in a PC, I see an attach event but spurious SE1s (illegal bus states) which makes me think that there's some oddness in the way the device is pulling D+/D-. Will require probing with a scope to find out what is happening.

@daaaaan

This comment has been minimized.

Copy link

commented Jul 3, 2019

Not sure if its relevant but on the rpi3 my stick exhibits no issue.

@markcarline

This comment has been minimized.

Copy link
Author

commented Jul 3, 2019

This is the USB hub that when I connect it to the pi 4 and the zwave USB device everything works fine:

https://rover.ebay.com/rover/0/0/0?mpre=https%3A%2F%2Fwww.ebay.co.uk%2Fulk%2Fitm%2F283514195231

@systemofapwne

This comment has been minimized.

Copy link

commented Jul 4, 2019

I might have a similar problem with a "WiMOD iM871A-usb". Whenever I plug in the stick, a new device is created in /dev. That stick has been configured to receive W-MBUS data. On my PC, it shows me data popping in when I connect to it via putty. But on the pi4 with Raspbian Buster, if I do "cat" on that device, the output is quiet (while on stretch, it was outputting received data).
I could reproduce a similar behaviour with a self-made "nano-cul" stick.

Error was on my end - Had to rebuild some node-js libraries.

@pelwell

This comment has been minimized.

Copy link
Contributor

commented Jul 4, 2019

There is something peculiar electrically about the Zwave dongle. When you plug it into the Pi 4 (through a USB analyser) the Pi tries to talk USB3 to it, and gets no response because the device is only USB2-capable. This shouldn't happen. Repeating the same test with a PC USB3 port as host you see the same USB3 chatter to start with, then after a few hundred milliseconds it falls back to USB3.

This suggests that the dongle has the electrical signature of a USB3 device and the VIA USB3 host controller doesn't get past that to try USB2. (I'm not sure that behaviour is required by the USB3 spec but it seems sensible)

@systemofapwne

This comment has been minimized.

Copy link

commented Jul 4, 2019

This is what I get with my stick:
[ 6951.473076] usb 1-1.4: new high-speed USB device number 8 using xhci_hcd
[ 6951.625698] usb 1-1.4: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice= 6.54
[ 6951.625712] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6951.625723] usb 1-1.4: Product: USB2.1 Hub
[ 6951.625732] usb 1-1.4: Manufacturer: GenesysLogic
[ 6951.634230] hub 1-1.4:1.0: USB hub found
[ 6951.634533] hub 1-1.4:1.0: 4 ports detected
[ 6951.973078] usb 1-1.4.4: new full-speed USB device number 9 using xhci_hcd
[ 6952.130569] usb 1-1.4.4: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
[ 6952.130579] usb 1-1.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 6952.130587] usb 1-1.4.4: Product: WiMOD iM871A-usb
[ 6952.130594] usb 1-1.4.4: Manufacturer: Silicon Labs
[ 6952.130601] usb 1-1.4.4: SerialNumber: 00B93F17
[ 6952.146717] cp210x 1-1.4.4:1.0: cp210x converter detected
[ 6952.152214] usb 1-1.4.4: cp210x converter now attached to ttyUSB1

For this test, I connected it to a hub this time. Yet, it fails to work, even though it gets added to /dev: There is no serial throughput whatsoever.
Error was on my end - Had to rebuild some node-js libraries.

@systemofapwne

This comment has been minimized.

Copy link

commented Jul 4, 2019

Just to make sure, that I did not mess anything up when I upgraded from stretch to buster: I just flashed buster (lite) from iso (on a RPi4), made an apt-get update/upgrade/dist-upgrade and tried it again:
"sudo cat /dev/ttyUSB1" does not print anything, while this stick definitely receives data and is supposed to print it here. There is definitly something messed up.

Error was on my end - Had to rebuild some node-js libraries.

@fribse

This comment has been minimized.

Copy link

commented Jul 9, 2019

There is something peculiar electrically about the Zwave dongle. When you plug it into the Pi 4 (through a USB analyser) the Pi tries to talk USB3 to it, and gets no response because the device is only USB2-capable. This shouldn't happen. Repeating the same test with a PC USB3 port as host you see the same USB3 chatter to start with, then after a few hundred milliseconds it falls back to USB3.
This suggests that the dongle has the electrical signature of a USB3 device and the VIA USB3 host controller doesn't get past that to try USB2. (I'm not sure that behaviour is required by the USB3 spec but it seems sensible)

Wouldn't that fit with those that have used a hub in between, if it's a USB2 hub, that it will not get confused, and just go to USB2?

@Mastiffen

This comment has been minimized.

Copy link

commented Aug 9, 2019

The Plexgear Desktop 500 still works 100 %, but I don't know if that's available everywhere. Here's the link so you can see what it looks like:

https://www.kjell.com/no/produkter/data-og-nettverk/kabler-og-adaptere/usb/usb-huber/plexgear-desktop-500-usb-3-0-hub-med-stromforsyning-4-veis-p69306

@CokkocZateki

This comment has been minimized.

Copy link

commented Aug 9, 2019

The Plexgear Desktop 500 still works 100 %, but I don't know if that's available everywhere. Here's the link so you can see what it looks like:

https://www.kjell.com/no/produkter/data-og-nettverk/kabler-og-adaptere/usb/usb-huber/plexgear-desktop-500-usb-3-0-hub-med-stromforsyning-4-veis-p69306

@Mastiffen do you have the Aeotec Z-Stick Series 5 and "Plexgear Desktop 500 USB 3.0-hub med strømforsyning 4-veis" with Raspberry PI 4?

@Mastiffen

This comment has been minimized.

Copy link

commented Aug 9, 2019

Yep.

@CokkocZateki

This comment has been minimized.

Copy link

commented Aug 9, 2019

Yep.

Great. I just started HA and ran into this issue. Going to buy one for myself :)

thank you

@Mastiffen

This comment has been minimized.

Copy link

commented Aug 9, 2019

No problem. :)

@bolausson

This comment has been minimized.

Copy link

commented Aug 10, 2019

Sabrent 4-Port USB 3.0 Hub mit einzelnen Power Schalter und LEDs (HB-UM43)

https://www.amazon.de/dp/B00JX1ZS5O/ref=cm_sw_em_r_mt_dp_U_SIUsDbGBZTS3Y

Now the big question is - will it work or not?!?

The Hub arrived today and I can confirm it is working. It works when plugged into the USB-3 port of the Pi4 - didn't test the USB-2 Ports.

pi@openhab $ lsusb 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 05e3:0616 Genesys Logic, Inc. hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB
Bus 001 Device 007: ID 1cf1:0030 Dresden Elektronik 
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Cheers,
Bjoern

@carloselectro

This comment has been minimized.

Copy link

commented Aug 11, 2019

I'm glad I have found this post, I can finally make my Zwave dongle work with this hub:

My hub

I have a raspberry pi 4 with the latest buster and Domoticz.

@fribse

This comment has been minimized.

Copy link

commented Aug 13, 2019

I finally got the Sabrent 4 port USB3 hub and my USB3 0,5 m extender cable, and I've plugged it into the lower USB3 port (no PSU for the hub).
I tried doing a complete shutdown and power-up, and it mounted immediately, so that config works perfectly.

@tomasz-darlowski

This comment has been minimized.

Copy link

commented Aug 22, 2019

I have still issue after reboot. When I manually replug usb hub, ACM0 device is correctly detected. But after reboot still nothing. Is there any command to execute (which I can put to crontab) which reset usb driver?

@LithiumNL

This comment has been minimized.

Copy link

commented Aug 23, 2019

I contacted the company of the stick last week and got this as a reply?

Unfortunately, this is a known problem, I have sent an RPi 4 to our team for testing and to search for an alternative solution. The current workaround is to use a powered USB 2.0 hub in between RPi4 and the Z-Stick Gen5 at this time.

If I get any more information over this issue, I will let you know.

I asked them what USB hub was needed and got this reply:

It must be an active USB hub. I cannot recommend a special product.
We hope to find a solution. Unfortunately we can't give out any details about the problem yet.

Just wanted to let you know.

@Gobolin80

This comment has been minimized.

Copy link

commented Aug 25, 2019

I can confirm that with a usb 2.0 hub (like this: https://www.amazon.it/gp/product/B00BWF5U0M/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1) works fine.

At first i tried with this 3.0 hub (https://www.amazon.it/gp/product/B00JX1ZS5O/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1) and it doesn't work

@frosso

This comment has been minimized.

Copy link

commented Aug 27, 2019

@Gobolin80 weird, i bought what seems to be the same item on amazon.com. It arrived today and I am using it right now.

https://www.amazon.com/gp/product/B00TPMEOYM/

I am currently using it with the wall charger. It doesn't look like on amazon.it they are selling it with the wall charger, although one review seems to be mention it.

@Gobolin80

This comment has been minimized.

Copy link

commented Aug 30, 2019

@Gobolin80 weird, i bought what seems to be the same item on amazon.com. It arrived today and I am using it right now.

https://www.amazon.com/gp/product/B00TPMEOYM/

I am currently using it with the wall charger. It doesn't look like on amazon.it they are selling it with the wall charger, although one review seems to be mention it.

@frosso it's realy weird! :)

@jsglazer

This comment has been minimized.

Copy link

commented Sep 3, 2019

I can confirm that Hassio 64bit (hassos_rpi4-64-3.4.img) on Pi4 16GB will work using an un-powered Sabrent Model HB-UM43 USB 2.0 hub plugged into Pi's USB 2 port. On /dev/ttyACM0. Can't wait to read the technical explanation for this one.

@pelwell

This comment has been minimized.

Copy link
Contributor

commented Sep 3, 2019

It's the hub - it insulates the Pi4's USB interface from the out-of-spec resistance of the ZWave module that makes it look like a USB3 device (which it isn't).

@skynet01

This comment has been minimized.

Copy link

commented Sep 7, 2019

I can also confirm that this usb 2.0 hub ( https://www.amazon.it/gp/product/B00BWF5U0M/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1) works fine. I tried other ones and they glitched, I got 50 zwave devices on it and it works pretty good.

@mattkime

This comment has been minimized.

Copy link

commented Sep 19, 2019

I have an older model of this guy (same model number) - https://www.amazon.com/D-Link-including-Charging-Adapter-DUB-H7/dp/B0000B0DL7

Works fine WITHOUT the power supply. Does not work with it. 🤷‍♂

@kelnos

This comment has been minimized.

Copy link
Contributor

commented Sep 19, 2019

I just purchased https://www.amazon.com/gp/product/B00BWF5U0M/ (the Sabrent 4-port hub) based on reports in this issue that it would work. However, the model that arrived in the mail didn't come with a power cable/adapter (there's a tiny barrel-type hole next to the USB-A cable, but it's unmarked). Anyone know what adapter might work with it?

Unfortunately, the Zwave stick doesn't work for me with this hub without external power. It is recognized and enumerated, and /dev/ttyACM0 appears, but shortly after OpenHAB starts talking to it, I see:

[ERROR] [ing.zwave.handler.ZWaveSerialHandler] - Got I/O exception Input/output error in writeArray during sending. exiting thread.

in the log, and after checking dmesg I see that the device disconnected and reconnected. So I'm guessing it's an issue of not enough provided power.

@skynet01

This comment has been minimized.

Copy link

commented Sep 19, 2019

I turned off all other porta and connected it to usb2.0 port on pi4, without external power to hub, seems to work fine for weeks now

@kelnos

This comment has been minimized.

Copy link
Contributor

commented Sep 19, 2019

I turned off all other porta and connected it to usb2.0 port on pi4, without external power to hub, seems to work fine for weeks now

I did the same with no luck :(

@fribse

This comment has been minimized.

Copy link

commented Sep 20, 2019

Ok, I got a reply from AEOTEC about the issue:

Attached is the electrical tests we have performed.
Conclusion: When Z-Stick is plugged into the USB port of RPi4, it causes the voltage of D- to be non-zero and has large noise; this is the main reason that causes the Z-Stick to be unrecognized by RPi4. By comparing other host device, we can conclude that this specific issue does not happen on other USB iterations.

We are looking into workarounds based on the data that we have tested with if we have any interesting information we will get back to you.

Z-Stick RPi4 Electrical Test Results.pdf

@fribse

This comment has been minimized.

Copy link

commented Sep 20, 2019

@kelnos

OpenHAB

I think most of us have tested it on RPi4 on HomeAssistant. I also have a 'powerless' Sabrent 4 port USB3 hub, and for me with RPi4 and HASS.IO it works, but it sounds like it's a different setup than yours.

@P33M

This comment has been minimized.

Copy link
Contributor

commented Sep 20, 2019

That's good. They've confirmed my findings (that the D+ pull is incorrect).

@pelwell

This comment has been minimized.

Copy link
Contributor

commented Sep 20, 2019

Can you explain why the laptop is showing different results (at an electrical level)?

@kelnos

This comment has been minimized.

Copy link
Contributor

commented Sep 20, 2019

I think most of us have tested it on RPi4 on HomeAssistant. I also have a 'powerless' Sabrent 4 port USB3 hub, and for me with RPi4 and HASS.IO it works, but it sounds like it's a different setup than yours.

Strange that there'd be a difference; maybe the HA vs. OpenHAB access patterns are different enough that HA is able to keep it from dropping off the bus. Anyway, I'll see if I can find a plug for the Sabrent hub, or find something similar and powered, and report back for posterity.

@P33M

This comment has been minimized.

Copy link
Contributor

commented Sep 20, 2019

Can you explain why the laptop is showing different results (at an electrical level)?

In the VIA case, after the +5V pull is detected by the downstream port then all bets are off. The reduction of the pull to a ~3.3V level suggests that the device itself is either driving J-state or has enabled its own internal pull to 3v3.

The only other odd behaviour is the D- line oscillating between 3.6V and 0V in the VIA case - but these oscillations are also present at a lesser amplitude on the laptop trace. I suspect measurement error as I don't see that when testing here.

@scorfman

This comment has been minimized.

Copy link

commented Oct 9, 2019

I have tested with this cheap USB 2.0 hub and it works great plugged into a 2.0 port on a Pi 4b 4Gb.

Same good results using this USB 3.0 hub in the 2.0 port

@SirAthos

This comment has been minimized.

Copy link

commented Oct 17, 2019

For those looking for something more compact and not powered, this hub also works well (plugged into a RPi4 USB3 slot, and using one of the hub's USB2 outlets for the Zwave module):
https://smile.amazon.com/gp/product/B071JTSMVQ
(Haven't yet done long term testing, but it's been stable for a couple of days now).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
You can’t perform that action at this time.