Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
We have a device which has multiple characteristics exposed via GATT. Now, we have some of them where the user should be able to wait for indications or notifications. As from the examples and the code generated from the wizard, we learned, that a indication is acknowledged by the peer and until the acknowledgment is received, no other indication is sent. Is this only valid for each characteristic or are all indications paused until the acknowledgement is received?
As we have multiple characteristics which are updated by the device at the same time and the probability that some of them change the value at the same time, we would like to ensure the peer receives not only the first indication. If possible, we would send out the updates at the same time without waiting for the acknowledgement of the first characteristic.
it is possible with notifications for now. We were just wondering if it is better with indications, as the framework offers this and gives a warranty that the content is received. But If we have to organize around the protocol, it is probably not our preferred solution.
(Our App developers also prefer notifications, so, I think we will select that)