Integration Driver mDNS advertisement
The Remote Two uses mDNS discovery to look for local integration drivers on the same network.
If an integration driver shall be discoverable, it needs to advertise the driver service using multicast DNS:
- Service type:
_uc-integration._tcp
- Instance name: unique identifier of the integration driver (
driver_id
in the API model).
TXT Record
Additional information is published in the TXT record.
Key | Required | Format | Description |
---|---|---|---|
name | x | text | Integration name |
developer | x | text | Developer or company of the integration |
ver | x | text | Integration version number |
ver_api | text | Implemented integration API version | |
ws_url | text | Override the WebSocket url. ws_path, wss, wss_port will be ignored | |
ws_path | text | WebSocket endpoint path. Default: / | |
wss | bool | Use secure WebSocket connection | |
wss_port | number | WebSocket SSL port if different from published port, or driver supports ws & wss connections | |
pwd | bool | Access token required |
Examples
Node.js
Using bonjour-service:
const { Bonjour } = require('bonjour-service');
const bonjour = new Bonjour();
bonjour.publish({
name: 'my-driver',
type: 'uc-integration',
port: 1234,
txt: {
name: 'My Driver',
ver: '1.0.0',
developer: 'Foobar Inc',
ws_path: '/ws',
pwd: 'true'
}
});