This page will be updated every week during this month.
Items marked as Beta are part of an early access program. Contact us to learn more or request access.
Items marked as Limited are available to a subset of customers. Contact support to learn more.
Items marked as Coming Soon are in development and not yet available.
September 16, 2026
New Features & Improvements
Collectors Page
- Organizations on the Collectors page — Each Collector now shows the organization and organization ID it belongs to, and the list can be grouped and sorted by them, so a large fleet can be arranged the way it’s organized.
Public API
- Public API documentation — The endpoints for managing a Collector’s default SNMP authentication have moved to the Collector section of the Public API documentation, alongside the other Collector endpoints.
Coming Soon
The following are in development and not yet available.
- Autotask asset management — An Autotask documentation and asset management integration will bring the devices a Collector discovers into Autotask, the way the IT Glue and Syncro integrations already do.
- Collaboration for RBAC — You’ll be able to invite someone from a different Domotz account to collaborate on your own — even if they already have their own Domotz account — and grant them exactly the permissions and Collectors you choose.
- Rediscover a device — A new Rediscover Device action will clear the data a Collector discovered about a device and run discovery again from scratch. Configuration and history will be kept, and the action will be recorded in the audit log.
Bug Fixes
Integrations
- Fixed: Software Reboot is now available from the Info tab of a UniFi device. It previously lived only on the Controller tab, which isn’t shown when the UniFi integration is set up with an API Key connection, leaving those devices with no way to be rebooted from Domotz.
- Fixed: Changing the ConnectWise board an integration points to now also applies the newly selected default closed status, so automatic ticket closing no longer fails and tickets are no longer left open.
- Fixed: The Controller tab of a UniFi controller now shows site and network data instead of staying on a discovery-in-progress message, so a Cloud Key or UDM Pro whose controller outlet wasn’t listed last no longer appears stuck in discovery.
Device Management
- Fixed: FortiGate firewalls are now classified reliably after their SNMP data is collected, so Configuration Management is offered on them.
- Fixed: Deleting a device now also clears its Wake-on-LAN entry, so the Collector no longer keeps sending magic packets to a MAC address that no longer belongs to any device.
- Fixed: Aruba Instant access points are now recognized correctly, since they respond to SNMP rather than HTTP.
- Fixed: A newly discovered device is now typed from its SNMP data when that contradicts the passive fingerprint, so a switch that identifies itself over SNMP is no longer listed as a NAS.
- Fixed: FortiLink-managed switches behind a FortiGate are discovered and mapped again, restoring their uplink and downstream connections in the topology map.
Topology
- Fixed: The topology map draws the gateway and Internet root again when it’s opened right after another page in the side menu, instead of rendering the rest of the network without its root.
- Fixed: The topology map no longer shows the wrong neighbor on a switch port when the LLDP chassis address advertised by the connected device isn’t already known for it.
Public API
- Fixed: The Public API endpoint that lists the alert rules applied to a Collector no longer returns a 404 error for accounts with alert rules enabled and bound at Collector level.
RBAC & Organizations
- Fixed: Bulk editing users can no longer remove the Account Owner from the Administrators group, so an account always keeps an administrator with full access.
- Fixed: User management no longer reports that an email address has no matching Domotz account, completing the removal of messages that could reveal whether an address is already registered.
Audit Log
- Fixed: The audit log no longer shows internal, backend-only entries, so the list stays limited to actions you can actually act on.
Mobile App
- Fixed: The Remove All Offline Devices button is docked at the bottom of the device list again, instead of appearing between device rows.
- Fixed: The scan method of a routed network (Ping or TCP) is readable again on Android and iOS — the label was previously hidden underneath the Edit button.
Domotz Collector
Network Collector 9.3.2 — Domotz Box
- SNMP template device properties are now supported on the Collector side.
- On-demand remote connections are now supported on BusyBox-based routers such as Netgear and Luxul.
- Fixed: A rapid crash loop that used to leave the service permanently stopped now recovers on its own.
- Fixed: The stall watcher now retires itself when a new listener takes over.
September 9, 2026
New Features & Improvements
MCP
- Device profiles — You can now create, read, update, and delete device profiles via MCP, so a monitoring standard can be defined and rolled out across a fleet without opening the app. Configuring individual modules within a profile isn’t supported yet.
- Discovery and port scanning controls — Device discovery and a Collector’s port scanners can now be switched off and back on via MCP, exactly as in the app, so scanning can be paused on a sensitive network from your MCP client.
- Remote access — You can now open a remote tunnel to a device via MCP and get back a link to a browser-based remote session, so a device can be reached directly from the conversation that diagnosed it.
- Additional Collector settings — More Collector settings — like Local Web Interface access and Round Trip Delay Monitoring — can now be configured via MCP.
AI Assistant
- Rate the AI Agent’s answers [Limited] — Replies in AI chat can now be marked helpful or not, so the AI Agent can be tuned against real feedback.
RBAC & Organizations
- Scope a role by Organization ID — Roles can now filter Collector access by Organization ID as well as by name, making it easy to grant access across every Collector under a given organization.
- Warning when a user has no group — Adding or editing a user without selecting a group now warns you before saving, since a user in no group is left without access.
Drivers
- New monitoring drivers — Added monitoring for Logitech CollabOS video conferencing devices, Shure ceiling microphones, and Epson projectors over PJLink.
New MIBs
- New MIB support — Added SNMP monitoring for Tycon Systems PoE switches and Rubrik appliances.
Other Improvements
- Redesigned Zigbee and Cresnet device screens — The Zigbee and Cresnet device screens have been rebuilt to match the rest of the app.
- Up-to-date Domotz Box links — The purchase links in the Add Collector dialog now point to the new Domotz Box.
Coming Soon
The following are in development and not yet available.
- New SNMP templates — SNMP monitoring templates for UCD-SNMP-MIB and LM-SENSORS-MIB will cover CPU, memory, disk, and hardware sensor readings on Linux hosts and appliances that expose them.
Bug Fixes
AI Assistant
- Fixed: The AI assistant chat can now be used while the Add a Collector dialog is open — it used to open behind the dialog and couldn’t be typed into.
RBAC & Organizations
- Fixed: A dynamic group filtered by Organization ID now returns the Collectors of organizations carrying that ID, instead of returning none at all.
- Fixed: Creating, inviting, or deleting a user no longer reveals whether that email address already belongs to an account.
- Fixed: Checkboxes in Access Management no longer lose their arrows and icons for a moment when clicked.
Alerts
- Fixed: The confirmation dialog shown when deleting or cloning an alert rule now describes the action it’s actually confirming.
Device Management
- Fixed: Adding a custom driver that needs device credentials to a device that has none now asks for those credentials as part of setup, instead of failing with no way to proceed.
- Fixed: The Alerts tab on a device now labels driver-based alerts “Drivers,” matching the naming used everywhere else.
- Fixed: The Add Collector dialog now opens at its intended width, instead of being squeezed into a narrow column.
- Fixed: Device Profiles now honor the device visibility restrictions of the user applying them and can target devices through a custom filter, along with a round of interface corrections.
- Fixed: An ONVIF camera whose firmware rejects one optional ONVIF request is no longer discarded during setup — a camera that reports valid video profiles now gets its ONVIF driver and Camera tab instead of going unrecognized.
Monitoring
- Fixed: The IP conflict history of a device shows the full details of each conflict again, not just that one occurred.
Audit Log
- Fixed: Basic authentication credentials are no longer visible in audit log entries.
- Fixed: Downloading a Windows Collector installer no longer adds an audit log entry for the internal API key embedded in it, which you never see and can’t act on.
Integrations
- Fixed: A site can be linked to ConnectWise again — linking used to fail with a “not found on remote” error even when the site existed.
Topology & Discovery
- Fixed: A routed network defined as a single host is now recognized as a routed network everywhere, including on discovery retries — it used to be treated as an external host, so it was TCP-scanned even with Advanced TCP Scan off, and a host that stopped responding never moved to offline.
- Fixed: A Linux Collector no longer stops discovering when its network scans time out — discovery, IP conflict detection, and interface binding all work again.
- Fixed: An external host reached over a lossy link no longer flaps between online and offline, which was triggering repeated false alerts at every site monitoring it.
Domotz Collector
Network Collector 9.2.0 — Windows, Docker, Synology, Linux Snap, and Domotz Box
- Fixed: Collectors on some networks no longer suffer intermittent connectivity to the Domotz cloud — the TLS handshake now fits in a single network packet instead of stalling when split.
- Fixed: A Windows Collector no longer reports an offline period far longer than the update that caused it — monitoring resumes as soon as the scheduled update finishes.
- Fixed: A Windows Collector no longer crashes when external-host checks and discovery together start more scan processes than the system can handle.
- Fixed: Custom driver inspections no longer fail en masse on Collectors with many devices — a watchdog was stopping busy (not stuck) drivers, and driver schedules are now spread out instead of all starting at once.
September 2, 2026
New Features & Improvements
MCP
- Power on and off — Individual PDU outlets and PoE ports can now be switched off and back on via MCP, not just power-cycled, so a device can be deliberately powered down and brought back up later.
- Collector SNMP defaults — A Collector’s default SNMP credentials and polling period can now be read and changed via MCP, so a site can be prepared for SNMP monitoring without opening the app.
Public API
- Alert identifier in webhook payloads — Alert webhook payloads now include a unique identifier for the alert, so a receiving system can correlate deliveries with the alert that produced them and recognize repeat notifications.
- Collector SNMP defaults via the Public API — The same default SNMP credentials and polling period can now be configured programmatically through the Public API, for provisioning a fleet of Collectors from an external system.
Coming Soon
The following are in development and not yet available.
- Collaboration for RBAC — You’ll be able to invite someone from a different Domotz account to collaborate on your own — even if they already have their own Domotz account — and grant them exactly the permissions and Collectors you choose.
Bug Fixes
Alerts
- Fixed: An alert rule on a driver or SNMP variable now triggers no matter where it was applied from — previously, rules bound through a device profile or the device Alerts tab weren’t firing, even though the same rule applied directly from the variable table was.
- Fixed: Applying an alert rule from a filtered device table now binds it only to the devices the filter actually shows, instead of spilling over onto other devices — and rules that had already been applied no longer disappear from the list intermittently.
RBAC & Organizations
- Fixed: An API key created for MCP by a user with limited permissions is now scoped to that user’s own permissions, instead of inheriting the full permissions of the account owner.
- Fixed: The built-in Team Member role no longer has access to the audit log by default — only Administrators and the Account Owner get it by default, though the permission can be extended to other roles via RBAC.
- Fixed: A Field Operator can no longer open, edit, or apply device profiles, and permission checks on the alerts contained in a profile have been corrected.
- Fixed: Loading the monitoring table no longer fails with a permission error for users whose role does grant access to it.
- Fixed: Creating a user with the email address of a previously deleted one now works — a stale cached entry was still being served.
Device Management
- Fixed: Device profiles that had been created are listed again — they had stopped appearing, and a new profile couldn’t be created reusing one of those names.
- Fixed: Restored the tabs that were missing from the Collector Dashboard.
- Fixed: The selection checkboxes for bulk device actions on the Inventory dashboard now work correctly.
- Fixed: Turning off Advanced TCP Scan on a routed network now actually stops TCP port checks against its devices, instead of continuing to probe ports 80, 443, and 3389.
- Fixed: IP cameras from a number of manufacturers are now recognized as ONVIF devices during analysis, so the ONVIF driver is applied and their details and streams are collected.
- Fixed: A Windows Collector no longer reports an offline period far longer than the update itself when its scheduled update task restarts the service.
- Fixed: A crash of the Windows Collector under heavy external-host and discovery-check load, which previously took the whole Collector down.
- Fixed: SNMP templates included in a device profile are now applied when the profile is applied to an External Host device.
Monitoring
- Fixed: An External Host monitored by ping only now goes down when it stops responding, instead of staying up indefinitely once its first check succeeded.
- Fixed: Custom driver inspections no longer fail in bulk on large Collectors — a watchdog was mistakenly terminating busy (not stuck) driver sandboxes, failing every inspection running in them.
Audit Log
- Fixed: Creating a monitoring profile is now correctly recorded in the audit log.
Have questions? Contact our support team at support@domotz.com