Updating Z-Wave Path

mwildrick · September 19, 2020, 2:42am

OK – so I found what i thought would be a solution on this forum, but i still can’t get this working so I thought i’d try a new post. (Running home assistant in docker on Ubuntu)

I have a good number of Z-Wave devices and I really, REALLY don’t want to delete my config and reinstall it.

I’m using the HUBZ Smart Home Controller with ZWave and Zigbee. Originally, the path for ZWave was /dev/ttyUSB1 (and Zigbee was /dev/ttyUSB2). Recently (today), I did a restart and the path changed to /dev/ttyUSB0 and /dev/ttyUSB1, respectively.

So obviously, i want to change this path but i set this up through the home assistant UI and not configuration.yaml. The post i linked too above had what i thought would be the solution i needed.
I did a sudo nano .storage/core.config_entries and changed the paths here. It doesn’t appeared to have worked though, as these are my logs.

Any suggestions on where else this change should be made or how to update my path of an existing zwave (and zigbee) config?

2020-09-18 22:28:06.890 Always, OpenZwave Version 1.4.3469 Starting Up
2020-09-18 22:28:18.886 Info, Setting Up Provided Network Key for Secure Communications
2020-09-18 22:28:18.888 Info, mgr,     Added driver for controller /dev/ttyUSB0
2020-09-18 22:28:18.891 Info,   Opening controller /dev/ttyUSB0
2020-09-18 22:28:18.892 Info, Trying to open serial port /dev/ttyUSB0 (attempt 1)
2020-09-18 22:28:18.921 Info, Serial port /dev/ttyUSB0 opened (attempt 1)
2020-09-18 22:28:18.921 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-09-18 22:28:18.921 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2020-09-18 22:28:18.921 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2020-09-18 22:28:18.921 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2020-09-18 22:28:18.921 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2020-09-18 22:28:18.921 Detail,
2020-09-18 22:28:18.921 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-09-18 22:28:18.930 Detail, Unsolicited message received while waiting for ACK.
2020-09-18 22:28:18.930 Detail, contrlr,   Received: 0x01, 0x10, 0x01, 0x15, 0x5a, 0x2d, 0x57, 0x61, 0x76, 0x65, 0x20, 0x34, 0x2e, 0x30, 0x35, 0x00, 0x01, 0x97
2020-09-18 22:28:18.930 Detail,
2020-09-18 22:28:18.930 Info, contrlr, Received reply to FUNC_ID_ZW_GET_VERSION:
2020-09-18 22:28:18.930 Info, contrlr,     Static Controller library, version Z-Wave 4.05
2020-09-18 22:28:18.930 Detail, Node045,   Expected reply was received
2020-09-18 22:28:18.930 Detail, Node045,   Message transaction complete
2020-09-18 22:28:18.930 Detail,
2020-09-18 22:28:18.930 Detail, contrlr, Removing current message
2020-09-18 22:28:18.930 Detail,
2020-09-18 22:28:18.930 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) - FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2020-09-18 22:28:18.975 Detail, contrlr,   Received: 0x01, 0x04, 0x01, 0x05, 0x08, 0xf7
2020-09-18 22:28:18.975 Detail,
2020-09-18 22:28:18.975 Info, contrlr, Received reply to FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES:
2020-09-18 22:28:18.975 Info, contrlr,     There is no SUC ID Server (SIS) in this network.
2020-09-18 22:28:18.975 Info, contrlr,     The PC controller is a primary controller.
2020-09-18 22:28:28.932 Error, contrlr, ERROR: Dropping command, expected response not received after 1 attempt(s)
2020-09-18 22:28:28.932 Detail, contrlr, Removing current message
2020-09-18 22:28:28.932 Detail, contrlr, Notification: Notification - TimeOut
2020-09-18 22:28:28.932 Detail,
2020-09-18 22:28:28.932 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) - FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2020-09-18 22:28:29.079 Detail, contrlr,   Received: 0x01, 0x25, 0x01, 0x02, 0x05, 0x00, 0x1d, 0xf1, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x05, 0x00, 0x34
2020-09-18 22:28:29.079 Detail,
2020-09-18 22:28:29.079 Fatal, Failed to get HomeID or Controller Node ID during Init Sequence, m_homeId = 0x00000000, m_Controller_nodeId = 255
2020-09-18 22:28:29.079 Detail, Notification: DriverFailed

finity · September 20, 2020, 9:19am

did you stop HA before you edited the storage files.

also I would recommend using either a udev rule to make your device path persistent. or use a path “by-id”.

I use udev rules for mine and have never had an issue.

If you want to go the udev route then let me know and i’ll try to help you get that set up. Or it’s probably easier to use “by-id”. I don’t use that so I’m not sure what the path would be for the HUSZBZ-1 stick for each device.

mwildrick · September 21, 2020, 12:16am

I’d be interested in learning more about that. i just switched over from Z-Wave on Home Assistant to zwave2mqtt. having good success with it so far but the by-id method has yet to work for me. So I’m back at USB0

finity · September 22, 2020, 5:26am

I’m going to assume that Ubuntu puts there files in the same locations as a pure Debian system. And of course, use this at your own risk…

Go to etc/udev/rules.d

you will probably (hopefully…) already have a file there called 99-com.rules.

add the following to it:

SUBSYSTEM=="tty", ATTRS{interface}=="HubZ ZigBee Com Port", SYMLINK+="zigbee"

SUBSYSTEM=="tty", ATTRS{interface}=="HubZ Z-Wave Com Port", SYMLINK+="zwave"

then save and restart the machine.

once you restart you should now have devices called “dev/zigbee” and “dev/zwave” and can use those in the device paths.

If you don’t like those names then just change those parts in the code above.

verify that they work by going to the CLI and type:

ls /dev/z*

or:

ls -l /dev/z*

Both of those commands will tell you if you were successful but the second one will give more info and will tell you how the udev rules are linked to the physical devices.

mwildrick · September 22, 2020, 2:54pm

I don’t have that file, but I do have…

/etc/udev/rules.d/70-snap.snapd.rules

it looks like this:

# This file is automatically generated.

# Concatenation of all ModemManager udev rules
# do not edit this file, it will be overwritten on update

ACTION!="add|change|move", GOTO="mm_cinterion_port_types_end"
SUBSYSTEM!="tty", GOTO="mm_cinterion_port_types_end"
ENV{ID_VENDOR_ID}!="1e2d", GOTO="mm_cinterion_port_types_end"

SUBSYSTEMS=="usb", ATTRS{bInterfaceNumber}=="?*", ENV{.MM_USBIFNUM}="$attr{bInt>

ATTRS{idVendor}=="1e2d", ATTRS{idProduct}=="0053", ENV{.MM_USBIFNUM}=="01", ENV>

LABEL="mm_cinterion_port_types_end"
# do not edit this file, it will be overwritten on update

ACTION!="add|change|move", GOTO="mm_mbm_end"
SUBSYSTEMS=="usb", GOTO="mm_mbm_check"
GOTO="mm_mbm_end"

finity · September 23, 2020, 3:21am

well…

I’m no expert but you could try to create that file with those contents and see how it goes.

But again, TBH, use it at your own risk. Maybe ask on the Ubuntu forum to make sure it won’t break anything.

Also, I’m not seeing your replies unless you tag me by using @ or you click on the “reply” button in my post.