PowerShell based cmdlets / Commands

Moderator: Telldus

c8h10n4o2
Posts: 61
Joined: Thu Jan 18, 2018 11:08 am
Contact:

Re: PowerShell based cmdlets / Commands

Post by c8h10n4o2 » Thu Jul 19, 2018 9:17 am

Roger that! :-)

ArneG
Posts: 26
Joined: Thu Jan 18, 2018 11:08 am

Re: PowerShell based cmdlets / Commands

Post by ArneG » Thu Jul 19, 2018 9:33 am

Also good to know regarding this issue: The collecting/maintaining of historydata even for ignored sensors still is working as usual (if the 'Save historydata' is checked). :D

So the "Get-TDSensorHistoryData"-function WILL still get the all historydata for both ignored and not ignored sensors (i.e. for ALL sensors that actually have the 'Save historydata' is checked')

ArneG
Posts: 26
Joined: Thu Jan 18, 2018 11:08 am

Re: PowerShell based cmdlets / Commands

Post by ArneG » Thu Jul 19, 2018 9:38 am

A completely different question: Does anyone know why each sensor has its own 'SensorID' in addition to already having its own unique 'DeviceID'. What is it (or can it be) used for? :?:

Post Reply