Check the power supply to ensure the thermostat is getting the proper voltage (about 24 volts). The red wire from the backplate and the red wire from the thermostat cable must both be in the R terminal. The black wire from the backplate and the common (color varies) wire from the thermostat cable must both be in the 24V(c) terminal.
FAQ
General
All of our thermostats are powered by 24VAC and they all require a common wire. If you do not have a common wire you can purchase the NT-PWIRE and it will give you a common wire. Alternatively, you can purchase a 24VAC power supply and plug it into an outlet.
Yes! There are several methods. You can integrate our software into your automation system via our API.
You can find the manual for all of our devices on the products page. Go to the desired device and look under the "Docs" tab. Note: If you have an older device that is no longer in production contact support for a copy of the manual.
All schedules must be in chronological order even if the schedules are inactive.
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 set up 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 set up 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.
We support all browsers supporting html5, however, as browser updates are released very quickly, if you experience usage issues with one browser, please try a different browser.
Yes, the NT-BAS device will allow integration with any BACnet system. As your company grows and adds further automation the NT-BAS will seamlessly integrate with additional systems.
Yes, as long as you are using a supported OS.
Yes, the NT-TEMP is required for remote sensing. NetX thermostats use an advanced remote sensor bus which has active electronics, not just a passive temperature sensor.
We do not currently support IPv6. If the demand for IPv6 increases we will implement it in our products, however at the moment it is not necessary.
Press and release the up and down arrows simultaneously.
You can find the manual for all of our devices on the products page. Go to the desired device and look under the "Docs" tab. Note: If you have an older device that is no longer in production contact support for a copy of the manual.
Adaptive Recovery ensures the area to be conditioned is at the setpoint at the beginning of a schedule.
Smart Schedule Recovery is a staggered HVAC start to prevent energy spikes at the beginning of a schedule or when recovering from a power loss. This is a great money-saving feature for commercial applications using NetX thermostats since peak demand loads can be very expensive.
Try using a different web browser (like Firefox or Chrome).
Wi-Fi Thermostats
Check the power supply to ensure the thermostat is getting the proper voltage (about 24 volts). The red wire from the backplate and the red wire from the thermostat cable must both be in the R terminal. The black wire from the backplate and the common (color varies) wire from the thermostat cable must both be in the 24V(c) terminal.
You must first register your thermostat under the configuration tab in either a browser or the Command Center. The information you used to register your device will be your login for the CloudConnect site. If you have more than one thermostat it is recommended that you register all of them with the same credentials.
Remove the faceplate then press and hold the “Setup” button until the LEDs flash then, do three short presses. The LEDs will go off and the thermostat will reboot. After this is done the thermostat will be back to the factory settings.
From the PC software, Cloud Connect, or directly from the IP address of the thermostat in a browser go to the schedules tab. Check the active box above the schedule number then set the time you would like the schedule to start. Enter the setpoints you would like the schedule to reflect, the cool temperature will be the maximum temperature that will be reached before the air conditioner will turn on and the heat temperature will be the lowest temperature that will be reached before the heat will turn on. Select whether the room will be occupied or unoccupied during this time and set the mode and fan to your desired setting. Click the “apply” button in the lower right corner to save the schedule.
It is recommended to have the schedules in chronological order. You may then copy the schedule to any additional days you want to have the same schedule. To do this you select the day of the week you would like to copy from the tabs at the top of the menu. Once you are on the correct day click the checkbox(es) for the day(s) you wish to copy down at the bottom of the menu. Click the “apply” button to save the changes you made.
Go into the configuration settings and select the time and date settings. Uncheck the "Sync Clock Automatically" checkbox and check the "Set Clock Manually" checkbox. Then you will be able to change the time to whatever you want.
This could be for either of two reasons. If the thermostat is being used on a Fahrenheit scale, the Up and Down buttons may have accidentally been pressed at the same time, which changes the display to Celsius mode. To correct this, press and release the Up and Down buttons simultaneously again. Another reason could be that the temperature sensor has been bent. Pull off the faceplate and check the thermistor to see if it is damaged or bent over. The thermistor is a little device sticking up in the bottom right of the circuit board, it will be either blue or black. Make sure it is not damaged and is standing up straight off the circuit board.
Windows 8.1 and 10 have disabled the feature to connect to ad hoc networks from the network browser. There is a workaround to allow ad hoc networks to be created which can be found here.
Make sure the thermostat is out of the ad-hoc network state (netx-setup) and on the network you are connected to.
Make sure that you have set up an account and that it is not expired. Make sure you are entering the correct email and password. If you cannot remember your password hit the "forgot password" button on the login page. If you have confirmed that the login credentials are correct, contact support and let them know you are having an issue.
Yes, however, you will need to purchase an NT-PWIRE which will take your four-wire system and convert it to five wires allowing you to have a common. You can purchase the NT-PWIRE at networkhvac.com.
If you would like individual readouts from each NT-TEMP, you will need probes connected to them via the Aux terminals and set them up as AUX devices.
With the faceplate connected to the backplate, look through the top vents of the backplate. If you see a red LED illuminated on the backplate then the backplate and faceplate are not communicating. If you do not see a red LED on then the backplate and faceplate are communicating.
Yes! There are several methods. You can integrate our software into your automation system via our API.
You can find the manual for all of our devices on the products page. Go to the desired device and look under the "Docs" tab. Note: If you have an older device that is no longer in production contact support for a copy of the manual.
If your equipment is 2-stage, first make sure your DIP switches are set correctly to allow second-stage operation. In order to bring on the second stage faster than the efficient fuzzy-logic algorithm (about 15-20min after the first stage, if needed):
1) set the heating or cooling setpoint at room temperature and let the display return to normal operation.
2) move the heat or cool setpoint up or down three degrees. After normal protection time-outs have been satisfied (2 or 4 minutes depending on your configuration), the thermostat will start the first stage.
3) Once the first stage is running, adjust the setpoint three more degrees in the same direction. The second stage will start.
This method bypasses the thermostatic control algorithm for this single heating/cooling cycle.
There is currently no native app set up in the App Store. However, each Wi-Fi and Ethernet thermostat has a built-in set of web pages with responsive design. The responsive design will automatically detect that you connected to the thermostat with an iPhone and show the thermostat pages in a manner that looks like a native app; it's called a web app. Additionally, both the CloudConnect and DirectConnect environments are of responsive design and have built-in web app features including connection for all of your thermostats, even multiple sites, right from a single mobile screen. You have the option of using the free DirectConnect service and port forwarding your devices or using the CloudConnect service without needing to port forward. Both methods allow a simple icon to be added to your home screen, giving you a single-tap launch for access to all of your thermostats.
We support all browsers supporting html5, however, as browser updates are released very quickly, if you experience usage issues with one browser, please try a different browser.
Yes, the NT-TEMP is required for remote sensing. NetX thermostats use an advanced remote sensor bus which has active electronics, not just a passive temperature sensor.
You will only need to port forward your thermostats if you are going to try to access them from outside the LAN and want to communicate directly with them. If you are unfamiliar with how to do port forwarding you can go to portforward.com for step-by-step instructions. If you cannot find instructions on portforward.com for your router refer to the user's manual or another online source for instructions. If you are planning to use the CloudConnect service you do not need to port forward your devices to access them from outside the LAN via the cloud service.
Look at the backplate with the faceplate off. There are two LEDs on the PCB, a green LED, and a red LED. If the green LED is off then the thermostat is not communicating with the WiFi network. If the green LED is blinking then the thermostat is in ad hoc mode and is ready to be put on your local network. If the green LED is solid then the thermostat is on the network and communicates.
Another way to see if your thermostat is communicating with the network without taking the faceplate off is to look at the LCD display. For newer backlight versions, the display will show a radio tower if the thermostat is in ad hoc mode, signal bars if the thermostat is on your network, and if there is neither the thermostat is not connected to a network and not in ad hoc mode. The signal bars do not indicate signal strength, only that there is a signal being detected. On older generation non-backlight thermostats, the display will show a satellite icon if the thermostat is in ad hoc mode, satellite+lightning bolt icons if the thermostat is on your network, and if there is neither the thermostat is not connected to a network and not in ad hoc mode.
Go to the configuration page in the thermostat settings and look for the box in the second row down labeled "Override Timer". Set the amount of time for an override. If you check the "Hold Override Until Occupied" box, the override changes will stay in effect until the next occupied schedule occurs.
To switch from Direct Connect to Cloud Connect you simply need to purchase a subscription to the cloud service and login using the same email and password that you used to claim the thermostat.
To change the password, access the thermostat and click on the Configuration tab. Down in the bottom right corner, there is a box labeled Password, enter the new password you want and click the Apply button.
To change the password go to the basic configuration page in either the IP Command Center or directly through IP address in a browser. From the configuration page enter the new password you wish to switch to and click the register thermostat button. If you are using the IP Command Center the software will prompt you to re-enter the new credentials to log in to the thermostat.
Press and release the up and down arrows simultaneously.
In your web browser address bar enter the thermostat IP address followed by “/configcc.htm”. Clear the text boxes following “Server” and “Port”, then set the value in the box following “Interval” to 0. Press the “Update” button on the bottom of the menu and the values will save.
To register your device you will go to the configuration tab and fill in at least the state and zip code under the address field. After you have filled in the address information hit the "Apply" button next to the "Contact" box. Then you will enter your email address and put in a password to create login credentials. After you have filled in the login credentials boxes hit the apply button. The page will refresh and ask you to log in using the information you just changed. You have now claimed your device.
This can be done by using our Cloud Connect service. The Cloud Connect service allows access to multiple thermostats via any web browser and mobile device. You can set different passwords to allow limited access to specific users.
Click the link below the log in fields labeled "forgot your password".
To remove a thermostat from your project file right click on the device in the tree on the left and select 'Remove'.
You can find the manual for all of our devices on the products page. Go to the desired device and look under the "Docs" tab. Note: If you have an older device that is no longer in production contact support for a copy of the manual.
Yes, there are several ways to access WiFi and Ethernet thermostats on different networks from one place. This can be done using our CloudConnect service, DirectConnect, a web browser via WAN IP address, or through the IP Command Center using external IP addresses.
In unlocked mode, if the thermostat is run without setting the time the override will run until manually changed or until the clock is set and schedules start running.
In locked mode when the thermostat is run without setting the time the override will last for the duration of the override timer (set in the basic configuration). The default override timer is 8 hours. Once the override timer has expired the thermostat will revert to the non-override manual setpoints.
There is not currently an Android app available, however, each Wi-Fi and Ethernet thermostat has a built-in set of web pages with a responsive design. The responsive design will automatically detect that you connected to the thermostat with a mobile device and show the thermostat pages in a manner that looks like a native app; it's called a web app. Additionally, both the CloudConnect and DirectConnect environments are of responsive design and have built-in web app features including connection for all of your thermostats, even multiple sites, right from a single mobile screen. You have the option of using the free DirectConnect service and port forwarding your devices or using the CloudConnect service without needing to port forward. Both methods allow a simple icon to be added to your home screen, giving you a single tap launch for access to all of your thermostats.
Sometimes WiFi thermostats are placed on the edge of the signal range, this can cause intermittent connectivity. Alternatively, obstructions of the thermostat signal is also a factor, anything that could potentially block the signal such as metal cabinets, large mirrors, or very thick walls could have an impact on how well the signal gets through. The easiest way to fix the issue may be to add another wireless access point and put it in between the router and the thermostat to boost the signal.
The default setpoints upon first powering the thermostat on are:
Cooling - 76 F
Heating - 68 F
Mode - Auto
A static IP address is an address that does not change. Alternatively, a dynamic address via DHCP (Dynamic Host Configuration Protocol) is an address that is assigned by the router and may change based on any of several parameter settings in the router, including lease time or if the router/access point resets. Your router will have a DHCP range and will randomly assign any devices on the network that are set to DHCP to an address within that range at designated intervals.
Leaving a NetX WIFi or Ethernet thermostat in DHCP mode is okay if you're using the CloudConnect option. If you are using CloudConnect, there is no need to have static IP addresses because the cloud identifies the thermostat via MAC ID, and that never changes.
If you're using the NetX-IP Command Center and/or DirectConnect for controlling your thermostats, it is important to use Static IP addressing for each thermostat. Otherwise, if you're using DHCP addressing when a thermostat's address changes due to DHCP reassignment the address in the NetX-IP Command Center will no longer be valid.
NetX thermostats and sensors are accurate to +/- 1º F. The accuracy of the thermistor is +/- .01%.
NetX Wi-Fi thermostats support WEP 40/64-bit ASCII, WEP 40/64-bit Hex, WEP 104/128-bit ASCII, WEP 104/128-bit Hex, WPA-PSK, and WPA2-PSK2. It is important to match the thermostat's Wi-Fi security type with that of your wireless network, otherwise, you will not be able to connect the thermostat to your network. It is highly recommended to use either WPA or WPA2 security on your network due to better security.
NetX Wi-Fi thermostats support WEP 40/64-bit ASCII, WEP 40/64-bit Hex, WEP 104/128-bit ASCII, WEP 104/128-bit Hex, WPA-PSK, and WPA2-PSK2. It is important to match the thermostat's Wi-Fi security type with that of your wireless network, otherwise, you will not be able to connect the thermostat to your network. It is highly recommended to use either WPA or WPA2 security on your network due to better security.
First, check to make sure that your scheduled setpoints are within the min/max cooling and heating setpoints on the configuration page. If this is correct then check your inactive schedules to make sure they are within the min/max cooling and heating parameters. Even if the schedules are inactive, it could cause an issue if the parameters are outside the min/max setpoints.
Check the override timer either in the software or the directly through the IP address in a browser. If the override timer is set to 00:00 the thermostat will not allow temperature changes via the physical buttons.
Check to make sure you are on the same network. If the green LED on the backplate of the thermostat is solid then it is connected to a network, your router settings may be preventing the Device Explorer from detecting the thermostat.
In order to use our DirectConnect service you will need to make sure you have claimed your devices and entered at least a state and zip code in the address field. Use the same login credentials on the DirectConnect page as you used to claim the device.
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.
If you are using an Android device, it is not configured to detect ad hoc networks by default. You will need to either find a third-party app that allows connection to ad hoc networks or try another device that allows ad hoc connections. Windows 7 and earlier will detect ad hoc networks, as well as all iOS devices.
It is not necessary to register your device. There are 3 main reasons for registering a thermostat:
1. Remote access via CloudConnect. Annual service fees apply.
2. Remote access via DirectConnect. Router port forwarding is required. No annual fees.
3. Courtesy connectivity alerts. If a registered thermostat does not "phone home" in any 4-hour period, a courtesy email is sent to the log-in email address.
In order for the occupancy sensor to switch the thermostat into occupied mode the override timer in the thermostat configuration must be set to greater than 0:00. This setting can be found on the configuration page.
Changing the mode will set the thermostat into override mode and it will continue in the altered mode for the duration of the override timer. To return to the schedule after changing the mode you can either press the resume button or allow the override timer to end.
Ethernet Thermostats
Check the power supply to ensure the thermostat is getting the proper voltage (about 24 volts). The red wire from the backplate and the red wire from the thermostat cable must both be in the R terminal. The black wire from the backplate and the common (color varies) wire from the thermostat cable must both be in the 24V(c) terminal.
All of our thermostats are powered by 24VAC and they all require a common wire. If you do not have a common wire you can purchase the NT-PWIRE and it will give you a common wire. Alternatively, you can purchase a 24VAC power supply and plug it into an outlet.
You must first register your thermostat under the configuration tab in either a browser or the Command Center. The information you used to register your device will be your login for the CloudConnect site. If you have more than one thermostat it is recommended that you register all of them with the same credentials.
Remove the faceplate then press and hold the “Setup” button until the LEDs flash then, do three short presses. The LEDs will go off and the thermostat will reboot. After this is done the thermostat will be back to the factory settings.
From the PC software, Cloud Connect, or directly from the IP address of the thermostat in a browser go to the schedules tab. Check the active box above the schedule number then set the time you would like the schedule to start. Enter the setpoints you would like the schedule to reflect, the cool temperature will be the maximum temperature that will be reached before the air conditioner will turn on and the heat temperature will be the lowest temperature that will be reached before the heat will turn on. Select whether the room will be occupied or unoccupied during this time and set the mode and fan to your desired setting. Click the “apply” button in the lower right corner to save the schedule.
It is recommended to have the schedules in chronological order. You may then copy the schedule to any additional days you want to have the same schedule. To do this you select the day of the week you would like to copy from the tabs at the top of the menu. Once you are on the correct day click the checkbox(es) for the day(s) you wish to copy down at the bottom of the menu. Click the “apply” button to save the changes you made.
Go into the configuration settings and select the time and date settings. Uncheck the "Sync Clock Automatically" checkbox and check the "Set Clock Manually" checkbox. Then you will be able to change the time to whatever you want.
The IP versions connect via an RJ45 jack on the backplate of the thermostat, there is no need to strip any wires to connect to the thermostat. The Ethernet cable from the thermostat would then connect directly to your hub that is plugged into your router.
This could be for either of two reasons. If the thermostat is being used on a Fahrenheit scale, the Up and Down buttons may have accidentally been pressed at the same time, which changes the display to Celsius mode. To correct this, press and release the Up and Down buttons simultaneously again. Another reason could be that the temperature sensor has been bent. Pull off the faceplate and check the thermistor to see if it is damaged or bent over. The thermistor is a little device sticking up in the bottom right of the circuit board, it will be either blue or black. Make sure it is not damaged and is standing up straight off the circuit board.
Make sure the thermostat is out of the ad-hoc network state (netx-setup) and on the network you are connected to.
Make sure that you have set up an account and that it is not expired. Make sure you are entering the correct email and password. If you cannot remember your password hit the "forgot password" button on the login page. If you have confirmed that the login credentials are correct, contact support and let them know you are having an issue.
If your router credentials changed then the thermostats will not have the correct login info to connect to it. There are multiple ways to fix this problem. The easiest way to fix it if you have many thermostats is to change the security type, SSID, and password of the new router to the same security type, SSID, and password as the old router. This will allow the thermostats to reconnect without having to adjust the settings.
Another way to get them on the network is to know what the new SSID and password will be ahead of time and go to the network settings page on the thermostat and change the settings before changing the router. This will allow the thermostats to automatically connect when the new router is installed.
The third way to put them on the new router network is to reset the thermostats and go from the ad hoc mode to the new network like you are setting up a new thermostat. If you choose to go this route you will need to reset your schedules afterward.
A fourth method would be to use WiFI Protected Setup (WPS) if your new router has that capability. You will need to place your router in WPS mode, go to a thermostat, remove the faceplate, and Press and release the SETUP button. This will put the thermostat into WPS mode and the router and thermostat will negotiate the security information, usually within about 60 seconds. Depending on the router, you may need to place the router into WPS mode again for each thermostat.
Yes, however, you will need to purchase an NT-PWIRE which will take your four-wire system and convert it to five wires allowing you to have a common. You can purchase the NT-PWIRE at networkhvac.com.
If you would like individual readouts from each NT-TEMP, you will need probes connected to them via the Aux terminals and set them up as AUX devices.
With the faceplate connected to the backplate, look through the top vents of the backplate. If you see a red LED illuminated on the backplate then the backplate and faceplate are not communicating. If you do not see a red LED on then the backplate and faceplate are communicating.
Yes! There are several methods. You can integrate our software into your automation system via our API.
Looking at the backplate with the faceplate removed you will see two LEDs, a green LED and a red LED. If the green LED is blinking the thermostat is at the default IP address 169.254.1.1. If the green LED is solid then the thermostat is connected to your network. If the green LED is not illuminated at all then there is no connection to the network.
Another way to check connectivity without removing the faceplate is to check the LCD. If you have a newer backlight version, a radio tower icon on the thermostat means it is at the default IP address. If you see a signal strength icon, the thermostat is connected to the local network. If you do not see either, the thermostat is not connected to any network. If you have an older non-backlight version, a satellite icon on the thermostat means it is at the default IP address. If you see a satellite+lightning bolt icon, the thermostat is connected to the local network. If you do not see either, the thermostat is not connected to any network.
You can find the manual for all of our devices on the products page. Go to the desired device and look under the "Docs" tab. Note: If you have an older device that is no longer in production contact support for a copy of the manual.
If your equipment is 2-stage, first make sure your DIP switches are set correctly to allow second-stage operation. In order to bring on the second stage faster than the efficient fuzzy-logic algorithm (about 15-20min after the first stage, if needed):
1) set the heating or cooling setpoint at room temperature and let the display return to normal operation.
2) move the heat or cool setpoint up or down three degrees. After normal protection time-outs have been satisfied (2 or 4 minutes depending on your configuration), the thermostat will start the first stage.
3) Once the first stage is running, adjust the setpoint three more degrees in the same direction. The second stage will start.
This method bypasses the thermostatic control algorithm for this single heating/cooling cycle.
There is currently no native app set up in the App Store. However, each Wi-Fi and Ethernet thermostat has a built-in set of web pages with responsive design. The responsive design will automatically detect that you connected to the thermostat with an iPhone and show the thermostat pages in a manner that looks like a native app; it's called a web app. Additionally, both the CloudConnect and DirectConnect environments are of responsive design and have built-in web app features including connection for all of your thermostats, even multiple sites, right from a single mobile screen. You have the option of using the free DirectConnect service and port forwarding your devices or using the CloudConnect service without needing to port forward. Both methods allow a simple icon to be added to your home screen, giving you a single-tap launch for access to all of your thermostats.
We support all browsers supporting html5, however, as browser updates are released very quickly, if you experience usage issues with one browser, please try a different browser.
Yes, the NT-TEMP is required for remote sensing. NetX thermostats use an advanced remote sensor bus which has active electronics, not just a passive temperature sensor.
You will only need to port forward your thermostats if you are going to try to access them from outside the LAN and want to communicate directly with them. If you are unfamiliar with how to do port forwarding you can go to portforward.com for step-by-step instructions. If you cannot find instructions on portforward.com for your router refer to the user's manual or another online source for instructions. If you are planning to use the CloudConnect service you do not need to port forward your devices to access them from outside the LAN via the cloud service.
Go to the configuration page in the thermostat settings and look for the box in the second row down labeled "Override Timer". Set the amount of time for an override. If you check the "Hold Override Until Occupied" box, the override changes will stay in effect until the next occupied schedule occurs.
To switch from Direct Connect to Cloud Connect you simply need to purchase a subscription to the cloud service and login using the same email and password that you used to claim the thermostat.
To change the password, access the thermostat and click on the Configuration tab. Down in the bottom right corner, there is a box labeled Password, enter the new password you want and click the Apply button.
To change the password go to the basic configuration page in either the IP Command Center or directly through IP address in a browser. From the configuration page enter the new password you wish to switch to and click the register thermostat button. If you are using the IP Command Center the software will prompt you to re-enter the new credentials to log in to the thermostat.
Press and release the up and down arrows simultaneously.
In your web browser address bar enter the thermostat IP address followed by “/configcc.htm”. Clear the text boxes following “Server” and “Port”, then set the value in the box following “Interval” to 0. Press the “Update” button on the bottom of the menu and the values will save.
To register your device you will go to the configuration tab and fill in at least the state and zip code under the address field. After you have filled in the address information hit the "Apply" button next to the "Contact" box. Then you will enter your email address and put in a password to create login credentials. After you have filled in the login credentials boxes hit the apply button. The page will refresh and ask you to log in using the information you just changed. You have now claimed your device.
This can be done by using our Cloud Connect service. The Cloud Connect service allows access to multiple thermostats via any web browser and mobile device. You can set different passwords to allow limited access to specific users.
Click the link below the log in fields labeled "forgot your password".
To remove a thermostat from your project file right click on the device in the tree on the left and select 'Remove'.
You can find the manual for all of our devices on the products page. Go to the desired device and look under the "Docs" tab. Note: If you have an older device that is no longer in production contact support for a copy of the manual.
Yes, there are several ways to access WiFi and Ethernet thermostats on different networks from one place. This can be done using our CloudConnect service, DirectConnect, a web browser via WAN IP address, or through the IP Command Center using external IP addresses.
In unlocked mode, if the thermostat is run without setting the time the override will run until manually changed or until the clock is set and schedules start running.
In locked mode when the thermostat is run without setting the time the override will last for the duration of the override timer (set in the basic configuration). The default override timer is 8 hours. Once the override timer has expired the thermostat will revert to the non-override manual setpoints.
There is not currently an Android app available, however, each Wi-Fi and Ethernet thermostat has a built-in set of web pages with a responsive design. The responsive design will automatically detect that you connected to the thermostat with a mobile device and show the thermostat pages in a manner that looks like a native app; it's called a web app. Additionally, both the CloudConnect and DirectConnect environments are of responsive design and have built-in web app features including connection for all of your thermostats, even multiple sites, right from a single mobile screen. You have the option of using the free DirectConnect service and port forwarding your devices or using the CloudConnect service without needing to port forward. Both methods allow a simple icon to be added to your home screen, giving you a single tap launch for access to all of your thermostats.
The default setpoints upon first powering the thermostat on are:
Cooling - 76 F
Heating - 68 F
Mode - Auto
A static IP address is an address that does not change. Alternatively, a dynamic address via DHCP (Dynamic Host Configuration Protocol) is an address that is assigned by the router and may change based on any of several parameter settings in the router, including lease time or if the router/access point resets. Your router will have a DHCP range and will randomly assign any devices on the network that are set to DHCP to an address within that range at designated intervals.
Leaving a NetX WIFi or Ethernet thermostat in DHCP mode is okay if you're using the CloudConnect option. If you are using CloudConnect, there is no need to have static IP addresses because the cloud identifies the thermostat via MAC ID, and that never changes.
If you're using the NetX-IP Command Center and/or DirectConnect for controlling your thermostats, it is important to use Static IP addressing for each thermostat. Otherwise, if you're using DHCP addressing when a thermostat's address changes due to DHCP reassignment the address in the NetX-IP Command Center will no longer be valid.
NetX thermostats and sensors are accurate to +/- 1º F. The accuracy of the thermistor is +/- .01%.
First, check to make sure that your scheduled setpoints are within the min/max cooling and heating setpoints on the configuration page. If this is correct then check your inactive schedules to make sure they are within the min/max cooling and heating parameters. Even if the schedules are inactive, it could cause an issue if the parameters are outside the min/max setpoints.
Check the override timer either in the software or the directly through the IP address in a browser. If the override timer is set to 00:00 the thermostat will not allow temperature changes via the physical buttons.
In order to use our DirectConnect service you will need to make sure you have claimed your devices and entered at least a state and zip code in the address field. Use the same login credentials on the DirectConnect page as you used to claim the device.
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.
It is not necessary to register your device. There are 3 main reasons for registering a thermostat:
1. Remote access via CloudConnect. Annual service fees apply.
2. Remote access via DirectConnect. Router port forwarding is required. No annual fees.
3. Courtesy connectivity alerts. If a registered thermostat does not "phone home" in any 4-hour period, a courtesy email is sent to the log-in email address.
In order for the occupancy sensor to switch the thermostat into occupied mode the override timer in the thermostat configuration must be set to greater than 0:00. This setting can be found on the configuration page.
Changing the mode will set the thermostat into override mode and it will continue in the altered mode for the duration of the override timer. To return to the schedule after changing the mode you can either press the resume button or allow the override timer to end.
Wi-Fi / Ethernet Software
You must first register your thermostat under the configuration tab in either a browser or the Command Center. The information you used to register your device will be your login for the CloudConnect site. If you have more than one thermostat it is recommended that you register all of them with the same credentials.
From the PC software, Cloud Connect, or directly from the IP address of the thermostat in a browser go to the schedules tab. Check the active box above the schedule number then set the time you would like the schedule to start. Enter the setpoints you would like the schedule to reflect, the cool temperature will be the maximum temperature that will be reached before the air conditioner will turn on and the heat temperature will be the lowest temperature that will be reached before the heat will turn on. Select whether the room will be occupied or unoccupied during this time and set the mode and fan to your desired setting. Click the “apply” button in the lower right corner to save the schedule.
It is recommended to have the schedules in chronological order. You may then copy the schedule to any additional days you want to have the same schedule. To do this you select the day of the week you would like to copy from the tabs at the top of the menu. Once you are on the correct day click the checkbox(es) for the day(s) you wish to copy down at the bottom of the menu. Click the “apply” button to save the changes you made.
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 to 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 a .ntp server or set the time manually.
Make sure that you have set up an account and that it is not expired. Make sure you are entering the correct email and password. If you cannot remember your password hit the "forgot password" button on the login page. If you have confirmed that the login credentials are correct, contact support and let them know you are having an issue.
If your router credentials changed then the thermostats will not have the correct login info to connect to it. There are multiple ways to fix this problem. The easiest way to fix it if you have many thermostats is to change the security type, SSID, and password of the new router to the same security type, SSID, and password as the old router. This will allow the thermostats to reconnect without having to adjust the settings.
Another way to get them on the network is to know what the new SSID and password will be ahead of time and go to the network settings page on the thermostat and change the settings before changing the router. This will allow the thermostats to automatically connect when the new router is installed.
The third way to put them on the new router network is to reset the thermostats and go from the ad hoc mode to the new network like you are setting up a new thermostat. If you choose to go this route you will need to reset your schedules afterward.
A fourth method would be to use WiFI Protected Setup (WPS) if your new router has that capability. You will need to place your router in WPS mode, go to a thermostat, remove the faceplate, and Press and release the SETUP button. This will put the thermostat into WPS mode and the router and thermostat will negotiate the security information, usually within about 60 seconds. Depending on the router, you may need to place the router into WPS mode again for each thermostat.
Yes! There are several methods. You can integrate our software into your automation system via our API.
You can find the manual for all of our devices on the products page. Go to the desired device and look under the "Docs" tab. Note: If you have an older device that is no longer in production contact support for a copy of the manual.
There is currently no native app set up in the App Store. However, each Wi-Fi and Ethernet thermostat has a built-in set of web pages with responsive design. The responsive design will automatically detect that you connected to the thermostat with an iPhone and show the thermostat pages in a manner that looks like a native app; it's called a web app. Additionally, both the CloudConnect and DirectConnect environments are of responsive design and have built-in web app features including connection for all of your thermostats, even multiple sites, right from a single mobile screen. You have the option of using the free DirectConnect service and port forwarding your devices or using the CloudConnect service without needing to port forward. Both methods allow a simple icon to be added to your home screen, giving you a single-tap launch for access to all of your thermostats.
All schedules must be in chronological order even if the schedules are inactive.
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 set up 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 set up 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.
For Single User Applications:
1) Install ONE copy of the NetX-IP 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-IP Command Center MAY BE RUN SIMULTANEOUSLY on the same PC, virtual machine, or Windows-based server, AS LONG AS THERE IS NO 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 NetX-IP 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-IP Command Center MAY BE RUN SIMULTANEOUSLY on the same PC, virtual machine, or Windows-based server, AS LONG AS THERE IS NO 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 NetX-IP 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-Cloud.com Web Environment
Yes, as long as you are using a supported OS.
You will only need to port forward your thermostats if you are going to try to access them from outside the LAN and want to communicate directly with them. If you are unfamiliar with how to do port forwarding you can go to portforward.com for step-by-step instructions. If you cannot find instructions on portforward.com for your router refer to the user's manual or another online source for instructions. If you are planning to use the CloudConnect service you do not need to port forward your devices to access them from outside the LAN via the cloud service.
Go to the configuration page in the thermostat settings and look for the box in the second row down labeled "Override Timer". Set the amount of time for an override. If you check the "Hold Override Until Occupied" box, the override changes will stay in effect until the next occupied schedule occurs.
To change the password, access the thermostat and click on the Configuration tab. Down in the bottom right corner, there is a box labeled Password, enter the new password you want and click the Apply button.
In your web browser address bar enter the thermostat IP address followed by “/configcc.htm”. Clear the text boxes following “Server” and “Port”, then set the value in the box following “Interval” to 0. Press the “Update” button on the bottom of the menu and the values will save.
Click the link below the log in fields labeled "forgot your password".
To remove a thermostat from your project file right click on the device in the tree on the left and select 'Remove'.
Yes, there are several ways to access WiFi and Ethernet thermostats on different networks from one place. This can be done using our CloudConnect service, DirectConnect, a web browser via WAN IP address, or through the IP Command Center using external IP addresses.
There is not currently an Android app available, however, each Wi-Fi and Ethernet thermostat has a built-in set of web pages with a responsive design. The responsive design will automatically detect that you connected to the thermostat with a mobile device and show the thermostat pages in a manner that looks like a native app; it's called a web app. Additionally, both the CloudConnect and DirectConnect environments are of responsive design and have built-in web app features including connection for all of your thermostats, even multiple sites, right from a single mobile screen. You have the option of using the free DirectConnect service and port forwarding your devices or using the CloudConnect service without needing to port forward. Both methods allow a simple icon to be added to your home screen, giving you a single tap launch for access to all of your thermostats.
NetX Wi-Fi thermostats support WEP 40/64-bit ASCII, WEP 40/64-bit Hex, WEP 104/128-bit ASCII, WEP 104/128-bit Hex, WPA-PSK, and WPA2-PSK2. It is important to match the thermostat's Wi-Fi security type with that of your wireless network, otherwise, you will not be able to connect the thermostat to your network. It is highly recommended to use either WPA or WPA2 security on your network due to better security.
First, check to make sure that your scheduled setpoints are within the min/max cooling and heating setpoints on the configuration page. If this is correct then check your inactive schedules to make sure they are within the min/max cooling and heating parameters. Even if the schedules are inactive, it could cause an issue if the parameters are outside the min/max setpoints.
Check to make sure you are on the same network. If the green LED on the backplate of the thermostat is solid then it is connected to a network, your router settings may be preventing the Device Explorer from detecting the thermostat.
In order to use our DirectConnect service you will need to make sure you have claimed your devices and entered at least a state and zip code in the address field. Use the same login credentials on the DirectConnect page as you used to claim the device.
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.
In order for the occupancy sensor to switch the thermostat into occupied mode the override timer in the thermostat configuration must be set to greater than 0:00. This setting can be found on the configuration page.
Make sure you are entering the ASCII port not the http port number. If you are seeing the IP address in the top right corner instead of the name of the thermostat, the information is not entered correctly.
StrongMesh Thermostats
For Single User Applications:
1) Install ONE copy of the NetX 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 NetX 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 NetX 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
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 to 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 a .ntp server or set the time manually.
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.
All schedules must be in chronological order even if the schedules are inactive.
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.
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 set up 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 set up 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.
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.
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.
Power cycle the controller and check to make sure you are running the most current version of the Command Center software.
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.
XBus Thermostats
For Single User Applications:
1) Install ONE copy of the NetX 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 NetX 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 NetX 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
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 to 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 a .ntp server or set the time manually.
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.
All schedules must be in chronological order even if the schedules are inactive.
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.
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 set up 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 set up 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.
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.
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.
Power cycle the controller and check to make sure you are running the most current version of the Command Center software.
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.
XBus / StrongMesh Software
For Single User Applications:
1) Install ONE copy of the NetX 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 NetX 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 NetX 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
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 to 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 a .ntp server or set the time manually.
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.
All schedules must be in chronological order even if the schedules are inactive.
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.
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 set up 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 set up 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.
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.
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.
Power cycle the controller and check to make sure you are running the most current version of the Command Center software.
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.
Remote Sensors
If you would like individual readouts from each NT-TEMP, you will need probes connected to them via the Aux terminals and set them up as AUX devices.
You can find the manual for all of our devices on the products page. Go to the desired device and look under the "Docs" tab. Note: If you have an older device that is no longer in production contact support for a copy of the manual.
Yes, the NT-TEMP is required for remote sensing. NetX thermostats use an advanced remote sensor bus which has active electronics, not just a passive temperature sensor.
You can find the manual for all of our devices on the products page. Go to the desired device and look under the "Docs" tab. Note: If you have an older device that is no longer in production contact support for a copy of the manual.
In order for the occupancy sensor to switch the thermostat into occupied mode the override timer in the thermostat configuration must be set to greater than 0:00. This setting can be found on the configuration page.
Accessories
If you would like individual readouts from each NT-TEMP, you will need probes connected to them via the Aux terminals and set them up as AUX devices.
You can find the manual for all of our devices on the products page. Go to the desired device and look under the "Docs" tab. Note: If you have an older device that is no longer in production contact support for a copy of the manual.
Yes, the NT-TEMP is required for remote sensing. NetX thermostats use an advanced remote sensor bus which has active electronics, not just a passive temperature sensor.
You can find the manual for all of our devices on the products page. Go to the desired device and look under the "Docs" tab. Note: If you have an older device that is no longer in production contact support for a copy of the manual.
In order for the occupancy sensor to switch the thermostat into occupied mode the override timer in the thermostat configuration must be set to greater than 0:00. This setting can be found on the configuration page.
Network Relays
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 to 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 a .ntp server or set the time manually.
Network Controllers & Gateways
Go into the configuration settings and select the time and date settings. Uncheck the "Sync Clock Automatically" checkbox and check the "Set Clock Manually" checkbox. Then you will be able to change the time to whatever you want.
The X1 and X2 terminals should be connected to the corresponding terminals on the thermostat. It is recommended to balance the number of connections to each of the four terminals on the controller. If you have an older controller with only three terminals balance the number of wires connecting to the two X1 terminals.
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.
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.
To change the password, access the thermostat and click on the Configuration tab. Down in the bottom right corner, there is a box labeled Password, enter the new password you want and click the Apply button.
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.
A static IP address is an address that does not change. Alternatively, a dynamic address via DHCP (Dynamic Host Configuration Protocol) is an address that is assigned by the router and may change based on any of several parameter settings in the router, including lease time or if the router/access point resets. Your router will have a DHCP range and will randomly assign any devices on the network that are set to DHCP to an address within that range at designated intervals.
Leaving a NetX WIFi or Ethernet thermostat in DHCP mode is okay if you're using the CloudConnect option. If you are using CloudConnect, there is no need to have static IP addresses because the cloud identifies the thermostat via MAC ID, and that never changes.
If you're using the NetX-IP Command Center and/or DirectConnect for controlling your thermostats, it is important to use Static IP addressing for each thermostat. Otherwise, if you're using DHCP addressing when a thermostat's address changes due to DHCP reassignment the address in the NetX-IP Command Center will no longer be valid.
It is not recommended to exceed 125ft between thermostats. For XBus systems, each CAT5 cable run can be no longer than 1,000ft in total with no more than 8 thermostats on a single CAT5 cable run. It is highly recommended to use an NT-TB terminal board as a hub for your XBus thermostat cabling. Each 'drive' (X1/X2) on a network controller can support up to 2,000ft and a maximum of 16 thermostats. With each controller having two drives, up to 32 thermostats can be supported on up to 4,000ft of CAT5 cable.
You must use CAT5 cable to wire the XBus terminals.