Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Nest driver disconnecting and reconnecting
#1
My Nest driver seems to be unstable after upgrading to 5.2.1.   I have attached a log if anyone has ideas.


Code:
 
{
   CQCKit, CQCIntfView_ThisFacility.cpp.203, Status/App Status
   CQCIntfView is starting up. Version=5.2.1
}
11/26 13:11:03-Office, CQCServer, CQCDrv_NestThread12
{
   CQCGenDrvS, MEng.System.CQC.Drivers.Nest.Cloud.DriverImpl.964, Status/App Status
   Poll failure. Error=Got an incomplete encrypted packet. Name=Secure Client Data Source
}
11/26 13:11:03-Office, CQCServer, CQCDrv_NestThread12
{
   CQCKit, CQCDriver_DriverBase.cpp.7255, Status/Lost Connection
   Driver 'Nest' has lost connection to it's device
}
11/26 13:11:03-Office, CQCServer, CQCDrv_NestThread12
{
   CQCKit, CQCDriver_DriverBase.cpp.7289, Status/Lost Connection
   Driver 'Nest' has lost its communcations resource
}
11/26 13:11:08-Office, CQCServer, CQCDrv_NestThread12
{
   CQCKit, CQCDriver_DriverBase.cpp.3445, Status/App Status
   Driver 'Nest' is trying to get its comm resource
}
11/26 13:11:08-Office, CQCServer, CQCDrv_NestThread12
{
   CQCKit, CQCDriver_DriverBase.cpp.3484, Status/App Status
   Driver 'Nest' has its comm resource
}
11/26 13:11:08-Office, CQCServer, CQCDrv_NestThread12
{
   CQCKit, CQCDriver_DriverBase.cpp.3502, Status/App Status
   Driver 'Nest' is trying to connect to its device
}
11/26 13:11:17-Office, CQCServer, CQCDrv_NestThread12
{
   CQCKit, CQCDriver_DriverBase.cpp.3544, Status/App Status
   Driver 'Nest' has connected to its device
}
11/26 13:11:29-Office, CQCServer, CQCDrv_NestThread12
{
   CQCGenDrvS, MEng.System.CQC.Drivers.Nest.Cloud.DriverImpl.964, Status/App Status
   Poll failure. Error=Got an incomplete encrypted packet. Name=Secure Client Data Source
}
11/26 13:11:29-Office, CQCServer, CQCDrv_NestThread12
{
   CQCKit, CQCDriver_DriverBase.cpp.7255, Status/Lost Connection
   Driver 'Nest' has lost connection to it's device
}
11/26 13:11:29-Office, CQCServer, CQCDrv_NestThread12
{
   CQCKit, CQCDriver_DriverBase.cpp.7289, Status/Lost Connection
   Driver 'Nest' has lost its communcations resource
}
11/26 13:11:34-Office, CQCServer, CQCDrv_NestThread12
{
   CQCKit, CQCDriver_DriverBase.cpp.3445, Status/App Status
   Driver 'Nest' is trying to get its comm resource
}
11/26 13:11:34-Office, CQCServer, CQCDrv_NestThread12
{
   CQCKit, CQCDriver_DriverBase.cpp.3484, Status/App Status
   Driver 'Nest' has its comm resource
}
11/26 13:11:34-Office, CQCServer, CQCDrv_NestThread12
{
   CQCKit, CQCDriver_DriverBase.cpp.3502, Status/App Status
   Driver 'Nest' is trying to connect to its device
}
11/26 13:11:43-Office, CQCServer, CQCDrv_NestThread12
{
   CQCKit, CQCDriver_DriverBase.cpp.3544, Status/App Status
   Driver 'Nest' has connected to its device
}
11/26 13:11:49-Office, CQCServer, CQCDrv_NestThread12
{
   CQCGenDrvS, MEng.System.CQC.Drivers.Nest.Cloud.DriverImpl.964, Status/App Status
   Poll failure. Error=Got an incomplete encrypted packet. Name=Secure Client Data Source
}
11/26 13:11:49-Office, CQCServer, CQCDrv_NestThread12
{
   CQCKit, CQCDriver_DriverBase.cpp.7255, Status/Lost Connection
   Driver 'Nest' has lost connection to it's device
}
11/26 13:11:49-Office, CQCServer, CQCDrv_NestThread12
{
   CQCKit, CQCDriver_DriverBase.cpp.7289, Status/Lost Connection
   Driver 'Nest' has lost its communcations resource
}
11/26 13:11:54-Office, CQCServer, CQCDrv_NestThread12
{
   CQCKit, CQCDriver_DriverBase.cpp.3445, Status/App Status
   Driver 'Nest' is trying to get its comm resource
}
11/26 13:11:54-Office, CQCServer, CQCDrv_NestThread12
{
   CQCKit, CQCDriver_DriverBase.cpp.3484, Status/App Status
   Driver 'Nest' has its comm resource
}
11/26 13:11:54-Office, CQCServer, CQCDrv_NestThread12
{
   CQCKit, CQCDriver_DriverBase.cpp.3502, Status/App Status
   Driver 'Nest' is trying to connect to its device
}
11/26 13:12:03-Office, CQCServer, CQCDrv_NestThread12
{
   CQCKit, CQCDriver_DriverBase.cpp.3544, Status/App Status
   Driver 'Nest' has connected to its device
}
11/26 13:13:01-Office, CQCServer, CQCDrv_NestThread12
{
   CQCGenDrvS, MEng.System.CQC.Drivers.Nest.Cloud.DriverImpl.964, Status/App Status
   Poll failure. Error=Got an incomplete encrypted packet. Name=Secure Client Data Source
}
11/26 13:13:01-Office, CQCServer, CQCDrv_NestThread12
{
   CQCKit, CQCDriver_DriverBase.cpp.7255, Status/Lost Connection
   Driver 'Nest' has lost connection to it's device
}
11/26 13:13:01-Office, CQCServer, CQCDrv_NestThread12
{
   CQCKit, CQCDriver_DriverBase.cpp.7289, Status/Lost Connection
   Driver 'Nest' has lost its communcations resource
}
11/26 13:13:06-Office, CQCServer, CQCDrv_NestThread12
{
   CQCKit, CQCDriver_DriverBase.cpp.3445, Status/App Status
   Driver 'Nest' is trying to get its comm resource
}
11/26 13:13:06-Office, CQCServer, CQCDrv_NestThread12
{
   CQCKit, CQCDriver_DriverBase.cpp.3484, Status/App Status
   Driver 'Nest' has its comm resource
}
11/26 13:13:06-Office, CQCServer, CQCDrv_NestThread12
{
   CQCKit, CQCDriver_DriverBase.cpp.3502, Status/App Status
   Driver 'Nest' is trying to connect to its device
}
11/26 13:13:15-Office, CQCServer, CQCDrv_NestThread12
{
   CQCKit, CQCDriver_DriverBase.cpp.3544, Status/App Status
   Driver 'Nest' has connected to its device
}
Reply
#2
Did it start immediately when you upgraded? If not, then it probably isn't related to the upgrade but just happenstance. If it happened immediately afterwards then maybe it is related. What version did you upgrade from? I'll give the driver a try and see if it's failing for me as well.
Dean Roddey
Software Geek Extraordinaire
Reply
#3
It's working OK for me. I am running the debug code here. Let me go try to run it in the production code just to make sure.
Dean Roddey
Software Geek Extraordinaire
Reply
#4
Although I wouldn't expect the side effects to be what you are seeing in the logs, we did add support for Eco modes on the thermostats and for the away/home state on structures. If you upgraded from a version from before we added that (which was added in 5.1.x I think) and your Nest system isn't up to the latest firmware, maybe that could cause an issue. If you were already on the version that had the Eco modes and such, then that wouldn't be it.
Dean Roddey
Software Geek Extraordinaire
Reply
#5
Production code is working fine for me as well. So my guesses are:

1. You were on a pre-5.1 version and now our changes to support Eco/Structures stuff isn't working because you are on older firmware.
2. Maybe you did something that got the access token wrong or the PIN has been cancelled, so that the driver can't successfully communicate with the server.
3. You either didn't just upgrade to 5.2.1 and there's now just some temporary issue between you and their servers, or by just random fluke you did just upgrade and this temporary issue happened around the same time.

Any chance it's any of those?
Dean Roddey
Software Geek Extraordinaire
Reply
#6
I was 5.1 and It may not have been exactly when I updated I wasn't paying attention. my thermostat is on version 5.6.5-1 and the smokes are at 3.1.2rc2. Oh and the thermostat responds fine with google assistant.
Reply
#7
I was wrong, the structures/Eco modes were introduced in the 5.2 release, so that would be a change for you from 5.1. Right click on the Nest driver and select Info and make sure it's not running some off to the side version (it should be in the MEng.CQC.System area, not .User area, and the latest version is 1.6.

Check and see if there's more recent thermostat firmware available. They may have fixed something. Also, do a reconfigure on the driver and make sure that the ID is correct. Also maybe regenerate a new one just in case, then reconfigure the driver and give it that new ID.
Dean Roddey
Software Geek Extraordinaire
Reply
#8
I think I figured it out. My master server was in a partial upgrade on the windows creators update and had got hung. It was still responding to all the other drivers fine but once I forced it to fully upgrade it seems to be stable again.
Reply
#9
The errors were security related, so some security bits maybe hadn't gotten done.
Dean Roddey
Software Geek Extraordinaire
Reply
#10
(11-26-2017, 04:51 PM)Dean Roddey Wrote: The errors were security related, so some security bits maybe hadn't gotten done.

As always Dean thank you for such excellent customer support!
Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  "Client Side Driver Directory Could Not be Cleaned Out" TurboSam 7 43 2 hours ago
Last Post: Dean Roddey
  CML Driver IDE docs - where? rbroders 1 35 Yesterday, 05:41 PM
Last Post: Dean Roddey
  Timer Driver Question kblagron 5 112 09-14-2018, 02:43 AM
Last Post: znelbok
  reset driver statistics? rbroders 9 344 09-11-2018, 07:50 PM
Last Post: Dean Roddey
  Driver Configuration w/8 prompts rbroders 1 255 09-03-2018, 09:28 PM
Last Post: Dean Roddey
  Driver info/stats rbroders 6 361 09-02-2018, 08:34 PM
Last Post: Dean Roddey
  Sonos Driver zra 3 185 09-01-2018, 03:09 PM
Last Post: Dean Roddey
  HTTP Get driver not working znelbok 10 513 08-28-2018, 10:10 AM
Last Post: Dean Roddey
  Can't add fields to ElkDev driver rbroders 4 288 08-07-2018, 06:24 PM
Last Post: Dean Roddey
  Possible to copy all the name in a driver so can paste is elsewhere? ghurty 11 665 07-14-2018, 05:24 PM
Last Post: Dean Roddey

Forum Jump:


Users browsing this thread: 1 Guest(s)