You are reading a single comment by @Gordon and its replies.
Click here to read the full conversation.
-
Thanks @Gordon!
I guessed it could be a limitation also because that bulb has a lot of custom UUIDs.
I will try the battery trick but in this case i think it will be better to use array index as i already did, so i am sure i will point to the right service/characteristic.
Could you try just taking the battery out and re-adding it to your Puck, then trying again?
The nRF52 chip can only have a certain number of long UUIDs in memory at once - and annoyingly I don't think they can be removed once added.
I'll see about increasing the number of usable UUIDs in the next version - that should help a lot. Otherwise it's hard to know what to do - I could add a function that let you explicitly restart the Bluetooth subsystem, but by the time Puck.js has got to getPrimaryService and realises there is not more storage for UUIDs, it's a bit late for it to do a restart automatically :)