I recently bought a new WD PR4100 (pro series) which offers the Z-Wave Smart Home Gateway. Therefore, I bought a Z-wave Smart Home Stick made for My Cloud by WD.
The first element on the dashboard prompts me to enter the license key, but I’m unable to find where exactly.
Go to the SmartHomeUI and select My Settings > Management > Licence Upgrade and enter the licence key.
There’s no such thing as license upgrade under management
The only place I can enter a code is the App Store Access Token.
I found in forums I could access the Expert page, which gives me a red ribbon with Error handling data from server
When visiting http://wd_ip:8083/expert/#/network/controller
It displays no values for the stick, no button to enter the key or update firmware.
In events page, I found
10:02 | Cannot start Z-Wave binding: Error: Invalid port
Which port should it bind to?
When the usb stick is inserted, it turns blue for 1 second then the led goes off.
I’ve tried connecting it with and without the provided extension cable to the back of my nas.
This is in the dmesg output,
[35018.881013] usb 1-3: new full-speed USB device number 8 using xhci_hcd
[35019.042321] usb 1-3: device descriptor read/64, error -71
[35019.302235] usb 1-3: device descriptor read/64, error -71
[35019.561989] usb 1-3: new full-speed USB device number 9 using xhci_hcd
[35019.723227] usb 1-3: device descriptor read/64, error -71
[35019.983145] usb 1-3: device descriptor read/64, error -71
(and it continues since I plugged the USB stick)
The software version is 2.20-64 according to MyCloud Apps interface.
2016-08-02 10:02:05.937] [D] [zway] SETDATA controller.data.softwareRevisionVersion = “v2.2.1”
[2016-08-02 10:02:05.937] [D] [zway] SETDATA controller.data.softwareRevisionId = “a52a38822b6872f5b9fab0903b30ab65a2c70605”
[2016-08-02 10:02:05.937] [D] [zway] SETDATA controller.data.softwareRevisionDate = “2016-02-18 17:41:33 +0300”
[2016-08-02 10:02:05.939] [C] [i/o] Failed to open device /dev/ttyACM0: No such file or directory
[2016-08-02 10:02:05.947] [I] [core] Notification: critical (z-wave): Cannot start Z-Wave binding: Error: Invalid port
I’ll try to wake this thread up again. Cause the problem seems still being unresolved…
Iv’e just bought a PR2100 and get the same error message. I’m running firmware version 2.21.126.
“Cannot start Z-Wave binding: Error: Invalid port”
I’ve tried different serial port devices under active apps/Z-Wave Network Access, without success.
The Stick is a Z-Wave Me uzb (Gen 5). When plugging the stick in, a blu led is lit for approximately 1 second.
I’m also confused about the instruction “My Settings > Management > Licence Upgrade”
There’s no such alternative under Management.
Oh man, WD Support is such a waste of time.
My ticket is open since August, escalating every month or so.
At some point I received an email from the Z-Wave team manager, who told me a firmware update would be ready the following week. That was in November. Since then, he’s AWOL.
I think the fix will need to come from the community, I haven’t had time to do it myself though.
But the idea is to download the latest build environment, with kernel 4.x, and recompile the usb stick driver.
You would think that would be an easy fix for WD’s team…
Sorry to hear that. Was really looking forward to use this feature. So is my colleague who is interested in buying my mirror gen 2 nas which I’ve upgraded from. I’ll have to tell him the bad news. That in combination with the fact that I’ve invested some money in various z-wave sensors.
I wish there was a chance for the community to up vote the priority of this task in wd’s backlog. But perhaps there are to few interested…
Synology and WD devices share quite a bit of “DNA”, so there is a good chance it will work. Also yes, once you login via ssh it will drop you in root’s home directory. Here are the copy/paste directions for using @Tfl’s module.
Step 2 (you should be able to do Step 2 + 3 in one command but BusyBox can be extremely fussy) mv 7bf6faa3dc0a07c8f921747b521d184370ff4a38.pdf cdc-acm.ko
WARNING: The next step will overwrite the existing cdc-acm.ko file. It would be possible to get it back, but to err on the side of caution, we can make a backup now.
Backup Step 2.5 (full path names used so that you can execute this command from root’s home but it won’t move the file there) mv /mnt/HD/HD_a2/Nas_Prog/Z-Way-Server/bin/driver/cdc-acm.ko /mnt/HD/HD_a2/Nas_Prog/Z-Way-Server/bin/driver/cdc-acm.ko.old