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.