Folks,
I dug through a ton of posts on this message board trying to find the answer to this but was unsuccessful - hopefully somebody or Ultra Jones can help.
I use to run Ultra View2 long ago but then I let it die as I was beta testing HomeSeer during the change over to XML for the config file. Now that it is all settled, I went to get Ultra View 2 going again and have run into a problem.
Floor plans, laying out devices, etc. is not a problem. When I access the ASP page, it draws my floorplan and then says that it is refreshing, it launches ultra_view2_xml.vbs and then that is it - goodnight HomeSeer - HomeSeer becomes unresponsive and never comes back. e.g. UltraLockup. ;-)
I know it used to have problems with virtual devices that have HTML in them, degree symbols, etc. but I thought that most of those issues were resolved. Am I wrong? Why would it start locking up HomeSeer instead of just erroring out?
Anyway, help would be appreciated - my wife would sure like UltraView going again.
Rick
I dug through a ton of posts on this message board trying to find the answer to this but was unsuccessful - hopefully somebody or Ultra Jones can help.
I use to run Ultra View2 long ago but then I let it die as I was beta testing HomeSeer during the change over to XML for the config file. Now that it is all settled, I went to get Ultra View 2 going again and have run into a problem.
Floor plans, laying out devices, etc. is not a problem. When I access the ASP page, it draws my floorplan and then says that it is refreshing, it launches ultra_view2_xml.vbs and then that is it - goodnight HomeSeer - HomeSeer becomes unresponsive and never comes back. e.g. UltraLockup. ;-)
I know it used to have problems with virtual devices that have HTML in them, degree symbols, etc. but I thought that most of those issues were resolved. Am I wrong? Why would it start locking up HomeSeer instead of just erroring out?
Anyway, help would be appreciated - my wife would sure like UltraView going again.
Rick
Comment