Newbie: Z-Wave Remotec Scene Master fails to add to network

I’ve installed HA version 193 using the generic Linux server instructions, i.e. via docker, and have got the Z-Wave.me USB dongle attached and working as /dev/ttyACM0. It appears as a node in the Configuration panel OK and appears to be working. In case it’s relevant, I didn’t need to make the device available in the docker container as hinted at in the documentation, I wouldn’t know how to do that anyway, it says to add the -device switch to the docker command but I can’t find any way to do that. But a symbolic persistent link to it via udev doesn’t appear in HA.

Anyway, I’ve tried adding a Remotec Scene Master 8-button switch as my first node. The instructions are a little contradictory - HA docs say press Add Node then put the device into inclusion mode, whereas the device docs say put the device into add mode then press the program button on the target, which I take to mean the Add Node button in HA. But whichever way round I do it, it doesn’t work.

Pressing Add Node causes the USB controller’s LED to flash and pressing the L+R buttons together on the device, the Add instruction, causes the device’s LED to flash, all according to the instructions. But nothing happens and it times out after 30 seconds. The controller doesn’t pair up with it.

Both controller and device are European Z-Wave Plus devices so should operate together. I have tried factory resetting the Remotec but to no avail.

Here are the contents of the ozw.log file, on initiating the inclusion then cancelling the command 30 seconds later when the device times out.

2020-01-10 20:50:20.696 Detail, Queuing (Controller) Add Device
2020-01-10 20:50:20.696 Info, Add Device
2020-01-10 20:50:20.696 Detail, contrlr, Queuing (Command) ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x0b, 0x7a
2020-01-10 20:50:20.696 Detail, Notification: ControllerCommand - Starting
2020-01-10 20:50:20.696 Detail, 
2020-01-10 20:50:20.696 Info, contrlr, Sending (Command) message (Callback ID=0x0b, Expected Reply=0x4a) - ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x0b, 0x7a
2020-01-10 20:50:20.698 Detail, contrlr,   Received: 0x01, 0x07, 0x00, 0x4a, 0x0b, 0x01, 0x00, 0x00, 0xb8
2020-01-10 20:50:20.698 Detail, 
2020-01-10 20:50:20.698 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2020-01-10 20:50:20.698 Info, contrlr, ADD_NODE_STATUS_LEARN_READY
2020-01-10 20:50:20.699 Detail, Node001,   Expected callbackId was received
2020-01-10 20:50:20.699 Detail, Node001,   Expected reply was received
2020-01-10 20:50:20.699 Detail, Node001,   Message transaction complete
2020-01-10 20:50:20.699 Detail, 
2020-01-10 20:50:20.699 Detail, contrlr, Removing current message
2020-01-10 20:50:20.699 Detail, Notification: ControllerCommand - Waiting
2020-01-10 20:50:20.699 Info, WriteNextMsg Controller nothing to do

2020-01-10 20:51:14.861 Info, Cancel Add Node
2020-01-10 20:51:14.861 Detail, contrlr, Queuing (Command) Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4
2020-01-10 20:51:14.861 Detail, Notification: ControllerCommand - Canceled
2020-01-10 20:51:14.861 Detail, 
2020-01-10 20:51:14.861 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x4a) - Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4
2020-01-10 20:51:14.914 Detail, contrlr,   Received: 0x01, 0x07, 0x00, 0x4a, 0x0b, 0x06, 0x00, 0x00, 0xbf
2020-01-10 20:51:14.914 Detail, 
2020-01-10 20:51:14.914 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2020-01-10 20:51:14.914 Info, contrlr, ADD_NODE_STATUS_DONE
2020-01-10 20:51:14.914 Detail, Node006,   Expected reply was received
2020-01-10 20:51:14.914 Detail, Node006,   Message transaction complete
2020-01-10 20:51:14.914 Detail, 
2020-01-10 20:51:14.914 Detail, contrlr, Removing current message
2020-01-10 20:51:14.914 Detail, Notification: ControllerCommand - Completed

Could anyone offer some advice?

Thank you.

I’ve managed to get it to work, strangely by taking the USB dongle out of the USB port on the PC and putting it on the end of a USB extension lead. Go figure.

Sounds like it’s a moot point now, but I believe the instructions you were following were to add other devices into a network where the ZRC-90 is the primary controller, which is why the instructions are “backwards”. The instructions to add the ZRC-90 to an existing primary controller (gateway) are listed in the section “Z-Wave Learn mode”, and they say to put the gateway (HA) into inclusion mode and then press the L button (at least going by this manual), which is the same instructions as HA. For Z-Wave you always need to initiate inclusion on the primary controller.

Many scene controllers also function as primary z-wave controllers, which is why there are different inclusion instructions. That way you can control things like lights without involving a gateway.

A steep learning cuirve regarding Z-Wave terminology! Anyway, yes, it all seems ot be working now. I did have a problem with the name of the /dev deiovce as hitned at in my original post, the USB stick changed its name when plugging into a different port and I wasn’t able to get HA to recognise its new name. So I rolled back the install (hassio on a generic server) and just installed HA itself via Docker. Doesn’t give me the full hassio interface but it allows me to remap the device name to something persistent for use in HA. I couldnt’ see any way of doing that with the hassio install.

My 8-way wall remote now working to switch my whole-house audio matrix device between 8 sources in a particular room! Working via a route of the Scene Master to Home Assistant, which triggers HTTP Post commands to a Keene KIRA128 I-to-IR module pointed at the audio matrix. Convoluted path but home automation now gives me a way to control things easier and transparently.