How to find a Kaleidescape server with unknown IP

Use a computer with a Windows operating system. (The following steps are for Windows XP, 7)

  1. Connect the computer by an Ethernet patch cable to the same switch as the Kaleidescape server. A wireless connection will not work.
  2. Disable any firewall.
  3. Check that NetBIOS name resolution is enabled. If not, install Bonjour Print Services for Windows according to the instructions at
  4. On the computer, select Start > Settings > Network Connections > LAN. The LAN Status window appears.
  5. Click Properties. The LAN Properties window appears.
  6. In the LAN Properties window, scroll down the list of items and select Internet Protocol (TCP/IP). Click Properties. The Internet Protocol (TCP/IP) Properties window appears.
  7. Take note of the settings in the Internet Protocol (TCP/IP) Properties window. You will change these settings, and then undo the changes.
  8. Click Use the following IP address and type for IP address and for Subnet mask. Do not change any other fields.
  9. Click OK. The Internet Protocol (TCP/IP) Properties window closes.
  10. Click Close in the LAN Properties window.
  11. Click Close in the LAN Status window, if still open.
  12. Check that the Kaleidescape server is powered on and connected to the network switch; the server front panel should glow blue.
  13. Find the serial number of the server.
  14. The link local address of the server is ll- followed by the 12-character serial number of the server. Here “ll” is two instances of the letter l. For example, if the server serial number is 0000 0001A2B3, then the link local address is ll-00000001A2B3. Enter http://ll-00000001A2B3 in a web browser. The browser interface should appear.
  15. In the browser interface, select the SETTINGS tab, then select Components in the second row of tab. Click the Settings button for the server. The Network Settings window appears. Configure the network.
  16. After the Kaleidescape System has been configured, undo the link local address. The link local address is not suitable for normal operation. To undo the link local address, select Start > Settings > Network Connections > LAN on the computer. In the LAN Status window, click Properties. In the LAN Properties window, select Internet Protocol (TCP/IP) and click Properties. Reset the settings in the Internet Protocol (TCP/IP) Properties window to the original settings previously noted. Click OK, then click Close in the LAN Properties window.
  17. The procedure for Mac users is similar, but append “.local” to link local address, for example, http://ll-00000001A2B3.local.

Advanced logging not using Composer

This is a Control4 knowledgebase entry, compressed to the imported facts

Composer logging is good for issues that you can reproduce on the fly. If you have an issue that is random and sporadic then Composer logging is not the best option

Using the command c4log you are able to enable logging on any service running on the device. This will save the log on the device under the /log/debug directory. It will create a text file that will fill upto 1 mb (megabyte). Once it gets to 1 mb it will zip that file into a .gz (gzip) file. Then start a new text file that will fill to 1 mb again. Then also will create a gzip file with .2.gz on the extension. It will create a max of 5 .gz files. Once there are 5 .gz files it will overwrite the 1.gz file and next the 2.gz and so on.. (logging zigbee will create a total of 20 .gz fi les.)
Activate/deactivate the log process:

  1. Login to the Controller by using openssh. Ask Google where to download:
  2. install openssh
  3. Open the windows command prompt and type ssh -l root (Enter button)
    (For sure replace the IP with the one of your Controller)
  4. Accept the warning by typing “yes” and copy and paste in the password: t0talc0ntr0l4!
  5. In the command prompt type c4log (Enter button) and you see the list which services can be log’d:
    •     all
    •     amgserver
    •     audio
    •     c4lookup
    •     c4rmengined
    •     daemon
    •     dhcp
    •     director
    •     dtserver
    •     intercom
    •     ioserver
    •     kernel
    •     mp3d
    •     navigator
    •     netusbserver
    •     performance
    •     raproxyd
    •     ripd
    •     sipproxy
    •     sysmand
    •     upman
    •     zap
    •     zserver
  6. To start the logging use the command c4log enable (service).
  7. To stop the logging use the command c4log disable (service).

To have a look to the log process youo can use the command tail to any file that is logged in /var/log/debug. Example: tail -f /var/log/debug/director.log

If you need to send the logs to someone you can locate the logs from SAMBA share of the device.