HOME › Forums › Gateways › EZSrve › Unable to modify scenes with uploaded scenes.xml file. › Reply To: Unable to modify scenes with uploaded scenes.xml file.
Did you do a restart (not reset) after uploading the new scene xml file?
EDIT: I added an additional Scene to my scenes.xml by copy/paste of an existing entry and changing the Scene name and Group number. Uploaded the scenes.xml file. Message said successfully uploaded and Restart required. Did Restart, can see the new Scene by doing another List Files and looking at the scenes.xml file but the Scene GUI does not show the new Scene. Tried the SYNCH DEVICES button because links did not exist for new scene but that did not cause the new scene to be visible in the Scenes GUI screen.
EDIT2: Changed the name of the second Scene which was in the original scenes.xml thinking that the third scene (the one I added manually) did not show because of a scene count somewhere that was not being updated. Same no change result. See the new Scene name in the List Files scenes.xml display but the Scenes GUI still shows old name and does not show the scene I added manually. Did do a restart.
EDIT3: Added a new Scene through the Scene GUI. Links were successful. The GUI added scene is third in the list, where the manually added scene should have been (and was when looking at the scenes.xml file from the List File function). The second scene name in the scenes.xml file from the List File function no longer has the extra character I added on the end of the scene name and the GUI added Scene is third in the file. The Upload File function puts the scenes.xml somewhere where it will be retrieved by the List File function but does not update what EZSrve is using during its execution. Manual changes to the scenes.xml are not visible during EZSrve GUI functions and GUI updates to the scene list is done against the original (non manually modified version) and eliminates access to the manually modified version by the List File function.
Summary: Upload File brings in the new scenes.xml file but does not make it accessible to EZSrve runtime, even with a Restart. EZSrve runtime continues to operate against the old scenes.xml file, applying any runtime GUI changes to the original scenes.xml file. I’m done.