Page 8 of 8

Re: PowerShell based cmdlets / Commands

Posted: Tue Jan 22, 2019 12:24 pm
by ArneG
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.

Re: PowerShell based cmdlets / Commands

Posted: Tue Jan 22, 2019 1:04 pm
by c8h10n4o2
Ahh, thanks for reporting back! I've added a fix to the module for that but I'm working a few other changes as well so I'd rather wait and release them all at the same time. Not sure when I'll do the release but I'll post back when I do!

Re: PowerShell based cmdlets / Commands

Posted: Tue Jan 22, 2019 2:25 pm
by ArneG
No problem. For a string in Delphi 'wgust' is just as friendly (or not) as 'WindGust' or any other string :D

Re: PowerShell based cmdlets / Commands

Posted: Thu Feb 07, 2019 9:23 am
by c8h10n4o2
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 store information about the clients/locations, devices, sensors, schedules and events that are associated with Telldus Live! account on local disk. This backup can be used to for example restore events in case they got lost, or as in my case, be used to migrate events from one client (Tellstick) to another (used it when I migrated from Tellstick Net to TellStick ZNet Lite v2).

The actual migration script is not published yet, but if anyone has need for it please ping me and we'll work something out! :wave:

Re: PowerShell based cmdlets / Commands

Posted: Wed Mar 06, 2019 10:50 pm
by c8h10n4o2
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) before giving up.

This could potentially cause a slight delay in the response, but will hopefully improve reliability of the module even when Telldus Live! is a bit shaky :)

Related error message you might have seen in the module:
Telldus Live! API responded with error: "Unable to connect to the remote server"

If you still see this message or something similar, please respond to this thread with the exact error and I'll have a look.

Re: PowerShell based cmdlets / Commands

Posted: Fri Mar 08, 2019 8:22 am
by ArneG
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-things right again...

Re: PowerShell based cmdlets / Commands

Posted: Fri Mar 08, 2019 8:31 am
by c8h10n4o2
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 connection failures happens within a specific time window.

Anyway, hope this change can fix that at least to some level so it becomes less of a problem from a module usage standpoint :-)