Aeotech Z-Stick seems to be installed correctly but can't add devices

162884 · February 17, 2018, 3:55am

My first post and I’m a novice to HA. So far I’ve managed to get HA installed and up and running on my RPi 2. I used the simple method by installing hass.io by flashing the SD card with the full image.

First thing I did was add the Z-Stick. The Overview reports it’s ready.

I then go to Configuration and select “Add Node”. I then immediately press the “Action” button on the Aeotech MultiSensor to get it discovered by the Z-Stick and HA. However, I get nothing. Everything is right next to each other during this time frame. I tried a different brand (Neo Coolcam) sensor with the same result.

I would appreciate some help to a HA newbie who is trying to get started!

anon43302295 · February 17, 2018, 4:03am

Is it just one button press on the multisensor for pairing? My fibaro one is 3 quick presses, and then another one a bit later to keep it awake.

May need to reset it to factory settings first, then include it.

Manual should tell you all the button presses needed.

162884 · February 17, 2018, 4:21am

Yes, the Aeotech MultiSensor is a one press of the button. The other sensor was 3 quickly. I’m not sure what to do next. Does it take a while before they show up? How do I know that the Stick even communicated with the sensor? Appreciate your help.

anon43302295 · February 17, 2018, 4:24am

At the bottom of the Zwave page in HA you can watch the log, click add node, click refresh and see that it’s waiting, hit the button on your sensor, click refresh again and see what is happening.

carbuthn · February 17, 2018, 4:37am

I am also using the same z-wave stick. I normally use the add node secure button. The message to the left of the button says that you will not see anything accept for in the log at the bottom.

They showed up as badges at the top of the overview page after restart / reboot of Hassio.

162884 · February 17, 2018, 5:06am

I click “Add Node” and the log shows what’s below. I have each of my 3 sensors in pairing mode and the log doesn’t change after a refresh.

2018-02-17 00:02:36.886 Detail, Queuing (Controller) Add Device
2018-02-17 00:02:36.886 Info, Add Device
2018-02-17 00:02:36.886 Detail, contrlr, Queuing (Command) ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x0b, 0x7a
2018-02-17 00:02:36.887 Detail, Notification: ControllerCommand - Starting
2018-02-17 00:02:36.939 Detail,
2018-02-17 00:02:36.939 Info, contrlr, Sending (Command) message (Callback ID=0x0b, Expected Reply=0x4a) - ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x0b, 0x7a
2018-02-17 00:02:36.942 Detail, contrlr, Received: 0x01, 0x07, 0x00, 0x4a, 0x0b, 0x01, 0x00, 0x00, 0xb8
2018-02-17 00:02:36.943 Detail,
2018-02-17 00:02:36.943 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2018-02-17 00:02:36.943 Info, contrlr, ADD_NODE_STATUS_LEARN_READY
2018-02-17 00:02:36.943 Detail, Node001, Expected callbackId was received
2018-02-17 00:02:36.943 Detail, Node001, Expected reply was received
2018-02-17 00:02:36.943 Detail, Node001, Message transaction complete
2018-02-17 00:02:36.943 Detail,
2018-02-17 00:02:36.944 Detail, contrlr, Removing current message
2018-02-17 00:02:36.944 Detail, Notification: ControllerCommand - Waiting
2018-02-17 00:02:36.971 Info, WriteNextMsg Controller nothing to do

anon43302295 · February 17, 2018, 5:09am

OK, that looks like it’s not getting anything from the sensor. Can you factory reset the sensor and try again?

162884 · February 17, 2018, 1:39pm

Restarted HA, factory reset the sensor and here’s the log from the latest attempt.

2018-02-17 08:36:39.875 Detail, Queuing (Controller) Add Device
2018-02-17 08:36:39.876 Info, Add Device
2018-02-17 08:36:39.876 Detail, contrlr, Queuing (Command) ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x0a, 0x7b
2018-02-17 08:36:39.877 Detail, Notification: ControllerCommand - Starting
2018-02-17 08:36:39.916 Detail,
2018-02-17 08:36:39.916 Info, contrlr, Sending (Command) message (Callback ID=0x0a, Expected Reply=0x4a) - ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x0a, 0x7b
2018-02-17 08:36:39.920 Detail, contrlr, Received: 0x01, 0x07, 0x00, 0x4a, 0x0a, 0x01, 0x00, 0x00, 0xb9
2018-02-17 08:36:39.928 Detail,
2018-02-17 08:36:39.928 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2018-02-17 08:36:39.928 Info, contrlr, ADD_NODE_STATUS_LEARN_READY
2018-02-17 08:36:39.929 Detail, Node001, Expected callbackId was received
2018-02-17 08:36:39.929 Detail, Node001, Expected reply was received
2018-02-17 08:36:39.929 Detail, Node001, Message transaction complete
2018-02-17 08:36:39.929 Detail,
2018-02-17 08:36:39.929 Detail, contrlr, Removing current message
2018-02-17 08:36:39.929 Detail, Notification: ControllerCommand - Waiting
2018-02-17 08:36:39.956 Info, WriteNextMsg Controller nothing to do
2018-02-17 08:36:48.160 Detail, Received: 0x01, 0x07, 0x00, 0x4a, 0x0a, 0x02, 0x00, 0x00, 0xba
2018-02-17 08:36:48.160 Detail,
2018-02-17 08:36:48.160 Info, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2018-02-17 08:36:48.160 Info, ADD_NODE_STATUS_NODE_FOUND
2018-02-17 08:36:48.160 Detail, Notification: ControllerCommand - InProgress
2018-02-17 08:36:51.358 Detail, Received: 0x01, 0x07, 0x00, 0x4a, 0x0a, 0x07, 0x00, 0x00, 0xbf
2018-02-17 08:36:51.358 Detail,
2018-02-17 08:36:51.358 Info, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2018-02-17 08:36:51.358 Info, ADD_NODE_STATUS_FAILED
2018-02-17 08:36:51.358 Detail, Removing current message
2018-02-17 08:36:51.358 Detail, contrlr, Queuing (Command) Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4
2018-02-17 08:36:51.359 Detail, Notification: ControllerCommand - Failed
2018-02-17 08:36:51.372 Detail,
2018-02-17 08:36:51.372 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x4a) - Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4
2018-02-17 08:36:51.426 Detail, contrlr, Received: 0x01, 0x07, 0x00, 0x4a, 0x0a, 0x06, 0x00, 0x00, 0xbe
2018-02-17 08:36:51.426 Detail,
2018-02-17 08:36:51.426 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2018-02-17 08:36:51.426 Detail, Node006, Expected reply was received
2018-02-17 08:36:51.426 Detail, Node006, Message transaction complete
2018-02-17 08:36:51.426 Detail,
2018-02-17 08:36:51.426 Detail, contrlr, Removing current message
2018-02-17 08:36:51.427 Detail, Notification: ControllerCommand - Completed

anon43302295 · February 17, 2018, 3:04pm

I’m at a loss mate tbh. I literally just added a fibaro light switch this morning (only to find it doesn’t work on tube lights, but that’s another story!!) and it worked fine.

The steps I took (which I’m pretty confident you’re already doing, but just for reference):

In HA go to configuration > z-wave > Add node secure

Go to device, click the button 3 times - wait a few seconds - refresh the log and there’s a load of handshake information there showing it’s picking it up.

Wait another couple of minutes, and there it is in HA.

I have no idea why this isn’t working for you

162884 · February 17, 2018, 3:09pm

@anon43302295… it just worked for me. Factory reset all 3 z-wave devices and they are seemingly getting initialized. How long does it take for them to be fully ready? Looks like I’ll need to name them so I know which one is which.

162884 · February 17, 2018, 7:56pm

I don’t believe my devices are 100%. The one that reports “Dead” is literally 6-feet from the Z-Stick and the others are still “Initializing” after a few hours…

nfh · August 6, 2018, 8:27am

@162884, did you manage to make it work? I am experiencing the exact same problem.
It all started when I tried to remove all my devices (with the remove node feature), that did not work for any of them and I ended up doing a factory reset on the Aeotec zwave stick and every zwave device.

Now I am trying to add them to the mesh and everytime I do it I just get the “Info, WriteNextMsg Controller nothing to do” on the last line of the OZW log file, it seems that it is not getting any reply from the devices (and I tried with every single one, so it should not be anything related to those devices).

I experienced the problem with 0.75.1, downgraded to 0.74.2 (with the CLI command via SSH) just to find that the problem remains.

Any clues?

Mike_Boiko · November 17, 2018, 4:28am

I’m having the exact same issue trying to get a Zooz ZSE40 (4 in 1 Sensor) to connect with my Aeotec Gen 5 Zwave stick. Hopefully somebody knows how to get these devices to pair. Thanks!

Mike_Boiko · November 17, 2018, 5:43am

I figured out what the problem was for me. I had purchased the Europeon version of the Aeotec Gen 5 Z-stick, which runs on 868.42 MHz. My device is a US Z-Wave device that runs on 908.42 MHz. Whoops!

shakazu · November 22, 2019, 9:17pm

When you add a device can you post the output? My device seems to sit on:

2019-11-22 16:16:10.606 Detail, contrlr, Queuing (Command) Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4
2019-11-22 16:16:10.606 Detail, Notification: ControllerCommand - Canceled
2019-11-22 16:16:10.608 Detail,
2019-11-22 16:16:10.609 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x4a) - Add Node Stop: 0x01, 0x04, 0x00, 0x4a, 0x05, 0xb4
2019-11-22 16:16:10.666 Detail, contrlr, Received: 0x01, 0x07, 0x00, 0x4a, 0x14, 0x06, 0x00, 0x00, 0xa0
2019-11-22 16:16:10.666 Detail,
2019-11-22 16:16:10.666 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2019-11-22 16:16:10.666 Info, contrlr, ADD_NODE_STATUS_DONE
2019-11-22 16:16:10.666 Detail, Node006, Expected reply was received
2019-11-22 16:16:10.666 Detail, Node006, Message transaction complete
2019-11-22 16:16:10.667 Detail,
2019-11-22 16:16:10.667 Detail, contrlr, Removing current message
2019-11-22 16:16:10.667 Detail, Notification: ControllerCommand - Completed
2019-11-22 16:16:12.698 Detail, Queuing (Controller) Add Device
2019-11-22 16:16:12.698 Info, Add Device
2019-11-22 16:16:12.698 Detail, contrlr, Queuing (Command) ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x15, 0x64
2019-11-22 16:16:12.698 Detail, Notification: ControllerCommand - Starting
2019-11-22 16:16:12.700 Detail,
2019-11-22 16:16:12.700 Info, contrlr, Sending (Command) message (Callback ID=0x15, Expected Reply=0x4a) - ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x15, 0x64
2019-11-22 16:16:12.704 Detail, contrlr, Received: 0x01, 0x07, 0x00, 0x4a, 0x15, 0x01, 0x00, 0x00, 0xa6
2019-11-22 16:16:12.704 Detail,
2019-11-22 16:16:12.704 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
2019-11-22 16:16:12.704 Info, contrlr, ADD_NODE_STATUS_LEARN_READY
2019-11-22 16:16:12.704 Detail, Node001, Expected callbackId was received
2019-11-22 16:16:12.704 Detail, Node001, Expected reply was received
2019-11-22 16:16:12.704 Detail, Node001, Message transaction complete
2019-11-22 16:16:12.704 Detail,
2019-11-22 16:16:12.704 Detail, contrlr, Removing current message
2019-11-22 16:16:12.704 Detail, Notification: ControllerCommand - Waiting
2019-11-22 16:16:12.705 Info, WriteNextMsg Controller nothing to do

anon43302295 · November 22, 2019, 9:23pm

No idea mate, sorry. I found Zwave horribly unreliable in the end and replaced it all with other protocols that have been far more stable.

shakazu · November 22, 2019, 9:33pm

Thanks for the input, Whats your preference? Zigbee?

That seemed to work fine until I reloaded my pi4 to just have the "HUSBZB-1 instead of 2 stick (plus the Aeotec needs to have a usb 2.0 hub on the pi4).

Now my samsung smart things motion/temp sensor thinks it is a water sensor every time i try to pair it lol. it also shows up like 5 times when in discovery.

anon43302295 · November 22, 2019, 9:49pm

I have a lot of zigbee, and a fair amount of WiFi stuff here.

colin8 · November 26, 2019, 2:58am

I had this same exact problem when I was getting started, but for the life of me cannot remember what finally got things to work. But now, about 15 devices in, it’s happening again. I’ve updated HA, restarted numerous times, healed the network, etc, and still get the same thing. Any advice would be very welcome.

EDIT: After trying everything else I could think of (deleting Z-Wave integration, using OpenZWave, and more), I was finally able to get it to add my switch by 1) factory resetting the device and 2) putting the device in pairing mode BEFORE I tried to add it via Node Management. The log starting at “Node001, Expected callbackId was received” showing up immediately after I attempted to add a node led me to believe that Node 1, the Z-Wave stick, was firing off a signal that was not allowing HA to look for any other devices. By starting the pair mode on the switch before hand, I guess it allowed HA to see those signals before the Node001 did it’s “thing.”

I could be completely wrong, and it could just be complete luck that it worked that time, but hopefully this helps someone else having the same issues.

aC23 · December 19, 2019, 4:26am

Just had this exact problem. I reset the light switches (tap-tap-tap-hold on button for 10+ seconds), restarted HA and was then able to add the node successfully. Hopefully this helps others