lordmilko/PrtgAPI v0.8.1 on GitHub

Improvements

Implemented support for resolving objects created via AddSensor, AddDevice, AddGroup and AddNotificationTrigger. Can be disabled by setting optional parameter resolve to false
Installing PrtgAPI from NuGet no longer imports PowerShell Help files into solution
PrtgAPI.cmd is now included in NuGet, allowing a PrtgAPI PowerShell prompt to be easily opened from your NuGet packages folder

Get-Sensor, Get-Device, Get-Group and Get-Probe can now filter for objects that contain all specified tags via -Tags parameter. Filtering for objects that contain any specified tag (previous -Tags behavior) can now be performed with new -Tag parameter
PrtgAPI.cmd can now be used regardless of the folder name the PrtgAPI module is installed in

NotificationAction objects now include enhanced properties detailing the specifics of each notification type they perform and the users these alerts are sent to

Fixed a bug wherein progress did not complete when an exception is thrown by a multi operation cmdlet

Resolved an issue wherein ErrorLimitMessage and WarningLimitMessage cannot be modified and LimitsEnabled cannot be set to true via SetObjectProperty / Set-ChannelProperty on PRTG 18.1.38+. Attempting to modify these properties when a limit value has not been set on the UpperErrorLimit, LowerErrorLimit, UpperWarningLimit or LowerWarningLimit of a channel will now generate an InvalidOperationException specifying the IDs of the sensors that require a limit
Fixed a bug wherein PrtgUrl construction would crash when the search filters of a request have been explicitly set to null

-Tags parameter of Get-Sensor, Get-Device, Get-Group and Get-Probe now performs logical AND instead of logical OR. Previous -Tags behavior can be attained via new -Tag parameter