My forum

Relaterat problem... Jag uppgraderade också nyligen till en znet, insåg då att samtliga event blev förstörda. Tack och lov drog jag ut en backup av alla inställningar och device med min PowerShell modul innan jag bytte då jag misstänkte att detta skulle hända då Telldus bara nämnde device och schema...

Just an FYI - I just upgraded to a TellStick ZNet Lite v2 and realized that no events are "migrated" during the switch, all are left broken. I've written a PowerShell script that can automatically fix all events so they work again (update the sensors/devices in all events so they match the...

@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"

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 ...

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 result...

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...

That's what I get for using native .net instead to enhance performance :banghead: It's case sensitive, so it didn't think Raintotal and RainTotal was the same thing. Updated version with (hopefully) a fix uploaded, also added friendly names for what I think are the correct types for wind sensors. Ho...

It isn't included? If you refer to the actual code it's not in the list of "Friendly names" because it's already called Humidity in the API

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

Hi c8h10n4o2, Thanks for your work! I have a question regarding Connect-TelldusLive : How do I make the credentials stick? Each time I open a powershell cli I need to connect first but I want to automate stuff through Event-Ghost, run on/off commands through a .bat file. Any suggestions on how to h...

Minor update, seems there have been some intermittent connection issues against the Telldus Live! API lately, I've therefor added "server side retries", ie. the backend service used by the module will automatically perform a few retries (for errors related to the specific connection issues...

Vet inte om det är ett alternativ för dig, men jag kör powershell för just det.

Alldeles gratis är det också (om du kör windows)

Se t.ex.:
http://www.telldus.com/forum/viewtopic.php?f=14&t=3483

Awesome! Happy to hear that. I don't think it has been fixed on the Telldus Live side, the app is logging an event every time this happens and it happened quite a few times yesterday as well. Nothing so far today though, but it seems to come in "bursts", where multiple timeouts and connect...

So, I've published a new version (1.4.0) now which should change wgust to WindGust (sorry, I guess this will be a breaking change for you but I hope you can manage :oops: :) ). I've also added a few new functions/cmdlets as well, one noteworthy function is "Backup-TDAccount" which will sto...

What about a set (rename?) devicename cmdlet? Winstick has this features so I think it is in the API...? Updated the module with Rename-TDDevice now. Also added Get-TDEvent, and up/down actions for Set-TDDevice. I don't have any device supporting that though, so I haven't been able to test that (up...