Improved support for Nortek GoControl GC-TBZ48 and GC-TBZ48L thermostat settings
I have a CT-50 and I canât get it to register as a C-Wire based thermostat. I want z-wave repeater functionality and I donât want low battery notifications.
Hey there. It sounds like your thermostat isnât pairing as a repeater in C-Wire mode. You may want to try to reset your thermostat to factory defaults and try pairing it again with your C-Wire connected before pairing. It may also indicate a faulty C-Wire with power line fluctuations.
Once it registers as a C-Wire you can disable battery notifications from the device setting page (battery levels are always on by default since folks like to use a battery backup even with the C-Wire for safety). If you have trouble feel free to email our support desk and we can look into whatâs going on.
Is anyone else having trouble getting the new smartthings app to pull up the thermostat? Works fine in the old app. New app doesnât connect.
Iâve noticed all of the âthingsâ lose connection every few seconds for a few seconds in the new app. On the same phone, clasic app has no problem. Is that what youâre seeing?
I just got notification of the classic app going away and platform updates. Has anyone experimented with the new app and if it will work with these thermostats?
It works with new app (and has been for months now), see the screenshots in the first post.
Most of the controls are already there, some custom controls will show up in the near future once ST enables custom controls for the new app.
I canât get the new app to connect to my CT-100s.
I can confirm that everything is working fine after the migration from Classic app to the new app.
Why doesnât the latest version of this DH (or the new app) report history for system state changes, setpoint, and fan mode changes? It only seems to show battery, temperature, and humidity history.
Iâm suddenly having problems with the battery draining every 2 or 3 days on my GoControl after having migrated it over to the new app and updating the device handler. Prior to updating the app, Iâve had the thermostat for over 3 years on the Classic app without any battery problems. Any thoughts?
To troubleshoot, Iâve updated the device handler to the latest version, changed the deviceâs device handler to another device handler and then back again, refreshed, checked that the âsave thermostat batteryâ setting is checked in the settings, etc., but nothing seems to stop the battery drain.
Any other ideas?
It was an issue with the new app, we reported it to ST and they appear to have fixed it. With the latest mobile app update today itâs showing the history now.
This is an important update for GoControl and Honeywell thermostats
Can I trigger humidity automations with this controller?
Having a lot of problems with both of my CT100 Thermostats.
ST is recognizing them as offline. But the my temperatures and set points are all accurate and update when I change them. Refreshing in the app doesnât seem to bring it back on line, but oddly, if I go into the menu on the thermostat itself refreshing in ST seems to bring it back online. Even without doing anything. Temperatures and set points remain accurate, but Iâm unable to update set points by ST/Zwave.
Totally stumped.
Iâve been using Rboyâs DH. was happening on a previous version of the DH and continues in 4.08.
Anyone have any ideas here?
I think if the device doesnât show some life in a set period of time itâs shown as offline. So if the activity doesnât have anything in there for a long time, IDK maybe 1 to 2 days may be more itâll show as being offline. Could this be happening?
I guess what would define activity? The temperature reading is changing all day.
If you open your thermostat in the app there is an activity area, like a history. If you look in there, what do you see? You should see temp info and I believe an entry for when the heat cycles on and off.
As @jpetrone said if the hub doesnât receive any events from the thermostat within a specified period of time, it marks the thermostat offline.
We have seen in our lab, some thermostat models firmwares lose directional connectivity with the hub, ie you can send it commands but not receive updates or vice versa. This was explained many posts above and is sometimes related to fluctuating power supply issues.
The simplest solution is to reset it as explained here:
If it still happens, the other solution is to exclude the device, factory reset it (see first post) and then pair it again.