@vidail Any chance this applies to custom configured zones or only normal zone reporting?
Tried the smart disarm this morning and can confirm that this firmware allowed the hardwired sensors to work in the smart disarm rule. Excellent work @vidail. I appreciate your assistance working with ADC to get this fixed.
1 Like
I noticed the system has begun to report additional hardware beyond sensors since the firmware update such as keypads, RF receiver and expansion modules. I seem to have duplicate keypads on slots 1 & 2 in the system sensor list. There is nothing working incorrectly so not a big issue just throws a warning to me that I have duplicate zone names.
Looking more into this I noticed that my AUI slots were enabled so I attempted to disable them but it did not change any keypad entry list. After disabling them, I noticed the SEM forced AUI slot 1 back to enabled so it must have to do with programming. However oddly enough it will not allow the SEM Keypad address 23 to be set to option 5 which would disable the auto stay setting for the remote arming through the app. This was possible on the other firmware. Is this normal for this release? If so I’m assuming I should disable the auto stay setting? This would explain the system reverting back to stay when armed with the app, but the SEM is changing my 5 entry back to 1 every time I attempt to change it.
Thank you for updating us. I am now looking into this. I will update you shortly on what I can find
Thank you for your patience
To confirm, you have 6160 keypads?
Correct I have 6160 and a 6160RF keypad.
I’m seeing that the keypads are being picked up as the same device number but as a different device type. The RF keypad is picked up as a keypad, rf, receiver, and communicator(this is what I’m trying to figure out). The regular 6160 Is picked up as a keypad and communicator. This could be a separate feature the keypad may have that the alarm.com communicator now picks up.
I currently do not see any duplicate zones.
What sections in programming sections are you trying to change when you mentioned the SEM keypad address and the sem changing the 5 back to 1?
I’m not sure what you are seeing perhaps you can see more details on the dealer portal.
I’m seeing duplicate keypads replicated on 1 & 2 positions, which I believe are keypads numbers but not the hardware address on the board. These are both labeled as control. Hence why I thought perhaps it was picking up AUI slots. Perhaps it’s just numbering of equipment types and not address as with the zones?
I have a push button control on 8 which I think is keypads 8 address 23 on the board. This should be the ADC communicator?
I see a RF Transceiver on 1 which also made sense because RF receivers are always on address 1 for Vista systems. This would be the 6160 RF so this being duplicate device make sense .
@vidail I also see a zone expansion module on item 2 which I do have one but it’s on device address 8 on the board.
The device manager did not like the replicated keypads 1 & 2 the control devices because when it brought them in it had the same name. I made it a repeat just to clear the error
For Vista with newer Prom chips you can set a keypad address to option to 5 for your communicator slot to disable the auto stay settings. This is entry 196 which aligns to keypad 8 address 23 for the SEM.
Hello,
Below is what I am able to see but it looks like the Reports sections is a bit different on my end. You can see below how it displays on my end.
I see what you mean for auto stay disarming option 5. This is most likely in the case you are using a TotalConnect2.0 communicator. Since we are using the alarm.com communicator, the auto stay arm will follow what is set in section 84. You can enable or disable Auto Stay Arm here.
@vidail any ideas on why device ID 1&2 are doubled as a keypad and communicator? I’m trying to figure out which device is the SEM and which are the keypads. At first I thought device ID 1 & 2 were keypads with some other function that duplicated. Now I see the other 1 & 2 device IDs are the communicator which I assume means it’s the SEM? Wonder if that is the broadband and cellular function? Then in that case Device ID 8 would that be the dealer portal emulated keypad for the SEM?
I though that it may behave that way as well but on the older firmware before we updated it was one of the tests I ran and option 5 worked on that release and the communicator would arm away even without an entry door trigger. Just thought it odd that one firmware it worked and this one it did not?