HUSBZB-1 doesn’t appear in installed NUC image #227

marthoc · 2017-10-20T20:20:54Z

Using the HASSIO 1.1 NUC image on a Chromebox M004U (an unsupported configuration, I realize). Everything works perfectly, except I can’t get the system to recognize the HUSBZB-1 stick and create /dev/tty entries. The same stick is recognized on both CentOS and Debian installs on the same box and tty entries are created on those oses.

Output of lsusb:

core-ssh:/lib# lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 003: ID 10c4:8a2a
Bus 002 Device 001: ID 1d6b:0003
Bus 001 Device 002: ID 13d3:3393

Relevant output of dmesg:

[    1.845747] usb 1-5: new full-speed USB device number 3 using xhci_hcd

Output of hassio host hardware:

{
  "serial": [],
  "input": [
    "HDA Intel PCH Headphone",
    "HDA Intel HDMI HDMI/DP,pcm=8",
    "HDA Intel PCH Mic",
    "Power Button",
    "HDA Intel HDMI HDMI/DP,pcm=7",
    "Video Bus",
    "HDA Intel HDMI HDMI/DP,pcm=3"
  ],
  "disk": [
    "/dev/sda3",
    "/dev/sda1",
    "/dev/sda4",
    "/dev/sda2",
    "/dev/sda",
    "/dev/sda5",
    "/dev/sda6"
  ],
  "audio": {
    "0": {
      "name": "HDA-Intel - HDA Intel HDMI",
      "type": "HDMI",
      "devices": {
        "3": "digital audio playback",
        "7": "digital audio playback",
        "8": "digital audio playback"
      }
    },
    "1": {
      "name": "HDA-Intel - HDA Intel PCH",
      "type": "PCH",
      "devices": {
        "0": "digital audio capture"
      }
    }
  }
}

Any ideas or suggestions? Thanks!

The text was updated successfully, but these errors were encountered:

tboyce021 · 2017-11-21T16:33:30Z

No suggestions on this? I'm having the same issue but actually running on a NUC.

pvizeli · 2017-12-01T14:38:04Z

This not work?
https://home-assistant.io/hassio/zwave/

tboyce021 · 2017-12-01T15:16:33Z

Nope. No device ever shows up in /dev for it. I had it working with the regular Docker image before switching to Hass.io. So I at least know it's not a hardware issue.

marthoc · 2017-12-01T15:18:07Z

My experience is the same as @tboyce021. Stick works fine on a regular install with Docker, but not with hassio.

sumitrajancse · 2017-12-01T19:26:31Z

You are talking about GoControl Linear HUSBZB-1. It works perfectly with hass.io.
Please use the CLI > hassio host hardware.
For My setup it shows like this
core-ssh:~# hassio host hardware { "serial": [ "/dev/ttyUSB0", "/dev/ttyUSB1" ], "input": [], "disk": [], "gpio": [ "gpiochip100", "gpiochip0" ], "audio": { "0": { "name": "bcm2835 - bcm2835 ALSA", "type": "ALSA", "devices": { "0": "digital audio playback", "1": "digital audio playback" } }, "1": { "name": "USB-Audio - AK5371", "type": "AK5371", "devices": { "0": "digital audio capture" } } } }

Please try to change the USB port and then reboot your rpi . It should work

tboyce021 · 2017-12-02T00:18:23Z

@sumitrajancse, this isn't on an rpi, it's on the Intel NUC. It's not listed in the host hardware.

tboyce021 · 2017-12-05T18:37:39Z

FYI, my host hardware looks identical to the one in the OP here. There's nothing listed under "serial". I can also see the output in dmesg when I plug it in, but I can't get it to show up in the list of devices and HA can't access it if I put the relevant entries in the config anyway.

tboyce021 · 2017-12-05T18:45:38Z

I tried using the curl command to add the mappings myself:

curl -d '{"devices": ["ttyUSB0", "ttyUSB1"]}' http://hassio/homeassistant/options

I get an "ok" response:

{"result": "ok", "data": {}}

But I still haven't managed to get it working after doing that. What exactly is that supposed to do? I still don't see anything listed under "serial" devices and HA can't reach it. Is it supposed to show up immediately if it works or do I need to restart first? Does it actually persist after a restart?

tboyce021 · 2018-01-12T06:48:59Z

Any other suggestions on this? I still can't get it working with the latest updates. I see a ton of stuff in serial now, but I don't think any of them are the USB stick:

core-ssh:~# hassio host hardware
{
    "result": "ok",
    "data": {
        "serial": [
            "/dev/ttyS29",
            "/dev/ttyS15",
            "/dev/ttyS18",
            "/dev/ttyS23",
            "/dev/ttyS24",
            "/dev/ttyS5",
            "/dev/ttyS4",
            "/dev/ttyS16",
            "/dev/ttyS3",
            "/dev/ttyS28",
            "/dev/ttyS26",
            "/dev/ttyS25",
            "/dev/ttyS12",
            "/dev/ttyS20",
            "/dev/ttyS2",
            "/dev/ttyS21",
            "/dev/ttyS8",
            "/dev/ttyS14",
            "/dev/ttyS17",
            "/dev/ttyS22",
            "/dev/ttyS19",
            "/dev/ttyS7",
            "/dev/ttyS31",
            "/dev/ttyS6",
            "/dev/ttyS9",
            "/dev/ttyS0",
            "/dev/ttyS11",
            "/dev/ttyS30",
            "/dev/ttyS13",
            "/dev/ttyS27",
            "/dev/ttyS1",
            "/dev/ttyS10"
        ],
        "input": [
            "HDA Intel HDMI HDMI/DP,pcm=7",
            "HDA Intel HDMI HDMI/DP,pcm=3",
            "HDA Intel PCH Mic",
            "Power Button",
            "HDA Intel PCH Headphone",
            "HDA Intel HDMI HDMI/DP,pcm=8",
            "Video Bus"
        ],
        "disk": [
            "/dev/sda3",
            "/dev/sda1",
            "/dev/sda4",
            "/dev/sda6",
            "/dev/sda2",
            "/dev/sda5",
            "/dev/sda"
        ],
        "gpio": [],
        "audio": {
            "0": {
                "name": "HDA-Intel - HDA Intel HDMI",
                "type": "HDMI",
                "devices": {
                    "3": "digital audio playback",
                    "7": "digital audio playback",
                    "8": "digital audio playback"
                }
            },
            "1": {
                "name": "HDA-Intel - HDA Intel PCH",
                "type": "PCH",
                "devices": {
                    "0": "digital audio capture"
                }
            }
        }
    }
}

tboyce021 · 2018-01-13T01:38:25Z

@pvizeli is it possible to get access to the host on the NUC? I tried adding an authorized_keys file to the flash-boot partition of the USB drive and flashing again, but it doesn't seem to work. It still denies my SSH key.

scfigg · 2018-03-09T01:07:22Z

ugh same issue here. Just switched over from my RPi3 to Intel NUC, was amazed by how fast it was, only to find out I can't use anything in my house because it can't find the USB. Need this fixed!

marthoc · 2018-03-09T05:23:41Z

After further testing I think this could be a ResinOS issue on the NUC/x64 platform. Unfortunately this probably isn’t going to get fixed since I think Hass.io is moving away from ResinOS and onto a customized Linux build (HassioOS?) in the coming months.

What you could do is install Debian on your NUC, install Docker, then run the Hassio installer. It will set up the Hassio environment for you just as if you were using the image, except you’d be on top of Debian and not ResinOS. When I do this, my HUSBZB-1 shows up inside the Hassio container ecosystem (it shows up under hassio host hardware with tty entries).

scfigg · 2018-03-09T13:24:21Z

Thanks for the update. I'll have to play with it I guess - I've never had luck with docker, and I hate Linux. Time to start breaking things I guess!

scfigg · 2018-03-09T13:25:46Z

Stupid question - but on my NUC, I installed Ubuntu server, then followed this guide:

https://www.youtube.com/watch?v=EMOLDrL6_7Q&index=1&list=PLOkeE2vyZtuKOKkK1RvCwnkHEbA1_r3jy&t=303s

Isn't that technically installing it into docker on top of Ubuntu?

marthoc · 2018-03-09T14:06:53Z

Sorry I’m not sure if I’m following why it’s a stupid question. That video shows you exactly how to do what I’m suggesting - which is to install Hass.io on top of a regular Linux distro rather than using the premade image for Intel NUC distributed by the Hass.io project. Yes, Docker is required because at its core Hass.io is a set of Docker containers (one for Home Assistant, and one for the Hass.io supervisor that handles all Hass.io functions, including updating Home Assistant and running Addons).

scfigg · 2018-03-09T14:13:45Z

Ok thanks. I did that yesterday, and 'hassio host hardware' doesn't show any USB devices plugged in when using the HUSBZB-1 stick. Just a bunch of serial connections like tboyce said above.

marthoc · 2018-03-09T14:30:16Z

Interesting - so that points to Hass.io as the culprit then. Can you do a couple of things for me to help troubleshoot? SSH into Ubuntu (not into the Hass.io addon) and do:

ls -l /dev | grep ttyUSB*

With your HUSBZB-1 attached, that command should return two entries - ttyUSB0 and ttyUSB1.

Also out of interest, what command did you run to install Hass.io? Was it:

curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | bash -s

Or did you specify the Intel NUC machine type with:

curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | bash -s -- -m intel-nuc

?

scfigg · 2018-03-09T14:32:57Z

I can test it later tonight for you - at work now, and I switched back to the RPi3 since I couldn't get NUC to work.

I did the first command:
curl -sL https://raw.githubusercontent.com/home-assistant/hassio-build/master/install/hassio_install | bash -s

marthoc · 2018-03-09T14:35:44Z

OK also interesting. Can you add to the list of things to try and report the output of:

docker ps

when SSH’d into Ubuntu. Just paste the whole result. Thanks!

scfigg · 2018-03-10T02:26:22Z

Any suggestions on how to SSH into the host since port 22 SSH server is already running on HassIO?

scfigg · 2018-03-10T03:02:56Z

Nevermind - got SSH server installed on Ubuntu. I may have been completely stupid - I have a couple NUCs laying around, and during various testing, I may have swapped them on accident. I verified the Ubuntu HassIO install was running today, then typed the "ls -l /dev | grep ttyUSB*" and it showed the USB ports once I did a show hardware command. Not sure what that command you gave me does (does it add it, or just list he USB ports?). Anyways, I got it working now. Thanks for your help!

Now I'm trying to figure out why my docker.io install is out of date somehow, so I can't install certain addons. Followed the instructions in the video, so maybe that repo sucks. Not sure how to upgrade it now.

marthoc · 2018-03-10T04:52:38Z

That command just lists (ls) the contents of the /dev directory and pipes ( | ) the output into grep to filter just for the ttyUSB entries. It wouldn’t have made anything work that wasn’t working already.

So the culprit may actually be ResinOS then!

To fix your Docker problem you’re going to need to install a newer version of Docker. That video had to install Docker.io from the Ubuntu repository but that version is probably significantly out of date by now. This page: https://docs.docker.com/install/linux/docker-ce/ubuntu/ has detailed instructions starting with removing your old version (this will/should preserve your Hass.io install). Follow the “Uninstall old versions” section and then skip down to “Install using the repository”. From there it’s pretty much copy and paste!

scfigg · 2018-03-11T01:34:59Z

Thanks - I forgot to update this again last night. Managed to figure out how to uninstall docker.io and install Docker-CE, and it kept my docker image/container just fine. Works great now! Thanks for your help. Looks like it was Resin-OS.

3lvl0 · 2018-05-13T19:17:30Z

Man this sucks. I got a NUC thinking I could flash Hass.io and it would work like it did on my RP3. As a noob I don't think I am up to the task of installing a linux distro with docker and hass.io inside of it. I doubt there is a guide good enough for that. Looks like I'm stuck waiting for Hassio OS whenever that will be released. Does anyone even know that the GoControl with work on NUCs with Hassio OS? Back to the Pi for now..

THland83 · 2018-07-08T17:13:43Z

Just to give this a bit more life.

HUSBZB-1:
This path works for me using the

zwave:
usb_path: /dev/ttyACM0

node name
Sigma Designs UZB Z-Wave USB Adapter
manufacturer name
Sigma Designs
product name
UZB Z-Wave USB Adapter
query stage
Complete
is awake
true
is ready
true
is failed
false
is info received
false
max baud rate
40000
is zwave plus
false

stale · 2019-04-16T14:04:37Z

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale bot added the stale label Apr 16, 2019

stale bot closed this as completed Apr 23, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

HUSBZB-1 doesn’t appear in installed NUC image #227

HUSBZB-1 doesn’t appear in installed NUC image #227

marthoc commented Oct 20, 2017

tboyce021 commented Nov 21, 2017 •

edited

pvizeli commented Dec 1, 2017

tboyce021 commented Dec 1, 2017

marthoc commented Dec 1, 2017

sumitrajancse commented Dec 1, 2017

tboyce021 commented Dec 2, 2017

tboyce021 commented Dec 5, 2017

tboyce021 commented Dec 5, 2017 •

edited

tboyce021 commented Jan 12, 2018 •

edited

tboyce021 commented Jan 13, 2018 •

edited

scfigg commented Mar 9, 2018

marthoc commented Mar 9, 2018

scfigg commented Mar 9, 2018

scfigg commented Mar 9, 2018

marthoc commented Mar 9, 2018 •

edited

scfigg commented Mar 9, 2018

marthoc commented Mar 9, 2018

scfigg commented Mar 9, 2018

marthoc commented Mar 9, 2018

scfigg commented Mar 10, 2018

scfigg commented Mar 10, 2018

marthoc commented Mar 10, 2018

scfigg commented Mar 11, 2018

3lvl0 commented May 13, 2018

THland83 commented Jul 8, 2018

stale bot commented Apr 16, 2019

HUSBZB-1 doesn’t appear in installed NUC image #227

HUSBZB-1 doesn’t appear in installed NUC image #227

Comments

marthoc commented Oct 20, 2017

tboyce021 commented Nov 21, 2017 • edited

pvizeli commented Dec 1, 2017

tboyce021 commented Dec 1, 2017

marthoc commented Dec 1, 2017

sumitrajancse commented Dec 1, 2017

tboyce021 commented Dec 2, 2017

tboyce021 commented Dec 5, 2017

tboyce021 commented Dec 5, 2017 • edited

tboyce021 commented Jan 12, 2018 • edited

tboyce021 commented Jan 13, 2018 • edited

scfigg commented Mar 9, 2018

marthoc commented Mar 9, 2018

scfigg commented Mar 9, 2018

scfigg commented Mar 9, 2018

marthoc commented Mar 9, 2018 • edited

scfigg commented Mar 9, 2018

marthoc commented Mar 9, 2018

scfigg commented Mar 9, 2018

marthoc commented Mar 9, 2018

scfigg commented Mar 10, 2018

scfigg commented Mar 10, 2018

marthoc commented Mar 10, 2018

scfigg commented Mar 11, 2018

3lvl0 commented May 13, 2018

THland83 commented Jul 8, 2018

stale bot commented Apr 16, 2019

tboyce021 commented Nov 21, 2017 •

edited

tboyce021 commented Dec 5, 2017 •

edited

tboyce021 commented Jan 12, 2018 •

edited

tboyce021 commented Jan 13, 2018 •

edited

marthoc commented Mar 9, 2018 •

edited