We are thrilled to share the latest news, enhancements, new integration scripts like VMWare vCenter, and updates from Domotz.
We highly value your feedback and encourage you to contact our support team at support@domotz.com for any comments, questions, or suggestions you may have.
New Features
More visibility and control of all your network-connected devices
Our latest update introduces significant enhancements to the Network Collectors in device-based mode, providing greater visibility and control over all network-connected devices.
Key improvements
- Unmanaged Devices on Topology Map and Device List: Network Collectors now display unmanaged devices on both the Topology Map and Device List, allowing for easier identification and management. This feature brings a comprehensive view of your network, highlighting both managed and unmanaged devices directly on the map, enhancing your ability to oversee and control network infrastructure.
- Improved Visibility and Control: You can now access the list of network-connected devices in a simpler and more intuitive way. Moreover, you can now seamlessly identify, access, and modify the list of managed devices using a per-device subscription model.
- Streamlined Access to Device Lists: Previously, the complete list of managed and unmanaged devices was only accessible through the collector settings, typically consulted during the initial setup. With the new update, this view is now directly accessible from the device list, a section used daily. This change ensures that network administrators can effortlessly monitor and manage all devices connected to the network without navigating through multiple settings.
- Distinct Tabs for Managed and Unmanaged Devices: Upon accessing the device list section, two distinct tabs will appear above the list: “Managed” and “Unmanaged.” Clicking on these tabs allows users to switch between views of monitored devices and those connected to the network but not actively managed. This feature ensures a clear distinction and easy navigation between different device statuses.
- Greater Control Over Network-Connected Devices: Last but not least, the enhancements to the per-device mode want to give you greater visibility and control over everything connected to the network, including devices that are not currently managed. This holistic view ensures that no device goes unnoticed, providing you with the tools needed to maintain a secure and efficient network environment.

Device Management Interface Overview
1. **Device Selection**: At the top, there are options to view 'Managed' or 'Unmanaged' devices. The 'Unmanaged' tab is currently selected.
2. **Unmanaged Devices Description**: Below the tabs, there is an explanation that unmanaged devices are detected but not monitored or included in your subscription. To manage these devices, you need to add them.
3. **Device List**: A list of unmanaged devices is displayed, each with a checkbox for selection, device name, zone information, and IP details. For example, one device listed is "Google!" with an unknown zone and IP address 8.8.8.8.
4. **Search Functionality**: There is a search bar to filter devices by text input.
5. **Manage Devices and Subnets Panel**: On the right, there are options to add dummy devices, external services, hostname/IP, configure network scan, and VLAN, each with an action button.
6. **Monitoring Settings**: Various settings can be adjusted, including device blacklist (currently showing 0), device auto discovery status (Active), and device RTD (active with a toggle switch).
For additional information on this device monitoring capability, visit our website or contact our sales team.
New Monitoring Flexibility with IP Lists and IP Ranges
Going forward, with this release, you will have the power to decide what to monitor in a flexible and dynamic manner. If you prefer not to monitor everything on your network but only specific devices, we provide the tools to do so. Utilizing IP lists and IP ranges, you can specify “monitor only these IP addresses or those within the range from A to B,” avoiding unnecessary stress on other devices.
Key Benefits:
- Firstly, flexibility to perform ping and recovery operations on selected IP addresses and subsets.
- Secondly, tailored monitoring to meet diverse needs and requirements.
This release is impactful for the device-based model, adding another layer of customization and control.
In conclusion, this feature complements the existing visibility of managed and unmanaged devices. It is a part of the same process, allowing you to decide where Domotz should search for devices on VLAN networks, routed networks, external hosts, or specified IP lists/IP ranges. Once devices are discovered, you can select which ones to continue monitoring.

Edit IP Address List Dialog in Monitoring Configuration
1. Open the "Edit IP Address List" dialog to define private IP addresses that need monitoring by the Network Collector.
2. Enter an IP address into the field labeled "IP Address."
3. Click the "Add to list" button to include the new IP address.
4. The list below displays current IP addresses, such as "192.168.2.0."
5. Use the "Cancel" button to discard changes, or click "Save" to confirm and apply updates.

Add an IP Address Range for Device Monitoring
1. In the "Monitoring Configuration" settings, select "Custom Selection Mode" for active management of devices.
2. Click on "IP Address Range" in the "Devices Explorer" section on the left.
3. In the pop-up window titled "Add an IP Address Range," enter the starting IP address in the "Starting IP Address" field.
4. Enter the ending IP address in the "Ending IP Address" field.
5. Click "Add" to save the IP address range for monitoring by the Network Collector.
Add support for Big Dog Power PDU
In addition, we now support Big Dog Power on the PDU management feature.
Thanks to this enhancement, you will be able to toggle on/off the power outlets or power-cycle them.

Device Details and Control Panel Overview
1. The header shows "Big Dog PDU" with the device status as online, along with its IP address and location.
2. Tabs are available for Info, Connect, Alerts, History, SNMP, TCP, and Outlets.
3. For outlets control, each outlet can have a custom name added by clicking the plus button. Outlets are numbered 1 to 6, with toggle switches to control each outlet. The default state for outlets varies.
4. Acknowledge instructions with the "OK, got it" button when linking devices to plugs.
5. The "Actions" section allows exporting and importing device settings, or deleting the device.
6. The "Latest Events" section shows recent changes like IP change and device status updates (Went Up/Down) with associated timestamps.
7. For "Latest Connections," there's an option to connect via the Web Portal HTTP using port 80.
8. "Latest Updated SNMP Sensors" and "Latest Updated TCP Sensors" sections allow adding new sensors by clicking the plus button.
Enhancements
External Services integrations for external UniFi Controllers do not consume External Hosts
We have refined the integration process for external UniFi Controllers, ensuring that they do not consume External Hosts. This change optimizes resource allocation, allowing you to maximize the utility of your External Hosts without unnecessary consumption. Streamlining this integration enhances overall system efficiency and ensures smoother operations.
Rebrand EBERTLANG into Elovade
In alignment with strategic rebranding initiative, EBERTLANG and Achab are now Elovade. We have updated the logos on our webapp to reflect this change, providing a unified and modernized look.
Navigate directly from Ubiquiti Devices to the External Services page
Starting from now, any Ubiquiti devices (Controllers, Access Points, Switches, etc) now allow direct navigation to the External Services page, where the customers can configure the integration with such brands to unlock more data and capabilities on Ubiquiti devices.
This enhancement reduces the time spent navigating through menus and improves the overall efficiency of device management.
Increase Persistent Devices threshold
To meet our users’ growing needs, we have increased the threshold for Persistent Devices to 15 units. Additionally, the Booster Pack now supports an increase of up to 30 Persistent Devices each. This expansion provides users with greater capacity to manage their devices, ensuring that their networks can scale effectively as they grow.
Enhancements for Docker and Luxul Network Collector
Allow users to configure VLANs on Collector with proper subnet netmask (Docker, Luxul Network Collector)
We have introduced the capability for users to configure VLANs on Collector with the appropriate subnet netmask. This feature enhances network segmentation and management, allowing for more precise control over network traffic and improving overall network performance and security.
Fortilink devices discovery does not require Routed Network configuration (Docker, Luxul Network Collector)
Discovering Fortilink devices is now more straightforward, as it no longer requires Routed Network configuration. This simplification makes it easier for users to identify and integrate Fortilink devices into their networks, reducing setup complexity and improving the user experience.
Integration Scripts and Pre-Configured SNMP Templates
Integration Scripts
Windows Physical Disks
We have enhanced the existing “Windows Physical Disks” script to monitor the free space available and the disk usage percentage.
The script now enables you to monitor the following additional information:
- Free Space
- Usage (%)
The script uses the WinRM protocol and has been validated and tested on Windows 11 and Windows Server 2019.

Windows Physical Disks Monitoring Overview
1. The interface displays the status of physical disks on a Windows machine.
2. A status message indicates that the monitoring is "RUNNING," with a sample period of 5 minutes and 8 metrics consumed.
3. Under the "Physical Disks" section, a table lists disk details:
- "Id" shows the identifier as "\\physicaldrive0."
- "Model" specifies "WDC WD10JPVX-08J..."
- "Status" confirms the disk is "OK."
- "Size" indicates a total of "931.51 GiB."
- "Free Space" shows "628.5 GiB" available.
- "Usage" is represented as "32.5%."
- "Media Type" is "Fixed hard disk media."
- "Serial Number" is "WD-WX81A67RP8K3."
- "Partitions" number is "4."
Windows Static IP Monitor
Easily monitor whether a static IP is assigned to a network interface on Windows by applying this script. Extract more details about the following information:
- Network ID
- IP addresses
- Static flag
- Connection State
The script uses WinRM protocol and has been validated and tested on Windows 11.

Windows Network Interfaces Overview
1. The status of the Windows network interfaces is displayed as "RUNNING."
2. The sample period for metrics is indicated as "5 Minutes."
3. "Metrics Consumed" shows the number 3.
Network Interfaces Table
- The table lists network interfaces with columns for Id, IP addresses, Static, and Connection State.
- Under "Id," two network interfaces are listed: "ethernet" and "wi-fi."
- "IP addresses" for ethernet is "192.168.117.15," and for wi-fi are "192.168.103.15" and "169.254.1.15."
- The "Static" column indicates "No" for both interfaces.
- The "Connection State" shows "Yes" for ethernet and "No" for wi-fi.
VMWare vCenter Certificate Expiration
Apply the VMWare vCenter script to monitor the expiration dates and validity status of certificates used in your VMware vCenter environment. It specifically monitors Machine SSL certificates, VMware Certificate Authority certificates, STS Signing Certificates, and Trusted Root certificates within VMware vCenter.
Apply this integration script to monitor the following information about the vCenter certificates:
- Issuer
- Usage
- Expiry
- Remaining days
- Is valid
This script has been validated and tested on VMware vCenter version 8.0.2 and uses HTTP protocol for API communication and SSH for executing commands on the VMware vCenter server.

VMware vCenter Monitoring Certificate Status
1. The status section indicates that the monitoring of VMware vCenter certificates is currently "RUNNING".
2. The sample period is set to "5 Minutes", and it has consumed a total of "5" metrics.
3. Below the status, there is a table titled "Certificates" consisting of three columns: Id, Issuer, and Usage.
4. The Id column lists unique identifiers for each certificate. Examples include "d2:2b:f8:8d:8b:b4:b6:9d" and "d2cb03c0654d3455".
5. The Issuer column provides the source of each certificate, such as "VMware Engineering - localhost".
6. The Usage column details the purposes of each certificate, mentioning terms like "critical", "Certificate Sign", and "digitalSignature".
7. There is an option to "Download CSV" for exporting the certificate data.
Hyper-V Virtual Machines Integration Services
Monitor the following information about the services running on Hyper-V with this script:
- Service Name
- Enabled flag
The script uses the WinRM protocol and has been validated and tested on Windows Server 2019.

Windows Hyper-V VM Integration Services Overview
1. Check the status at the top, which indicates “RUNNING” in green. This shows that the integration services are active.
2. Note the sample period stated as “5 Minutes,” which defines the data collection frequency.
3. The parameters and metrics consumed are listed with values: Parameters as "1" and Metrics Consumed as "2."
4. In the integration services table, observe columns: Id, Name, and Enabled.
5. Each row provides service details: unique Id, service Name such as "Time Synchronization," and whether it is "Enabled” with Yes or No.
6. Use the “Download CSV” link on the right to download the table data in CSV format for further analysis.
MacOS General Information
Monitor the following information by applying this script:
- OS Name
- OS Version
- Build Number
- Machine Model
- Machine Name
- Architecture
- Serial Number
This Domotz script uses the SSH communication protocol to execute commands on the macOS. It has been validated and tested on macOS Version 14.5.

macOS General Information Monitoring Panel
1. The panel title reads "macOS - OS General Information" and describes that it monitors general information for macOS.
2. Status information is shown: the system is currently "RUNNING," with a sample period of "5 Minutes" and "Metrics Consumed" totaling 7.
3. A table displays system variables:
- "Architecture" is listed as "x86_64."
- "Build Number" is "23F79."
- "Machine Model" is "MacBookPro16,2."
- "Machine Name" is "MacBook Pro."
- "OS Name" is "macOS."
- "OS Version" is "14.5."
- "Serial Number" is "C02DV6UMML7L."
4. The "Last change" column indicates all entries were updated "a few seconds ago."
Cradlepoint NetCloud Network Device Status
You can use this script to monitor the status of a network device managed by Cradlepoint NetCloud Manager. You can monitor the following:
- Device model
- Device product
- Status
The script uses HTTPS protocol and has been validated and tested on Cradlepoint AER 2200.

Network Device Status Overview
1. The page is titled "Cradlepoint NetCloud Manager - Network Device Status" and provides monitoring information for network devices.
2. The status of the monitoring operation is displayed as "RUNNING."
3. Network Devices Status includes columns for Id, Model, Product, and Status of each device. Each column allows filtering options.
4. Device entries include:
- Id 37322195 with status "connected" and product "10/100/1000 Ethernet."
- Id 37322196 with status "standby" and product "Internal 600M (SIM1)."
- Id 37322197 with status "disconnected" and product "Internal 600M (SIM2)."
- Remaining entries show devices with status "unplugged."
5. Additional information includes a sample period of "5 Minutes," parameters value "5," and metrics consumed "3."
Pre-Configured SNMP Template
Brother Printer Status
Use this SNMP template to monitor the status of a Brother Printer.

Brother Printer Status Display
1. The section displays the status of a Brother printer.
2. A red circle with an 'X' indicates an issue with the printer.
3. Below, the word "Status" is followed by the color "green" in blue text, suggesting a normal or operational state.
4. Additional icons are present for expanded details or notifications.
MIBs
- AVPro Edge Network Switches MIB
- The MIBs that you shared a screenshot of here
Fixes
- Fix the issue that was preventing the creation of Monitoring Dashboard Tables for certain Integration Scripts, including Dell Power Vault SAN (System General) script.
- Fix issues on Configuration Management for HP Switches and Dell OS Devices.
- Fix the issue on the Unifi Access Point. There is broken radio information due to missing the RAM data point.
- Fix the issue preventing the load of Device Types on the Devices List after bulk edits are performed.
- Fix issue throwing errors when deleting Offline Device.
- Some icons were not displayed properly on the new version of Chrome 126.x.
- Fix issue for UK customers with VAT not being able to update their payment method from Portal.
- Fix the issue that was preventing customers with all expired/deactivated Network Collectors from accessing the WebApp.
- Fix the issue on the LAN Configuration Change alert when the Primary and Secondary DNS servers swap orders.
- Fix an issue on the Device Detail Interfaces tab where the Reachable Devices counter was inconsistent and did not always display all the reachable devices from that port.
- Fix the RSSI badge on the Device Detail that is not being rendered with appropriate colors.
- Prevent the Booster Pack modal from being opened multiple times from the Collector Settings page.