My forum

Set-TDSensor -NewName can not be used to delete the name (set it to blank) ?!

It's no big deal anyway. I like to have ignored sensors with no name :D In my case it's about the fact that some of my sensors get a new ID when I change batteries. The old sensor ID hangs in there (in Telldus Live sensorlist) for a long time before it's removed due to lack of new readings. For such...

The cmdlet for the sensorhistory data is collecting the complete history available on the telldusserver each time. This results in a lot of duplicate sensordata when the cmdlet is uses to poll the telldus server on a regular basis. Of course it is no problem handling/filtering out duplicate sensorda...

Got it
Thanx!

Well, you did forget 'Humidity' this time?

I know, just checking to see that it was intentional

What about a set (rename?) devicename cmdlet? Winstick has this features so I think it is in the API...?

Got my windsensor up and running today. Info will follow.

Tested Oregon windsensor:
Seems to work fine with latest AutomatD, but a tiny little issue (in 'properties to output'): This windsensor sends 3 values to Telldus Live; wavg, wdir and wgust. In current AutomatD wgust is not translated into a friendly name like wavg and wdir is.

Yes, either you fixed it or Telldus fixed their api. Not sure, but got lots of those timeouts you refer to during the last week or so, but now it's been 24 hours plus with no timeouts :) I've noticed that the script execution times is now back to more or less 'normal', so maybe Telldus got their api...

I know. I''m collecting devicehistory via that cmdlet on a regular basis. I also do poll the sensors via TD-GetSensor every 15 minutes or so, and that way collecting/storing my own sensorhistory locally via a simple Delphi-application that I've hacked together...But it would be nice to get this hist...

No problem. For a string in Delphi 'wgust' is just as friendly (or not) as 'WindGust' or any other string

Thanks. Works fine appearanty

Btw: maybe the example in the code should reflect that the cmdlet uses UTC times (since the timedata from Telldus live is in UTC, and getdate() returns local time by default)

Glad it works! :) Hmm... I think I see your point. The way it works now will make sure the user will get the expected data back from Telldus Live (converts the date you add to UTC). What I really should do though is convert the returned dates to the local time for the whole thing to make more sense...

I don't know if it is editable, but the keephistory-switch does work, so probably the sensor it is indeed editable. I also tried many other sensors, same shit. BUT, I just tried it agian now: "https://live.telldus.com/sensor/setIgnore?id=10324063&ignore=1" The telldus site returns an e...