Just starting out, and I already hit a snag (again)

Configuration
1

Hello everyone, to start off and hopefully make things simpler, I’ll describe what I am trying to do. I have a RPi 3 with a 32GB card that I have flashed HASSbian onto, a Linear HUSBZB-1 USB dongle, and a Linear/GOControl WNK01-21KIT (2x door sensors and a motion sensor). What I am trying to do is to set up the sensors to send out alerts via text when triggered, but at this point, just getting them to work is my next step.

So I’ve got HASSbian setup, and I have been using WinSCP to edit configuration.yaml. But, thus far, all that I’ve been able to successfully add has been
zwave: usb_path: /dev/ttyUSB1

Everything else has caused the HA web GUI to stop loading, for some reason. At first, because both ttyUSB0 and 1 were showing up, I actually thought my HUSBZB-1 was defective, because I had /ttyUSB0 in my config file. On a whim, I decided to switch it to 1, and Z-Wave suddenly showed up in the GUI, and I was thrilled! But, I soon hit another snag; I cannot, for the life of me, get these sensors to add. From the manual, it says to add the battery to the sensor, and it will be ready for the controller’s inclusion (shown with a flashing light). It says to prepare the Controller to include a unit by adding it to a group; then you must depress the tamper switch for a second, and the sensor will be added as a node. I must have tried this at least 15 times, and no joy. Any ideas as to what I could be doing wrong? Here is the error I keep getting in the OZWlog, which keeps bringing up a HomeId?

2017-07-11 00:39:22.835 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) - FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2017-07-11 00:39:23.836 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-07-11 00:39:23.836 Detail, contrlr, Removing current message
2017-07-11 00:39:23.836 Detail, contrlr, Notification: Notification - TimeOut
2017-07-11 01:22:04.442 Error, mgr, Manager::GetDriver failed - Home ID 0x00000000 is unknown
2017-07-11 01:22:04.443 Warning, Exception: Manager.cpp:373 - 100 - Invalid HomeId passed to GetDriver
2017-07-11 01:24:30.685 Error, mgr, Manager::GetDriver failed - Home ID 0x00000000 is unknown
2017-07-11 01:24:30.686 Warning, Exception: Manager.cpp:373 - 100 - Invalid HomeId passed to GetDriver

Thanks in advance!

2

Ok, first try excluding the sensors. This kind of resets their brains so they can be included.

Second, don’t worry about groups right now on HA. Just do what the documentation says to put the sensor in inclusion mode under the zwave manager, just click add node secure and see if that doesn’t take care of it.

As far as the rest of your config, you would have to post it and let us know what you are trying to do so we can help you. Please make sure to retain all formatting so we can see the spacing. YAML is very sensitive to spacing. And lets attack one thing at a time.

1 Like
3

Thank you for replying, turboc!

It seems that I cannot exclude the sensor, either. I click the remove node button, and the sensor just continues to blink. I tried the motion sensor, hoping that maybe I just have a bad door sensor, but that one will not pair, either. They just continue to blink for a minute or two. To recap, I put the battery in, click “ADD NODE”, and in the door sensor’s case, I have to depress a tamper switch for 1 second and release; for the motion sensor, I have to use a paper clip to depress a program button. In both cases, the lights just continue to blink, and there is no change in the light on the HUSBZB-1. It is both frustrating and disheartening, at this point.

In any case, here is my configuration.yaml file, although I’m pretty sure it is still default:

homeassistant:
  # Name of the location where Home Assistant is running
  name: Home
  # Location required to calculate the time the sun rises and sets
  latitude: 41.9389
  longitude: -73.9901
  # Impacts weather/sunrise data (altitude above sea level in meters)
  elevation: 86
  # metric for Metric, imperial for Imperial
  unit_system: imperial
  # Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
  time_zone: America/New_York

# Show links to resources in log and frontend
introduction:

# Enables the frontend
frontend:

# Enables configuration UI
config:

http:
  # Uncomment this to add a password (recommended!)
  # api_password: 
  # Uncomment this if you are using SSL or running in Docker etc
  # base_url: example.duckdns.org:8123

# Checks for available updates
# Note: This component will send some information about your system to
# the developers to assist with development of Home Assistant.
# For more information, please see:
# https://home-assistant.io/blog/2016/10/25/explaining-the-updater/
updater:
  # Optional, allows Home Assistant developers to focus on popular components.
  # include_used_components: true

# Discover some devices automatically
discovery:

# Allows you to issue voice commands from the frontend in enabled browsers
conversation:

# Enables support for tracking state changes over time.
history:

# View all events in a logbook
logbook:

# Track the sun
sun:

# Weather Prediction
sensor:
  platform: yr

# Text to speech
tts:
  platform: google

group: !include groups.yaml
automation: !include automations.yaml

zwave:
  usb_path: /dev/ttyUSB1

Thanks in advance!

4

Does the phone app require the PC software, or does it talk directly to the HUSBZB-1? If it talks directly to the HUSBZB-1, see if the phone app can help you get the devices paired? Take HA out of the mix to verify that the HUSBZB-1 works right.

5

I am actually doing this all from my PC; I did not try from my tablet or phone. However, I did restart HA, and reran the OZWLog, and new results appeared. I am not sure if these help or not, but hopefully they will:

2017-07-11 03:07:34.821 Always, OpenZwave Version 1.4.2508 Starting Up
2017-07-11 03:07:36.218 Info, Setting Up Provided Network Key for Secure Communications
2017-07-11 03:07:36.218 Warning, Failed - Network Key Not Set
2017-07-11 03:07:36.218 Info, mgr,     Added driver for controller /dev/ttyUSB1
2017-07-11 03:07:36.218 Info,   Opening controller /dev/ttyUSB1
2017-07-11 03:07:36.218 Info, Trying to open serial port /dev/ttyUSB1 (attempt 1)
2017-07-11 03:07:36.221 Info, Serial port /dev/ttyUSB1 opened (attempt 1)
2017-07-11 03:07:36.221 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2017-07-11 03:07:36.221 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2017-07-11 03:07:36.221 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2017-07-11 03:07:36.221 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2017-07-11 03:07:36.222 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2017-07-11 03:07:36.222 Detail, 
2017-07-11 03:07:36.222 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2017-07-11 03:07:37.222 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-07-11 03:07:37.222 Detail, contrlr, Removing current message
2017-07-11 03:07:37.222 Detail, contrlr, Notification: Notification - TimeOut
2017-07-11 03:07:37.223 Detail, 
2017-07-11 03:07:37.223 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) - FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2017-07-11 03:07:38.223 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-07-11 03:07:38.224 Detail, contrlr, Removing current message
2017-07-11 03:07:38.224 Detail, contrlr, Notification: Notification - TimeOut
2017-07-11 03:07:38.224 Detail, 
2017-07-11 03:07:38.224 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) - FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2017-07-11 03:07:39.225 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-07-11 03:07:39.225 Detail, contrlr, Removing current message
2017-07-11 03:07:39.225 Detail, contrlr, Notification: Notification - TimeOut
2017-07-11 03:07:39.226 Detail, 
2017-07-11 03:07:39.226 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x07) - FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2017-07-11 03:07:40.226 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-07-11 03:07:40.226 Detail, contrlr, Removing current message
2017-07-11 03:07:40.226 Detail, contrlr, Notification: Notification - TimeOut
2017-07-11 03:07:40.227 Detail, 
2017-07-11 03:07:40.227 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) - FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2017-07-11 03:07:41.227 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2017-07-11 03:07:41.228 Detail, contrlr, Removing current message
2017-07-11 03:07:41.228 Detail, contrlr, Notification: Notification - TimeOut

I must give up for the night, unfortunately, but I will be back at it ASAP tomorrow some time after work. Thanks again, I really appreciate it :slight_smile:

6

This bit indicates that there’s no key setup for adding secure nodes.

This bit indicates that the device has stopped responding or isn’t responding.

Can you give us the output of the command ‘lsusb’ and a ‘ls -al /dev’?

1 Like
7

Also, remember when you reboot your serial ports assigned to usb ports can change.

1 Like
8

Thank you both for replying. I am at work right now, but I will get back at it as soon as I am able to.

firstof9, I am not sure how to create a key, so I will have to research that. Also, from what I gathered from the error, the controller (the HUSBZB-1) isn’t responding? I am a bit worried that the stick isn’t working properly, as it actually arrived from Amazon in a crushed box in a padded envelope. In any case I will run those commands as soon as I can and post the results.

And turboc, I will rerun the command to ensure that I my USB ports are still the same. Thanks!

9

If I am not mistaken, the HUSBZB-1 can support both Zwave and Zigbee. They will show up as 2 separate devices,
likely the /dev/ttyUSB0 and /dev/ttyUSB0 so each radio can be accessed. As @turboc says the device name could change. You might want to search for and create rules to force the devices to be recognized by name rather than the dev listing. ie /dev/ttyUSB0 would become /dev/zigbee and /dev/ttyUSB1 could become /dev/zigbee regardless of how the were naturally identified.

1 Like
10

Yes, zarthan, that is correct, the HUSBZB-1 supports Z-WAVE and Zigbee. How would I go about creating such a rule? Would that go into my config file, or would that be separate?

Thanks in advance!

11

Remember, I believe he is in Windows not Linux.

12

He is on hasbian coming from Windows

13

I would try doing a
lsusb
at the command line. That will show you what USB devices your Pi sees. I don´t know how each of them will show up but hopefully it will help you identify which is which. You will then need to use
ls /dev/serial/by-id/
That will show you how the devices are identified using their device IDs rather than what ports they are attached to.
Replace the /dev/ttyUSB1 with /dev/serial/by-id/usb-xxxxxxxxx.
That should remain constant no matter how the ports are recognized.

1 Like
14

Okay, will do. I will make the change and update soon. Thanks again!

15

Ok, Where does your PC fit into this?

16

I’m just using my PC to access my RPi via PuTTY and WinSCP, and HA via the web UI.

17

I ran > lusb and received these results:
Bus 001 Device 004: ID 10c4:8a2a Cygnal Integrated Products, Inc.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I then ran > ls -al /dev, and there are those results:

total 4
drwxr-xr-x 15 root root        3400 Jul 11 00:31 .
drwxr-xr-x 21 root root        4096 May  9 20:02 ..
crw-------  1 root root     10, 235 Jul 11 00:31 autofs
drwxr-xr-x  2 root root         580 Jul 11 00:31 block
crw-------  1 root root     10, 234 Jul 11 00:31 btrfs-control
drwxr-xr-x  3 root root          60 Jan  1  1970 bus
crw-------  1 root root     10,  63 Jul 11 00:31 cachefiles
drwxr-xr-x  2 root root        2500 Jul 11 00:31 char
crw-------  1 root root      5,   1 Jul 11 00:31 console
crw-------  1 root root     10,  62 Jul 11 00:31 cpu_dma_latency
crw-------  1 root root     10, 203 Jul 11 00:31 cuse
drwxr-xr-x  7 root root         140 Jul 11 00:31 disk
crw-rw----  1 root video    29,   0 Jul 11 00:31 fb0
lrwxrwxrwx  1 root root          13 Jan  1  1970 fd -> /proc/self/fd
crw-rw-rw-  1 root root      1,   7 Jul 11 00:31 full
crw-rw-rw-  1 root root     10, 229 Jul 11 00:31 fuse
crw-------  1 root root    254,   0 Jul 11 00:31 gpiochip0
crw-------  1 root root    254,   1 Jul 11 00:31 gpiochip1
crw-------  1 root root    254,   2 Jul 11 00:31 gpiochip2
crw-rw----  1 root gpio    243,   0 Jul 11 00:31 gpiomem
crw-------  1 root root     10, 183 Jul 11 00:31 hwrng
lrwxrwxrwx  1 root root          25 Jan  1  1970 initctl -> /run/systemd/initctl/fifo
drwxr-xr-x  2 root root          60 Jan  1  1970 input
crw-r--r--  1 root root      1,  11 Jul 11 00:31 kmsg
lrwxrwxrwx  1 root root          28 Jan  1  1970 log -> /run/systemd/journal/dev-log
brw-rw----  1 root disk      7,   0 Jul 11 00:31 loop0
brw-rw----  1 root disk      7,   1 Jul 11 00:31 loop1
brw-rw----  1 root disk      7,   2 Jul 11 00:31 loop2
brw-rw----  1 root disk      7,   3 Jul 11 00:31 loop3
brw-rw----  1 root disk      7,   4 Jul 11 00:31 loop4
brw-rw----  1 root disk      7,   5 Jul 11 00:31 loop5
brw-rw----  1 root disk      7,   6 Jul 11 00:31 loop6
brw-rw----  1 root disk      7,   7 Jul 11 00:31 loop7
crw-rw----  1 root disk     10, 237 Jul 11 00:31 loop-control
drwxr-xr-x  2 root root          60 Jul 11 00:31 mapper
crw-r-----  1 root kmem      1,   1 Jul 11 00:31 mem
crw-------  1 root root     10,  59 Jul 11 00:31 memory_bandwidth
brw-rw----  1 root disk    179,   0 Jul 11 00:31 mmcblk0
brw-rw----  1 root disk    179,   1 Jul 11 00:31 mmcblk0p1
brw-rw----  1 root disk    179,   2 Jul 11 00:31 mmcblk0p2
drwxrwxrwt  2 root root          40 Jan  1  1970 mqueue
drwxr-xr-x  2 root root          60 Jul 11 00:31 net
crw-------  1 root root     10,  61 Jul 11 00:31 network_latency
crw-------  1 root root     10,  60 Jul 11 00:31 network_throughput
crw-rw-rw-  1 root root      1,   3 Jul 11 00:31 null
crw-------  1 root root    108,   0 Jul 11 00:31 ppp
crw-rw-rw-  1 root tty       5,   2 Jul 11 22:31 ptmx
drwxr-xr-x  2 root root           0 Jan  1  1970 pts
brw-rw----  1 root disk      1,   0 Jul 11 00:31 ram0
brw-rw----  1 root disk      1,   1 Jul 11 00:31 ram1
brw-rw----  1 root disk      1,  10 Jul 11 00:31 ram10
brw-rw----  1 root disk      1,  11 Jul 11 00:31 ram11
brw-rw----  1 root disk      1,  12 Jul 11 00:31 ram12
brw-rw----  1 root disk      1,  13 Jul 11 00:31 ram13
brw-rw----  1 root disk      1,  14 Jul 11 00:31 ram14
brw-rw----  1 root disk      1,  15 Jul 11 00:31 ram15
brw-rw----  1 root disk      1,   2 Jul 11 00:31 ram2
brw-rw----  1 root disk      1,   3 Jul 11 00:31 ram3
brw-rw----  1 root disk      1,   4 Jul 11 00:31 ram4
brw-rw----  1 root disk      1,   5 Jul 11 00:31 ram5
brw-rw----  1 root disk      1,   6 Jul 11 00:31 ram6
brw-rw----  1 root disk      1,   7 Jul 11 00:31 ram7
brw-rw----  1 root disk      1,   8 Jul 11 00:31 ram8
brw-rw----  1 root disk      1,   9 Jul 11 00:31 ram9
crw-rw-rw-  1 root root      1,   8 Jul 11 00:31 random
drwxr-xr-x  2 root root          60 Jan  1  1970 raw
crw-rw-r--  1 root root     10,  58 Jul 11 00:31 rfkill
drwxr-xr-x  4 root root          80 Jul 11 00:31 serial
lrwxrwxrwx  1 root root           7 Jul 11 00:31 serial1 -> ttyAMA0
drwxrwxrwt  2 root root          40 Jan  1  1970 shm
drwxr-xr-x  3 root root         160 Jul 11 00:31 snd
lrwxrwxrwx  1 root root          15 Jan  1  1970 stderr -> /proc/self/fd/2
lrwxrwxrwx  1 root root          15 Jan  1  1970 stdin -> /proc/self/fd/0
lrwxrwxrwx  1 root root          15 Jan  1  1970 stdout -> /proc/self/fd/1
crw-rw-rw-  1 root tty       5,   0 Jul 11 00:31 tty
crw--w----  1 root tty       4,   0 Jul 11 00:31 tty0
crw--w----  1 root tty       4,   1 Jul 11 00:32 tty1
crw--w----  1 root tty       4,  10 Jul 11 00:31 tty10
crw--w----  1 root tty       4,  11 Jul 11 00:31 tty11
crw--w----  1 root tty       4,  12 Jul 11 00:31 tty12
crw--w----  1 root tty       4,  13 Jul 11 00:31 tty13
crw--w----  1 root tty       4,  14 Jul 11 00:31 tty14
crw--w----  1 root tty       4,  15 Jul 11 00:31 tty15
crw--w----  1 root tty       4,  16 Jul 11 00:31 tty16
crw--w----  1 root tty       4,  17 Jul 11 00:31 tty17
crw--w----  1 root tty       4,  18 Jul 11 00:31 tty18
crw--w----  1 root tty       4,  19 Jul 11 00:31 tty19
crw--w----  1 root tty       4,   2 Jul 11 00:31 tty2
crw--w----  1 root tty       4,  20 Jul 11 00:31 tty20
crw--w----  1 root tty       4,  21 Jul 11 00:31 tty21
crw--w----  1 root tty       4,  22 Jul 11 00:31 tty22
crw--w----  1 root tty       4,  23 Jul 11 00:31 tty23
crw--w----  1 root tty       4,  24 Jul 11 00:31 tty24
crw--w----  1 root tty       4,  25 Jul 11 00:31 tty25
crw--w----  1 root tty       4,  26 Jul 11 00:31 tty26
crw--w----  1 root tty       4,  27 Jul 11 00:31 tty27
crw--w----  1 root tty       4,  28 Jul 11 00:31 tty28
crw--w----  1 root tty       4,  29 Jul 11 00:31 tty29
crw--w----  1 root tty       4,   3 Jul 11 00:31 tty3
crw--w----  1 root tty       4,  30 Jul 11 00:31 tty30
crw--w----  1 root tty       4,  31 Jul 11 00:31 tty31
crw--w----  1 root tty       4,  32 Jul 11 00:31 tty32
crw--w----  1 root tty       4,  33 Jul 11 00:31 tty33
crw--w----  1 root tty       4,  34 Jul 11 00:31 tty34
crw--w----  1 root tty       4,  35 Jul 11 00:31 tty35
crw--w----  1 root tty       4,  36 Jul 11 00:31 tty36
crw--w----  1 root tty       4,  37 Jul 11 00:31 tty37
crw--w----  1 root tty       4,  38 Jul 11 00:31 tty38
crw--w----  1 root tty       4,  39 Jul 11 00:31 tty39
crw--w----  1 root tty       4,   4 Jul 11 00:31 tty4
crw--w----  1 root tty       4,  40 Jul 11 00:31 tty40
crw--w----  1 root tty       4,  41 Jul 11 00:31 tty41
crw--w----  1 root tty       4,  42 Jul 11 00:31 tty42
crw--w----  1 root tty       4,  43 Jul 11 00:31 tty43
crw--w----  1 root tty       4,  44 Jul 11 00:31 tty44
crw--w----  1 root tty       4,  45 Jul 11 00:31 tty45
crw--w----  1 root tty       4,  46 Jul 11 00:31 tty46
crw--w----  1 root tty       4,  47 Jul 11 00:31 tty47
crw--w----  1 root tty       4,  48 Jul 11 00:31 tty48
crw--w----  1 root tty       4,  49 Jul 11 00:31 tty49
crw--w----  1 root tty       4,   5 Jul 11 00:31 tty5
crw--w----  1 root tty       4,  50 Jul 11 00:31 tty50
crw--w----  1 root tty       4,  51 Jul 11 00:31 tty51
crw--w----  1 root tty       4,  52 Jul 11 00:31 tty52
crw--w----  1 root tty       4,  53 Jul 11 00:31 tty53
crw--w----  1 root tty       4,  54 Jul 11 00:31 tty54
crw--w----  1 root tty       4,  55 Jul 11 00:31 tty55
crw--w----  1 root tty       4,  56 Jul 11 00:31 tty56
crw--w----  1 root tty       4,  57 Jul 11 00:31 tty57
crw--w----  1 root tty       4,  58 Jul 11 00:31 tty58
crw--w----  1 root tty       4,  59 Jul 11 00:31 tty59
crw--w----  1 root tty       4,   6 Jul 11 00:31 tty6
crw--w----  1 root tty       4,  60 Jul 11 00:31 tty60
crw--w----  1 root tty       4,  61 Jul 11 00:31 tty61
crw--w----  1 root tty       4,  62 Jul 11 00:31 tty62
crw--w----  1 root tty       4,  63 Jul 11 00:31 tty63
crw--w----  1 root tty       4,   7 Jul 11 00:31 tty7
crw--w----  1 root tty       4,   8 Jul 11 00:31 tty8
crw--w----  1 root tty       4,   9 Jul 11 00:31 tty9
crw-rw----  1 root dialout 204,  64 Jul 11 00:32 ttyAMA0
crw-------  1 root root      5,   3 Jul 11 00:31 ttyprintk
crw-rw----  1 root dialout 188,   0 Jul 11 00:31 ttyUSB0
crw-rw----  1 root dialout 188,   1 Jul 11 03:07 ttyUSB1
crw-------  1 root root     10, 239 Jul 11 00:31 uhid
crw-------  1 root root     10, 223 Jul 11 00:31 uinput
crw-rw-rw-  1 root root      1,   9 Jul 11 00:31 urandom
crw-------  1 root root    250,   0 Jul 11 00:31 vc-cma
crw-rw----  1 root video   246,   0 Jul 11 00:31 vchiq
crw-rw----  1 root video   248,   0 Jul 11 00:31 vcio
crw-------  1 root root    249,   0 Jul 11 00:31 vc-mem
crw-rw----  1 root tty       7,   0 Jul 11 00:31 vcs
crw-rw----  1 root tty       7,   1 Jul 11 00:31 vcs1
crw-rw----  1 root tty       7,   2 Jul 11 00:31 vcs2
crw-rw----  1 root tty       7,   3 Jul 11 00:31 vcs3
crw-rw----  1 root tty       7,   4 Jul 11 00:31 vcs4
crw-rw----  1 root tty       7,   5 Jul 11 00:31 vcs5
crw-rw----  1 root tty       7,   6 Jul 11 00:31 vcs6
crw-rw----  1 root tty       7, 128 Jul 11 00:31 vcsa
crw-rw----  1 root tty       7, 129 Jul 11 00:31 vcsa1
crw-rw----  1 root tty       7, 130 Jul 11 00:31 vcsa2
crw-rw----  1 root tty       7, 131 Jul 11 00:31 vcsa3
crw-rw----  1 root tty       7, 132 Jul 11 00:31 vcsa4
crw-rw----  1 root tty       7, 133 Jul 11 00:31 vcsa5
crw-rw----  1 root tty       7, 134 Jul 11 00:31 vcsa6
crw-rw----  1 root video   245,   0 Jul 11 00:31 vcsm
crw-------  1 root root     10, 137 Jul 11 00:31 vhci
crw-------  1 root root     10, 130 Jul 11 00:31 watchdog
crw-------  1 root root    252,   0 Jul 11 00:31 watchdog0
prw-r-----  1 root adm            0 Jul 11 06:51 xconsole
crw-rw-rw-  1 root root      1,   5 Jul 11 00:31 zero
18

Lastly, when I ran > ls /dev/serial/by-id/, I received these results:

usb-Silicon_Labs_HubZ_Smart_Home_Controller_C0F009ED-if00-port0
usb-Silicon_Labs_HubZ_Smart_Home_Controller_C0F009ED-if01-port0

So, in my config file, I should replace

usb_path: /dev/ttyUSB1

with

usb_path: /dev/serial/by-id/usb-Silicon_Labs_HubZ_Smart_Home_Controller_C0F009ED-if01-port0
usb_path: /dev/serial/by-id/usb-Silicon_Labs_HubZ_Smart_Home_Controller_C0F009ED-if00-port0

Or am I off the mark, there?

19

Try that one first.

1 Like
20

Okay, I tried that one, and I am now seeing a Zwave window on my States page, containing a “Sigma Designs UZB Z-Wave USB Adapter (Node:1 Complete) Ready” listing. When I open the Z-Wave page, under Z-Wave Node Manage, the Sigma Designs UZB Z-Wave USB Adapter shows up there as well. Is this normal? Does Sigma Designs manufacture the dongles for the larger branded companies?