Important Notice Regarding Apple HomeKit
Posted By Michael GorisAlarm Grid has received important information from Honeywell, stating that any Lyric Controller using a WIFI-only communication setup is currently unable to work with an existing Apple HomeKit integration. Additionally, Honeywell has temporarily disabled the ability to activate new HomeKit service for all Lyric Controller Systems.
According to Honeywell, the Lyric Controller Security Systems are experiencing problems with WIFI connectivity when they are used with the HomeKit service. Honeywell is currently taking action to address this problem. The company says these issues should be fully resolved sometime in the third week of June.
Starting on Wednesday, May 23rd, Honeywell will disable all HomeKit features for any Lyric Controller that uses WIFI as its only communication path. This update will come in the form of a panel reboot while the system is in a disarmed state. The update may require up to three minutes to fully complete.
After the reboot, the panel should function as normal, though the HomeKit service will be disabled. Please note that this update is only being applied to Lyric Controller Systems that use a strictly WIFI connection. Lyric Controller Systems that use a dual-path setup with both WIFI and cellular, as well as those that use strictly cellular, are unaffected. Furthermore, Honeywell Lyric Gateway Systems are also unaffected.
Additionally, Honeywell has temporarily disabled the Apple HomeKit feature in AlarmNet 360. This makes it currently impossible to activate HomeKit service for any Lyric Controller System. New HomeKit activations will be possible once Honeywell restores the HomeKit feature sometime in the third week of June. Honeywell says that they plan to release more information regarding the restoration in the coming weeks.
If you have any questions regarding these issues, please email us at support@alarmgrid.com, or call us at 888-818-7728 between 9am and 8pm EST M-F. We apologize for any issues that this may cause.
Note: This issue has since been fixed.