Indigo Domotics

I'm new.
Just bought a AeoTec Z-Stick Gen-5.
Just installed 7.4 on Catalina.
Z-Stick works fine to my GoControl thermostat. And I ordered some cheap Wink devices off ebay to start playing with.

My Wink contact sensors register and work fine.
But the Motion doesn't seem to work and I don't know if its DOA or incompatible.
See image:

You see it can be discovered, but then nothing after that.
I checked supported devices and nothing is even listed for Wink on that page.
Do I need to pay more attention to which devices I purchase?
Didn't think a simple motion detector (this Wink one) would be unsupported.
Do I need to return this motion?

I picked Z-Wave because I moved into a house that had Z-Wave devices already. I'm not planning to change.
I wasted a few hours trying to get HomeAssistant and domoticz going. Indigo (although I can't really afford it) was easy and I don't need the frustration of dealing with the freebies.
i'm just wondering if I made the right choice.

Welcome. I’m sure no one here will think you made a mistake with indigo and hopefully we’ll help so that the wink purchases weren’t either. But yes, often worth checking supported devices or asking on here if you aren’t sure.

Yes indigo is more expensive than the free options, and not insubstantially so, but it’s often only a small part of the cost of a home automation setup and without doubt the most important.

Also your time is no doubt important and hopefully you’ll spend a lot less time adding new devices and setting up logic in indigo than in the others. Unless you decide to start plugin development of course!!

The device looks to have paired but I’m surprised it says notification sensor rather than motion. Looks like that’s a default but someone might correct me.

I’m not surprised the status request failed as the device is probably asleep. In the main screen what does the indigo device show as an icon?

I’m sure others will have better ideas but you could try turning on zwave debug under the interfaces menu and then activating motion. You may see zwave commands that even if indigo natively didn’t pick up could be used with a plugin.

Hope some of this helps.

I agree with siclark's post above.

The status request failing is expected for a battery operated module.

It is probably sending a message to Indigo, but not the one Indigo is expecting. To see what it is sending turn on Indigo's Z-Wave Debug Logging checkbox via the Interfaces->Z-Wave->Configure... menu item. Next, clear the Event Log window and then trip the motion sensor a couple of times (wait a couple of minutes between tripping it so that it resets). Copy/paste the Event Log window results into a reply for us and we can help you create a Trigger that will catch the message.

We'll also add a device definition for it (presuming our assumption that it is just sending a command that isn't caught by Indigo without a definition is accurate), so then in the next version of Indigo you can use a normal Trigger off of the device state changing.

thx for the replies

From the activated log:
several of these from my newbie attempts to get devices installed:
Z-Wave found module included in controller with no matching device (missing or disabled): 005 - Notification Sensor
Z-Wave Debug SENT getNodeProtocolInfo: 01 04 00 41 06 BC
Z-Wave Debug RCVD getNodeProtocolInfo: 01 09 01 41 53 9C 01 04 07 01 7A (no inbound callback)
Z-Wave Debug . . getNodeProtocolInfo: node 006, class name: Notification Sensor
Z-Wave Debug . . getNodeProtocolInfo: class hierarchy: Routing Slave : Notification Sensor : Notification Sensor (04 : 07 : 01)
Z-Wave Debug . . getNodeProtocolInfo: base class command: 00
Z-Wave Debug . . getNodeProtocolInfo: supported class commands: 20
Z-Wave Debug . . getNodeProtocolInfo: encrypt class commands:
Z-Wave Debug . . getNodeProtocolInfo: features: routing, beaming
Z-Wave found module included in controller with no matching device (missing or disabled): 006 - Notification Sensor
Z-Wave Debug SENT getNodeProtocolInfo: 01 04 00 41 07 BD
Z-Wave Debug RCVD getNodeProtocolInfo: 01 09 01 41 53 9C 01 04 07 01 7A (no inbound callback)
Z-Wave Debug . . getNodeProtocolInfo: node 007, class name: Notification Sensor
Z-Wave Debug . . getNodeProtocolInfo: class hierarchy: Routing Slave : Notification Sensor : Notification Sensor (04 : 07 : 01)
Z-Wave Debug . . getNodeProtocolInfo: base class command: 00
Z-Wave Debug . . getNodeProtocolInfo: supported class commands: 20
Z-Wave Debug . . getNodeProtocolInfo: encrypt class commands:
Z-Wave Debug . . getNodeProtocolInfo: features: routing, beaming


And then I moved the motion sensor and got this:
Jun 22, 2020 at 10:31:07 AM
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 0F 00 04 00 0B 09 71 05 00 00 00 FF 07 08 00 72
Z-Wave Debug . . requestAlarmSensorStatus: node 011, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 7, valueExt 8, classSubKeyExt 7100000708
Z-Wave Debug RCVD requestBinarySensorStatus: 01 0A 00 04 00 0B 04 30 03 FF 0C 3E
Z-Wave Debug . . requestBinarySensorStatus: node 011, endpoint None, type 12, value 255
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 0F 00 04 00 0B 09 71 05 00 00 00 FF 07 08 00 72
Z-Wave Debug . . requestAlarmSensorStatus: node 011, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 7, valueExt 8, classSubKeyExt 7100000708
Z-Wave Debug RCVD requestBinarySensorStatus: 01 0A 00 04 00 0B 04 30 03 FF 0C 3E
Z-Wave Debug . . requestBinarySensorStatus: node 011, endpoint None, type 12, value 255
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 10 00 04 00 0B 0A 71 05 00 00 00 FF 07 00 01 08 6F
Z-Wave Debug . . requestAlarmSensorStatus: node 011, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 7, valueExt 0, classSubKeyExt 7100000700
Z-Wave Debug RCVD requestBinarySensorStatus: 01 0A 00 04 00 0B 04 30 03 00 0C C1
Z-Wave Debug . . requestBinarySensorStatus: node 011, endpoint None, type 12, value 0

Jun 22, 2020 at 10:42:51 AM
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 0F 00 04 00 0B 09 71 05 00 00 00 FF 07 08 00 72
Z-Wave Debug . . requestAlarmSensorStatus: node 011, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 7, valueExt 8, classSubKeyExt 7100000708
Z-Wave Debug RCVD requestBinarySensorStatus: 01 0A 00 04 00 0B 04 30 03 FF 0C 3E
Z-Wave Debug . . requestBinarySensorStatus: node 011, endpoint None, type 12, value 255
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 0F 00 04 00 0B 09 71 05 00 00 00 FF 07 08 00 72
Z-Wave Debug . . requestAlarmSensorStatus: node 011, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 7, valueExt 8, classSubKeyExt 7100000708
Z-Wave Debug RCVD requestBinarySensorStatus: 01 0A 00 04 00 0B 04 30 03 FF 0C 3E
Z-Wave Debug . . requestBinarySensorStatus: node 011, endpoint None, type 12, value 255
Z-Wave Debug RCVD requestAlarmSensorStatus: 01 10 00 04 00 0B 0A 71 05 00 00 00 FF 07 00 01 08 6F
Z-Wave Debug . . requestAlarmSensorStatus: node 011, endpoint None, cmdClass 71, type 0, value 0, classSubKey 710000
Z-Wave Debug . . requestAlarmSensorStatus: typeExt 7, valueExt 0, classSubKeyExt 7100000700
Z-Wave Debug RCVD requestBinarySensorStatus: 01 0A 00 04 00 0B 04 30 03 00 0C C1
Z-Wave Debug . . requestBinarySensorStatus: node 011, endpoint None, type 12, value 0

siclark wrote:

I’m not surprised the status request failed as the device is probably asleep. In the main screen what does the indigo device show as an icon?

This makes sense - it is a battery device, and it seems to only blink (and transmit) when it senses motion.
Thx for the help.

We should be able to get this one supported working in the next version of Indigo (by adding a device definition). In the mean time, follow the instructions on this forum post to create a Trigger on the raw Z-Wave command.

Jaymer wrote:

siclark wrote:

I’m not surprised the status request failed as the device is probably asleep. In the main screen what does the indigo device show as an icon?

Screen Shot 2020-06-22 at 10.36.19 AM.png

This makes sense - it is a battery device, and it seems to only blink (and transmit) when it senses motion.
Thx for the help.

Does the Off change to On when it is triggered? I am guessing not, but hopefully you can create a trigger to change on the thread Matt mentions.

Indigo 7.5 is now available and includes support for the Wink Motion Sensor (WNK-MOT1).