I was wondering if anyone had started a list of known issues upgrading to UI5? I’ve held off knowing that their would be some bugs but it would be great to see a check list of some sort for bugs that have been resolved (and possibly what those fixes are) and those still waiting to be resolved.
The bug list started many months ago, but I doubt you will ever see a compiled working one.
You could use Mantis for the publically reported issues? Bear in mind, what you see based on being logged in or not will differ.
http://bugs.micasaverde.com/view_all_bug_page.php
JOD.
is it possible to schedule devices to turn on and off based on sunrise sunset with the new ui5?
Yes, you can. This has always been a feature in previous UI versions.
- Garrett
Is anyone else having a problem with the smartphone interface on UI5?
I tried uninstalling and re-installing the app/plugin. Didn’t seem to help.
Update: In case anyone has the same problem an upgrade to the latest UI5 fixed things. I must have been caught up the floating point precision bug.
Am I missing something… what is the link and/or procedure for upgrading to UI5? I would have thought that MCV would be announcing that VERA3’s are being shipped and that UI5 upgrade is available but instead ping no echo!! Never mind found the link… pray tell why isn’t this in the forum under Blog or new releases?
[quote=“radarengineer, post:6, topic:169745”]About five hours ago on Micasaverde’s Facebook page (Redirecting...) this was posted:
Vera2 owners, upgrade to UI5 here - http://cp.mios.com/firmware! Enjoy[/quote]
Ok, I’ve updated to UI5, the GUI takes some getting use to… :
I seem to have a problem Houston!!! when ever I select any z-wave device I get the message “ZWave not ready”, my camera’s seem to work along with my “other” devices such as “Luup System Information”.
I attempted to conduct a Heal under the “Z-Wave Settings”“Repair” option, I get the following message “Command failed ZWave not ready”. When I look at my status (top of screen) I see that “Z-WAVE: Starting Z-wave Network”. HELP!!! 
Version 3.20 L:1
House/Node
Role Suc SIS:YES PRI:YES
Last update N/A
Last dongle backup N/A
Port
By default MiOS should automatically configure devices
X Use Z-Wave version 3.20 instead of 2.78 IMPORTANT: Read this first
X Use MiOS routing instead of Z-Wave (requires 4.5)
X Limit neighbors to Z-Wave discovery (requries MiOS routing)
X Poll nodes learn more
Number of seconds to wait to start polling 20
Only poll a node if the Z-Wave network is idle at least seconds. 10
Poll a node every seconds. 60
Unless specified otherwise, poll each node at most once every seconds. 30
Version 3.20 L:1 Role Suc SIS:YES PRI:YESI think the issue is the above. 3.20 does not support Suc SIS. I'm guessing the conversion is not 100% complete yet?
JOD.
@MNB - Is the Zwave port set? in your copy it doesn’t show. It should be /dev/ttyS0
What I’ve observed, thus far, on UI5 (1.5.233)/Vera2:
[ul][li]Enough leaking memory to cause LUA restarts every 3(ish) hours.[/li]
[li]A number of 3rd party plugins do not work (DAD, Ping Sensor)[/li]
[li] Ping Sensor plugin causes perma-restart of the Luup engine, which in turns causes the UI to be non-functional[/li]
[li]call_delay() does not return the expected 0 value when successful (I get NAN when “tostring()”'ing the result of successfully calling the function)[/li]
[li]luup.devices array is impacted by the bug referrenced by @mcvflorin (which has been fixed but the fix is not yet available to “us” mere mortals 
They expect a release sometime soon though!)[/li][/ul]
Edit: And I just realized the light sensor on my EZmotion 3-in-1 appears to be non-functional. Not sure (yet) if that is due to the UI5 upgrade or it just decided to die on me (the 3-in-1 is mounted outdoors so can be a little flakey :))
Another Edit: Also, the app installation page/routine insists on removing a plugin/app from the “My Apps” page whenever a single instance of the app is removed (regardless of how many instances I am using. This will be an issue for things like the ping sensor, for instance). I’m also noticing that two-finger scrolling (the equivalent of the “scroll wheel” on a mouse?) gestures on my macbook pro w/Chrome doesn’t work. (Does UI5 trap scroll-wheel signals & discard/use them for something else?)
I have noticed that I only get email notifications now for triggers. Text messaging does not seem to work at all (I am on Verizon). I have tried removing my information from the User area, saving it, and then adding it back to no avail.
Also, where is the remote control functionality? It used to be on the Remote tab of a scene, which does not exist in UI5 and did not work in UI4. Has it been removed, or does it now become an option on the control pad of a device that is associated with an IR port?
There needs to be some official documentation on what’s changed in UI5.
@sjolshagen: "Edit: And I just realized the light sensor on my EZmotion 3-in-1 appears to be non-functional. Not sure (yet) if that is due to the UI5 upgrade or it just decided to die on me (the 3-in-1 is mounted outdoors so can be a little flakey "
I have been on build 5.1.213 now for a couple of weeks and I have the same problem. Motion sensor works as before, but temperature and light do not report back correctly. I had to remove the dependency I have on that info from a lot of scripts for the time being and make hour of day dependent. What version of the firmware do you have?
From the sounds of it, an MCV/Mios bug wrap-up would be nice.
After upgrading to v1.5.236, things have changed a little (see strikeouts)
[ul][li]Battery level indicator for my PIR sensors (Intermatic & ZIR000) appear to be borked after upgrading to 1.5.236[/li]
[li]Battery level indicator for my Everspring temp/humidity sensor is borked after upgrading to 1.5.236[/li][/ul]
[quote=“sjolshagen, post:10, topic:169782”]What I’ve observed, thus far, on UI5 (1.5.233)/Vera2:
[ul][li]Enough leaking memory to cause LUA restarts every 3(ish) hours. [/li]
[li]A number of 3rd party plugins do not work (ADD, DAD, Ping Sensor)[/li]
[li]Ping Sensor plugin causes perma-restart of the Luup engine, which in turns causes the UI to be non-functional[/li]
[li]call_delay() does not return the expected 0 value when successful (I get NAN when “tostring()”'ing the result of successfully calling the function)[/li]
[li]luup.devices array is impacted by the bug referrenced by @mcvflorin (which has been fixed but the fix is not yet available to “us” mere mortals They expect a release sometime soon though!)[/li][/ul]
Edit: And I just realized the light sensor on my EZmotion 3-in-1 appears to be non-functional. Not sure (yet) if that is due to the UI5 upgrade or it just decided to die on me (the 3-in-1 is mounted outdoors so can be a little flakey :))
Another Edit: Also, the app installation page/routine insists on removing a plugin/app from the “My Apps” page whenever a single instance of the app is removed (regardless of how many instances I am using. This will be an issue for things like the ping sensor, for instance). I’m also noticing that two-finger scrolling (the equivalent of the “scroll wheel” on a mouse?) gestures on my macbook pro w/Chrome doesn’t work. (Does UI5 trap scroll-wheel signals & discard/use them for something else?)[/quote]
@wseverion, I believe your indicating that it should be “/dev/tts/0”, mine was set to 1 vs 0 what is the difference? I changed it to 0 but still end up with “ZWAVE: Starting ZWave Network” followed with “Server Busy.” cycling several times and then end up with “ZWAVE: No ZWave Dongle” I’m still dead in the water, I open a ticket for support. Mike
[quote=“MNB, post:14, topic:169782”]@wseverino, I believe your indicating that it should be “/dev/tts/0”, mine was set to 1 vs 0 what is the difference? I changed it to 0 but still end up with “ZWAVE: Starting ZWave Network” followed with “Server Busy.” cycling several times and then end up with “ZWAVE: No ZWave Dongle” I’m still dead in the water, I open a ticket for support. Mike
@MNB,
In UI4, on Vera2 HW, the built-in Z-Wave had an IO address like:
[tt] /dev/tts/1[/tt]
In UI5, on Vera3 HW, the built in Z-Wave has an IO address like:
[tt] /dev/ttyS0[/tt]
different format in each case, not just a difference in “0” or “1” suffix. From the descriptions above, it sounds like a Vera2 → Vera3 cross-grade/restore may bring forward this setting for some reason.
On Vera 2, regardless of the UI version, the Z-Wave port must be: /dev/tts/1. On Vera 3 it must be /dev/ttyS0.
Ap15e’s plugins haven’t been updated to be compatible with UI5. Some work and some don’t.
[tt]http://forum.micasaverde.com/index.php/topic,8643.msg55823.html#msg55823[/tt]
[tt]http://forum.micasaverde.com/index.php/topic,8665.0.html[/tt]
Yes, I realized that. But it’s an incompatibility none the less and I thought it prudent to highlight (again) in this post
I upgraded to the latest UI5 and I’ve ran into an issue with editing a scene. After I edit the scene and save the changes, If I try to run the scene it keeps telling me “This scene was changed the changes are not saved yet. Please save first then you can execute the scene.” even though I already saved it. I’ve even rebooted the system.