[OpenTRV-dev] tinyHAN application protocol and mapping to MQTT

[Damon Hart-Davis]

Maybe we (you, I, others) can discuss in the IRC session tomorrow night?

I do want to support one-way encryption for deployments using transport other than TinyHAN where a backchannel is hard/slow/expensive/periodic, and I’d prefer to avoid doing security stuff twice!  B^>

(I’m up to my eyes in motor drive code kinda sorta; production engineering is moving along well.)

Rgds

Damon


> On 10 Dec 2014, at 13:47, Mike Stirling <EMAIL ADDRESS HIDDEN> wrote:
> 
> Hi All,
> 
> I've been thinking about the proposed TinyHAN binary protocol and how to automatically map it to grown-up IoT protocols such as MQTT. I've committed my initial thoughts to virtual paper here and would be grateful for comments: http://www.mike-stirling.com/redmine/projects/tinyhan/wiki/TinyHAN_application_protocol
> 
> The write access is something that has been bothering me, because MQTT does not actually seem like that good a fit for what is essentially a remote procedure call.  However, the approach I've proposed on the wiki feels reasonable.
> 
> I've got most of what I've described up and running with a couple of sensors and I'm quite pleased with the result so far.
> 
> Mike
> 
> _______________________________________________
> OpenTRV-dev mailing list
> EMAIL ADDRESS HIDDEN
> http://lists.opentrv.org.uk/listinfo/opentrv-dev