You got the graphs working? Tellmon does not query Telldus live for data, instead it stores the data locally as its pushed from Telldus to Tellmon in real-time as your sensors and devices change state.
Telldus has a public API (documented at http://api.telldus.com). One method in the API I can call is to turn on push messages for a user once he or she has logged on (this is done on Tellmon as soon as you login).
If you are a developer and want to get push for your own application you'll need to go though some steps:
1. Register as a developer at developer.telldus.com 2. Get your developer API-keys and develop your application. 3. Register your application to get public API-keys 4. You'll need to setup a push endpoint (URL) and give that to Telldus
Once all that is done you can call the api-function setPush(true) to start having Telldus send sensor and device info to your application.
The data is actually just a normal HTTP POST message with some OAUTH headers for authentication and the device/sensor ID, timestamp and state/value.
For Tellmon the endpoint used is http://push.tellmon.net/ which you can actually visit in your browser. You can see that Tellmon is actually receiving about 150 values per second which is quite a lot.
Thank's Pål, very interesting, your information is very useful.
I have quite a lot of sensors and switches and got the idea to develop my own application and collect values in own server(s). I'm an old Delphi/pascal programmer (and other languages before that), but I'm now using Lazarus/pascal as Lazarus is free, running on Windows, Mac OS X, Linux and in the very beginning of Android.
So far i have a sensor chart up and running, getting sensor results from Telldus live, thru "java reader" as described in the Telldus forum. This has beed running perfect for a while now. I'm collecting values only every 15 min and have the idea to make this indivudal pr. sensor as i don't need the temp in the basement of the cabin that often. Besides that I want to reduce (possible pr. sensor) the frequence of values as they are getting older. Eks: After a month temperatres (etc), I think Min and Max pr.day is what I need. This will reduce the amount of data.
I want to quit the java and is now in the middle of the process of the "oAuth1 dance". Seems i have the authentication strings correct, but no luck so far.....only 401...
Telldus support is asking me of my endpoint, ..... indicating this is the error! I can't see endpoint is defined as a "must" in the oAuth1 spec nor in some Telldus doc. I Hope I don't need one as i'm reciving returned values i streams as now. Or am I wrong?
Thank you for your feedback.
If you are a developer and want to get push for your own application you'll need to go though some steps:
1. Register as a developer at developer.telldus.com
2. Get your developer API-keys and develop your application.
3. Register your application to get public API-keys
4. You'll need to setup a push endpoint (URL) and give that to Telldus
Once all that is done you can call the api-function setPush(true) to start having Telldus send sensor and device info to your application.
The data is actually just a normal HTTP POST message with some OAUTH headers for authentication and the device/sensor ID, timestamp and state/value.
For Tellmon the endpoint used is http://push.tellmon.net/ which you can actually visit in your browser. You can see that Tellmon is actually receiving about 150 values per second which is quite a lot.
I have quite a lot of sensors and switches and got the idea to develop my own application and collect values in own server(s).
I'm an old Delphi/pascal programmer (and other languages before that), but I'm now using Lazarus/pascal as Lazarus is free, running on Windows, Mac OS X, Linux and in the very beginning of Android.
So far i have a sensor chart up and running, getting sensor results from Telldus live, thru "java reader" as described in the Telldus forum. This has beed running perfect for a while now.
I'm collecting values only every 15 min and have the idea to make this indivudal pr. sensor as i don't need the temp in the basement of the cabin that often.
Besides that I want to reduce (possible pr. sensor) the frequence of values as they are getting older.
Eks: After a month temperatres (etc), I think Min and Max pr.day is what I need. This will reduce the amount of data.
I want to quit the java and is now in the middle of the process of the "oAuth1 dance".
Seems i have the authentication strings correct, but no luck so far.....only 401...
Telldus support is asking me of my endpoint, ..... indicating this is the error!
I can't see endpoint is defined as a "must" in the oAuth1 spec nor in some Telldus doc.
I Hope I don't need one as i'm reciving returned values i streams as now.
Or am I wrong?