Hi Claudio, On Wed, Dec 14, 2011 at 12:46 PM, Claudio Takahasi <claudio.takahasi@xxxxxxxxxxxxx> wrote: > Removing the timeout and write to "none" has a side effect: the remote > and the local value can have different values if the remote changes > the value. Alert Level characteristic doesn't support read, > notification or indication. Probably, all devices disable the alert > after some seconds to avoid drain the battery or be annoying. > The main problem is consistency: show to the user the correct value. In this case, I think the ImmediateAlertLevel should be write only (not readable). This forces applications to always write the level they want the peer device to alert. It means some spurious ATT write commands, but I think the spec assumes this is the case (otherwise it would allow read or notify). The problem is: is there such thing as "write only property" in BlueZ? Regards, -- Anderson Lizardo Instituto Nokia de Tecnologia - INdT Manaus - Brazil -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
