![]() ![]() In houses/apartments where the partitions are set up for different families or individuals, this can cause problems, potentially serious. If you are using multiple partitions, and P2 is set up for say, medical alerts, and you try to trigger it, it will trigger the alarm on P1 instead. It should be mentioned the Honeywell panels expect a minimum 2 second delay between sending different sequences of commands to the panel, so if you need to toggle a connected relay, you cannot do it for less than 2 seconds, for example, a toggle of relay 11 is a set of 8 character sequences CODE#711 and CODE#811, but since they need to be different commands, the min 2s delay must be inserted before the 2nd sequence.Īlarm_trigger does not appear to send the trigger to the specified keypad for Honeywell, but rather the keypad for partition 1, this is hard coded in the library. An example is a zone bypass, CODE615 is the 7 character sequence to bypass zone 15, and that indeed works. Also you can for sure send more than 6 characters at least for Honeywell panels, there does not actually seem to be a defined limit anywhere for those. Well, internally ALL the other functions use the keypress function to send commands to the panel, so it is definitely working. The integration documentation lists the alarm_keypress function working on DSC and probably on Honeywell. HOWEVER, I have noticed some things that are either incorrect or could lead to unexpected behavior when auditing the code. I will list other changes in another post when I get them working. I am now doing the same thing to the integration component, such as supporting the new vacation arm mode. ![]() In the past I had made some updates to the upstream python library used by the integration, in order to add additional features. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |