Currently, if you try to load a new state configuration via a URL, the default network loads. This is irrespective of the URL passed, as it also fails when passed the URL for the Les Miserables sample.
From my investigations so far, it appears the state is not being stored at the instances/sectionId/state URL, so fetching from the app fails and it reverts to the default state.
This may also require changes to how the logging is implemented in the api.js file of the OVE Core component to ensure it's possible to see how the state is being saved when the section is created.