I’ve only seen it twice. Most of the time it seems to be working as intended now. Is it possible that when you manually add the RTS to the thermostat, that it only stays paired until the next schedule change? (For example, if I pair it in home mode, it will unpair when the thermostat sets to sleep?) That might explain some of the behavior.
At any rate, I have my schedule set up now so it only does averaging when set for sleep, and that has been working reliably enough.
Is it possible that when you manually add the RTS to the thermostat, that it only stays paired until the next schedule change? (For example, if I pair it in home mode, it will unpair when the thermostat sets to sleep?) That might explain some of the behavior.
I suppose any error is possible, but that certainly would not be intended.
If you have any follow up observations let us know. We will be working with Alarm.com on the seemingly aggressive error reporting that is occurring with some of these units.
As a follow up, what is the model number on your 2GIG panel? is it a CNTRL2? or is it a CP21-345?
I’m not entirely sure, but it says “Emergency” under the emergency button instead of the three symbols.
I’ve been following the z-wave version thread. I’ve pretty much just given up on the temp sensors.
Ah, alright, yeah if it does not have the symbols that would indicate the older Zwave version in the panel.
If panel says ‘Emergency’, he probably has 2.78. My understanding is even a panel with symbols manufactured prior to march of last year will be on zwave 3.42.
Didn’t you say anything less than zwave 4.55 is no good (for the alarm.com t2000 temp sensors)? Any news on compatibility with older zwave versions?
Apparently it is more convoluted than that.New panels show 3.42. Unfortunately, ADC is not referring to the Z-wave Version listed in the panel version screen. It is an internal build version. 2GIG does not release details about it (apparently not even readily to ADC) but generally, all GC2’s should be compatible.
It’s likely that it lines up 1 for 1 with 3.42 in the panel version screen, and they did say that anything with symbols under the emergency button is technically what 2GIG refers to now as a GC2. All GC2’s supposedly have this 4.5X internal Zwave build supporting NWI.
The internal build necessary for the RTS would have had to be available from near the beginning of development for the device I would think, so it makes a lot more sense than a brand new revision.
So, if you have an older panel showing 2.78 in the version screen and the word “Emergency” on the front, the RTS will definitely have problems.
While the answers were not as solid as I would hope, you should be ok with either B or C from your above image.
3.42 is what you want to see. The 4.5X is an internal build version not shown on the panel. Related to hardware. I’ve been told all GC2 panels should be fine, which means anything with symbols, which means 3.42 visible version listed in the GC2 settings.
3.42 is what you want to see. The 4.5X is an internal build version not shown on the panel. Related to hardware
So, just to be clear on this… if you look at the version screen on a brand new 2016 manufactured GC2 panel on firmware 1.14.0.1, it will show zwave version ‘2GIG-b 3.42’, or 3.42?
Yes, just opened a late 2015 manufactured panel (after RTS was released, I believe). 3.42 is the visible version. If you have a panel with symbols under the emergency button you should be fine with the RTS.