Hi Per, Haven't forgotten - just away from home a bit - and very busy - should get some feedback on those TSC messages to you shortly - hopefully some others...
I got an idea this evening, on how to handle the 1-Wire-to-xAP conversion without restricting the support for one single schema for published messages (much...
Hm, the posting-page only gave a 'moderator-warning' for new threads, nothing was indicated for replies. Ah well, I guess that's sorted now :) The two-way I/O...
Hi Per, The first few posts by new members of the group are moderated on Yahoo groups - and I was out tonight - I guess the other moderators were too. I...
Hello again, I got some minutes over last night and changed the output. They now looks as follows. I would very much like some feedback :) -- Switch-device...
I'm not sure what happened to my reply I sent 10min ago, so sorry if this is a double post. I had some minutes left yesterday so I changed the output, it now...
Actually, I've never thought of it. But as you say, using 4 instead of 16 or more characters will make it more compatible with embedded devices. Thanks // Per...
Kevin, Ok, so as much as possible of the adressing in the header, which implies one message for each separate endpoint - unless the target is using a wildcard,...
Per - I'm sure you already know - but you could use the 1-wire ID as the end portion of the UID should you wish .. and then use a name for the device in the...
Hi Per, Using the BSC or TSC schema the issue with including several blocks within one message is that the identifier for the endpoint that is being reported...
Kevin, Regarding the naming of the message blocks the xAP protocol specification, 1.2-9, states: Message Body Policy: ...Multiple message blocks may share the...
Hi Per I think you have two sensors reporting here , channel 0 and 1 , although both are possibly within the same physical device. Best for TSC if each...
The spec has not been updated to reflect the extended UID in v1.3. The ID is indeed the same as the sub part of the UID. ABDC in this case. The same appiles to...
Hello, I'm a bit confused regarding the mandatory ID pair in the TSC.cmd body. Based on the following xAP message, what would be the correct ID value to set...
Ok, I will stick with the TSC schema, and add .query and .cmd support. I'll likey be back soon with more questions! Cheers, Per ... schema ... test ... ...
Welcome Per, nice to have you on board. As you say we are in early days re the adoption of TSC - we do need some real world implementation feedback so that we...
Greetings all, Let me introduce myself; the name's Per Malmberg and I'm the author of MSure (pronounced 'measure'), an application that serves as a foundation...
Following my own considerations... We could implement point 2 without altering the current spec as follows: value=[0, 1] min=0 max=1 Thus we get a nice binary...
4. I'd prefer to do unit=(unit designation) -- desirable rather than unit=(unit designation) -- mandatory Thus, instead of doing unit=arb, the sender wouldn't...
It's certainly not too late Daniel, I think we have to have a few real implementations of TSC to see if it is actually fit for purpose and then we can look to...
Hi Kevin, I can't speak for others but I was waiting for a wider adoption of TSC before doing the jump :-) Anyway, I agree that xAP applications will never...
http://mi4.biz/files/xapfloorplan/floorplantsctest.zip Hopefully this is a start. It supports TSC pretty much the same way it does with BSC devices. Auto...
Hi Kevin, I can't speak for others but I was waiting for a wider adoption of TSC before doing the jump :-) Anyway, I agree that xAP applications will never...
Following Kevin's call-up request, I've revisited the TSC (v.42) specification draft and have found some points that I would like to discuss here: 1. TSC.query...
We have a bit of a Catch22 situation with xAP TSC. Until we have supporting applications then people don't want to write data sources and vica versa and we...
Hi Mikko, I haven't myself had an opportunity to try your application but it looks most useful. However one user has done so and he has encountered some...