The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: Hue musings ...



--------------030201020704080401010700
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

Although the control of Hue lamps from ST is pretty fast it still
doesn't achieve this via local control on your network. Incredulously it
goes via both the ST cloud and the Hue cloud when using a Hue hub.  This
means that ST can't control your Hue lights if your Internet is down. A
quick disconnect of the Internet cable from your router will ascertain
if a device has local control from ST.

The status of my Hue lights as shown in ST is frequently wrong and
doesn't correct even after hours. This means you can't  use Hue status
as a trigger or the Hue switch to control a ST device. If you pair the
Hue bulbs directly to the ST hub , thus not using the Hue hub,  then you
might get local control at a reduced functionality level. The Hue switch
will pair with the ST hub but seems to drop out after a few hours.,
possibly something Philips has implemented to keep you loyal to their
system.

The only thing that the ST hub can control locally are some ZigBee
devices (ST supplied devices are ZigBee) and I believe a handful of
Z-Wave devices. No Ethernet device can (as yet) be locally controlled.
Also if you modify the device code for any local device away from the ST
approved template then it is considered a custom device and won't run
locally. Local devices have to have drivers supplied in firmware so can
only be added via ST via a firmware update ... that's a humdinger of a
restriction if you think about it.

You can check which devices and Apps are considered local to your hub
with these links  Warning :-(  you'll likely be disappointed at how few
are listed,  I think there's only the single SmartLights App available
currently.

https://graph-eu01-euwest1.api.smartthings.com/localDevice/list
https://graph-eu01-euwest1.api.smartthings.com/localInstalledSmartApp/list

Aside from the current reliability issues and the still appalling UK
deficiencies this is my fundamental concern with the ST architecture.
The other issues will be fixed over time but this cloud dependency
likely won't.    A home control system should control your home locally
wherever possible not relying on Internet connectivity and multiple
cloud services.  This is for speed, reliability and security all of
which are impacted by using cloud control.

Samsung have announced they are building the hub into all their 2016
Tizen based TV offerings. The ST hub is a well priced product and
currently the only one positioned for mass market, which is a good thing
for HA. So I do hope they get their act together  - but there's a lot to
sort out.

K

On 02/01/2016 11:07, Paul Gale groups2@xxxxxxx [ukha_d] wrote:
> The new Hue dimming kits don't need the hub - they link directly to
> the lamp out of the box but you can then link them to the hub for
> wider control. Important to note that the Hue hub operates the lamps
> LOCALLY - it doesn't need to go via their servers for local control
> which makes it nice and responsive. ST on the other hand DOES operate
> via the cloud servers. With the new v2 hub, they have brought some
> processing local to the hub to try and prevent the longer delays and
> latency that a cloud based service inherently has. Linking the ST hub
> to the Hue hub works well as its a local connection so lamps respond
> instantly. Status of lamps on ST when not operated via ST can take a
> few moments to register though. So yes, ST HAS to be connected to the
> Internet to operate.
>
>


--------------030201020704080401010700
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit





<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 content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">


<!-- **begin egp html banner** -->

<br><br>

<!-- **end egp html banner** -->



<div class="moz-cite-prefix">Although the control of Hue
lamps from
ST is pretty fast it still doesn't achieve this via local control
on your network. Incredulously it goes via both the ST cloud and
the Hue cloud when using a Hue hub.  This means that ST can't
control your Hue lights if your Internet is down. A quick
disconnect of the Internet cable from your router will ascertain
if a device has local control from ST.  <br>
<br>
The status of my Hue lights as shown in ST is frequently wrong and
doesn't correct even after hours. This means you can't  use Hue
status as a trigger or the Hue switch to control a ST device. If
you pair the Hue bulbs directly to the ST hub , thus not using the
Hue hub,  then you might get local control at a reduced
functionality level. The Hue switch will pair with the ST hub but
seems to drop out after a few hours., possibly something Philips
has implemented to keep you loyal to their system.<br>
<br>
The only thing that the ST hub can control locally are some ZigBee
devices (ST supplied devices are ZigBee) and I believe a handful
of Z-Wave devices. No Ethernet device can (as yet) be locally
controlled.  Also if you modify the device code for any local
device away from the ST approved template then it is considered a
custom device and won't run locally. Local devices have to have
drivers supplied in firmware so can only be added via ST via a
firmware update ... that's a humdinger of a restriction if you
think about it.<br>
<br>
You can check which devices and Apps are considered local to your
hub with these links  Warning :-(  you'll likely be disappointed
at how few are listed,  I think there's only the single
SmartLights App available currently.<br>
<br>
<a class="moz-txt-link-freetext" href="https://graph-eu01-euwest1.api.smartthings.com/localDevice/list";>https://graph-eu01-euwest1.api.smartthings.com/localDevice/list</a><br>
<a class="moz-txt-link-freetext" href="https://graph-eu01-euwest1.api.smartthings.com/localInstalledSmartApp/list";>https://graph-eu01-euwest1.api.smartthings.com/localInstalledSmartApp/list</a><br>
<br>
Aside from the current reliability issues and the still appalling
UK deficiencies this is my fundamental concern with the ST
architecture.  The other issues will be fixed over time but this
cloud dependency likely won't.    A home control system should
control your home locally wherever possible not relying on
Internet connectivity and multiple cloud services.  This is for
speed, reliability and security all of which are impacted by using
cloud control.  <br>
<br>
Samsung have announced they are building the hub into all their
2016 Tizen based TV offerings. The ST hub is a well priced product
and  currently the only one positioned for mass market, which is a
good thing for HA. So I do hope they get their act together  - but
there's a lot to sort out.<br>
<br>
K<br>
<br>
 On 02/01/2016 11:07, Paul Gale <a
class="moz-txt-link-abbreviated" href="mailto:groups2@xxxxxxx";>groups2@xxxxxxx</a>
[ukha_d]
wrote:<br>
</div>
<blockquote
cite="mid:29C77AD5-935B-4B23-BF31-0B2E1C294913@xxxxxxx"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<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>
<!-- **begin egp html banner** --> 
<div>The new Hue dimming kits don't need the hub - they link
directly to the lamp out of the box but you can then link them
to the hub for wider control. Important to note that the Hue hub
operates the lamps LOCALLY - it doesn't need to go via their
servers for local control which makes it nice and responsive. ST
on the other hand DOES operate via the cloud servers. With the
new v2 hub, they have brought some processing local to the hub
to try and prevent the longer delays and latency that a cloud
based service inherently has. Linking the ST hub to the Hue hub
works well as its a local connection so lamps respond instantly.
Status of lamps on ST when not operated via ST can take a few
moments to register though. So yes, ST HAS to be connected to
the Internet to operate. </div>
<div><br>
</div>
<br>
</blockquote>
<br>




<!-- **begin egp html banner** -->

<br>


<br>

<!-- **end egp html banner** -->


<div width="1" style="color: white; clear:
both;"/>__._,_.___</div>





<div id="fromDMARC" style="clear:both; margin-top:
10px;">
<hr style="height:2px ; border-width:0; color:#E3E3E3;
background-color:#E3E3E3;">
Posted by: Kevin Hawkins &lt;yahoogroupskh@xxxxxxx&gt;        
<hr style="height:2px ; border-width:0; color:#E3E3E3;
background-color:#E3E3E3;">
</div>
<!-- Start Recommendations -->
<!-- End Recommendations -->


<!-- **begin egp html banner** -->

<br><br>
<tt>
&lt;*&gt; Join the Automated Home Forums<BR>
&nbsp;&nbsp;&nbsp;&nbsp; <a href="http://www.automatedhome.co.uk/vbulletin/";>http://www.automatedhome.co.uk/vbulletin/</a><BR>
<BR>
&lt;*&gt; UKHA_D Mailing list in association with:<BR>
&nbsp;&nbsp;&nbsp;&nbsp; <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=165657/stime=1451738997";
width="1" height="1"> <br>

<!-- **end egp html banner** -->


<!-- **begin egp html banner** -->

<br>






<!-- **begin egp html banner** -->
<div id="ygrp-vital" style="background-color: #f2f2f2;
font-family: Verdana; font-size: 10px; margin-bottom: 10px; padding:
10px;">

<span id="vithd" style="font-weight: bold; color: #333;
text-transform: uppercase; "><a href="https://groups.yahoo.com/neo/groups/ukha_d/info;_ylc=X3oDMTJlcmlqbmh2BF9TAzk3MzU5NzE0BGdycElkAzExMDk2MzkEZ3Jwc3BJZAMxNzA1MDQxOTkyBHNlYwN2dGwEc2xrA3ZnaHAEc3RpbWUDMTQ1MTczODk5Nw--";
style="text-decoration: none;">Visit Your
Group</a></span>

<ul style="list-style-type: none; margin: 0; padding: 0; display:
inline;">
<li style="border-right: 1px solid #000; font-weight: 700; display:
inline; padding: 0 5px; margin-left: 0;">
<span class="cat"><a href="https://groups.yahoo.com/neo/groups/ukha_d/members/all;_ylc=X3oDMTJmOGVzaXZ1BF9TAzk3MzU5NzE0BGdycElkAzExMDk2MzkEZ3Jwc3BJZAMxNzA1MDQxOTkyBHNlYwN2dGwEc2xrA3ZtYnJzBHN0aW1lAzE0NTE3Mzg5OTc-";
style="text-decoration: none;">New
Members</a></span>
<span class="ct" style="color:
#ff7900;">1</span>
</li>
</ul>
</div>


<div id="ft" style="font-family: Arial; font-size: 11px;
margin-top: 5px; padding: 0 2px 0 0; clear: both;">
<a href="https://groups.yahoo.com/neo;_ylc=X3oDMTJkdDh2MDZlBF9TAzk3NDc2NTkwBGdycElkAzExMDk2MzkEZ3Jwc3BJZAMxNzA1MDQxOTkyBHNlYwNmdHIEc2xrA2dmcARzdGltZQMxNDUxNzM4OTk3";
style="float: left;"><img src="http://l.yimg.com/ru/static/images/yg/img/email/new_logo/logo-groups-137x15.png";
height="15" width="137" alt="Yahoo! Groups"
style="border: 0;"/></a>
<div style="color: #747575; float: right;"> &bull;
<a href="https://info.yahoo.com/privacy/us/yahoo/groups/details.html";
style="text-decoration: none;">Privacy</a> &bull;
<a href="mailto:ukha_d-unsubscribe@xxxxxxx?subject=Unsubscribe";
style="text-decoration: none;">Unsubscribe</a>
&bull; <a href="https://info.yahoo.com/legal/us/yahoo/utos/terms/";
style="text-decoration: none;">Terms of Use</a>
</div>
</div>

<!-- **end egp html banner** -->

</div> <!-- ygrp-msg -->




<br>

<!-- **end egp html banner** -->


<div style="color: white; clear:
both;"/>__,_._,___</div>
</body>
</html>

--------------030201020704080401010700--

UKHA_D Main Index | UKHA_D Thread Index | UKHA_D Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.