Z-Wave Me wall switch (ZME_WALLC-S) shows up as 'Initialising (Probe)’

Hey,

I have troubles connecting the Z-Wave Me wall switch (ZME_WALLC-S). I am already running Home Assistant and an Aeotec Z-Wave stick to control a couple of thermostats without any troubles.
After including the wall switch into the Z-Wave network, it shows up as ‘Initialising (Probe)’ in Home Assistant. I tried pressing buttons on the switch and re-booting Home Assistant but it doesn’t help at all. As I thought it might be a one time setup issue, I tried to exclude and reset the wall switch and include it again. Unfortunately, that did not help either but I have multiple devices showing up as ‘Initialising (Probe)’ in Home Assistant.

So now I have two problems:

  1. I can’t connect the wall switch to Home Assistant.
  2. I can’t get rid of the ‘Initialising (Probe)’ devices.

Any help is appreciated,
flodifl

Battery operated devices most often show Initialising (Probe) because they are asleep until activated. It is the expected behavior. If you need to make settings changes to the switch, there will be a way to keep the device awake for a short period of time so that it can accept the settings from Homeassistant. I would run
tail -f OZW_Log.txt
from the command line, as you press the switch. You should see some indication that the node is sending information to HA. You may need to craft an automation that uses the state change from the switch to trigger whatever you want to happen.

1 Like

Thanks for the input, I solved the issue. Here some details for people running into the same problem:
Running tail -f OZW_Log.txt printed the following when pressing a button on the switch:

2018-03-11 09:28:37.731 Detail, Node008, Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x08, 0x05, 0x5b, 0x03, 0x7e, 0x00, 0x01, 0xda 2018-03-11 09:28:37.732 Detail, 2018-03-11 09:28:37.732 Info, Node008, ApplicationCommandHandler - Unhandled Command Class 0x5b

In other threads I read that this might come from the device requiring secure communication. Thus, I set a network key in options.xml, rebooted Home Assistant and included the switch as a secure node via Home Assistant’s configuration panel.

Running tail -f OZW_Log.txt again, I saw that the communication was basically working. The only part missing was to update my zwcfg_…xml file as mentioned in “Central Scene” Command Class - Fibaro Swipe, HomeSeer WS-100D Switches .

Now it is working :grinning:!

Glad you got it working. You might want to consider moving your network key to your configuration.yaml file to align it with current practices.

zwave:
  usb_path: /dev/serial/by-id/usb-0658_0000
  network_key: "0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00"

I got it to work by following the following steps

NB! Make sure you have the device in factory default mode. If not remove the device and factory reset it.

  • click “add node secure” and press any button on the ZME controller for >1 sec until it starts blinking
  • wait until the logs (tail -f /config/OZW_Log.txt) stops printing information about your node
  • look in zwcfg_xxx.xml to see that your node is there “ZME-WALLC-S”. If not restart hassio and it should show up

// the following 2 should be preceeded by pressing all 4 buttons until blinking and then push button 2. blinking rapidly

  • set association to the z-wave controller in the HA zwave config menu

  • Click refresh node. This will put the device in probe state // maybe not needed but I had to

  • Stop HA by ssh into HA and run hassio homeassistant stop

  • edit /config/owxfg_.xml and look for ZME_WALLC-S Secure Wall Controller.
    In this Node you replace CommandClass id=“91” with this:

<CommandClass id="91" name="COMMAND_CLASS_CENTRAL_SCENE" version="1" request_flags="5" innif="true" scenecount="0">
<Instance index="1" />
	<Value type="int" genre="system" instance="1" index="0" label="Scene Count" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
	<Value type="int" genre="system" instance="1" index="1" label="Button One" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
	<Value type="int" genre="system" instance="1" index="2" label="Button Two" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
	<Value type="int" genre="system" instance="1" index="3" label="Button Three" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
	<Value type="int" genre="system" instance="1" index="4" label="Button Four" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
	<Value type="int" genre="system" instance="1" index="5" label="Other" units="" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="0" />
</CommandClass>
  • Start HA by ssh into HA and run hassio homeassistant start
  • do tail -f /config/OZW_Log.txt and then press a button on your WALL-C controller and see that it should have output like this:
2019-02-17 12:08:39.667 Detail, Node010,   Received: 0x01, 0x0b, 0x00, 0x04, 0x00, 0x0a, 0x05, 0x5b, 0x03, 0xd8, 0x00, 0x01, 0x7e
2019-02-17 12:08:39.667 Detail,
2019-02-17 12:08:39.667 Info, Node010, Received Central Scene set from node 10: scene id=1 in 0 seconds. Sending event notification.
2019-02-17 12:08:39.667 Detail, Node010, Refreshed Value: old value=0, new value=0, type=int
2019-02-17 12:08:39.667 Detail, Node010, Changes to this value are not verified
2019-02-17 12:08:39.667 Detail, Node010, Notification: ValueChange
  • Note the scene id=<number which should be 1 if the top left button was pressed

  • Add automation to test it

alias: Test zwave event
trigger:
  platform: event
  event_type: zwave.scene_activated
  event_data:
    entity_id: zwave.z_wave_me_zme_wallc_s_secure_wall_controller_2
    scene_id: 1
action:
  - service: notify.notify
    data_template:
      message: >
        Got event for scene id 1 from the controller