Intruder partition not automatically armed away anymore using Kwikset Zwave Smartlock on 1.3.13e
Anywone has the same type of issue I have?
Since I upgraded my system with latest firmware (1.3.13e), the Intruder partition is not automatically armed away when I lock the front door using my pin number on my Kwikset Zwave Smart lock. This functionality was working flawlessly for the last 6-8 months and it is not working anymore since I upgraded to the latest firmware.
I tried to re-installed 1.2.29m from app repo and then the functionality start working again as before meaning that the intruder partition is armed away when I'm locking the front door using my pin number on my Kwikset Zwave smartlock keypad.
I raised a ticket to support and follow their guidance which was to delete the smartlock and pair it again with my zipatile under 1.3.13e Firmware, I reconfigured the users PIN numbers and remap the event under the user tab of the intruder alarm partition and this is still not working, meaning that when I lock the door using my pin number on my smartlock keypad, the intruder partition is not notified and armed away or it is not taking into consideration anymore the notification command coming from the smartlock Zwave device.
Now support claims that I have Unsupported devices that may cause this issue, but looking at the list provided by Mislav Culo, the claimed unsupported devices are part of the list of devices supported by Zipato.
The devices are the following (See Attached the file provided by Zipato I found from another topic:
My Dimmers are Leviton DZ6HD Z-Wave Dimmers,
My Kitchen Door Sensor is an Everspring HSM02 Door/Window sensor
My siren is an Aeon Labs Wall Socket Siren GEN5
The only one I see that is not part of the list is my Ecolink Garage Door Tilt Sensor but in the list there are several other supported Ecolink Sensors, door/window sensors for instance.
I'm asking support to look at this for more than a month and it is getting no where. They even want me to buy professional services to audit my system configuration but the system configuration hasn't change since I only upgraded to the newest Firmware.
Today I have downgraded again the firmware to1.2.29m and I gained back that functionality that i lost for more than a month now (It is working as expected after a simple rollback to 1.2.29m without any configuration changes or required synchronization). I would like this to be fix in the newest Firmware and I'm wondering if anyone else has experienced this type of issue with the new firmware. To me it is a SW problem that should be properly looked at and fixed by Zipato.
I'm running out of resources and I do not know what to do more.