When closing ZAP sometimes a system error shows up (#1613) - Believe that this was being caused by asynchronous reporting that we do for dirty flag and session notification counts on a periodic interval. When we close ZAP some of these reporting events are running queries on a closed database and thus throw a bunch of errors. The changes here stop the asynchronous reporting events from running when the database has been closed. - Taking AI's suggestion on the PR to put it in a try catch block - Adding error handling as suggested by the github AI assistant on the PR. The main reason db._closed is used is because when this chnage was not there and ZAP is closed/quit then a bunch of errors pop up. - JIRA: ZAPP-1607
ZAP is a generic generation engine and user interface for applications and libraries based on Zigbee Cluster Library, the specification developed by the Connectivity Standards Alliance.
ZAP allows you to perform the following:
ZAP is a generic templating engine. Examples are provided for how to generate artifacts for the C language environment, but one could easily add new templates for other language environments, such as C++, java, node.js, python or any other.
Refer to Setup Instructions
Refer to development instructions for more details.
This software is licensed under Apache 2.0 license.