<div dir="ltr"><div>Hi,</div><div><br></div>It may be a good idea to consider how integration with TR-069 (<a href="http://en.wikipedia.org/wiki/TR-069">http://en.wikipedia.org/wiki/TR-069</a>) might work. This is extremely common when managing large numbers of devices, eg if you have a ISP provided router in your home that will be managed using TR-069. <div><br></div><div>Not that I am suggesting that this should be on the leaf nodes but it would be a good idea to make it easy for some intermediate device to translate, eg a similar data model.</div><div><br></div><div>One other point, you may want to try to avoid polling a URL for config updates as once a system is setup config changes tend to happen infrequently so it can be a huge waist of resources both in terms of the leaf node's radio, power, etc but also the serving endpoint, especially when you are dealing with thousands of devices. That being said it is also a lot simpler to implement on the leaf node and can be very useful as a kind of heartbeat.</div><div><br></div><div>Cheers,</div><div><br></div><div>Jeremy</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 6 June 2015 at 11:02, Damon Hart-Davis <span dir="ltr"><<a href="mailto:dhd@exnet.com" target="_blank">dhd@exnet.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Aideen: I’ve added a note here:<br>
<br>
<a href="http://www.earth.org.uk/note-on-IoT-comms-backhaul.html#Opensensors" target="_blank">http://www.earth.org.uk/note-on-IoT-comms-backhaul.html#Opensensors</a><br>
<br>
Is my ‘generic MQTT proxy’ comment on the right lines do yo think? If not, what would be the right thing to do?<br>
<br>
Rgds<br>
<span class="HOEnZb"><font color="#888888"><br>
Damon<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
> On 6 Jun 2015, at 10:57, Damon Hart-Davis <<a href="mailto:dhd@exnet.com">dhd@exnet.com</a>> wrote:<br>
><br>
> Hi,<br>
><br>
> <a href="http://opensensors.io" target="_blank">opensensors.io</a> is MQTT in, and I have a very simple test feed into it from elsewhere.<br>
><br>
> At the moment they don’t have a secure route to feed data in. When they do I’ll try to support it pronto!<br>
><br>
> Rgds<br>
><br>
> Damon<br>
><br>
><br>
>> On 6 Jun 2015, at 10:54, Aideen McConville <<a href="mailto:aideen@amcc.myzen.co.uk">aideen@amcc.myzen.co.uk</a>> wrote:<br>
>><br>
>> No mention of MQTT?<br>
>><br>
>> Aideen<br>
>><br>
>><br>
>> On 6 Jun 2015, at 10:24, Damon Hart-Davis <<a href="mailto:dhd@exnet.com">dhd@exnet.com</a>> wrote:<br>
>><br>
>>> <a href="http://www.earth.org.uk/note-on-IoT-comms-backhaul.html#config" target="_blank">http://www.earth.org.uk/note-on-IoT-comms-backhaul.html#config</a><br>
>>><br>
>>> Interested in any input from the dev list.<br>
>>><br>
>>> Ideally someone has already done all this work, eg as one of the Apache projects, and we might merely need to write a shim/adaptor to achieve our aims.<br>
>>><br>
>>> Or maybe I’m thinking about this all wrong!<br>
>>><br>
>>> Rgds<br>
>>><br>
>>> Damon<br>
>>> _______________________________________________<br>
>>> OpenTRV-dev mailing list<br>
>>> <a href="mailto:OpenTRV-dev@lists.opentrv.org.uk">OpenTRV-dev@lists.opentrv.org.uk</a><br>
>>> <a href="http://lists.opentrv.org.uk/listinfo/opentrv-dev" target="_blank">http://lists.opentrv.org.uk/listinfo/opentrv-dev</a><br>
>> _______________________________________________<br>
>> OpenTRV-dev mailing list<br>
>> <a href="mailto:OpenTRV-dev@lists.opentrv.org.uk">OpenTRV-dev@lists.opentrv.org.uk</a><br>
>> <a href="http://lists.opentrv.org.uk/listinfo/opentrv-dev" target="_blank">http://lists.opentrv.org.uk/listinfo/opentrv-dev</a><br>
><br>
<br>
_______________________________________________<br>
OpenTRV-dev mailing list<br>
<a href="mailto:OpenTRV-dev@lists.opentrv.org.uk">OpenTRV-dev@lists.opentrv.org.uk</a><br>
<a href="http://lists.opentrv.org.uk/listinfo/opentrv-dev" target="_blank">http://lists.opentrv.org.uk/listinfo/opentrv-dev</a><br>
</div></div></blockquote></div><br></div>