◆ pm_evt_id

#include <peer_manager_types.h>

Types of events that can come from the Peer Manager module.

Enumerator
PM_EVT_BONDED_PEER_CONNECTED	A connected peer has been identified as one with which we have a bond. When performing bonding with a peer for the first time, this event will not be sent until a new connection is established with the peer. When we are central, this event is always sent when the Peer Manager receives the BLE_GAP_EVT_CONNECTED event. When we are peripheral, this event might in rare cases arrive later.
PM_EVT_CONN_CONFIG_REQ	A new connection has been established. This event is a wrapper for BLE_GAP_EVT_CONNECTED event and contains its parameters. Reply with pm_conn_exclude before the event handler returns to exclude Bluetooth LE events targeting this connection from being handled by the Peer Manager.
PM_EVT_CONN_SEC_START	A security procedure has started on a link, initiated either locally or remotely. The security procedure is using the last parameters provided via pm_sec_params_set. This event is always followed by either a PM_EVT_CONN_SEC_SUCCEEDED or a PM_EVT_CONN_SEC_FAILED event. This is an informational event; no action is needed for the procedure to proceed.
PM_EVT_CONN_SEC_SUCCEEDED	A link has been encrypted, either as a result of a call to pm_conn_secure or a result of an action by the peer. The event structure contains more information about the circumstances. This event might contain a peer ID with the value PM_PEER_ID_INVALID, which means that the peer (central) used an address that could not be identified, but it used an encryption key (LTK) that is present in the database.
PM_EVT_CONN_SEC_FAILED	A pairing or encryption procedure has failed. In some cases, this means that security is not possible on this link (temporarily or permanently). How to handle this error depends on the application.
PM_EVT_CONN_SEC_CONFIG_REQ	The peer (central) has requested pairing, but a bond already exists with that peer. Reply by calling pm_conn_sec_config_reply before the event handler returns. If no reply is sent, a default is used.
PM_EVT_CONN_SEC_PARAMS_REQ	Security parameters (ble_gap_sec_params_t) are needed for an ongoing security procedure. Reply with pm_conn_sec_params_reply before the event handler returns. If no reply is sent, the parameters given in pm_sec_params_set are used. If a peripheral connection, the central's sec_params will be available in the event.
PM_EVT_STORAGE_FULL	There is no more room for peer data in non-volatile storage. To solve this problem, delete data that is not needed anymore and run a garbage collection procedure in ZMS.
PM_EVT_ERROR_UNEXPECTED	An unrecoverable error happened inside Peer Manager. An operation failed with the provided error.
PM_EVT_PEER_DATA_UPDATE_SUCCEEDED	A piece of peer data was stored, updated, or cleared in non-volatile storage. This event is sent for all successful changes to peer data, also those initiated internally in Peer Manager. To identify an operation, compare the store token in the event with the store token received during the initiating function call. Events from internally initiated changes might have invalid store tokens.
PM_EVT_PEER_DATA_UPDATE_FAILED	A piece of peer data could not be stored, updated, or cleared in non-volatile storage. This event is sent instead of PM_EVT_PEER_DATA_UPDATE_SUCCEEDED for the failed operation.
PM_EVT_PEER_DELETE_SUCCEEDED	A peer was cleared from non-volatile storage, for example because of a call to pm_peer_delete succeeded. This event can also be sent as part of a call to pm_peers_delete or internal cleanup.
PM_EVT_PEER_DELETE_FAILED	A peer could not be cleared from non-volatile storage. This event is sent instead of PM_EVT_PEER_DELETE_SUCCEEDED for the failed operation.
PM_EVT_PEERS_DELETE_SUCCEEDED	A call to pm_peers_delete has completed successfully. The non-volatile storage now contains no peer data.
PM_EVT_PEERS_DELETE_FAILED	A call to pm_peers_delete has failed, which means that at least one of the peers could not be deleted. Other peers might have been deleted, or might still be queued to be deleted. No more PM_EVT_PEERS_DELETE_SUCCEEDED or PM_EVT_PEERS_DELETE_FAILED events are sent until the next time pm_peers_delete is called.
PM_EVT_LOCAL_DB_CACHE_APPLIED	Local database values for a peer (taken from non-volatile storage) have been provided to the SoftDevice.
PM_EVT_LOCAL_DB_CACHE_APPLY_FAILED	Local database values for a peer (taken from non-volatile storage) were rejected by the SoftDevice, which means that either the database has changed or the user has manually set the local database to an invalid value (using pm_peer_data_store).
PM_EVT_SERVICE_CHANGED_IND_SENT	A service changed indication has been sent to a peer, as a result of a call to pm_local_database_has_changed. This event will be followed by a PM_EVT_SERVICE_CHANGED_IND_CONFIRMED event if the peer acknowledges the indication.
PM_EVT_SERVICE_CHANGED_IND_CONFIRMED	A service changed indication that was sent has been confirmed by a peer. The peer can now be considered aware that the local database has changed.
PM_EVT_PERIPHERAL_SECURITY_REQ	The peer (peripheral) has requested link encryption, which has been enabled.
PM_EVT_FLASH_GARBAGE_COLLECTED	The non-volatile storage has been garbage collected, possibly freeing up space.
PM_EVT_FLASH_GARBAGE_COLLECTION_FAILED	Garbage collection was attempted but failed.