@stuartofmt Yeah that's kind of the logic I use but there's a chicken and egg thing going on because you have to find a config file before you can get the settings out of it but you have to have some settings already to know where to look.
I think I have it working now but I'm going to wait until tomorrow and test it again before doing a beta3.
I obviously got side-tracked with polling not being "On" and the non-error error messages.
I went back to the nginx setup on the raspberry pi and "ta-da"
Of course there is always cookies ... and why it would not remember the configuration.
My default browser settings are to delete cookies on exit .... when I realized, I added an exception for localhost. So all is well.
This is a terrific piece of work ! Because the Touch Screen on the Pi (7") is "real estate challenged" and struggles with the example, default layout - I will need to work on my own, config. In any case, I want to make it quite minimal since my intention is just to have an essential "next to printer" experience.
When I have something reasonable - I'll post it in the appropriate discussion.
@hauschka Sure! The website that serves the UI, the website that serves the config file, and the Duet itself can all be configured separately.
The website that serves the UI is the URL you enter in the browser's address window. The website that serves the config file is configured in DueUI's Settings page under "DueUI config file URL". The address of the Duet itself (or the RPi/SBC) is configures in DueUI's Settings page under "Duet hostname or IP address:" or "SBCt hostname or IP address:" depending on whether you're directly connecting to the Duet or the SBC.
So you can certainly have the UI and config file served from the same web server. The path to the config file auto populates with a default if its empty but you can change that and it will be saved.