We currently do not support dynamic changing of the sharedID of the collections.What's your use case? Does your case work with the same sharedID you created already?
It's probably not necessary to switch SharedID's but it wasn't entirely clear when/why/what SharedID's did, so I erred on the side of safety...can you explain the usage/purpose of SharedID's?
To support switching SharedID's (if it is something you want to do), you can set the model to "null" as provided in the unsubscribe method implementation in original post.
The sharedID's are the names of collectionNodes used for identifying them on the server for that room. So, collectionNodes should all have unique sharedIDs in a room, if the user doesn't assign, it gets assigned to some default value.
When we do a dynamic switching, we don't want to destroy the entire model and recreate everything and rather resync the messages for the new room. This saves work and other technical complications.