PowerShell based cmdlets / Commands

Moderator: Telldus

c8h10n4o2
Posts: 86
Joined: Fri Mar 17, 2023 9:45 am
Contact:

Re: PowerShell based cmdlets / Commands

Post by c8h10n4o2 »

hmm, alright I get the problem at least. Might not be easy to solve "client side" but I guess I could potentially add a switch (-ConfirmCommand or something like that) that polls the history and wait for the verification to be registered, and if not resend the same command as a "retry".

Or maybe that would too much of a hack... What do you think? :-)

I can try to take a look at the API docs and see if Telldus have added some info about how to handle this as well when I get some time.
Masonit
Posts: 79
Joined: Fri Mar 17, 2023 9:45 am

Re: PowerShell based cmdlets / Commands

Post by Masonit »

I think if it would be possible to trigger re-fresh of status, then that would be great. But the "hack" stuff I think is best to leave out of the module.. :)

\Masonit
c8h10n4o2
Posts: 86
Joined: Fri Mar 17, 2023 9:45 am
Contact:

Re: PowerShell based cmdlets / Commands

Post by c8h10n4o2 »

ArneG wrote: Mon Sep 30, 2019 7:37 pm Set-TDSensor -NewName can not be used to delete the name (set it to blank) ?!
Seems you're right. I can't get the API explorer to clear the name of a sensor either. If I post a empty value using the Telldus Live! web page it does set the name of the sensor to "(no name)", but as soon as a I refresh the page the old name is back.

So not entirely sure it's possible to clear the name, or I've misunderstood something.

What would be the use case of that?
Post Reply