Telldus Technologies

Probably because you're excluding sensors with those properties when you do that, if no sensor is reporting that type of sensor value, it wont be included in the results. It will just make sure all objects have the same properties. I've done another update though (1.3.2), so now the ConvertTo-TDNorm...

Ok, so I've updated the module again, it would be great to hear your opinion about the solution to this in 1.3.0. I've added the "ConvertTo-TDNormalizedOutput" cmdlet now which will make sure all objects have the same properties which should hopefully solve your issue. Just pipe the results to that ...

hmmm, I get what you mean but I think hardcoding the properties again is not a good approach for the module at least, as soon as someone buys another type of sensor it will be "broken" again, this problem is more related to exporting things to CSV instead of a format that handle different objects. A...

@ArneG Could you try the latest version (1.2.0) and check if it now works as you expect?

Get-TDSensorData and Get-TDSensorHistoryData should now hopefully post all values from the sensors "out of the box"

I'm afraid not, looks like the module has to be updated to support that.

I guess that could make sense, I'll try to look into it when I get a chance! Meanwhile, you could try this: $SensorData=Get-TDSensor | Get-TDSensorData $SensorData | select *, @{N='RainRate';e={ $_.data.where({$_.name -eq 'rrate'}).value }}, @{N='RainTotal';e={ $_.data.where({$_.name -eq 'rtot'}).va...

Great!

Does that work for you?

If you store the output from Get-TDSensorData and look in the data-property, do you see the values there?

For example:
$Sensor = Get-TDSensorData -DeviceID 123456789
$Sensor.Data

Doh!

Of course! Fixed in 1.1.7! Thanks again for reporting

Sorry for my late reply, somehow I didn't get any notification about your post, so I just noticed it now.

Anyway, I hope I've fixed that bug now, please update to version 1.1.6 and try again! (Update-Module AutomaTD -Force)

Thanks for reporting the bug!

Roger that!

Ah, OK. Seems they have no plans to fix it?

Oh well, at least it's fixable by them manually then. Thanks for reporting back!

Seems you are right @ArneG, I get the same behavior (and now I can't get my sensor back! :( ) I know that this has worked fine in the past, and as you say, the Telldus Live! website is broken in the same way, so seems this is a problem on their end. I'll add a support ticket to them asking about it....

Just wanted to mention that the module has been updated to version 1.1.4 now. Added some validation that the saved/specified credentials actually work when executing the Connect-TelldusLive cmdlet, and I've also made some improvements on the backend service, error messages should now hopefully be at...

Awesome! :D Glad to hear it works now. Yes, you are exactly right. First time you use the module on a computer you run: Connect-TelldusLive -SaveCredential Then authenticate the module through the Telldus website. After that, you can simply run: Connect-TelldusLive -UseSavedCredential And the access...