# August 30, 2024 – Improved security and flexibility on Ubiquiti UniFi Controllers, additional integration scripts, enhancements, and more.

We are thrilled to share the latest improvements on Ubiquiti UniFi Controllers, enhancements, new integration scripts, and updates from Domotz.  

We highly value your feedback and encourage you to contact our support team at [support@domotz.com](mailto:support@domotz.com) for any comments, questions, or suggestions you may have. 

  New features and integrations

### New feature

#### Support Accounts with MFA on Ubiquiti UniFi Controllers integration

Firstly, we introduce support for Multi-Factor Authentication (MFA) within the integration of Ubiquiti UniFi Controllers. This new feature provides enhanced security and flexibility for you by offering two distinct options for account management: 

- Option 1 (recommended): Configure a Local Admin Account – This approach is ideal for users who need a simple configuration flow and serves as an effective workaround for your Sites even after the Ubiquiti Cloud Accounts MFA enforcement. 
- Option 2: Use the Multi-Factor Authentication Seed – Specifically designed for users who need to comply with stringent security protocols, this option ensures that MFA is fully integrated and operational, providing more protection. 

Local UniFi Controller accounts already in use by users would remain unaffected.

Our help article, [Ubiquiti UniFi Integration, provides a comprehensive guide ](https://help.domotz.com/integrations/ubiquiti-unifi-integration/)[to help you implement this feature seamlessly](https://help.domotz.com/integrations/ubiquiti-unifi-integration/). We encourage you to take advantage of these new capabilities to enhance your network security.

### New Integration Scripts

  MacOS

#### Physical Disks

You can use this script to monitor physical disks on a Macintosh machine.

You will be able to monitor the following:

- ID
- Model
- Status
- Size
- Free space
- Usage
- Serial number
- Partitions number

macOS Physical Disks Monitoring Overview

1. The image shows a monitoring interface for physical disks on a macOS machine.
2. The status is displayed as "RUNNING," indicating that the disk monitoring is active.
3. The sample period is set to "5 Minutes," with "Metrics Consumed" indicating the number 7.
4. A table below lists details of physical disks, with columns for Id, Model, Status, Size, and Free Space.
5. Under "Id," there is "disk0" listed, with the model as "APPLE SSD AP0512N."
6. The "Status" is marked as "Verified."
7. The "Size" of the disk is 500.28 GB, with "Free Space" noted as 441.45 GB.
8. There is an option to "Download CSV" for further analysis or record-keeping.

Monitoring Physical Disks on macOS

1. The tool monitors the status of physical disks on a Macintosh machine.
2. The current status is "RUNNING."
3. The sample period for data collection is five minutes.
4. A total of seven metrics have been consumed.
5. Under "Physical Disks," there are columns for Usage, Serial Number, and Partitions Number.
6. The usage is currently at 11.7%.
7. The serial number for the disk is C02050401QBP9KC1F.
8. The disk has two partitions.
9. Option to download the disk data as a CSV file is available.

The script uses SSH to execute commands on macOS, and we have validated and tested it on macOS Version 14.5.

#### Services

Apply this specific script to monitor the status of services on a Macintosh machine.

You will be able to monitor the following information:

- ID (service name)
- Status

macOS Services Monitoring Dashboard

1. The status of the monitoring system is displayed as "RUNNING" in green text.
2. The sample period for data collection is set to 5 minutes.
3. One parameter is in use, and the metrics consumed are listed as one.
4. In the Services List, a table shows service IDs on the left and their corresponding statuses on the right.
5. Example services include "2h5gfh3774.com.sophos.endpoint.scanextension" with a status of "Terminated (SIGKILL)" and "com.apple.findmymacmessenger" as "Not Running."
6. Each service status helps identify active, inactive, or error conditions.

The script uses SSH to execute commands on macOS, and it has been validated and tested on macOS Version 14.5.

#### CPU and Memory

We developed this script to simplify the Mac CPU and Memory management.

Easily select and apply the script to extract the following information:

- Total memory
- Available memory
- Memory usage
- CPU Name
- Processor Speed
- Physical Processors Packages
- Logical Processors Number
- Cores Number
- CPU Load Average (1min)

macOS CPU and Memory Usage Information

1. The current status is "RUNNING," with a sample period of 5 minutes and 9 metrics consumed.
2. The variables section includes:
   - Available Memory: 12.64 GB
   - Cores Number: 4
   - CPU Load Average (1 min): 114.2%
   - CPU Name: Quad-Core Intel Core i5
   - Logical Processors Number: 8
   - Memory Usage: 21%
   - Physical Processors Packages: 1
   - Processor Speed: 2 GHz
   - Total Memory: 16 GB
3. The "Last change" column indicates a timestamp of 4 minutes ago for most entries, except CPU Load Average, last updated 3 minutes ago.
4. Option to download data as a CSV file is available.

The script has been validated and tested on macOS Version 14.5. It uses SSH as a communication protocol for executing commands on macOS.

#### Applications

You can use this script to monitor applications installed on a Macintosh machine.

Use the script to monitor the following information:

- Name
- Version
- Path
- Architecture
- Last Modified
- Source
- Signed by

Listing Installed macOS Applications

1. The interface displays a title, "macOS - Applications," indicating the retrieval of details about installed applications on macOS.

2. Status information is shown: "Status: RUNNING," "Sample period: 5 Minutes," "Parameters: 1," and "Metrics Consumed: 7."

3. A table under the heading "macOS Applications" lists details of applications with columns for Id, Name, Version, and Path.

4. Example entries include:
   - "Id: messages-14.0," "Name: Messages," "Version: 14.0," "Path: /System/Applications/Messages.app"
   - "Id: mrt-1.93," "Name: MRT," "Version: 1.93," "Path: /Library/Apple/System/Library/CoreServices/MRT.app"

5. A link labeled "Download CSV" allows downloading the list in CSV format.

Viewing Installed macOS Applications

1. The interface displays details of installed applications on macOS.
2. The status is labeled as "RUNNING" with a sample period set to "5 Minutes."
3. Parameters and metrics consumed are identified with values "1" and "7," respectively.
4. A table titled "macOS Applications" lists applications with columns: Architecture, Last Modified, Source, and Signed By.
5. Filter options are available for each column.
6. Users can download the data as a CSV file via a "Download CSV" link.

We tested the script and confirmed it works on macOS Version 14.5, using SSH as the communication protocol to execute commands on the system.

  VMware ESXi

#### General Information

You can easily apply this script to oversee your VMWare ESXi general information effectively.

The following information can be monitored:

- Name
- Connection State
- System Model
- System Vendor
- Number of NICs
- Number of HBAs
- Product Version
- API Version
- OS Type
- Product Line ID

ESXi General Information and Status Overview

1. Title: "esxi_general_information" with a status indicator showing "RUNNING."
2. Status Details: The sample period is indicated as "5 Minutes," and "Metrics Consumed" are listed as "10."
3. Variables Section: A table with three columns – Name, Value, and Last change.
   - "API Version" has a value of "8.0.0.2."
   - "Connection State" shows "connected."
   - "System Model" lists "Standard PC (i440FX)."
   - "Name" shows "localhost.localdomain."
   - "Number of HBAs" is "2."
   - "Number of NICs" is "4."
   - "OS Type" displays as "vmnix-x86."
   - "Product Line ID" shows "embeddedEsx."
   - "Product Version" is "8.0."
   - "System Vendor" is "QEMU."
4. The "Last change" column indicates all entries were updated "a few seconds ago."

The script uses the HTTP protocol, and it has been validated and tested on VMware vCenter 8.0.2

#### CPU Details

Use this script to monitor and retrieve detailed CPU information on ESXi hosts.

Apply the script to be able to extract the following:

- CPU Vendor
- Speed (Hz)
- Bus Speed (Hz)
- CPU Name

ESXi CPU Monitoring Interface

1. The top section displays "ESXi CPU Details" with a description indicating it monitors the ESXi host CPU details.

2. It shows "Status: RUNNING," confirming active monitoring, and "Sample period: 5 Minutes," indicating the data collection frequency.

3. "Metrics Consumed: 4" suggests how many metrics are being tracked.

4. The table under "CPU Details" lists CPU information with columns for Id, CPU Name, CPU Vendor, Speed, and Bus Speed.

5. Row entries show details for CPU Ids 0 and 1:
   - CPU Name: "Intel(R) Xeon(R) CPU ..."
   - CPU Vendor: "intel"
   - Speed: "2494.22 MHz"
   - Bus Speed: "99.77 MHz"

The script has been validated and tested on ESXi 8.0.0. It also uses the HTTPS protocol.

#### Services

This script might be used to monitor and manage services on ESXi hosts.

The following information can be monitored:

- Name
- Is Required
- Is Uninstallable
- Is Running
- Policy

ESXi Service Monitoring Dashboard

1. The dashboard monitors ESXi host services with the status displayed as "RUNNING."
2. The sample period for monitoring is set to 5 minutes, and 5 metrics are consumed.
3. In the "Services Details" section, a table lists various services with columns for Id, Name, Is Required, Is Uninstallable, Is Running, and Policy.
4. Each column allows filtering options.
5. Example services include "Direct Console UI" (DCUI) with "Running" status true, and "SSH" (TSM-SSH) also running, highlighted with "on" under Policy.
6. The "Policy" column indicates the status of each service with options like "on" or "off."

As the previous one, it has been validated and tested on ESXi 8.0.0 and uses the HTTP protocol.

#### File System Volume

Proactively monitor and manage file system volumes on ESXi hosts by applying our integration script.

Easily apply the script in order to monitor the following:

- Name
- Type
- Access Mode
- Is Accessible
- Capacity
- Block Size (MB)
- Max Blocks
- Major Version
- Version
- Disk Name
- Partition
- Path
- Is VMFS Upgradable

File System Volume Details Overview

1. The table lists details of file system volumes, with columns such as Id, Name, Type, Access Mode, Is Accessible, Capacity, Block Size, Major Version, Version, Disk Name, Partition, Path, and Is VMFS Upgradable.

2. Status is indicated as "RUNNING" with a sample period of "5 Minutes." Metrics consumed are noted with the number 13.

3. Each row represents a volume with specific attributes, such as:
   - Id: The identifier number.
   - Name: The volume name, e.g., "1TB."
   - Type: File system type, e.g., "VMFS" or "OTHER."
   - Access Mode: Indicates access permissions like "readWrite" or "readOnly."
   - Is Accessible: Shows whether the volume is accessible as "true" or "false."
   - Capacity: Storage capacity in GB.
   - Block Size: Block size in MB.
   - Major Version / Version: File system version details.
   - Disk Name / Partition: The associated disk name and partition number.
   - Path: Filesystem path such as "/vmlsVolume…"
   - Is VMFS Upgradable: Indicates upgrade status with "true" or "false."

4. A download link for the data is visible in the top right corner.

The script uses the HTTPS protocol. It has been validated and tested on ESXi 8.0.0.

#### Physical NIC Configuration

Use our script to monitor and configure the physical NIC settings on ESXi hosts.

The following information can be monitored:

- Device
- PCI Slot
- Driver
- Link Speed (Mb)
- Duplex
- DHCP Enabled
- IP Address
- Subnet Mask
- Wake-on-LAN Supported
- MAC Address

Network Physical NIC Configuration Table

1. **Id**: Displays unique identifiers for each NIC, named as "key-vim.host.PhysicalNic...".
2. **Device**: Lists network interface card names like "vmnic0," "vmnic1," and "vmnic2."
3. **PCI Slot**: Provides the slot information, such as "0000:00:19.0" and "0000:0b:00.0."
4. **Driver**: Shows driver types, including "ne1000" and "qlfqge."
5. **Link Speed**: Indicates the speed in MB, ranging from "0 MB" to "1000 MB."
6. **Duplex**: Describes the duplex mode, such as "Full" or "Half."
7. **DHCP Enabled**: Notes whether DHCP is enabled with "No" or "Yes."
8. **IP Address**: Displays the IP address if available; otherwise, "N/A."
9. **Subnet Mask**: Shows the subnet mask, with entries like "N/A."
10. **Wake-on-LAN Supported**: Indicates if the feature is supported, marked as "Yes."
11. **MAC Address**: Lists the MAC addresses associated with each NIC.

The script has been validated and tested on ESXi 8.0.0 and uses HTTPS protocol.

#### Virtual NIC Configuration

Monitor and configure the virtual NIC settings on ESXi hosts by applying this script.

You can monitor the following metrics:

- Device
- Port Group
- DHCP Enabled
- IP Address
- Subnet Mask
- MAC Address

ESXi Network Virtual NIC Configuration Overview

1. The ESXi Network Virtual NIC Configuration page monitors the Network Virtual NIC settings on the ESXi host.
2. The status is indicated as "RUNNING," with a sample period set at every 5 minutes. A total of 6 metrics are consumed.
3. The configuration table includes columns for ID, Device, Port Group, DHCP Enabled, IP Address, Subnet Mask, and MAC Address.
4. The current entry shows:
   - ID: key-vim.host.VirtualNic-...
   - Device: vmk0
   - Port Group: Management Network
   - DHCP Enabled: Yes
   - IP Address: 192.168.43.114
   - Subnet Mask: 255.255.255.0
   - MAC Address: 18:66:da:19:db:1e

The script has been validated and tested on ESXi 8.0.0 and uses the HTTPS protocol.

#### CPU and Memory Information

This script lets you gather a detailed view of ESXi hosts' CPU and memory usage.

The following information can be monitored:

- Memory Usage (GB)
- Memory Size (GB)
- CPU Usage (GHz)
- CPU Speed (GHz)
- CPU Model
- Number of CPU Cores
- Number of CPU Threads

ESXi CPU and Memory Information Overview

1. The page monitors CPU and memory information of the ESXi host, indicating a status of "RUNNING."
2. Displays a sample period set to "5 Minutes" with "7" metrics consumed.
3. A table lists variables including:
   - CPU Speed: 2.49 GHz
   - CPU Model: Intel(R) Xeon(R) CPU
   - Memory Size: 127.92 GB
   - Number of CPU Cores: 24
   - Number of CPU Threads: 48
   - CPU Usage: 1.00 GHz
   - Memory Usage: 47.66 GB
4. The "Last change" column shows updates occurred "a few seconds ago."
5. A "Download CSV" option is available for exporting data.

The script uses the HTTPS protocol. It also has been validated and tested on ESXi 8.0.0.

  Dante

#### Director Device Status

Our script integrates seamlessly with the Dante Managed API. This will allow you to easily monitor and manage Dante devices.

It provides comprehensive details on each device, including the following:

- Name
- Manufacturer Name
- Product Model
- Dante Version
- Address
- Status ID
- Clocking Status
- Latency Status
- Connectivity Status
- Subscription Status
- RX Channels
- TX Channels
- Alert Message Clocking
- Alert Message Connectivity
- Alert Message Latency
- Alert Message Subscriptions

Dante Director API Integration Status Overview

1. Shows the connection status of the Dante Director API integration, which is currently running.
2. Displays additional information: a sample period of 5 minutes, 2 parameters, and 5 metrics consumed.
3. Under the "Devices" section, a table lists device details.
4. The columns include "Id," "Name," "Connectivity Status," and "Subscription Status."
5. The table provides two example entries:
   - First entry: Id "001dc1fffe527e4f:0," Name "AVIOAO2-527e4f," both connectivity and subscription statuses are "OK."
   - Second entry: Id "001dc1fffe54d737:0," Name "AVIOUSB-54d737," both connectivity and subscription statuses are "OK."
6. A "Download CSV" option is available for exporting the data.

Dante Director API Integration Status and Device Information

1. The header displays "Dante Director API Integration," indicating a section to manage API integration for device information at an individual site.
2. The current status is "RUNNING," shown in green text, suggesting the API is actively operating.
3. Sample period is indicated as "5 Minutes," showing the frequency of data collection.
4. It lists "Parameters: 2" and "Metrics Consumed: 5," indicating the quantity of parameters and metrics being used.
5. The "Download CSV" option is available, allowing users to download data in a CSV format.
6. Under "Devices," there are sections for "RX Channels" and "TX Channels."
7. "RX Channels" lists CH1 and CH2 as DYNAMIC, with left and right channels marked as NONE.
8. "TX Channels" are listed as N/A for the first device, with the second device indicating both left and right channels.

Dante Director API Integration Status and Device Information

1. The Dante Director API integration is currently running, indicated by the status "RUNNING."
2. The sample period for data collection is set to 5 minutes.
3. Two parameters are being monitored, consuming a total of 16 metrics.
4. Under the "Devices" section, details are listed in a table format with the following columns: Subscription Status, RX Channels, TX Channels, and Alert Message Clocking.
5. The Subscription Status for both entries is "OK."
6. RX Channels options include "CH1 (DYNAMIC)," "CH2 (DYNAMIC)," "Left (NONE)," and "Right (NONE)."
7. TX Channels display "N/A" for the first entry and "Left, Right" for the second.
8. Alert Message Clocking shows "N/A" for both entries.
9. A "Download CSV" option is available to export the data.

Dante Director API Integration Status Overview

1. The integration status is running, indicated by the label "RUNNING" in green.
2. The sample period is set to 5 minutes.
3. There are two parameters, and the metrics consumed count is 16.
4. The "Devices" section lists columns for Alert Message Connectivity, Alert Message Latency, and Alert Message Subscriptions, but shows "N/A" under each due to no available data.
5. A link is available to download the information in CSV format.

The script has been validated and tested with the Dante Director using the Dante Managed API. In addition, it uses the HTTPS protocol.

  SonicWall Firewall

#### Failover Load Balancing Groups

Apply this script to monitor the failover load balancing groups on a SonicWall firewall.

You can get access to the following information:

- Group Name
- Member Name
- IP Address
- Link Status
- Load balancing status
- Probe status
- Main target status
- Alternate target status

Failover Load Balancing Groups Table

1. The table lists different failover load balancing groups.
2. Columns include "Id," "Group Name," "Member Name," and "Link Status."
3. Under "Id," entries are "x1-default-lb-group-ipv6," "x1-default-lb-group," and "x2-default-lb-group."
4. Corresponding "Group Names" are "Default LB Group IPv6" and "Default LB Group."
5. "Member Names" listed are "X1" and "X2."
6. "Link Status" shows "No WAN Configuration" for the first entry and "Link Up" for the others.
7. A "Download CSV" option is available for exporting the table data.

The script uses HTTP as a communication protocol.

  Enhancements

### Collector Settings Section

We’re continuing to work on adding new information and details in the Collector Settings section. These updates aim to further centralize the initial configuration and management processes, allowing users to enjoy a more streamlined and efficient way of managing their collectors.  

This month, you’ll see significant improvements regarding the following: 

- Access Management 
- Support Team 
- Manufacturer Support 
- Residential Support App 

We implement these changes to improve customer information and provide better visibility into key properties, ultimately enhancing the user experience. 

  Access Management

This section allows you to manage access to people from the same organization to access, in a controlled way, the same pool of Network Collectors. and grant complete access to your Network Collector and Devices to a trusted person with a Domotz Account, even if this person is outside your organization. 

Access Management Panel Overview.

1. Under "Access Management," there are two sections: "Your Team" and "External Collaborators."
2. "Your Team" shows 5 members. You can edit this number using the pencil icon next to it.
3. "External Collaborators" shows 11 collaborators. Editing is also available with the adjacent pencil icon.

  Support Team

Through this tab, you can enable access for Domotz Support Team, if requested, when opening tickets.

Enable Access for Support Team in Domotz

1. Read the instructions: "Enable the access to your Network Collector to let the Support Teams help you more efficiently."
2. Ensure the status indicator labeled "Enabled" is visible in green next to the Domotz logo.
3. If changes are needed, use the pencil icon next to "Enabled" to modify the access settings.

  Manufacturer Support

By accessing this section, you’ll grant access to your Network directly to the manufacturer. Please note that the access will expire 3 hours after it is activated.  

Please note that this section is only visible when supported devices are present in the network. 

  Residential Support App (or residential and integrator use)

In this section, you can enable your Customer to access their network through the Violet  - Residential Support App, and manage their permissions, limiting Devices visibility or actions. 

Residential Support App Status Overview

1. The title displays as "Residential Support App" accompanied by a gear icon.
2. Below the title, "Violet - Residential Support App" is shown in blue, followed by customer information: "support@domotz.com."
3. On the right, the status of the app is indicated as "Enabled" in green text, with an editable icon next to it, suggesting that users can change the status.

  New MIBs

- WatchGuard Wireless Access Points 
- Pepwave 
- Peplink

  Fixes

- Re-add “Back Button” for Desktop App users 
- Device Interfaces tab: not always displaying reachable devices on the ports 
- Preventing Unifi Controller-connected devices from toggle PoE control 
- The PoE option was not visible on Switch devices integrated with External Cloud services 
- Domotz WebApp login page: freezing when using Keeper password manager 
- Collector Settings and Inactive Sites URLs in Persistent Devices emails 
- Scroll missing from integrations mf 
- Communication channels are constantly being fetched in the integrations of mf 
- Preventing IP Addresses List/Range options from being displayed in the Monitoring Configuration view 
- ESXi Devices: it was not displaying the Virtual Machine list in the System tab 
- Sites Explorer Map: where clustered pins were not being updated correctly when inner Sites status changed 
- Auto-Closure feature for HaloPSA Ticketing System, which was causing a wrong update of tickets 
- Ubiquiti Unifi devices are erroneously as locked 
- Rendering issues on the Ubiquiti Unifi Access Point tab 
- Collector Location: Agent Location change broken on MF Collector Settings 
- Devices Interfaces tab: showing 1 Reachable Device instead of mapping it directly on the port