Running groovFinder from macOS may otherwise require starting a Windows virtual machine. The available evidence describes an unofficial macOS utility that can discover groov devices, but its limited testing, unsigned application bundle, and undocumented discovery traffic require a cautious deployment and verification process.
Compatibility and Support Boundaries
| Item | Evidence | Engineering decision |
|---|---|---|
| Minimum operating system | macOS 10.10 Yosemite or newer | Do not attempt installation on an earlier macOS release. |
| Tested operating system | Reported testing was limited to macOS 10.13 | Treat other releases as unverified and perform a discovery test before relying on the utility. |
| Vendor support | The macOS utility is not supported by Opto 22 | Keep a supported discovery method available for commissioning and recovery. |
| Application signing | The utility is not signed for Gatekeeper | Expect macOS to block its first normal launch. |
| WINE | A reported test did not run successfully | Do not select WINE as the fallback without separate validation. |
Launching the Unsigned macOS Utility
Because the application is unsigned, Gatekeeper may prevent the initial launch. Use the explicit macOS Open action only after obtaining the utility from a source your organization trusts.
- Confirm the Mac runs macOS 10.10 or newer.
- Right-click the application and select Open for the first launch.
- After the initial approval, launch the application normally.
- Run a device search and confirm that every expected groov device appears before using the utility during commissioning.
Discovery Traffic and Network Diagnostics
Network inspection suggested that discovery sends a 1024-byte UDP packet to port 2022 and waits for a response. However, the port was recalled rather than confirmed, the packet contents were reported as inconsistent, and no official protocol specification is present in the evidence. Treat these details as diagnostic hypotheses, not interface requirements.
If discovery fails, capture traffic from the Mac during a search and verify whether an outbound UDP datagram and device response are present. If no datagram leaves the Mac, investigate application launch and local network permissions. If the datagram leaves but no response returns, check the selected network interface, host and network filtering, and whether the Mac and target devices have a valid communication path. Do not implement a replacement discovery client from the observed packet size and tentative port alone.
Verification and Operational Use
Validate the result against the actual device inventory: compare discovered devices with the expected units, repeat the search, and confirm stable results. Because the utility is unofficial and minimally tested, retain the Windows virtual-machine workflow or another supported method until the macOS result has been validated on the specific macOS release and network.
FAQ
What macOS version does the unofficial groovFinder utility require?
The reported minimum is macOS 10.10 Yosemite. Testing cited in the evidence was limited to macOS 10.13, so validate later releases before operational use.
How do I open groovFinder when macOS Gatekeeper blocks it?
Right-click the unsigned application and select Open for its first launch. After that approval, it should launch normally.
Which UDP port does groov device discovery use?
Observed traffic was described as a 1024-byte UDP packet sent to port 2022, but the port was not confirmed and packet contents varied. Verify the traffic with a capture rather than treating those observations as a protocol specification.