We have moved at community.getvera.com

Author Topic: GCAL3 - General Discussion  (Read 192696 times)

Offline minimoibientot

  • Sr. Newbie
  • *
  • Posts: 30
  • Karma: +0/-0
Re: GCAL3 - V 1.1 Released
« Reply #285 on: February 09, 2015, 03:54:51 am »
Hello
I have a little trouble with a GCal3 in v1.1 under UI5

at 6:20, it remained tripped until I make a check around 7:40
While the event lasts 2 minutes

yesterday morning my vera planted was also cause for my GCAL3
I have these concerns since I went in 1.1

Thank you

edit
error : Fatal error - access token
check  = checking ... faor many minutes

Code: [Select]
02/09/15 20:23:37.160 luup_log:206: GCal3 V 1.1:Device 206 claimed semaphore <0x2f291680>
01 02/09/15 20:23:37.163 LuaInterface::CallFunction_Timer-5 function GCalMain failed [string "local GCAL_VERSION = "V 1.1"  ..."]:220: attempt to concatenate field 'access_token' (a nil value) <0x2f291680>
« Last Edit: February 09, 2015, 02:25:16 pm by minimoibientot »

Offline Stuart

  • Moderator
  • Hero Member
  • *****
  • Posts: 728
  • Karma: +71/-2
Re: GCAL3 - V 1.1 Released
« Reply #286 on: February 09, 2015, 04:01:54 pm »
Hate to be that guy.. I cant seem to find the setup information for this plugin. I keep getting an error, Its attached as an image... cant seem to figure out what it is i am doing wrong.

They are on the very first post of this thread. Enjoy.

Offline Octoplayer

  • Jr. Member
  • **
  • Posts: 82
  • Karma: +3/-0
Re: GCAL3 - Google Calendar 3
« Reply #287 on: February 09, 2015, 06:44:14 pm »
Quote

I have a 'one word' answer ....... PLEG.  .

Hi,
I have been using PLEG (another wonderful plugin) to generate events, and then run an appropriate Scene. Having finally got my TRVs and Ping Sensors under control, I want to make a more flexible control process. My intent is to use the GCal plugin, as it looks ideal for family access.
 
So far I have got GCal3 set up and reading events into gc_jsonEVENTS. (I get 404 on the calendar tab, and nothing in _value yet, but early days).

My thinking is to create events saying SCENE{Bedtime} or SCENE{Holiday}, trigger PLEG with an action that then runs the scene as defined in parameter gc_value field. I have been through all the posts, and cannot see anything that looks like that - before I start reinventing the wheel... has anyone tried such a process, or is there a simpler way to do it?

Thanks

Offline Octoplayer

  • Jr. Member
  • **
  • Posts: 82
  • Karma: +3/-0
Re: GCAL3 - V 1.1 Released
« Reply #288 on: February 12, 2015, 08:10:46 am »
Quote
My thinking is to create events saying SCENE{Bedtime} or SCENE{Holiday}, trigger PLEG with an action that then runs the scene as defined in parameter gc_value field

FWIW, I now have this working: I can now create GCal events saying Scene{50} or Scene{51} for example, and it executes the appropriate scene  :)

I look for a keyword SCENE, have a PLEG trigger (tGCal) on the GCAL trip, with a Device Property input looking gc_value (pGCalValue). I check for a condition of tGCal being true, then the action is to Run Scene, with {(pGCalValue)} as the scene to run.

For some reason, putting the Scene name in as the parameter does not work, which would make the calendar more readable. I have been doing some tests, but cannot find a format that works (yet).

Octoplayer




Offline minimoibientot

  • Sr. Newbie
  • *
  • Posts: 30
  • Karma: +0/-0
Re: GCAL3 - V 1.1 Released
« Reply #289 on: February 12, 2015, 01:32:33 pm »
again of the problems this morning:
lock on "succefull initialized"
  ???

Offline Stuart

  • Moderator
  • Hero Member
  • *****
  • Posts: 728
  • Karma: +71/-2
Re: GCAL3 - V 1.1 Released
« Reply #290 on: February 12, 2015, 09:18:45 pm »
again of the problems this morning:
lock on "succefull initialized"
  ???
The problem is being caused (based on your earlier post) because the plugin is unable to get a valid access token from google.  This could be for a number of reasons including not being able to contact google.

The snippit of the log file you sent is a symptom not the cause i.e. the real problem occurred before that line of code.  Please set gc_debug to 3 and get a log file and we can see where the error is occurring.  I'll also look to see if the failure can be made more graceful.

Offline minimoibientot

  • Sr. Newbie
  • *
  • Posts: 30
  • Karma: +0/-0
Re: GCAL3 - V 1.1 Released
« Reply #291 on: February 14, 2015, 05:12:37 am »
Code: [Select]
50 02/14/15 10:40:23.101 luup_log:203: GCal3 V 1.1:Delay = delayedstart <0x2ecdb680>
50 02/14/15 10:40:23.101 luup_log:203: GCal3 V 1.1:Checking semaphore <0x2ecdb680>
50 02/14/15 10:40:23.143 luup_log:204: GCal3 V 1.1:Delay = delayedstart <0x2eedb680>
50 02/14/15 10:40:23.143 luup_log:204: GCal3 V 1.1:Checking semaphore <0x2eedb680>
50 02/14/15 10:40:23.171 luup_log:204: GCal3 V 1.1:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2eedb680>
50 02/14/15 10:40:23.191 luup_log:204: GCal3 V 1.1:Semaphore file returned 194 <0x2eedb680>
50 02/14/15 10:40:23.213 luup_log:203: GCal3 V 1.1:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2ecdb680>
50 02/14/15 10:40:23.215 luup_log:203: GCal3 V 1.1:Semaphore file returned 194 <0x2ecdb680>
06 02/14/15 10:40:23.264 Device_Variable::m_szValue_set device: 193 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: Watts was: 2410 now: 5450 #hooks: 0 upnp: 0 v:0xdf70e8/NONE duplicate:0 <0x3131c680>
06 02/14/15 10:40:23.265 Device_Variable::m_szValue_set device: 193 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: Log was: 2410,2291,3010,1423906821,622 now: 5450,2291,5450,1423906823,624 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x3131c680>
50 02/14/15 10:40:23.283 luup_log:203: GCal3 V 1.1:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2ecdb680>
50 02/14/15 10:40:23.301 luup_log:203: GCal3 V 1.1:Device 194 blocked semaphore request from device 203 <0x2ecdb680>
06 02/14/15 10:40:23.301 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_NextEvent was: Waiting for startup now: Waiting for startup #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2ecdb680>
06 02/14/15 10:40:23.301 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_NextEventTime was:  now:  #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2ecdb680>
50 02/14/15 10:40:23.292 luup_log:204: GCal3 V 1.1:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2eedb680>
50 02/14/15 10:40:23.320 luup_log:204: GCal3 V 1.1:Device 194 blocked semaphore request from device 204 <0x2eedb680>
06 02/14/15 10:40:23.321 Device_Variable::m_szValue_set device: 204 service: urn:srs-com:serviceId:GCalIII variable: gc_NextEvent was: Waiting for startup now: Waiting for startup #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2eedb680>
06 02/14/15 10:40:23.322 Device_Variable::m_szValue_set device: 204 service: urn:srs-com:serviceId:GCalIII variable: gc_NextEventTime was:  now:  #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2eedb680>

Offline Stuart

  • Moderator
  • Hero Member
  • *****
  • Posts: 728
  • Karma: +71/-2
Re: GCAL3 - V 1.1 Released
« Reply #292 on: February 14, 2015, 11:10:41 am »
Code: [Select]
50 02/14/15 10:40:23.101 luup_log:203: GCal3 V 1.1:Delay = delayedstart <0x2ecdb680>
50 02/14/15 10:40:23.101 luup_log:203: GCal3 V 1.1:Checking semaphore <0x2ecdb680>
50 02/14/15 10:40:23.143 luup_log:204: GCal3 V 1.1:Delay = delayedstart <0x2eedb680>
50 02/14/15 10:40:23.143 luup_log:204: GCal3 V 1.1:Checking semaphore <0x2eedb680>
50 02/14/15 10:40:23.171 luup_log:204: GCal3 V 1.1:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2eedb680>
50 02/14/15 10:40:23.191 luup_log:204: GCal3 V 1.1:Semaphore file returned 194 <0x2eedb680>
50 02/14/15 10:40:23.213 luup_log:203: GCal3 V 1.1:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2ecdb680>
50 02/14/15 10:40:23.215 luup_log:203: GCal3 V 1.1:Semaphore file returned 194 <0x2ecdb680>
06 02/14/15 10:40:23.264 Device_Variable::m_szValue_set device: 193 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: Watts was: 2410 now: 5450 #hooks: 0 upnp: 0 v:0xdf70e8/NONE duplicate:0 <0x3131c680>
06 02/14/15 10:40:23.265 Device_Variable::m_szValue_set device: 193 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: Log was: 2410,2291,3010,1423906821,622 now: 5450,2291,5450,1423906823,624 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x3131c680>
50 02/14/15 10:40:23.283 luup_log:203: GCal3 V 1.1:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2ecdb680>
50 02/14/15 10:40:23.301 luup_log:203: GCal3 V 1.1:Device 194 blocked semaphore request from device 203 <0x2ecdb680>
06 02/14/15 10:40:23.301 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_NextEvent was: Waiting for startup now: Waiting for startup #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2ecdb680>
06 02/14/15 10:40:23.301 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_NextEventTime was:  now:  #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2ecdb680>
50 02/14/15 10:40:23.292 luup_log:204: GCal3 V 1.1:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2eedb680>
50 02/14/15 10:40:23.320 luup_log:204: GCal3 V 1.1:Device 194 blocked semaphore request from device 204 <0x2eedb680>
06 02/14/15 10:40:23.321 Device_Variable::m_szValue_set device: 204 service: urn:srs-com:serviceId:GCalIII variable: gc_NextEvent was: Waiting for startup now: Waiting for startup #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2eedb680>
06 02/14/15 10:40:23.322 Device_Variable::m_szValue_set device: 204 service: urn:srs-com:serviceId:GCalIII variable: gc_NextEventTime was:  now:  #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2eedb680>

This portion of the log tells me that you have 3 GCal3 devices 203,204 and 194.  Device 194 is either trying to startup (more likely) or busy doing something(less likely)  -so we need to see the portion of the log before this to see shat device 194 is doing - probably what errors it is reporting.

These semaphore messages are normal - not an error - but can point to which device is causing an error.

Offline minimoibientot

  • Sr. Newbie
  • *
  • Posts: 30
  • Karma: +0/-0
Re: GCAL3 - V 1.1 Released
« Reply #293 on: February 15, 2015, 07:47:50 am »
Here are the logs
GCal3 blocking Today # 206 of checking

Code: [Select]
08 02/15/15 13:19:18.979 JobHandler_LuaUPnP::HandleActionRequest device: 206 service: urn:srs-com:serviceId:GCalIII action: GCalCheck <0x3128b680>
08 02/15/15 13:19:18.979 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=206 <0x3128b680>
08 02/15/15 13:19:18.979 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:srs-com:serviceId:GCalIII <0x3128b680>
08 02/15/15 13:19:18.979 JobHandler_LuaUPnP::HandleActionRequest argument action=GCalCheck <0x3128b680>
08 02/15/15 13:19:18.980 JobHandler_LuaUPnP::HandleActionRequest argument rand=0.10461730132162972 <0x3128b680>
06 02/15/15 13:19:18.980 Device_Variable::m_szValue_set device: 206 service: urn:srs-com:serviceId:GCalIII variable: gc_NextEvent was: Checking ... now: Checking ... #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x3128b680>
06 02/15/15 13:19:18.981 Device_Variable::m_szValue_set device: 206 service: urn:srs-com:serviceId:GCalIII variable: gc_NextEventTime was:  now:  #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x3128b680>
06 02/15/15 13:19:19.455 Device_Variable::m_szValue_set device: 193 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: Watts was: 3080 now: 3060 #hooks: 0 upnp: 0 v:0xb1dbb0/NONE duplicate:0 <0x30048680>
06 02/15/15 13:19:19.456 Device_Variable::m_szValue_set device: 193 service: urn:micasaverde-com:serviceId:EnergyMetering1 variable: Log was: 3080,2996,5150,1424002756,2957 now: 3060,2996,5150,1424002759,2960 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x30048680>
02 02/15/15 13:19:19.526 ZW_Send_Data node 4 NO ROUTE (nil) <0x2b807680>
06 02/15/15 13:19:20.004 Device_Variable::m_szValue_set device: 206 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-15 at 12:55:20 now: 2015-02-15 at 13:19:20 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2ea07680>
06 02/15/15 13:19:20.005 Device_Variable::m_szValue_set device: 206 service: urn:srs-com:serviceId:GCalIII variable: gc_jsonEvents was: [] now: [] #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2ea07680>
50 02/15/15 13:19:20.006 luup_log:206: GCal3 V 1.1:Checking semaphore <0x2ea07680>
50 02/15/15 13:19:20.055 luup_log:206: GCal3 V 1.1:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2ea07680>
50 02/15/15 13:19:20.056 luup_log:206: GCal3 V 1.1:Semaphore file returned 206 <0x2ea07680>
50 02/15/15 13:19:20.128 luup_log:206: GCal3 V 1.1:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2ea07680>
50 02/15/15 13:19:20.129 luup_log:206: GCal3 V 1.1:Device 206 claimed semaphore <0x2ea07680>
50 02/15/15 13:19:20.131 luup_log:206: GCal3 V 1.1:StartMin is 2015-02-15T00:00:00.000Z StartMax is 2015-02-16T15:19:20.000Z <0x2ea07680>
50 02/15/15 13:19:20.131 luup_log:206: GCal3 V 1.1:End of day is 2015-02-15T23:59:59 <0x2ea07680>
50 02/15/15 13:19:20.131 luup_log:206: GCal3 V 1.1:Function: requestCalendar <0x2ea07680>
50 02/15/15 13:19:20.132 luup_log:206: GCal3 V 1.1:Function: get_access_token <0x2ea07680>
06 02/15/15 13:19:21.109 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-15 at 13:19:16 now: 2015-02-15 at 13:19:21 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2e607680>
06 02/15/15 13:19:21.171 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_jsonEvents was: [] now: [] #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2e607680>
06 02/15/15 13:19:21.227 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_nextCheck was: 2015-02-15 at 13:19:21 now: 2015-02-15 at 13:19:26 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2e607680>
50 02/15/15 13:19:21.228 luup_log:203: GCal3 V 1.1:Next check will be in 5 sec on 2015-02-15 at 13:19:26 <0x2e607680>
02 02/15/15 13:19:21.656 ZW_Send_Data node 4 USING ROUTE 3.0.0.0 <0x2b807680>
04 02/15/15 13:19:21.797 <0x2b407680>
06 02/15/15 13:19:26.101 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-15 at 13:19:21 now: 2015-02-15 at 13:19:26 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2e607680>
06 02/15/15 13:19:26.135 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_jsonEvents was: [] now: [] #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2e607680>
06 02/15/15 13:19:26.191 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_nextCheck was: 2015-02-15 at 13:19:26 now: 2015-02-15 at 13:19:31 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2e607680>
50 02/15/15 13:19:26.192 luup_log:203: GCal3 V 1.1:Next check will be in 5 sec on 2015-02-15 at 13:19:31 <0x2e607680>
06 02/15/15 13:19:31.101 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-15 at 13:19:26 now: 2015-02-15 at 13:19:31 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2e607680>
06 02/15/15 13:19:31.222 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_jsonEvents was: [] now: [] #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2e607680>
06 02/15/15 13:19:31.289 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_nextCheck was: 2015-02-15 at 13:19:31 now: 2015-02-15 at 13:19:36 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2e607680>
50 02/15/15 13:19:31.290 luup_log:203: GCal3 V 1.1:Next check will be in 5 sec on 2015-02-15 at 13:19:36 <0x2e607680>
01 02/15/15 13:19:35.159 LuaInterface::CallFunction_Timer-5 function GCalMain failed [string "local GCAL_VERSION = "V 1.1"  ..."]:222: attempt to concatenate local 'status' (a nil value) <0x2ea07680>
06 02/15/15 13:19:36.101 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-15 at 13:19:31 now: 2015-02-15 at 13:19:36 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2e607680>
06 02/15/15 13:19:36.162 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_jsonEvents was: [] now: [] #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2e607680>
06 02/15/15 13:19:36.219 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_nextCheck was: 2015-02-15 at 13:19:36 now: 2015-02-15 at 13:19:41 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2e607680>
50 02/15/15 13:19:36.220 luup_log:203: GCal3 V 1.1:Next check will be in 5 sec on 2015-02-15 at 13:19:41 <0x2e607680>
06 02/15/15 13:19:41.101 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-15 at 13:19:36 now: 2015-02-15 at 13:19:41 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2e607680>
06 02/15/15 13:19:41.133 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_jsonEvents was: [] now: [] #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2e607680>
06 02/15/15 13:19:41.192 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_nextCheck was: 2015-02-15 at 13:19:41 now: 2015-02-15 at 13:19:46 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2e607680>
50 02/15/15 13:19:41.193 luup_log:203: GCal3 V 1.1:Next check will be in 5 sec on 2015-02-15 at 13:19:46 <0x2e607680>
06 02/15/15 13:19:46.101 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-15 at 13:19:41 now: 2015-02-15 at 13:19:46 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2e607680>
06 02/15/15 13:19:46.133 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_jsonEvents was: [] now: [] #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2e607680>
06 02/15/15 13:19:46.189 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_nextCheck was: 2015-02-15 at 13:19:46 now: 2015-02-15 at 13:19:51 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2e607680>
50 02/15/15 13:19:46.190 luup_log:203: GCal3 V 1.1:Next check will be in 5 sec on 2015-02-15 at 13:19:51 <0x2e607680>
02 02/15/15 13:19:47.103 ZW_Send_Data node 11 USING ROUTE 3.0.0.0 <0x2b807680>
06 02/15/15 13:19:51.101 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-15 at 13:19:46 now: 2015-02-15 at 13:19:51 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2e607680>
06 02/15/15 13:19:51.135 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_jsonEvents was: [] now: [] #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2e607680>
06 02/15/15 13:19:51.191 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_nextCheck was: 2015-02-15 at 13:19:51 now: 2015-02-15 at 13:19:56 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2e607680>
50 02/15/15 13:19:51.192 luup_log:203: GCal3 V 1.1:Next check will be in 5 sec on 2015-02-15 at 13:19:56 <0x2e607680>
02 02/15/15 13:19:51.387 ZW_Send_Data node 11 USING ROUTE 3.0.0.0 <0x2b807680>
06 02/15/15 13:19:56.101 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-15 at 13:19:51 now: 2015-02-15 at 13:19:56 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2e607680>
06 02/15/15 13:19:56.205 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_jsonEvents was: [] now: [] #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2e607680>
06 02/15/15 13:20:01.101 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-15 at 13:19:56 now: 2015-02-15 at 13:20:01 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2e607680>
06 02/15/15 13:20:01.132 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_jsonEvents was: [] now: [] #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2e607680>
06 02/15/15 13:20:01.190 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_nextCheck was: 2015-02-15 at 13:20:01 now: 2015-02-15 at 13:20:06 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2e607680>
50 02/15/15 13:20:01.191 luup_log:203: GCal3 V 1.1:Next check will be in 5 sec on 2015-02-15 at 13:20:06 <0x2e607680>
06 02/15/15 13:20:06.101 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-15 at 13:20:01 now: 2015-02-15 at 13:20:06 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2e607680>
06 02/15/15 13:20:06.159 Device_Variable::m_szValue_set device: 203 service: urn:srs-com:serviceId:GCalIII variable: gc_jsonEvents was: [] now: [] #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2e607680>

and
Quote
http error code : closed

Code: [Select]
06 02/15/15 13:55:00.101 Device_Variable::m_szValue_set device: 206 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-15 at 13:39:27 now: 2015-02-15 at 13:55:00 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2ee09680>
06 02/15/15 13:55:00.131 Device_Variable::m_szValue_set device: 206 service: urn:srs-com:serviceId:GCalIII variable: gc_jsonEvents was: [{'eventEnd':1423958460,'eventStart':1423958400,'eventParameter':'ON','eventName':'CHARGE'},{'eventEnd':1423978020,'eventStart':1423977900,'eventParameter':'LED_cuisine_ON','eventName':'LAMPE'},{'eventEnd':1423979820,'eventStart':1423979700,'eventParameter':'\'PROG\':\'JOUR\'','eventName':'CHAUFF'},{'eventEnd':1423980000,'eventStart':1423979880,'eventParameter':'OFF','eventName':'CHARGE'},{'eventEnd':1423980420,'eventStart':1423980300,'eventParameter':'LED_cuisine_OFF','eventName':'LAMPE'},{'eventEnd':1423998360,'eventStart':1423998300,'eventParameter':'ON','eventName':'CHARGE'},{'eventEnd':1424004960,'eventStart':1424004900,'eventParameter':'OFF','eventName':'CHARGE'},{'eventEnd':1424017920,'eventStart':1424017800,'eventParameter':'LED_cuisine_ON','eventName':'LAMPE'},{'eventEnd':1424025120,'eventStart':1424025000,'eventParameter':'\'PROG\':\'NUIT\'','eventName':'CHAUFF'},{'eventEnd':1424025660,'eventStart':1424025600,'eventParameter':'chLampe_ON','eventName':'LAMPE'},{'eventEnd':1424027460,'eventStart':1424027400,'eventParameter':'fleurs_ON','eventName':'LAMPE'},{'eventEnd':1424034420,'eventStart':1424034300,'eventParameter':'fleurs_OFF','eventName':'LAMPE'},{'eventEnd':1424035860,'eventStart':1424035800,'eventParameter':'chLampe_OFF','eventName':'LAMPE'},{'eventEnd':1424037120,'eventStart':1424037000,'eventParameter':'LED_cuisine_OFF','eventName':'LAMPE'},{'eventEnd':1424044860,'eventStart':1424044800,'eventParameter':'ON','eventName':'CHARGE'},{'eventEnd':1424064420,'eventStart':1424064300,'eventParameter':'LED_cuisine_ON','eventName':'LAMPE'},{'eventEnd':1424066220,'eventStart':1424066100,'eventParameter':'\'PROG\':\'JOUR\'','eventName':'CHAUFF'},{'eventEnd':1424066400,'eventStart':1424066280,'eventParameter':'OFF','eventName':'CHARGE'},{'eventEnd':1424066820,'eventStart':1424066700,'eventParameter':'LED_cuisine_OFF','eventName':'LAMPE'},{'eventEnd':1424084760,'eventStart':1424084700,'eventParameter':'ON','eventName':'CHARGE'},{'eventEnd':1424091360,'eventStart':1424091300,'eventParameter':'OFF','eventName':'CHARGE'}] now: [] #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2ee09680>
50 02/15/15 13:55:00.131 luup_log:206: GCal3 V 1.1:Checking semaphore <0x2ee09680>
50 02/15/15 13:55:00.157 luup_log:206: GCal3 V 1.1:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2ee09680>
50 02/15/15 13:55:00.157 luup_log:206: GCal3 V 1.1:Semaphore file returned 0 <0x2ee09680>
50 02/15/15 13:55:00.158 luup_log:206: GCal3 V 1.1:Device 206 requested semaphore <0x2ee09680>
50 02/15/15 13:55:00.183 luup_log:206: GCal3 V 1.1:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2ee09680>
50 02/15/15 13:55:00.184 luup_log:206: GCal3 V 1.1:Device 206 claimed semaphore <0x2ee09680>
50 02/15/15 13:55:00.187 luup_log:206: GCal3 V 1.1:StartMin is 2015-02-15T00:00:00.000Z StartMax is 2015-02-16T15:55:00.000Z <0x2ee09680>
50 02/15/15 13:55:00.187 luup_log:206: GCal3 V 1.1:End of day is 2015-02-15T23:59:59 <0x2ee09680>
50 02/15/15 13:55:00.188 luup_log:206: GCal3 V 1.1:Function: requestCalendar <0x2ee09680>
50 02/15/15 13:55:00.188 luup_log:206: GCal3 V 1.1:Function: get_access_token <0x2ee09680>
50 02/15/15 13:55:02.267 luup_log:206: GCal3 V 1.1:Token info status: HTTP/1.1 200 OK <0x2ee09680>
50 02/15/15 13:55:02.272 luup_log:206: GCal3 V 1.1:Token will expire in 2666 sec <0x2ee09680>
50 02/15/15 13:55:02.272 luup_log:206: GCal3 V 1.1:Checking google calendar <0x2ee09680>
06 02/15/15 13:55:02.273 Device_Variable::m_szValue_set device: 206 service: urn:srs-com:serviceId:GCalIII variable: gc_NextEvent was: CHARGE now: Accessing Calendar #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2ee09680>
06 02/15/15 13:55:02.274 Device_Variable::m_szValue_set device: 206 service: urn:srs-com:serviceId:GCalIII variable: gc_NextEventTime was: 13:55 Feb 15 to 13:56 Feb 15 now:  #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2ee09680>
50 02/15/15 13:55:02.275 luup_log:206: GCal3 V 1.1:Requested url: https://www.googleapis.com/calendar/v3/calendars/cb99pkuse41r6f4fjkatc3unpc@group.calendar.google.com/events?access_token=ya29.GwGJHiXFXxv87hi4ux4M4An9aoB7O3A65KNs4K9sF85k9lAcI2Ha49VE&timeZone=utc&singleEvents=true&orderBy=startTime&timeMax=2015-02-16T15:55:00.000Z&timeMin=2015-02-15T00:00:00.000Z&fields=items(description%2Cend%2Cstart%2Csummary) <0x2ee09680>
50 02/15/15 13:55:34.467 luup_log:206: GCal3 V 1.1:Http request error. Code : closed <0x2ee09680>
06 02/15/15 13:55:34.468 Device_Variable::m_szValue_set device: 206 service: urn:srs-com:serviceId:GCalIII variable: gc_NextEvent was: Accessing Calendar now: http error code: closed #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2ee09680>
06 02/15/15 13:55:34.469 Device_Variable::m_szValue_set device: 206 service: urn:srs-com:serviceId:GCalIII variable: gc_NextEventTime was:  now:  #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:1 <0x2ee09680>
50 02/15/15 13:55:34.471 luup_log:206: GCal3 V 1.1:Device 206 released the semaphore - reason: calendar check complete <0x2ee09680>
06 02/15/15 13:55:34.473 Device_Variable::m_szValue_set device: 206 service: urn:srs-com:serviceId:GCalIII variable: gc_nextCheck was: 2015-02-15 at 13:55:00 now: 2015-02-15 at 16:55:00 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2ee09680>
50 02/15/15 13:55:34.473 luup_log:206: GCal3 V 1.1:Next check will be in 10800 sec on 2015-02-15 at 16:55:00 <0x2ee09680>
« Last Edit: February 15, 2015, 10:29:36 am by minimoibientot »

Offline Stuart

  • Moderator
  • Hero Member
  • *****
  • Posts: 728
  • Karma: +71/-2
Re: GCAL3 - V 1.1 Released
« Reply #294 on: February 15, 2015, 11:29:03 am »
@minimoibientot

It looks a time out on the request to get the calendar data.  There is a ~30 sec delay between the request for the data and the error and this is the same as the request timeout setting.

50   02/15/15 13:55:34.467   luup_log:206: GCal3 V 1.1:Http request error. Code : closed <0x2ee09680>

Also - the error code "closed" is not a http error code and may be being generated by the lua module that is making the call.

I will post a version of GCal3.lua later today that has some debug code around this to see if we can figure out what's going on.

My best guess is that this is a network or google related error.  Do you have a very reliable network ?   Do you sometimes have trouble accessing google ?

Also - what version of vera UI, what vera hardware and what release level are you using ?  The reason I ask is that there are differences - so I want to make sure we understand if that's a possibility.

Offline minimoibientot

  • Sr. Newbie
  • *
  • Posts: 30
  • Karma: +0/-0
Re: GCAL3 - V 1.1 Released
« Reply #295 on: February 15, 2015, 11:54:10 am »
thank you for the help

what is strange is that I have 5 GCal3
and only the # 206 raises concerns

I am under :
UI5
1.5.622FR
GCal3 v1.1

Offline Stuart

  • Moderator
  • Hero Member
  • *****
  • Posts: 728
  • Karma: +71/-2
Re: GCAL3 - V 1.1 Released
« Reply #296 on: February 15, 2015, 03:05:39 pm »
thank you for the help

what is strange is that I have 5 GCal3
and only the # 206 raises concerns

I am under :
UI5
1.5.622FR
GCal3 v1.1

What happens if you set device 206 to a different calendar (i.e. one of the other calendars that you have set and which work ?).  There is no problem pointing 2 instances of GCal3 to the same calendar.

Offline minimoibientot

  • Sr. Newbie
  • *
  • Posts: 30
  • Karma: +0/-0
Re: GCAL3 - V 1.1 Released
« Reply #297 on: February 15, 2015, 03:31:44 pm »
I actually #206 and #203 that are on the same schedule
1 Trigge on "chauff"
and another without keyword


and only #206 indicates errors

Offline Stuart

  • Moderator
  • Hero Member
  • *****
  • Posts: 728
  • Karma: +71/-2
Re: GCAL3 - V 1.1 Released
« Reply #298 on: February 15, 2015, 05:56:08 pm »
I actually #206 and #203 that are on the same schedule
1 Trigge on "chauff"
and another without keyword


and only #206 indicates errors

Try this version og GCal3.lua.  I do not expect it to fix anything - just give a bit more debug info.  Also - I noticed an error being thrown after what looks like the https.request timeout which I  hope is now suppressed.

Then take a look at the lines that look like this - for both #206 and #203

Requested url: https://www.googleapis.com/calendar/v3/calendars/cb99pkuse41r6f4fjkatc3unpc@group.calendar.google.com/events?access_token=ya29.GwGJHiXFXxv87hi4ux4M4An9aoB7O3A65KNs4K9sF85k9lAcI2Ha49VE&timeZone=utc&singleEvents=true&orderBy=startTime&timeMax=2015-02-16T15:55:00.000Z&timeMin=2015-02-15T00:00:00.000Z&fields=items(description%2Cend%2Cstart%2Csummary)

They should be identical.

EDIT: Removed attachment
« Last Edit: February 25, 2015, 03:26:58 pm by Stuart »

Offline minimoibientot

  • Sr. Newbie
  • *
  • Posts: 30
  • Karma: +0/-0
Re: GCAL3 - V 1.1 Released
« Reply #299 on: February 16, 2015, 04:51:29 am »
file installed
thank you

I watch the logs