Vision Siren and others

I recently joined the home automation [z]"wave" and on the advice of a friend I bought Indigo to be able to fully control my house in the way I wanted. While this required me to get my hands dirty I am happy to do so although of course I would have preferred an easier setup. Anyway issues I can solve myself I can moan about but at the end of the day I have managed to solve pretty much all the issues I found. What I don't seem to be able to work around is the issue of supported devices. Having done the basic home automation setup with motion sensors and light switches I now want to move into home security so I need a siren and a door sensor. I looked at the devices pages (http://www.indigodomo.com/devices/#zwave) and to my disappointment I can only see two supported sirens: one from FortrezZ and the other from Vision / Yale. The one from FortrezZ is not available in the UK and even if I were to buy it from the US where it is available it won't work on my network as I live in the UK and the RF frequencies are different (see this thread). The Vision / Yale AM1601 (also known as Vision ZM1601) seems to have been replaced by the Vision ZM1602 but there are no signs of this new device being supported. Any ideas if the Vision ZM1602 will work with Indigo?

On the recessed door sensor I found pretty much the same issue (see this thread). Now I understand that supporting new devices being released to the market takes time and money. I also understand that Indigo has no control of when an existing device is replaced. But the issue I am seeing is that increasingly the list Indigo supported Z-wave devices that is available for purchase is narrowing and this makes your software much less valuable. In my case I just wanted a siren and recessed door sensor and it seems there aren't any supported devices that I can buy. So any indication as to where your direction is with regards to new devices will be much appreciated. From my side I can offer you my time and the willingness to test new devices if that's needed.

Thanks

[jay (support)]

We understand the frustration - there are thousands of Z-Wave devices, many of which get upgrades and many more are added almost daily. As we say at the top of the Z-Wave list, we can't possibly verify that they all work (like you, we can't test devices from outside North America). When a device is updated, sometimes they will just work because they support standard the Z-Wave classes that Indigo supports and they don't have new model IDs.

Sometimes the manufacturer changes the model ID but the classes stay the same, in which case adding them to Indigo is usually quick - a user can report the model ID (by doing a device information submission) and we can get it into the next dot release (those are usually done every 3-4 weeks, and we can get a prerelease Z-Wave library out to those that need them sooner).

Sometimes, a device supports a new command class that Indigo doesn't support. In those cases, more work is required on our side and we schedule it along with all of the other priorities that we have.

Bottom line: we keep up as much as we can with the device churn, but a small company like us can only do so much. I'd recommend you get one of each of the devices you want to use and try them. If they work, then please report this to us and we can add them to the supported device list. If they don't work or only partially work, let us know and we'll resolve any issues as quickly as we can.

Hi Jay, makes sense. Will order them and give them a try and report back.

Thanks,
Christian

Hi,

I have submitted the device information for the recessed door sensor. Are you able to see my submission? I would imagine the recessed door sensor should be an easy device to add since it's very simple sensor. I have some comments on the Submit a Device page:

1) I noticed that the URL was full of parameters so initially I assumed there was an issue with my browser or the page itself and no information is displayed, despite all the parameters being in the URL. Eventually I figured it out that you are simply not using this parameters on the page and must be capturing them when the form submits. I would suggest to display them in the page (as read only fields) itself so that users can see them. It should be trivial to do so since they are being passed in the URL. That way it will be more clear what information is being submitted.

2) I would like to see an automatic email confirmation once the submission is received. That way I know someone is looking at it.

Thanks,
Christian

[matt (support)]

Hello Christian,

Thanks for the submission – we have received it. No ETA at this time, but it is in the queue for us to look at/implement after Indigo Touch is released.

[matt (support)]

The Vision / Yale AM1601 (also known as Vision ZM1601) seems to have been replaced by the Vision ZM1602 but there are no signs of this new device being supported. Any ideas if the Vision ZM1602 will work with Indigo?

Although we have the device submission for the recessed door sensor, I don't see any submission for the Vision ZM1602. Can you submit it? It would also be helpful if you define/sync it and copy/paste the Event Log results onto this forum thread for me.

Hi Jay,

I have a Vision ZM1602 (although the sync log suggests it is an AM1601?) siren/strobe that I would like to configure in Indigo. I have been able to add it as a device, but cannot seem to be able to configure it to alarm or flash lights, ideally I would be able to get it to beep, full siren, flash lights in a configurable pattern, or all combined. Is this possible? Below is the sync log for the device;
6 Jun 2015 7:48:11 pm
Z-Wave Debug intiatingSyncUI (timeout in 300 seconds)
Z-Wave Syncing - started for device "Alarm Strobe & Siren"
Z-Wave Debug SENT getNodeNeighbors: 01 06 00 80 0E 01 01 77
Z-Wave Debug RCVD getNodeNeighbors: 01 20 01 80 41 80 EA 17 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 62
Z-Wave Debug . . getNodeNeighbors: nodeId 014, neighbors: 1, 7, 16, 18, 20, 22, 23, 24, 25, 26, 27, 29
Z-Wave Syncing - retrieved module neighbors list: 1, 7, 16, 18, 20, 22, 23, 24, 25, 26, 27, 29
Z-Wave Syncing - requesting neighbor list update of "014 - Alarm Strobe & Siren"
Z-Wave Debug SENT requestNeighborUpdate: 01 04 00 48 0E BD
Z-Wave Debug RCVD requestNeighborUpdate: 06 (ACK)
Z-Wave Debug RCVD requestNeighborUpdate: 01 05 00 48 01 21 92
Z-Wave Debug . . requestNeighborUpdate: node 014, update starting
Z-Wave Debug RCVD requestNeighborUpdate: 01 05 00 48 01 22 91
Z-Wave Debug . . requestNeighborUpdate: node 014, update finished
Z-Wave Debug SENT getNodeNeighbors: 01 06 00 80 0E 01 01 77
Z-Wave Debug RCVD getNodeNeighbors: 01 20 01 80 01 80 EA 17 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 22
Z-Wave Debug . . getNodeNeighbors: nodeId 014, neighbors: 1, 16, 18, 20, 22, 23, 24, 25, 26, 27, 29
Z-Wave Syncing - neighbor list updated from 1, 7, 16, 18, 20, 22, 23, 24, 25, 26, 27, 29 to 1, 16, 18, 20, 22, 23, 24, 25, 26, 27, 29
Z-Wave Syncing - assigning return route to "014 - Alarm Strobe & Siren"
Z-Wave Debug SENT assignReturnRoute: 01 05 00 46 0E 01 B3
Z-Wave Debug RCVD assignReturnRoute: 01 04 01 46 01 BD
Z-Wave Debug RCVD assignReturnRoute: 01 05 00 46 01 00 BD
Z-Wave Debug . . assignReturnRoute: node 014, success 1
Z-Wave Syncing - assigned return route
Z-Wave Debug SENT requestNodeInfo: 01 06 00 60 0E 04 5C CF
Z-Wave Debug RCVD requestNodeInfo: 01 0E 00 49 84 0E 08 04 10 00 25 80 70 72 86 0F
Z-Wave Debug . . requestNodeInfo: node 014, combined class list: 20v1 80v1 25v1 86v1 70v1 72v1
Z-Wave Debug SENT requestManufactureInfo: 01 09 00 13 0E 02 72 04 05 5D C7
Z-Wave Debug RCVD requestManufactureInfo: 01 0E 00 04 00 0E 08 72 05 01 09 20 05 05 03 AF
Z-Wave Debug . . requestManufactureInfo: node 014, manufacturerId 0109, productId 20050503
Z-Wave Debug . . requestManufactureInfo: Vision / Yale, Siren/Strobe (AM1601)
Z-Wave Syncing - retrieved manufacture and model names: Vision / Yale - 0109, Siren/Strobe (AM1601) - 20050503
Z-Wave Debug SENT requestVersInfoGen: 01 09 00 13 0E 02 86 11 05 5E 25
Z-Wave Debug RCVD requestVersInfoGen: 01 0D 00 04 00 0E 07 86 12 06 03 2A 01 41 04
Z-Wave Debug . . requestVersInfoGen: node 014, protoVers 3.42, appVers 1.65
Z-Wave Syncing - retrieved protocol version 3.42, app version 1.65
Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Relay Switch : -- (04 : 10 : 00, base 25)
Z-Wave Syncing - retrieved command classes: 20v1 80v1 25v1 86v1 70v1 72v1
Z-Wave Debug SENT requestBatteryLevel: 01 09 00 13 0E 02 80 02 05 5F 31
Z-Wave Debug RCVD requestBatteryLevel: 01 09 00 04 00 0E 03 80 03 64 18
Z-Wave Debug . . requestBatteryLevel: node 014, level 100
Z-Wave Syncing - retrieved battery level of 100%
Z-Wave Syncing - complete
Z-Wave Debug SENT requestRelayStatus: 01 09 00 13 0E 02 25 02 05 60 AB
Z-Wave Debug terminatingSyncUI
Z-Wave sent "Alarm Strobe & Siren" status request
Z-Wave Debug SENT requestBatteryLevel: 01 09 00 13 0E 02 80 02 05 61 0F
Z-Wave Debug RCVD requestBatteryLevel: 01 09 00 04 00 0E 03 80 03 64 18
Z-Wave Debug . . requestBatteryLevel: node 014, level 100
Z-Wave received "014 - Alarm Strobe & Siren" status update battery level 100%
Z-Wave Debug RCVD requestBatteryLevel: 01 09 00 04 00 0E 03 80 03 64 18
Z-Wave Debug . . requestBatteryLevel: node 014, level 100
Z-Wave received "014 - Alarm Strobe & Siren" status update battery level 100%

Thanks

[matt (support)]

I'm not sure what options the ZM1602 supports, but I believe the ZM1601 just has a couple of options. One is the Operation Mode which can be set between: siren and strobe, siren only, and strobe only. The other is the Alarm Duration which can be set to 30, 60, 120 seconds, or no limit.

From your Event Log it doesn't look like Indigo is reading those configuration options though. If you press the Edit Device Settings button, do you see the 2 options above? If so, can you set them? Can you try the Define/Sync a couple more times to see if it ever reads those configuration options?

Lastly, what version of Indigo are you running?

Hi Matt,

I can see the two settings you mentioned, but I can't set them (they are greyed out). Below is the device information, if that helps. I think the difference between the 1601 & 1602 is that the 1602 has battery backup and wired power options.

Z-Wave Indigo Device "Alarm Strobe & Siren" Z-Wave Properties:
Indigo Z-Wave Version: 1.0.350
Node ID: 14
Model: Siren/Strobe (AM1601)
Model ID: 20050503
Manufacturer: Vision / Yale
Manufacturer ID: 0109
Protocol Version: 3.42
Application Version: 1.65
Model Definition Version: 1
Library Type: 6
Class Name: Relay Switch
Class Hierarchy: 04 : 10 : 00
Command Class Base: 25
Command Versions: 20v1 80v1 25v1 86v1 70v1 72v1
Multi-Endpoint Types: - none -
Multi-Endpoint Classes: - none -
Multi-Instance Counts: - none -
Features: routing, battery, beaming, frequentWaking
Neighbors: 1, 16, 18, 20, 22, 23, 24, 25, 26, 27, 29
Associations: - none -
Config Values: - none -

What I would really like to be able to do is to choose the action Indigo sends to the device, so I can use it to strobe, siren, or strobe and siren (rather than set it in the settings and only be able to use one of the configurations). Is this possible?

Thank you

Sorry, I'm running Indigo 6.1.

You can send parameters on-the-fly using an action group, as long as the device is powered and therefore always awake.

It's something like Action > Devices > Send Config Parameter.

[matt (support)]

This thread is old but I wanted to follow-up that Indigo 7.0 is now available (has been for a while). It adds supports for dozens of new Z-Wave devices, including several Vision models.

Thanks Matt. Installed it over the weekend. Confirmed as working, no issues with it!