RTL-SDR v3 usb dongle not recognized by HA OS running on NUC

I just bought a RTL-SDR v3 usb dongle to use w the wmbusmeters add-on in order to pick up signals from my mbus watermeter. However, I cannot get HA to recognize the usb device.

I have tried all usb ports on the NUC. Tried unpluggning all other dongles. Done multiple restarts w different combinations of plugging and unplugging but no luck. Nothing seems to be picked up in the “All Hardware” section of HA. I have verified that the dongle works by running wmbusmeters on my Ubuntu 22.04 laptop and it picks up my watermeter fine.

Is this particular dongle not supported by HA OS? Is there something I am missing?

Many thanks

I’m in the same boat- did you find a solution?

[edit] I changed three things and one of them worked.

  • First, I moved the radio to a USB2 port (vs USB3 on my Pi4)
    ** No immediate changes seen
  • Then, I plugged the dongle into a Win10 box and installed the WinUSB driver using the Zadig software.
    ** I was able to get a signal using SDR Console v3.1
  • Next, I plugged the dongle back into my Pi and ran dmesg, but instead of the previous “unable to enumerate USB device”, it said “Cannot enable. Maybe the USB cable is bad?”
    ** I swapped to a know good cable and dmesg now says “usbcore: registered new interface driver dvb_usb_rtl28xxu”

Thanks for the update.

I returned my RTL-SDR v3 and ordered another dongle but this sounds interesting and makes me willing to go back.

When you “installed the WinUSB driver”, did that also update the firmware of the SDR somehow?
Otherwise, the way I understand it, you solved this with a new USB cable? A bit confusing as I plugged in the dongle directly into the NUC box and it still didn’t work.

Thnks

Missed this post and I’ve only got very unsatisfying answers- I don’t think it did anything to the dongle, clearly updating my Windows drivers should have zero impact on the Hass.io OS. And exactly, if it wasn’t the drivers and instead purely the cable, then the new cable should have solved the issue.

Leaving it as an anomaly as my dongle has worked great since and I haven’t experimented more other than to verify the cable was fine in different, data-transfer applications further solidifying I have no idea what happened.