I have a powermaster 30 great kit just upgraded the installation to the new lastest powerlink 3 etc instead of the gsm for the cam units x 5 ,  but whilst programming thought i'd do some other bits at same time , a few more smoke detectors and extra tower cams etc and some spare fobs i had for "just in case" standby loss etc.

 

Point, obviously sticking to the right freq of 868hz of my kit,  I can get a new key fob( kf-234pg2 868:0:030) to be recognised by its i.d. by main panel, but  tried and tried but no joy to get it to work fully , issue light on ( yell triangle) going to put in x4 fobs but can not get the one to work, but states it will not network at all, any suggestions?

 

 

the other kit just went in a treat except one tower that had a "wrong" id code stated "142-xxxx"  was actually "140-xxxx" after tapping the the enroll button to get it in the system. I would have thought that would be rare with visonics quality control.

 

Strike that just had a tower fail through condensation the top circuit board in the head, took to bits dried on radiator, placed in x 2 1g silica packets to see how it performs in service( only one way signal), **** idea on seeing the unit stripped down, battery compartment has a gasket the unit, but  is open from top down with just a clip lid that obviously allows in atmosphere over time... ( designed to external use)

Meh, Visonic...

The warning will be something else not the keyfob.

Keyfobs should enroll easily with the ID, arm and disarm with them and will show networked.

it did see it and took the id in,  but then going to device settings it would not let it complete the process.. once i cancel the fob / delete it the warning goes. hence the "not networked"

Edited February 18, 201610 yr by todcctv