Dome Siren fails to find neighbours

Posted on
Fri May 03, 2019 8:21 am
rbrouwer1 offline
Posts: 4
Joined: Oct 14, 2018

Dome Siren fails to find neighbours

I am having trouble getting the Dome Siren DSM01 to work unless it is within 2m of the Z stick. It will not find any neighbours if I move it to another location. Hence it fails with the 'Module might be asleep error.' I have 10 neighbouring, hard wired Z wave devices within 6m of where I want the siren (fibaro dimmers and switches) so I can't figure out why the Siren won't find a neighbour and hence a route back to the Z stick (Gen 5).

I have tried:

1. removing the device, re-adding, factory resetting, re-syncing multiple times.
2. including the siren with the Z stick in the final location for the siren
3. re-syncing all the neighbouring nodes with the device active (3 presses on button)
4. optimising Z wave network
5. changing batteries
6. Z stick is plugged directly into back of mac mini. I have no problems with my battery powered fibaro motion detectors.

Would love some advice.

Logs:
1. From the Dome siren itself
2019-05-04 00:01:18.542 Z-Wave Syncing - started for "021 - Siren (DSM01)"
2019-05-04 00:01:18.552 Z-Wave Debug SENT getNodeNeighbors: 01 06 00 80 15 01 01 6C
2019-05-04 00:01:18.558 Z-Wave Debug RCVD getNodeNeighbors: 01 20 01 80 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 00 00 00 00 5E
2019-05-04 00:01:18.558 Z-Wave Debug . . getNodeNeighbors: nodeId 021, neighbors: - none -
2019-05-04 00:01:18.559 Z-Wave Syncing - retrieved module neighbors list: - none -
2019-05-04 00:01:18.559 Z-Wave Syncing - assigning return route to "021 - Siren (DSM01)"
2019-05-04 00:01:18.560 Z-Wave Debug SENT assignReturnRoute: 01 05 00 46 15 01 A8
2019-05-04 00:01:18.583 Z-Wave Debug RCVD assignReturnRoute: 01 04 01 46 01 BD
2019-05-04 00:01:22.106 Z-Wave Debug RCVD assignReturnRoute: 01 05 00 46 01 01 BC
2019-05-04 00:01:22.107 Z-Wave Debug . . assignReturnRoute: node 021, success 0
2019-05-04 00:01:22.107 Z-Wave Error Syncing - failed to assign return route
2019-05-04 00:01:22.108 Z-Wave Debug SENT requestNodeInfo: 01 06 00 60 15 24 0B A3
2019-05-04 00:01:25.641 Z-Wave Debug RCVD requestNodeInfo: 01 06 00 49 81 00 00 31
2019-05-04 00:01:25.641 Z-Wave Debug RCVD requestNodeInfo: failed (module asleep or doesn't support command)
2019-05-04 00:01:25.642 Z-Wave Error Syncing - failed
2019-05-04 00:01:25.676 Z-Wave Error No response from "021 - Siren (DSM01)". Module might be asleep, or is unreachable.
2019-05-04 00:01:52.540 Z-Wave Debug terminatingSyncUI

2. From the nearest neighbour which is 1m from where I want the siren.
2019-05-03 23:55:16.903 Z-Wave Syncing - started for "n_kitchen_pendant lights"
2019-05-03 23:55:16.954 Z-Wave Syncing - retrieved module neighbors list: 5, 6, 7, 11, 12, 13, 14, 16, 17, 19
2019-05-03 23:55:16.954 Z-Wave Syncing - assigning return route to "004 - n_kitchen_pendant lights"
2019-05-03 23:55:17.665 Z-Wave Syncing - assigned return route
2019-05-03 23:55:18.223 Z-Wave Syncing - retrieved manufacture and model names: Fibaro System - 010F, Relay Power Switch - 0400300A
2019-05-03 23:55:18.510 Z-Wave Syncing - retrieved protocol version 3.42, app version 2.01
2019-05-03 23:55:18.798 Z-Wave Syncing - retrieved class hierarchy: Routing Slave : Relay Switch : Relay Power Switch (04 : 10 : 01, base 25)
2019-05-03 23:55:18.799 Z-Wave Syncing - retrieved command classes: 20v1 60v2 25v1 86v1 27v1 8Ev1 70v1 72v1 73v1 7Av1 85v1
2019-05-03 23:55:18.799 Z-Wave Syncing - retrieved encrypt commands: - none -
2019-05-03 23:55:18.800 Z-Wave Syncing - retrieved capabilities: routing, beaming
2019-05-03 23:55:19.366 Z-Wave Syncing - retrieved multi-endpoint types: 1:(10 : 01), 2:(10 : 01)
2019-05-03 23:55:19.366 Z-Wave Syncing - retrieved multi-endpoint classes: 1:[25], 2:[25]
2019-05-03 23:55:19.948 Z-Wave Syncing - retrieved group 1 associations: [1]
2019-05-03 23:55:20.239 Z-Wave Syncing - retrieved group 2 associations: []
2019-05-03 23:55:20.530 Z-Wave Syncing - retrieved group 3 associations: []
2019-05-03 23:55:20.531 Z-Wave Syncing - group 1 association to interface already exists (skipping)
2019-05-03 23:55:20.798 Z-Wave Syncing - complete

Posted on
Fri May 03, 2019 9:06 am
jay (support) offline
Site Admin
User avatar
Posts: 18220
Joined: Mar 19, 2008
Location: Austin, Texas

Re: Dome Siren fails to find neighbours

When you add it to the Z-Stick while it's close does it have any other neighbors listed other than the Z-Stick (normally node 1)?

Jay (Indigo Support)
Twitter | Facebook | LinkedIn

Posted on
Fri May 03, 2019 3:49 pm
rbrouwer1 offline
Posts: 4
Joined: Oct 14, 2018

Re: Dome Siren fails to find neighbours

No it never finds any neighbours even though there are tons right next to it.

Posted on
Tue May 07, 2019 2:55 am
rbrouwer1 offline
Posts: 4
Joined: Oct 14, 2018

Re: Dome Siren fails to find neighbours

I guess I'm trying to figure out if the problem is with the device itself - and thus I should return it - or is it to do with it's implementation in Indigo. I thought this siren was a supported device.

Posted on
Tue May 07, 2019 8:22 am
matt (support) offline
Site Admin
User avatar
Posts: 21417
Joined: Jan 27, 2003
Location: Texas

Re: Dome Siren fails to find neighbours

It is not in Indigo's implementation. The commands to discover/read neighbor nodes are very simple and the same for all devices. I don't know if your particular siren module is marginal, or if it is in some bad state. It is also possible your Z-Stick is in a bad state and the factory reset isn't helping for some reaosn. You can factory reset the Z-Stick (Interfaces->Z-Wave menu in Indigo), but then of course you have to re-include all your modules into it which can be a pain (if you have a lot).

Image

Posted on
Tue May 07, 2019 7:48 pm
rbrouwer1 offline
Posts: 4
Joined: Oct 14, 2018

Re: Dome Siren fails to find neighbours

I have a new Gen 5 Z stick - a month old. To test, I excluded all devices, factory reset everything but the same problem persists. I then used an old S2 Z-stick, went through it all again, same problem. Yes it was a bit of a pain !!!

So I guess it must be the device itself. I will return it and look at other options for a siren/doorbell.

Page 1 of 1

Who is online

Users browsing this forum: No registered users and 6 guests