Envisalink 4 out of sync with 6160rf keypad when arming/disarming

[pinkchry]

Hi, Just setting up a new system with a Vista 20p, 6160RF and an Envisalink 4.
My envisalink is keypad 18, wherease my 6160rf is keypad 16.
I've gone through the step detailed (including enabling all reports for all partitions) and arming/disarming via the web interface works and faults are reported correctly.
However when I arm through the web interface, I don't get any notification on the keypad about the arm. It still says "Disarmed - Ready to Arm"
I also don't seem to get the disarmed messages. Here's a snapshot my of my log

January 26, 2018, 2:30 pm EST - Stay Arming by User Code 2 - Partition 2
January 26, 2018, 2:28 pm EST - Battery Trouble Alarm
January 26, 2018, 1:40 pm EST - Opening By User Code 2 - Partition 1
January 26, 2018, 1:38 pm EST - Stay Armed - Partition 1
January 26, 2018, 1:37 pm EST - Away Arming by User Code 2 - Partition 1
January 26, 2018, 1:36 pm EST - Opening By User Code 2 - Partition 2
January 26, 2018, 1:35 pm EST - Stay Arming by User Code 2 - Partition 2
January 26, 2018, 1:24 pm EST - Opening By User Code 2 - Partition 2
January 26, 2018, 1:22 pm EST - Stay Arming by User Code 2 - Partition 2
January 26, 2018, 1:18 pm EST - Battery Trouble Alarm

Any ideas on what I could be doing wrong?

[pinkchry]

Also, when I arm the system using the keypad, I get the following events

January 26, 2018, 9:15 pm EST - Stay Armed - House
January 26, 2018, 9:14 pm EST - Away Arming by User Code 2 - House


However the web page shows the House as Ready to Arm. It's not updated the state to be Armed Away.

[GrandWizard]

You have a Keypad address conflict. The Envisalink has to have an unique address on the bus otherwise it will conflict and you won't be able to control the partition.

[pinkchry]

I re-entered the keypad addresses and disabled the other keypads and it seems to be working now.

Thanks!