@jkandasa
I see this thread is quite old, nevertheless I'd like to share my thoughts after having played with MyController 1.5 snapshot for a while. As a almost non-programmer, quick changes in GUI or implementation of own scripts is a major hurdle. I have fun in designing the sensor nodes, tweaking the PCBs even further (I may publish the result at openhardware.io one day!). Regarding the controller GUI, the so-called WAF is not to be underestimated. I need expressed acceptance of my wife to install some funny electronics device in our living room. And I only get approval, if the look&feel is most easy and convenient and if the device is useful and non-obtrusive. I see many very convenient setup and configuration options in MyController, but I regret to say there are also some drawbacks with the current version that make me hope for a version 2 one day. I would be more than happy if I could find that one or another of these drawbacks were solved at a later date.

1. Changes in layout are almost impossible.
I found the *.css file and could vary font sizes for sensor display values, but this is extremely troublesome, as the *.css file is not structured. I helped myself with the browser's debugger and tried to find the relevant locations in the *.css file and was partly successful - but this is no method that I can carry out after every version step you may publish.
Why do I need this? I want a nice display in my living room. Not everything is formatted in a way I need it. For example, outside temperature display should be as big as possible. Sunrise/Sunset maybe medium size, whereas I pretty well know the name of my village, so that I'd be fine with 6 pt

2. No information on aged or non-available data
This has been posted before. If a sensor fails, the last reading will always remain displayed. This gives a false feeling of confidence. For example, temperature changes in my deep freeze should be actual, or I wouldn't need a supervision at all. A greyed-out display or a simple "n/a" would do very well.

3. Some browsers cannot process the active contents
I reported this for my old iPad 2 (which is a excellent choice as it consumes a mere 3 watts, which is less than a Raspi Zero W plus a DIY TFT). I found a workaround, but on account of flexibility.

4. Dashboard logs me out after three days
This is a no-go for a stationary display. I cannot go there every third day and type in my account/password.

5. Battery status beside sensor reading
Well, this may be more sort of a luxus item, but if I have a "show only" display without touch ability and only one screen that should fit all purpose, the battery percentage value in a (configurable) small font would help to check the status by just having a closer look.

@jkandasa
If you ask whether I have included my own scripts: No.
It is just a "virgin install" without any customizations.
The four fields displayed in the GUI under Utilities- HTML additional headersare all empty.

Edit: Oh, and if some testing on old hardware should be required, no problem! I will be happy to try things out. The only limiting factor might be my little to non-existing programming skills

@Tag @jkandasa
I have done a bit fault finding and want to share my results with you.

First, the issue you mentioned in which two lines were calling the same script did not apply in my case. So I looked further.

When I connect an iPad 2 or iPad 3 (=iOS 9) the page does not load properly. The behaviour is independent of whether I am running Safari, Edge, iCab or Firefox. I see only the view as above (which is the same view that one gets when index.html is loaded without the web server running). So my guess was that processing the code of the page did not complete properly.

I hooked the old iPad via "Developer Options" to desktop Safari and looked at the debugger.

With iOS9 I get an error in ../www/_configurations/additional.js, line 8: Unexpected Identifier aModules.
If I watch the expression "aModules", it says aModules: [Exception: ReferenceError: Can't find variable: aModules]

With actual iOS 12 I don't get this error message, the page loads perfectly. The value is then aModules=[0].
So it is somehow client-dependent.

From the comment "...is automatically generated..." in file "additional.js" I concluded by means of a full text search that the file additional.js is generated by the source text file SettingsUtils.java.

As the folder ../www/_configurations with all files inside (among them additional.js) is created on every server start, I cirumvented this problem temporarily by overwriting the freshly generated additional.js with a backup version that comments out most of the code (=all between line 8 and 24) and which adds the desired result aWorkingModules=[]; before the last line angular.resumeBootstrap(aWorkingModules); is called. Of course this procedure will not allow me to include my own scripts later, but I can at least use an iPad 2 to display the GUI for the time being.

To me it looks as if older iOS cannot properly deal with the variable aModules. Newer versions seem to assume an empty string, while older iOS versions throw an error, which prevents the page from loading correctly.

I kindly ask whether there is a way to prevent this error from occurring in later versions of MyController.

Kind regards, Matt.

@jkandasa Hello and first of all many thanks for this great work! I am setting up a sensor network in my home based on MySensors and find this project the best compared to FHEM, OpenHAB, Home Assistant (which I all tried out...).

I have the same problem when I call the GUI. But it occurs to me only on an old iPad 3, which I wanted to use as public display. The installation of "1.4 final" from your download section and also the iPad were set up from scratch. The problem persists after restarting the server and clearing all Safari settings. On other browsers (actual Chrome, Safari, mobile Safari) the display is OK. Side note: I have not yet installed a certificate for https, but I don't know if this is important.