EZSnsRF 3 wireless sensors all keep showing up as button 1

[Anonymous]

#39998

Hi All

A Mac question…..

I have upgraded to version Indigo 3.0.2 and can link my EZSnsRF to it.

I do this to add a module:

I hold the EZSnsRF button down for 4 seconds, Light starts flashing one a sec.

trip the motion on unit one, light flashing changes

Hit the “Send PowerLinc Set Button Pressed” In the device window of Indigo.

Hold down the set button on the EZSnsRF for 4 seconds. Light goes out.

I wanted a delay on the “off command” from the EZSnsRF – so I hit the set button on the EZSnsRF 10 times (the light is off at this point)

I hold the set button 4 sec – Light comes back on.

That should exit the “add a module” process.

I trip motion on the unit I just setup –
YEA – I get in the log “Dakota” on (button 1)” (I called the EZSnsRF “Dakota”)

So I repeat the entire process a second time with a different motion sensor. When finished Boo — the log says “Dakota” on (button 1)”

I was expecting button 2 or something.

What The heck am I doing wrong?

Thanks
Bob

[Anonymous]

#41971

Did you assign unique codes to each of the Dakota Alert motion sensors? If I remember right all my motion sensors came with the same code assigned.

[Anonymous]

#41972

No – Did not know I needed to –

I will research and report back

Bob

[Anonymous]

#41973

@grif091 wrote:

Did you assign unique codes to each of the Dakota Alert motion sensors? If I remember right all my motion sensors came with the same code assigned.

So are we talking about the last two DIP switches (first 8 being frequency)??

Thanks
Bob

[Anonymous]

#41974

I used a different frequency number (first 8 DIP switches) but I would think just changing the Zone number would be sufficient if you will have no more than 4 motion sensors or want to differentiate no more than four motions. You can have multiple sensors covering the same area (ie 2 covering front yard) in which case those would use the same frequency and zone number.

In addition to the motion sensors which are on different frequencies, I have two Dakota Alert magnetic driveway sensors, one EZLQD water level senor and one Dakota Alert Universal Transmitter monitoring dock power, all on the same frequency with a different zone number. Have not seen any conflicts but I don’t expect those four devices to overlap. I wanted the motion sensors as unique as possible in case multiple sensors tripped at the same time.

[Anonymous]

#41975

Well – you live and you learn!!!

Thanks for the hint – I do not know how to change the receiver freq of the EZSnsRF… But those last two dip switches worked.

I re-synced the devices and now they are button 1, 2, 3 – just the way it should be…..

the instructions are not very clear, but this helped!!!

Bob

[Anonymous]

#41976

Good to hear you are seeing desired results. Unlike Dakota Alert receivers that have to be set to the specific xmit device frequency, differentiating only the 4 zones, the 20 possible Virtual Inputs of the EZSnsRF cover the full xmit frequency range of the Dakota Alert 3000 devices.

[Anonymous]

#41977

@grif091 wrote:

Good to hear you are seeing desired results. Unlike Dakota Alert receivers that have to be set to the specific xmit device frequency, differentiating only the 4 zones, the 20 possible Virtual Inputs of the EZSnsRF cover the full xmit frequency range of the Dakota Alert 3000 devices.

Question – with 2 switches (9 and 10) that allows the RZSnsRF 4 different modules. How do you get to 20???

Do you change the frequency and then get 4 more on that frequency??

Thanks
Bob

[Anonymous]

#41978

That is correct. When you put the EZSnsRF into the first phase of linking (listening for Dakota signals), and cause a Dakota signal to be sent, the EZSnsRF looks through the existing Virtual Input definitions to see if the signal is new (different frequency and or zone from existing definitions). If “new”, it is added to the next available Virtual Input slot. Each Virtual Input slot is a unique button. Like a Keypadlinc has 6 or 8 buttons, the EZSnsRF has 20 buttons (Virtual Inputs).

[Author]

Posts