search

home-assistant / operating-system

:beginner: Home Assistant Operating System
Apache License 2.0
5.02k stars 982 forks source link

HA Blue does not recognize zooz s2 USB stick #1602

Closed froz closed 2 years ago

froz commented 3 years ago

Hardware Environment

Home Assistant OS release:

agners commented 3 years ago

Is /dev/ttyUSB* not available in the odroid kernel?

Various USB to serial drivers are enabled, so /dev/ttyUSB* devices are available on ODROID kernels. The fact that it does not show up on lsusb is rather concerning: It seems that the USB stack cannot enumerate that device.

Can you check a different device? Is it also not appearing on lsusb?

If so, this might be a hardware problem.

knwpsk commented 3 years ago

Having same problem.

@agners when you say try a different device: should I just plug in a plain USB "storage" stick, and should it be recognized by HA? Edit: I tried this. Nothing happened. Blue doesn't recognize the "storage" stick either, as far as I can tell. Nothing new shows up in Supervisor > System > Hardware. (Not sure if it matters that the stick was Windows-formatted??) But the storage stick does have power - it has LED lights that come on. So that at least verifies that the port is powered.

Forwarded link to this ticket to Zooz support so they know about the issue. Still working with them to try to troubleshoot.

agners commented 3 years ago

From what I understand the device should appear as /dev/ttyACMx (see https://www.getzooz.com/downloads/zooz-z-wave-plus-radio-s2-usb-stick-zst10-manual.pdf).

@knwpsk if none of the USB port is working, it could be a hardware issue. There are similar reports on the ODROID forum: https://forum.odroid.com/viewforum.php?f=181&sid=777a8ae2aa4be255a9ef55c98e2d09f9

knwpsk commented 3 years ago

@agners Agree, Zooz says it should show up as tty/ACMx. But it doesn't, not in any of the Blue's ports. I got it from Ameridroid, so I'm contacting them also. Very hard for me to tell what the issue is, or even where to start!

(If anyone has had success with HA Blue and the Zooz stick, please let me know. If anyone has had success with HA Blue and another z-wave controller stick, please let me know.)

knwpsk commented 3 years ago

Update: I plugged a keyboard into the same USB port on the Blue where I had the zooz stick. (And connected a monitor via hdmi.) The keyboard works, and I can type on the console page, and the Blue's startup logging clearly recognized "Dell wired keyboard." So, the physical port seems to be OK. That's not our problem.

basnagel commented 3 years ago

The aluminum cover on the Blue is to wide for some usb connectors and they don't connect, (Conbee|| stick for example)

agners commented 3 years ago

The aluminum cover on the Blue is to wide for some usb connectors and they don't connect, (Conbee|| stick for example)

Hm, I think the power leads are slightly longer, so that would explain why the USB stick LEDs did light up.

@knwpsk try without the front plate or using a USB extension cord, this should avoid the problem @basnagel is mentioning.

Also, do you see something in the Supervisor Host logs? Those are the kernel logs and definitly should show something when a new USB device gets enumerated.

knwpsk commented 3 years ago

I'll be damned. That worked! @agners @basnagel you guys are my heroes for seeing this through. Thank you!!

Recap: I can definitively confirm (by testing and contra-testing) that the problem I had with HA Blue detecting the Zooz S2 700 z-wave stick was that the Blue's silver faceplate is "too thick" and it doesn't let the stick plug all the way into the USB port. I removed the faceplate, plugged the stick in again, and it now appears in Blue's hardware list. In the attached photos, you can see that the difference is about 2 mm.

PXL_20211103_123203231 PXL_20211103_123339187 20211029 HA doesn't show S2 stick 20211103 HA shows S2 stick without faceplate

agners commented 3 years ago

@knwpsk thanks for the update and details. Yeah that is unfortunate, I think its the second USB dongle we found now which causes problems :cry:

@froz can you check if that is the problem in your case as well (pun not intended :sweat_smile: )

xeger commented 2 years ago

FYI - I had this precise problem, and after a few hours of searching various forums, came across this issue. Verified that the Zooz stick is talking to my N2 after plugging it in via an extension cable. Thank you so much to the person who suggested this solution (and to the person who was thoughtful enough to post it for others to find.

(Addendum: for me, it shows up not as /dev/ttyACM0 but as a /dev/serial/by-id dynamic device; no functional difference though. I'm guessing it's some devfs magic.)

agners commented 2 years ago

@froz closing this issue since I assume your problem is also related to the case/distance. Test with an USB extension cable.

rice1204 commented 2 years ago

Sorry to spam the thread, but just needed to say thanks!! I was tearing my hair out for the past hour trying to figure this out until I came across this thread. I have a machined aluminum case from ameridroid for the XU4 and the cause/solution was exactly the same!

numindast commented 2 years ago

Came here to add my voice of support. The HA Blue custom (beautiful) case prevented fully inserting the Zooz ZST10 700 stick. I went on a hunt and found an extension and less than 5 minutes later it's up and running in HA.

AJolly commented 11 months ago

Thanks! I thought my ha blue odroid N2+s usb ports were broken