My forum

There seems to be a problem with Set-TDSensor. Ignoring a sensor works fine, but unignoring it does not. This may be an api-problem because when trying the same thing manually on Telldus Live web-site also fails. The sensor seems to be 'unignored' on the screen, but the setting won't stick, the sens...

Will there be any Get-TDSensorHistory soon ? The data from Telldus Live may be available now like it is with the Device-History ?

And this line: '$SensorData=Get-TDSensor | Get-TDSensorData' does not collect ignored sensors?!

The unignore-thing is a bug in Tellstick NET. Got this answer from support:
"Yes, I´m afraid that is right.
There is a bug that occurs when you have TellStick Net that doesnt allow users to take back ignored sensors.
We can do this manually though."

I don't know yet, I asked them if it will be fixed, but hasn't got an answer for that..yet?

A few other tasks that we have to log on to Teldus Live manually to perform would be nice to be able to do via the CMDLet:
Turn on/off the Telldus live's 'store history'-function for sensors.
Set the Ignore/Show switch for devices/sensors

Set-TDSensor: "-newname" and "-keephistory" options works, "-IgnoreSensor" does not?

I Will debug my code a little bit more and report back...

Maybe a clue: I tried something directly when logged in on the telldus site: "https://live.telldus.com/sensor/setKeepHistory?id=10324063&keepHistory=1" Telldus site returns "{"status":"success"}" and does what it should "https://live.telldus.com/senso...

And now it is back to returning nothing.
How to best check if my sensor(s) are "editable"? As I said; -keephistory and -newname works as it should.

Just checked to be sure: Sensor IS editable

Yes, it works the UI-way

YES, there it was. The clue you need to understand why it not worked for me is that I am still using older version of 'teldus.psm1'-module and have forked the new Set-TDSensor function into it (with some changes to the login-stuff and URI invoking-stuff, i.e. I use the live.telldus.com endpoint yes....

Yes, I know. I' m still on Win7, Office 2010 and Delphi 7........"When things stops working, THEN fix it"

Log inn manually on web and accept the new 'terms&conditions'. The modules should work again after this. Worked for me when they stopped workng like that 10-12 days ago