Make sure the tables button is active. If the button is active make sure the window isn't resized to the bottom of the screen.

Check your DNS settings to make sure they are correct. If you don't have valid DNS addresses to use, you can always use google's defaults of 8.8.8.8 for the Primary DNS and 8.8.4.4 for the Secondary DNS.

Power cycle the controller and check to make sure you are running the most current version of the Command Center software.

To do this you must have polling turned on. In the Command Center software navigate to the graphing tab on the thermostat menu. This will show you a graph of the data that is being logged for the thermostat. If you wish to export the data click the button labeled show large graph. When the larger graph pops up click the button labeled export to the left of the screen. You may then name the file and export it as a .csv.

In the event of a power outage or power surge, the thermostats may reset and go back to address 1. Check the thermostat addresses by holding the mode and fan buttons simultaneously for twelve seconds, this will show the address of the thermostat. Multiple thermostats with the same address will cause the controller not be able to communicate with them. In this case, set the thermostats back to the correct addresses. If you do not find a solution to the issue in this FAQ section, contact support.

A power surge may damage the network controller and/or the thermostats. Check the NT-IPXB controller and make sure it has information scrolling across the LCD. Try logging in to the controller via IP address in a browser and see if it is showing up. If it is showing up, make sure all the settings are correct. If all settings are correct, try doing a power cycle on the controller. If it is still not connecting, check the thermostats to make sure there is not a bad thermostat in the chain (XBus) somewhere by pulling off the faceplates one by one and see if the connection re-establishes during this process. You may also check the X1 and X2 terminals to make sure they did not get shorted out. If you are still having issues you may have a damaged controller, contact support for further troubleshooting.

For Single User Applications:
1) Install ONE copy of the Net/X Command Center on a PC, virtual machine or Windows-based server.
2) Up to 500 thermostats can be in a single project file
3) MULTIPLE INSTANCES of the NetX Command Center MAY BE RUN SIMULTANEOUSLY on the same PC, virtual machine or Windows-based server, AS LONG AS THERE IS NO CONTROLLER/THERMOSTAT IN MORE THAN ONE PROJECT FILE that is open at the same time. It is required that the user manage this.

For Multi-User Applications:
1) Install ONE copy of the Net/X Command Center on a PC, virtual machine or Windows-based server.
2) Up to 500 thermostats can be in a single project file
3) MULTIPLE INSTANCES of the NetX Command Center MAY BE RUN SIMULTANEOUSLY on the same PC, virtual machine or Windows-based server, AS LONG AS THERE IS NO CONTROLLER/THERMOSTAT IN MORE THAN ONE PROJECT FILE that is open at the same time. It is required that the user manage this.

If multiple users need access to the Net/X Command Center, it is highly recommended that it be installed on a server and only ONE user be active in a project file at a time.

For Applications Needing Simultaneous Access via Multiple Users:
1) Use the NetX-Web.com Web Environment

Log in to the device via the IP address. Go to the configuration tab and fill in at least the zip code and the state and click apply.

There are two ways you can set the time on your NT-RELAY. The first option is to set the time through the Command Center software. Depending on which version of the Command Center you are using the menu will vary slightly. First select the tab at the top of the screen labeled tasks. From the drop down menu you will either select set controller clock or set relay clock. You will get a pop up that will ask if you want to sync the time. Click okay to set the time.

The second way to set the time on your NT-RELAY is to go the IP address of your relay followed by /setup.html. Select the tab labeled date/time at the top of the screen. From there you will be able to sync the time with an .ntp server or set the time manually.

This depends on what you are looking to do and what hardware you have. If you are using the StrongMesh/XBus system and would like to keep everything on a LAN, the Command Center would be your preferred solution. If you want to be able to access the Command Center from multiple places you can set up a VPN to the machine running the Command Center. Alternatively if you do not wish to setup a VPN and still want to be able to access your setup remotely you can sign up for the netx-web service. You may also access your system remotely in the Command Center using the WAN IP addresses of your controllers.

If you are using our Wi-Fi or Ethernet thermostats and want to connect using a LAN you will want the NetX-IP Command Center. You may also setup a VPN for the IP Command Center to access it from multiple places. If you want to connect through the WAN there are multiple options available. You can use the direct connect service by claiming your device and logging into the DirectConnect page on the Network Thermostat website.  There is also the CloudConnect service that will allow you to connect using the Cloud. Finally you can use the WAN IP addresses in the IP Command Center to access the system remotely.

For more information, feel free to contact a solutions specialist to help you work through the wide array of options.

Yes, as long as you are using a supported OS.