UI5 Issues - Revision history

Henk at 09:45, 18 September 2011

2011-09-18T09:45:50Z

Mcv.mirela: /* strangely */

2011-09-06T12:48:06Z

‎strangely

OTi: Added comments.

2011-09-02T12:18:20Z

Added comments.

OTi: Added comments.

2011-09-02T12:10:29Z

Added comments.

Micasaverde at 07:03, 31 August 2011

2011-08-31T07:03:44Z

Micasaverde at 07:00, 31 August 2011

2011-08-31T07:00:34Z

Micasaverde: /* strangely */

2011-08-31T06:38:03Z

‎strangely

Micasaverde: /* oTi@ */

2011-08-31T06:25:47Z

‎oTi@

Micasaverde at 01:49, 31 August 2011

2011-08-31T01:49:18Z

Micasaverde at 23:18, 30 August 2011

2011-08-30T23:18:01Z

← Older revision		Revision as of 09:45, 18 September 2011
Line 1:		Line 1:
		+	[[Category:UI5]]
		+
	=== Problems reported ===		=== Problems reported ===

@@ Line 29: / Line 29: @@
 ==strangely==
-. You shouldn't have to click the wrench to view a camera.
+. <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
@@ Line 58: / Line 58: @@
 <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
-. 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?
+. <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

@@ Line 158: / Line 158: @@
 . Can the sort order of stuff be changed? <br>vali: mantis http://bugs.micasaverde.com/view.php?id=1684
-. 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.
+. 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>
 . 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.

@@ Line 5: / Line 5: @@
 . 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
-. 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.
+. 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>
 . It looks like some of my scenes didn't carry over properly. (Dimmer settings lost.)
@@ Line 21: / Line 22: @@
 . 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.
-. 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
+. 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>
 . 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

@@ Line 215: / Line 215: @@
 |- style="background:#00C000; color:black;"
 |Resolved
 |-
 |}

← Older revision		Revision as of 07:00, 31 August 2011
Line 209:		Line 209:
	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		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		<br>vali: to be discuss for new graphics
		+
		+	{\| class=sortable border="0"
		+	!style="background:lightgrey;" \| LEGEND
		+
		+	\|- style="background:#00C000; color:black;"
		+	\|Resolved
		+	\|-
		+	\|}

@@ Line 35: / Line 35: @@
 <br>vali: to be discuss
-. Notification scenes are now showing up
+<span style="background:#00C000">27. Notification scenes are now showing up
-<br>vali: mantis http://bugs.micasaverde.com/view.php?id=1690
+<br>vali: mantis http://bugs.micasaverde.com/view.php?id=1690</span>
 . Where are you supposed to set notifications?
@@ Line 44: / Line 44: @@
 <br>vali: mantis http://bugs.micasaverde.com/view.php?id=1701
-. Scenes that involved the old advanced tab in UI4 don't seem to be editable or viewable anymore?
+<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
+<br>vali: mantis http://bugs.micasaverde.com/view.php?id=1691</span>
 . Standard scenes don't seem to editable either

@@ Line 11: / Line 11: @@
 . 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
-. 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 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>
 . Dimmers will show the percentages, right? (Especially useful when setting a scene.) <br>vali: yes

@@ Line 82: / Line 82: @@
 ==Henk==
 . USB logs are wiped ( but that also happened on UI4 upgrades)
@@ Line 90: / Line 88: @@
 . 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
 . 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
@@ Line 104: / Line 99: @@
 . 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
 .. My camera plugin did not show snapshot (had that on UI4 for a while too)
@@ Line 142: / Line 134: @@
 . 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
-. trash bins for devices and for scenes are at different positions - absolutely unacceptable!
-<br>vali: to be discuss for new graphics
-−
-. auto-layout should use fixed width/height for device boxes
-<br>vali: to be discuss for new graphics
-−
-. 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
 . motion sensors and smoke sensors are "Other" devices
@@ Line 178: / Line 162: @@
 . 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
 === Cosmetic ===
@@ Line 210: / Line 197: @@
 . I guess the energy monitory will come shortly? <br>vali: yes

@@ Line 1: / Line 1: @@
 === Problems reported ===
 == oTi@  ==
@@ Line 5: / Line 6: @@
 . 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.
 . It looks like some of my scenes didn't carry over properly. (Dimmer settings lost.)
@@ Line 15: / Line 12: @@
 . 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
 . Dimmers will show the percentages, right? (Especially useful when setting a scene.) <br>vali: yes
 . (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
@@ Line 45: / Line 26: @@
 ==strangely==
 . You shouldn't have to click the wrench to view a camera.
@@ Line 77: / Line 52: @@
 . 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
 . Sensors do not visually show if tripped or not
@@ Line 96: / Line 68: @@
 . Notification of command sent does not clear <br>vali: mantis http://bugs.micasaverde.com/view.php?id=1700
 . 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
@@ Line 205: / Line 165: @@
 . GUI calendar has some interesting dates, e.g. 2011/11/31 ...