Hi. I am curious if anyone here has run into an issue where having too many characteristics (12) can cause a Nordic Semi Bluetooth chipset to stop acting as a peripheral. Our hardware team is reporting that they have issues with having all 12 characteristics and reducing to 2 seems to work. They recommend that we create a struct with 6 or so members and expose those two structs as 2 characteristics instead of exposing 12 characteristics. I’d rather not, since once you start adding structs, you’ll have to add versioning, while keeping them as separate characteristics can allow the freedom to modify the characteristics more freely, while supporting older characteristics… Is there an issue with having too many characteristics? How have you overcome them? If you are using a Nordic implementation and haven’t had this issue, I’d love to hear from you too. Thanks. Mahboud _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.... This email sent to site_archiver@lists.apple.com