Telldus Net message format

Moderator: Telldus

Post Reply
gth
Posts: 2
Joined: Fri Mar 17, 2023 9:45 am

Telldus Net message format

Post by gth »

I'm writing a parser for the messages sent by Telldus Net. I've looked at the a description of the message format here:
https://developer.telldus.com/doxygen/h ... ckNet.html

However, there is something that I do not understand. The messages containing sensor readings from my Oregon sensors look like this:

Code: Select all

28:F927E3D44633EED2818179D1997BDB92C0BADF2D52:7:RawDatah5:class6:sensor8:protocol6:oregon5:modeli1A2Ds4:datai10FD801760054873sss
28:36FE7F4BBF82379EB85FFABB4D4C23E2D212104B50:7:RawDatah5:class6:sensor8:protocol6:oregon5:modeliF824s4:datai26E06220838059sss
According to the documentation, the character 's' is used to terminate lists, dictionaries and integers. The messages above contain three 's' characters - and as far as I can understand that is one 's' too many. The first 's' should terminate the integer, the second should terminate the dictionary starting after 'RawData'. But what about the third 's'?

Has anyone seen this before? Is it a bug, or have I misunderstood the message format? Probably the latter...so please enlighten me :)
stefan.persson
Posts: 353
Joined: Fri Mar 17, 2023 9:45 am

Re: Telldus Net message format

Post by stefan.persson »

You are quite right. This is a bug in the latest firmware, it will be fixed in the next version.
Stefan Persson
Software
Telldus Technologies
gth
Posts: 2
Joined: Fri Mar 17, 2023 9:45 am

Re: Telldus Net message format

Post by gth »

Thanks, Stefan.
Post Reply