I experienced this problem last Friday and Saturday, where VT (0.50.09) would stop getting data about 30 minutes after each restart. Also worth noting is that VT is not reporting any errors. The main symptom I see is that the graphs screen is not getting data points. The overview page did seem to refresh, but I may have fooled myself.
A quick check of the VT log showed the following unusual combination of warnings (these occur multiple times separated by anywhere from 1 to 20 minutes):
Aug 21, 2015 4:27:03 PM org.noroomattheinn.tesla.Streamer refreshAuthentication
WARNING: Error: couldn't retreive auth tokens
Aug 21, 2015 4:27:03 PM org.noroomattheinn.tesla.Streamer establishStreamingConnection
WARNING: Can't authenticate for streaming!
(I can provide more details on request)
As of Sunday, everything is working normally again for me.
To minimize the load on Tesla servers, I leave VT in sleep mode except when I want to actively track charging or driving data. Sleep mode is sufficient to track vampire losses.
That said, I was not logging much data on Friday and Saturday, when I experienced VT's difficulty retrieving data, so I don't think it is the pattern of access which is provoking the problem. More likely, Tesla is tweaking something in their authentication infrastructure and VT may more trouble handling the reauthentication errors than the phone apps.
A quick check of the VT log showed the following unusual combination of warnings (these occur multiple times separated by anywhere from 1 to 20 minutes):
Aug 21, 2015 4:27:03 PM org.noroomattheinn.tesla.Streamer refreshAuthentication
WARNING: Error: couldn't retreive auth tokens
Aug 21, 2015 4:27:03 PM org.noroomattheinn.tesla.Streamer establishStreamingConnection
WARNING: Can't authenticate for streaming!
(I can provide more details on request)
As of Sunday, everything is working normally again for me.
To minimize the load on Tesla servers, I leave VT in sleep mode except when I want to actively track charging or driving data. Sleep mode is sufficient to track vampire losses.
That said, I was not logging much data on Friday and Saturday, when I experienced VT's difficulty retrieving data, so I don't think it is the pattern of access which is provoking the problem. More likely, Tesla is tweaking something in their authentication infrastructure and VT may more trouble handling the reauthentication errors than the phone apps.