[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: Homeseer 3
--Apple-Mail-7ACD33F3-5E97-4BB7-87F6-F1B1E6A47ABC
Content-Type: text/plain;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
My honest advice? Steer clear.
First off, although it's being sold as a finished product, with no mention
=
of a beta, I have been assured by those on the forums that it IS still in
b=
eta. I have a very simple setup, with just a few X10, Z-wave and RFXCom
dev=
ices.=20
None of your devices will be imported. They have apparently changed the
ver=
y core of how devices are addresses and it basically means all devices
apar=
t from those that vpcan be imported from devices, like zwave, will need to
=
be manually created. Even the zwave ones need manual intervention to get
wo=
rking. I basically had to create all mine manually.
This leads to the next issue. It's buggy as hell. Very often codes are
lost=
whilst saving new devices. Locations are randomly removed. Basically every=
time you save/modify a device, you will loose some of it's info. You'll th=
en find when you restart it, duplicate devices are made and are next to
imp=
ossible to get rid of. I've had major issues getting X10 to work, and when
=
it finally did, the x10 interface would crash then be unable to reopen
auto=
matically and just sit there. This resulting in me having to reboot the
who=
le PC, 3 or 4 times a day.=20
The interface is a major bugbear. It's ugly as hell and a real step back.
W=
hen devices all over the tech world are coming onto market with slick
fluid=
interfaces as default, Homeseers is ugly, clunky, and complex. Oh, and bug=
gy.=20
Homeseer are in real danger of being left behind (for want of a
competitor)=
. They need to take more responsibility for its interface and function, ra=
ther than leaving it to tinkerers. I expected a slick new product.. What I
=
got was a box of bolts As an avid, long term Homeseer user, I bought in
fa=
ith and trust I would be getting a good product. They have destroyed that
t=
rust.=20
Ok, ok.. A little dramatic, but in this day and age with technology and
int=
erfaces becoming more and more advanced, I was hugely disappointed with
Hom=
eseer.
And no.. I'm not using it. It is, for want of a better word, unusable in
it=
s current form. HS2 may be dated, but at least it works. Feel free to ask
a=
ny questions.=20
Cheers
Marc
=20
Sent from my iPad
> On 16 Jan 2014, at 02:58, "Dave McLaughlin"
<dave@xxxxxxx>=
wrote:
>=20
> Anyone here upgraded to Homeseer 3?
>=20
>=20=20
>=20
> They have a special offer just now to upgrade to it from HS2 for $99
and =
I am tempted but I want to know if there are going to be issues with
import=
ing my existing HS2 setup?
>=20
>=20=20
>=20
> I run a custom app that talks to HS2 over TCP using HS Speaker. I have
a =
feeling this will not work anymore once I upgrade.
>=20
>=20=20
>=20
> As for the rest, I just use HS Touch and it should be OK.
>=20
>=20=20
>=20
> Regards
>=20
> Dave
>=20
>=20=20
>=20
>=20
--Apple-Mail-7ACD33F3-5E97-4BB7-87F6-F1B1E6A47ABC
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<head>
<style type="text/css">
<!--
/* start of attachment style */
.ygrp-photo-title{
clear: both;
font-size: smaller;
height: 15px;
overflow: hidden;
text-align: center;
width: 75px;
}
div.ygrp-photo{
background-position: center;
background-repeat: no-repeat;
background-color: white;
border: 1px solid black;
height: 62px;
width: 62px;
}
div.photo-title
a,
div.photo-title a:active,
div.photo-title a:hover,
div.photo-title a:visited {
text-decoration: none;
}
div.attach-table div.attach-row {
clear: both;
}
div.attach-table div.attach-row div {
float: left;
/* margin: 2px;*/
}
p {
clear: both;
padding: 15px 0 3px 0;
overflow: hidden;
}
div.ygrp-file {
width: 30px;
valign: middle;
}
div.attach-table div.attach-row div div a {
text-decoration: none;
}
div.attach-table div.attach-row div div span {
font-weight: normal;
}
div.ygrp-file-title {
font-weight: bold;
}
/* end of attachment style */
-->
</style>
</head>
<html><head><meta http-equiv="content-type"
content="text/html; charset=utf-8"></head><body
dir="auto">
<!-- **begin egp html banner** -->
<br><br>
<!-- **end egp html banner** -->
<div>My honest advice? Steer
clear.</div><div><br></div><div>First off,
although it's being sold as a finished product, with no mention of a beta,
I have been assured by those on the forums that it IS still in beta. I have
a very simple setup, with just a few X10, Z-wave and RFXCom
devices. </div><div><br></div><div>None
of your devices will be imported. They have apparently changed the very
core of how devices are addresses and it basically means all devices apart
from those that vpcan be imported from devices, like zwave, will need to be
manually created. Even the zwave ones need manual intervention to get
working. I basically had to create all mine
manually.</div><div><br></div><div>This leads
to the next issue. It's buggy as hell. Very often codes are lost whilst
saving new devices. Locations are randomly removed. Basically every time
you save/modify a device, you will loose some of it's info. You'll
then find when you restart it, duplicate devices are made and are n
ext to impossible to get rid of. I've had major issues getting X10 to work,
and when it finally did, the x10 interface would crash then be unable to
reopen automatically and just sit there. This resulting in me having to
reboot the whole PC, 3 or 4 times a
day. </div><div><br></div><div>The
interface is a major bugbear. It's ugly as hell and a real step back. When
devices all over the tech world are coming onto market with slick fluid
interfaces as default, Homeseers is ugly, clunky, and complex. Oh, and
buggy. </div><div><br></div><div>Homeseer
are in real danger of being left behind (for want of a competitor) . They
need to take more responsibility for its interface and function, rather
than leaving it to tinkerers. I expected a slick new product.. What I got
was a box of bolts As an avid, long term Homeseer user, I bought
in faith and trust I would be getting a good product. They have destroyed
that trust. &l
t;/div><div><br></div><div>Ok, ok.. A little d
ramatic, but in this day and age with technology and interfaces becoming
more and more advanced, I was hugely disappointed with
Homeseer.</div><div><br></div><div>And no..
I'm not using it. It is, for want of a better word, unusable in its current
form. HS2 may be dated, but at least it works. Feel free to ask any
questions. </div><div><br></div><div>Cheers</div><div><br></div><div>Marc</div><div><br></div><div> <br>Sent
from my iPad</div><div><br>On 16 Jan 2014, at 02:58,
"Dave McLaughlin" <<a href="mailto:dave@xxxxxxx";>dave@xxxxxxx</a>>
wrote:<br><br></div><blockquote
type="cite"><div>
<span style="display:none"> </span>
<div id="ygrp-text">
<p></p><div class="WordSection1"><p
class="MsoNormal"><span
style="font-size:10.0pt;">Anyone here upgraded to Homeseer
3?<o></o></span></p><p
class="MsoNormal"><span
style="font-size:10.0pt;"><o> </o></span></p><p
class="MsoNormal"><span
style="font-size:10.0pt;">They have a special offer just now
to upgrade to it from HS2 for $99 and I am tempted but I want to know if
there are going to be issues with importing my existing HS2
setup?<o></o></span></p><p
class="MsoNormal"><span
style="font-size:10.0pt;"><o> </o></span></p><p
class="MsoNormal"><span
style="font-size:10.0pt;">I run a custom app that talks to HS2
over TCP using HS Speaker. I have a feeling this will not work anymore once
I upgrade.<o>&l
t;/o></span></p><p
class="MsoNormal"><span
style="font-size:10.0pt;"><o> </o></span></p><p
class="MsoNormal"><span
style="font-size:10.0pt;">As for the rest, I just use HS Touch
and it should be OK.<o></o></span></p><p
class="MsoNormal"><span style="font-size:10.
0pt;"><o> </o></span></p><p
class="MsoNormal"><span
style="font-size:10.0pt;">Regards<o></o></span></p><p
class="MsoNormal"><span
style="font-size:10.0pt;">Dave<o></o></span></p><p
class="MsoNormal"><o> </o></p></div><p></p>
</div>
<!-- end group email -->
</div></blockquote>
<!-- **begin egp html banner** -->
<br>
<br>
<!-- **end egp html banner** -->
<div width="1" style="color: white; clear:
both;"/>__._,_.___</div>
<!-- Start Recommendations -->
<!-- End Recommendations -->
<!-- **begin egp html banner** -->
<br><br>
<tt>
<*> Join the Automated Home Forums<BR>
<a href="http://www.automatedhome.co.uk/vbulletin/";>http://www.automatedhome.co.uk/vbulletin/</a><BR>
<BR>
<*> UKHA_D Mailing list in association with:<BR>
<a href="http://www.automatedhome.co.uk";>http://www.automatedhome.co.uk</a><BR>
<BR>
<BR>
</tt>
<br><br>
<!-- **end egp html banner** -->
<!-- **begin egp html banner** -->
<img src="http://geo.yahoo.com/serv?s=97476590/grpId=1109639/grpspId=1705041992/msgId=164603/stime=1389859621";
width="1" height="1"> <br>
<!-- **end egp html banner** -->
<!-- **begin egp html banner** -->
<br>
<div style="font-family: verdana; font-size: 77%; border-top: 1px
solid #666; padding: 5px 0;" >
Your email settings: Individual EmailTraditional <br>
<a href="http://groups.yahoo.com/group/ukha_d/join;_ylc=X3oDMTJmZzlrbHJrBF9TAzk3NDc2NTkwBGdycElkAzExMDk2MzkEZ3Jwc3BJZAMxNzA1MDQxOTkyBHNlYwNmdHIEc2xrA3N0bmdzBHN0aW1lAzEzODk4NTk2MjE-";>Change
settings via the Web</a> (Yahoo! ID required) <br>
Change settings via email: <a href="mailto:ukha_d-digest@xxxxxxx?subject=Email
Delivery: Digest">Switch delivery to Daily Digest</a> <a
href = "mailto:ukha_d-fullfeatured@xxxxxxx?subject=Change
Delivery Format: Fully Featured">Switch to Fully Featured</a>
<br>
<a href="http://groups.yahoo.com/group/ukha_d;_ylc=X3oDMTJkNGY1YTRsBF9TAzk3NDc2NTkwBGdycElkAzExMDk2MzkEZ3Jwc3BJZAMxNzA1MDQxOTkyBHNlYwNmdHIEc2xrA2hwZgRzdGltZQMxMzg5ODU5NjIx";>
Visit Your Group
</a>
<a href="http://info.yahoo.com/legal/us/yahoo/utos/terms/";>
Yahoo! Groups Terms of Use
</a>
<a href="mailto:ukha_d-unsubscribe@xxxxxxx?subject=Unsubscribe";>
Unsubscribe
</a>
<br>
</div>
<br>
<!-- **end egp html banner** -->
<div style="color: white; clear:
both;"/>__,_._,___</div>
</body></html>
--Apple-Mail-7ACD33F3-5E97-4BB7-87F6-F1B1E6A47ABC--
UKHA_D Main Index |
UKHA_D Thread Index |
UKHA_D Home |
Archives Home
|