Search the Community
Showing results for tags 'remote connection'.
Found 2 results
Hello, Here's how to connect to a remote QSC Q-Sys Core via Domotz. These directions and the attached script are based off the Extron from remote thread. I've modified the script to work with the ports Q-Sys uses. Q-Sys Instructions 1. Select the Q-Sys Core from the Domotz WebApp → Device list → Device 2. Go to "Connect" tab 3. Click on "Open a TCP tunnel" 4. Insert the TCP Port. By default you will need to open 3 tunnels for the following ports: 80, 1700 and 6504. 5. Wait to have the tunnel setup 6. Repeat steps 3 and 4 for each port. 7. You will have a host and a port for each TCP Tunnel (see the Extron thread linked at the top for screenshots). 8. Open the .bat file as Administrator (see link below) and enter the requested information on the screen. 9. Add a hard link within Q-Sys Designer following QSC's documentation and use the loopback address you chose (e.g. 127.0.0.100). Note: Make sure the mode is set to HTTP. You should see it turn green. 10. Click OK, then File -> Load from Core & Connect and you should see the Core listed there to connect to. Domotz Q-Sys Connect.bat
This change log covers what's changed in Domotz Pro service since previous Release Notes. These changes include Domotz Pro cloud, Domotz Agent and Domotz Pro App. Since previous Release Notes new versions of Domotz Agent and Domotz Pro App have been released. In order to fully exploit the new features, functionalities and bug fixes released, please make sure you have installed the latest version of Domotz Pro Mobile App: check on Apple Store or Google Play. Latest version as of today is 1.5.13 Domotz Agent: check on Domotz Portal under the subscription tab. Latest version as per today is 1.5.0 Violet Digital Support: check on Apple Store or Google Play. Latest version as of today is 2.2.4 Domotz Pro WebApp is already updated to the latest version. November 19th, 2017 Domotz Pro App: 1.5.13 - Domotz Agent: 1.5.0 Violet 2.2.4 What's new: New Payment System: Domotz Portal now have a better online store. For orders made after November 1, you will also be able to retrieve invoices directly online. Sonos tab on Sonos device details, which: shows connection type and status, WiFi strength, player status allows to permanently disable Wi-Fi when the Sonos device is also connected through Ethernet Customer ID and search functionality: Domotz Pro users can now associate an arbitrary ID to any single site/customer so that they can be associated in their proprietary CRM system and searched across Domotz Portal and WebApp Daily Alert Digest: Domotz PRO users can now schedule a daily email that summarize all triggered alerts in the previous day Improvements: Control4 Tile: Multiple Control4 controllers are now supported New Luxul PDUs (PDV-1608, PDV-908, PDV-202) supported PS Audio PDU (IPC-9000) supported (enable SNMP for full support required) Megatec PDU supported APC Smart-UPS supported Ruckus/Brocade PoE switches supported Midspans PoE switches supported HP PoE switches supported Device model displayed directly on device list in case no better name is available Enhanced Note field within the Customer Management tile Debian Agent package can now be downloaded directly from the Portal FIX: Uptime in Domotz report ELK Product identification SNMP OID trigger emails are now correctly dispatched Report emails are now also delivered to email servers not allowing long single-line text Known limitations: Simultaneous Remote Connections might override each other in terms of cookies Eyes configured for deleted devices affect the total counting of Eyes Devices with multiple network interfaces (multiple MAC address) can't be merged into single device Field Operators can't set alerts on Domotz Eyes (SNMP Custom OID and TCP Services monitoring) Important offline Devices with custom down period configured are wrongly calculated in the global overview. This should be fixed by end of November 2017