CT101 Thermostat Polling Issues - Any Updates?

Other Devices & Integrations Climate Control & Temperature Sensors
#1

I’ve recently purchased a CT101 thermostat (Iris/Lowe’s version) from an online vendor. Been doing a lot of reading since experiencing the polling issues noted in the forums. My device is the 9.0 firmware, but there are conflicting posts about whether that is an issue. Its not a proximity to controller issue as I have done a test case with the controller within 3ft of the thermostat. With each test, I’ve done the exclude/include recommended.

Currently I’m running the default CT100 configuration and the default Z-wave network settings (poll a node every 30 sec). My controller is a VeraPlus with firmware 1.7.4453. As most posts, the thermostat appears to respond to commands sent, but then at the next polling, shows Can’t Detect Device. When sending a command, I will receive a notification that the device is responding again, but I haven’t yet figured out the pattern as to when I receive the Not Responding notification.

Does anyone have any recent updates or suggestions for bettering the experience with this device?

Thanks.

Here is a snippet from the logs if that is helpful to anyone willing to offer suggestions:

ZWJob_PollNode::ReceivedFrame HandlePollUpdate failed job job#397 :pollnode #6 dev:230 (0x15ae660) N:6 P:100 S:5 Id: 397 got after 0 seconds FUNC_ID_APPLICATION_COMMAND_HANDLER node info for 6 status 0 data 0x5 0x1 0x2a 0x2 0xa8 (##*##)
ZWaveSerial::GetFrame 0x75eabc98 timed out now 0 m_listGetFramePending 0
ZWaveJobHandler::SendDataAbort got m_iFrameID 0
ZWJob_PollNode::ReturnMessageNotReceived -end- job job#397 :pollnode #6 dev:230 (0x15ae660) N:6 P:100 S:5 Id: 397 node 6 didn’t reply iOK 0 iBadTx 0 iNoReply 50 Abort returned m_iFrameID 0
ZWJob_PollNode::PollFailed job job#397 :pollnode #6 dev:230 (0x15ae660) N:6 P:100 S:5 Id: 397 node 6 battery 1 notlist:0
Device_Variable::m_szValue_set device: 230 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: ConsecutivePollFails was: 640 now: 641 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0
Device_Basic::AddPoll 230 poll list full, deleting old one
Device_Variable::m_szValue_set device: 230 service: urn:micasaverde-com:serviceId:HaDevice1 variable: PollRatings was: 0.00 now: 0.00 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1

JobHandler::PurgeCompletedJobs purge job#397 :pollnode #6 dev:230 (0x15ae660) N:6 P:100 S:2 Id: 397 pollnode #6 9 cmds status 2

#2

If this device is on battery mode: Maybe that the polling itself is the only problem. I had similar problems with some of my battery devices. I switched polling of for these devices (poll intervall = 0) and had no more problems.

#3

I am an “Iris refugee” that migrated a CT-101 over, It was previously battery-powered and I ended up turning off polling and connecting a C-wire to get this thermostat to play well with Vera.

#4

My CT-101 has been humming on my Vera 3 for years. C-wire only.