View source for UI5 Issues

[[Category:UI5]]

=== Problems reported ===

== oTi@  ==

1. The upgrade wiped out the logs on the USB stick. <br>vali: mantis http://bugs.micasaverde.com/view.php?id=1699 assigned to it_team 

2. MiOS routing may have been automatically enabled? I'd have to downgrade to make sure it wasn't already automagically enabled before the upgrade.<br> aaron:This shouldn't have happened. We'll check the logs.<br>
''oTi@: turned out MiOS routing was already enabled before the upgrade; so not an upgrade issue.''

5. It looks like some of my scenes didn't carry over properly. (Dimmer settings lost.) 

6. When I tried to edit the scene remotely through cp.mios, I got a message saying: 'You are not allowed to save the settings on this system'. <br>vali: you were probably connected as a guest, in UI5 only administrators are allowed to save

<span style="background:#00C000">7. Switched to VPN and edited the scene; let me save it, but it doesn't look like it actually saved. <br>vali: http://bugs.micasaverde.com/view.php?id=1694</span> 

14. Dimmers will show the percentages, right? (Especially useful when setting a scene.) <br>vali: yes 

17. (repeat) Devices &gt; Sensor tab would be nice; somewhere towards the left. Motion/3-in-1/Door-Window stuff now shows up all the way to the right under Other. I imagine many folks may have some of these. <br>vali: mantis http://bugs.micasaverde.com/view.php?id=1698 

18. What's Devices &gt; Mobile Phones? 

19. Events/Timers get names. Given the various times it has come up on the forum, it seems intuitive for folks that you can then later refer to these events/timers and not have to define them again. I.e. defining 'Kitchen Motion Sensor Tripped' and 'Wednesday at 5pm' once. This probably has some UI design impact; but well, this is a new major version. 

20. SQRemote rejects version 1.5.56. That should probably be mentioned somewhere (or made compatible by SquareConnect) upon public release. <br>vali: scenes syntax is different, the other stuff should work<br>
''oTi@: ok, but when are changes communicated to CP developers? It would be nice if they could upgrade their apps before public release of UI5, and/or there should be an item in the UI5 release notes that warns the user. It's not fun for users to upgrade to UI5 and then have SQRemote not work.''

21. When adding a device it is now not quite clear where to look for it / see what's going on. It'll show up as Other for a bit and then jump to whatever tab is appropriate, once Vera has configured it. Likely to confuse folks? (Example: add a relay; shows up in Other; than jumps to Lights.) <br>vali: we may have another tab in devices for Un-configured devices and have all the other tabs to show only devices which are configured (e.g. working devices); to be discuss

==strangely==

24. <span style="background:#00C000"> You shouldn't have to click the wrench to view a camera.
<br>vali: camera devices should have buttons to view and achive

25. Still no conditional expressions.

26. There should be another tab next to pinned devices in the dashboard that allows you to see all devices on one page without pinning.
<br>vali: to be discuss

<span style="background:#00C000">27. Notification scenes are now showing up
<br>vali: mantis http://bugs.micasaverde.com/view.php?id=1690</span>

28. Where are you supposed to set notifications?
<br>vali: as always, in control panel of the device, click on notifications

29. When trying to edit a scene that involves my alarm plugin, there is no panel or partition device available under any of the category tabs
<br>vali: mantis http://bugs.micasaverde.com/view.php?id=1701

<span style="background:#00C000">30. Scenes that involved the old advanced tab in UI4 don't seem to be editable or viewable anymore?
<br>vali: mantis http://bugs.micasaverde.com/view.php?id=1691</span>

31. Standard scenes don't seem to editable either
<br>vali: possible conversion failure, trouble ticket needed to investigate

32. There doesn't seem to be any way to see what the existing timers are? I'm not talking about scheduled timers, but more things like "after 2 hours turn off etc" which I've found out dont seem to work after migrating anyway.
<br>vali: friendly description for timers is very difficult due localization, since the wording is different in other languages than English 

34. Sensors do not visually show if tripped or not
<br>vali: mantis http://bugs.micasaverde.com/view.php?id=1702, Aaron please comment on it since Alexus team said design is made with static icons

35. <span style="background:#00C000"> What is the purpose of the small arrow highlighted in my attached picture, and why do some devices have these only on the bypass button only?
<br>vali: it's "restore to previous settings" button, and should not appear for both controls, mantis http://bugs.micasaverde.com/view.php?id=1703

== garretwp ==

36. Thermostat: shows my temperatures in C and not in F. <br>vali: mantis http://bugs.micasaverde.com/view.php?id=1704 

37. Thermostat: does not show the current temp. <br>vali: mantis http://bugs.micasaverde.com/view.php?id=1705 

38. Thermostat: fan mode still not working. 

39. Notification of command sent does not clear <br>vali: mantis http://bugs.micasaverde.com/view.php?id=1700 

46. oTi@ reported not all scenes carried over properly. I can also state the same. Especially the scenes that involve dimmers. This also goes for thermostats as well 

47. Edit a scene that involves a dimmer and having the level set in the scene does not get saved. <br>vali: mantis http://bugs.micasaverde.com/view.php?id=1547 

mirela: mantis&nbsp;[http://bugs.micasaverde.com/view.php?id=1724 http://bugs.micasaverde.com/view.php?id=1724]

48. Schedules in the automation section should show the scene name that belongs to that schedule. I have similar schedule names for different scenes (e.g. wed). And looking at the schedule section shows a ton of wed names, but have no clue what scene owns that schedule. <br>vali: click on wrench next to schedule/trigger go to edit schedule/trigger, no need to know the scene name, but in any case I added mantis http://bugs.micasaverde.com/view.php?id=1707 

49. Formatting is messed up in the schedules section with having long names or long description. See attached image <br>vali: mantis http://bugs.micasaverde.com/view.php?id=1708 

50. Creating Scene to adjust my thermostat to a certain temperature does not save the temperature value. <br>vali: mantis http://bugs.micasaverde.com/view.php?id=1709

==Henk==

52. USB logs are wiped ( but that also happened on UI4 upgrades)
<br>vali: see #1

53. i had some issues when removing a scene (bin didnt work) that were solved after a CTRL F5
<br>vali: we'll try to reproduce

55. My SM103 doorsensor does not show up in climate& security but in "other devices" where most custom plugins reside. In fact, why is there not a 
secion for "Motorized control"  to sort window coverings etc in?
<br>vali: see #17

56. Pinned scenes do not "stick" even after saves. the show up unpinned after a refresh.
<br>vali: we'll try to reproduce
i LOVE the breakout of scenes triggers and schedules. It made me aware that i had not named a few of them at all.

57. The button under create/save is merely invisible and therefore unreadable. After clicking the edge that WAS visible, i found out it was a "return home button"  ?
<br>vali: it's "restore to previous settings" actually; to be discuss usability in this section

59.. My camera plugin did not show snapshot (had that on UI4 for a while too)
Worse, also streaming was broken (worked flawlessly on UI4).
I decided to remove the plugin completely and build it from scratch. Will report my findings later!

60. Hide / autocollapse emtpy rooms from any view as to not confuse users and claim more realastate for important info.
<br>vali: to be discuss

61. Apps/plugins installed under UI4 that get migrated to UI5 do not show version number. Workaround is to remove the plugin/app and reinstall it in UI5 using the new APPS section

62. am having trouble with luup code in events.  the same luupcode for a binary light switch works. 1 binary Duewi light switch
send notification via Prowl when lights go OFF notification works when lights shut OFF.,  1 FCM luup plugin (works)
Scene to pickup events from the plugin  (LUUP) Event for the scene coded to send notification via prowl (same code as before and similar to the luup event for the binary switch, worked under UI4).

63. Notification does not work!
<br>vali: new servers issue

64.   1. Missing and corrupted scenes after migration, 2. LUUP code not working anymore after migration although the code itself is intact (luup events), 3. I have seen information from one plugin depicted in another (weather depicting FCM caller data), 4. I have noticed scenes to pop up unexpected and ive had scenes that were hard to delete, only refreshing, reloading and trying time after time made it work., 5. Pinning of scenes doesnt work (after a save and reload they are gone from the pinning list.
<br>vali: issue 64.4 working to reproduce, 64.5 mantis http://bugs.micasaverde.com/view.php?id=1688

65. Vera started acting up, she switched my binary plugin module off time after time when i switched it on manually at the device, using the device ON/OFF button.
<br>vali: any timer/event setup on it?

==mario23==

66. all scene settings didn't make it over. Also, how do I now set a scene conditions like before. Example, Turn dimmer to 50% for two hours then down to 20%???
<br>vali: add command to turn dimmer to 50%, type 120 next to "Add commands to be run" and click Add, add command to set dimmer to 20%. Need to add help pages for scenes editor

67. Saving settings in some scenes aren't working for me.
<br>vali: same as #47 I assume

==Ap15e==

68. Archive old logs: might have been activated by upgrade to UI5
<br>vali: this is activated by default in ui4 too
<br>aaron: but an upgrade with preserve settings should keep the old settings

72. motion sensors and smoke sensors are "Other" devices
<br>mirela: http://bugs.micasaverde.com/view.php?id=1698

73. Help is empty
<br>vali: we're working on it

74. Control Panels for all devices auto-close after less than a second
<br>vali: trying to reproduce

75. Add Devices -> most of the Add buttons don't work
<br>vali: need more details

76. GUI calendar has some interesting dates, e.g. 2011/11/31 ...

=== Feature requests ===

3. No more sections? 

4. Can the sort order of stuff be changed? <br>vali: mantis http://bugs.micasaverde.com/view.php?id=1684 

15. I would love for the 'On' button on a dimmer to cause the dimmer to go the last setting, rather than full on, or some way at least to tell a dimmer to go the last setting. I've been missing this (and wrote a bug on it) a lot. (Currently working around it with a low-level basic set 255, followed by a poll.) <br>vali: if we add a new upnp variable for last setting, we can also add a new button for dimmers.<br>
''oTi@: The proposal is for the dimmer itself to go back to its last setting, as Vera may not have the last setting (depending on device features, polling, etc.). So just have Vera send a level 255 (instead of 100), just like (motion) sensors typically do by default. (E.g. my making the level for the On button user-configurable in Vera.)''

33. Lights should be labeled lights and appliances, and if it's not possible to distinguish between these then the picture of a bulb should be editable.
<br>vali: to be discuss

44. The idea of hitting the on button and having the dimmer go back to last state would be nice. (I am going to add that idea into my android application!) <br>vali: see #15 

58. In devices i miss an ALL devices tab
<br>vali: same as #26, to be discuss

=== Cosmetic ===

8. Prefer a clock with seconds (or switchable on/off) and all digits the same size. <br>vali: seconds won't be added because they may flip when the clock is resyncronized with the unit, for size mantis http://bugs.micasaverde.com/view.php?id=1697 

9. I'd move the username over to the left, and remove the permanent 'Welcome:'. <br>vali: to be discuss 

10. A quick 'info' button to pull up firmware versions (Vera and Z-Wave), IP, PRI status, etc. would be nice. <br>vali: to be discuss 

11. Would like to be able to make the status window bigger and perhaps it can float, so all messages fit. It's an important window. <br>vali: to be discuss, it can be different under new graphics 

12. Will wait for the new graphics, etc., but I still see a lot of 'dead' space, boxes are big, etc. <br>vali: same as #11 

13. The way stuff gets laid out on the screen seems unnatural, because dimmers are bigger than switches (i.e. it's not always left-aligned). <br>vali: same as #11 

16. Minimize the number of different font types. Probably just pick one for a consistent look and feel. <br>vali: same as #11 

22. The turquoise and orange really don't work well with the rest of the colours.
<br>vali: to be discuss if still apply in new graphics

23. Why is there still an annoying pop up when activating a scene?
<br>vali: mantis http://bugs.micasaverde.com/view.php?id=1700

40. The status window should be wider. There is all that space up top. Why not either get rid of the extra space or use it for the status window. That would allow us not have to scroll in the window. <br>vali: to be discuss for new graphics 

41. Yes, graphics are missing and will have to wait when they get finished and packed into the next firmware. 

42. The devices boxes should all be the same size and the alignments do get messed up. Attached image. <br>vali: reported in mantis http://bugs.micasaverde.com/view.php?id=1581 but resolves as "by design". Please reopen and comment 

43. Text in the devices that show information is too close to the veritical bar, it should be larger and darker in color. <br>vali: mantis http://bugs.micasaverde.com/view.php?id=1706 

45. I guess the energy monitory will come shortly? <br>vali: yes

54. There are some parts of the menu that seem " unfinished" as in the text is black (default?) and not in line with the overal theme. This occurs especially in the settings tab.
<br>vali: mantis http://bugs.micasaverde.com/view.php?id=1710

69. trash bins for devices and for scenes are at different positions - absolutely unacceptable!
<br>vali: to be discuss for new graphics

70. auto-layout should use fixed width/height for device boxes 
<br>vali: to be discuss for new graphics

71. device boxes are too large, current layout is unusable if there are > 10 devices, scene boxes are too large, current layout is unusable if there are > 15 scenes
<br>vali: to be discuss for new graphics

{| class=sortable border="0"
!style="background:lightgrey;"            | LEGEND

|- style="background:#00C000; color:black;" 
|Resolved
|-
|- style="background:#B0C4DE; color:black;" 
|Not an issue
|-
|- style="background:#F0E68C; color:black;" 
|To discuss
|-
|- style="background:#FFA07A; color:black;" 
|Unable to reproduce
|-
|}