We have moved at community.getvera.com

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

Offline Stuart

  • Moderator
  • Hero Member
  • *****
  • Posts: 728
  • Karma: +71/-2
Re: GCAL3 - V 1.1 Released
« Reply #300 on: February 24, 2015, 12:43:08 pm »
file installed
thank you

I watch the logs

How is it working ?

Offline minimoibientot

  • Sr. Newbie
  • *
  • Posts: 30
  • Karma: +0/-0
Re: GCAL3 - V 1.1 Released
« Reply #301 on: February 25, 2015, 01:05:21 pm »
goodnight Stuart

until today to 12:10
yes i do  ;)

but since "fatal error"

Code: [Select]
06 02/25/15 18:08:24.101 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-25 at 18:08:19 now: 2015-02-25 at 18:08:24 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f867680>
06 02/25/15 18:08:24.193 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_nextCheck was: 2015-02-25 at 18:08:24 now: 2015-02-25 at 18:08:29 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f867680>
50 02/25/15 18:08:24.194 luup_log:230: GCal3 V 1.2B:Next check will be in 5 sec on 2015-02-25 at 18:08:29 <0x2f867680>
06 02/25/15 18:08:29.101 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-25 at 18:08:24 now: 2015-02-25 at 18:08:29 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f867680>
06 02/25/15 18:08:29.204 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_nextCheck was: 2015-02-25 at 18:08:29 now: 2015-02-25 at 18:08:34 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f867680>
50 02/25/15 18:08:29.206 luup_log:230: GCal3 V 1.2B:Next check will be in 5 sec on 2015-02-25 at 18:08:34 <0x2f867680>
06 02/25/15 18:08:34.101 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-25 at 18:08:29 now: 2015-02-25 at 18:08:34 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f867680>
06 02/25/15 18:08:34.189 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_nextCheck was: 2015-02-25 at 18:08:34 now: 2015-02-25 at 18:08:39 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f867680>
50 02/25/15 18:08:34.260 luup_log:230: GCal3 V 1.2B:Next check will be in 5 sec on 2015-02-25 at 18:08:39 <0x2f867680>
06 02/25/15 18:08:39.102 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-25 at 18:08:34 now: 2015-02-25 at 18:08:39 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f867680>
06 02/25/15 18:08:39.188 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_nextCheck was: 2015-02-25 at 18:08:39 now: 2015-02-25 at 18:08:44 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f867680>
50 02/25/15 18:08:39.189 luup_log:230: GCal3 V 1.2B:Next check will be in 5 sec on 2015-02-25 at 18:08:44 <0x2f867680>
06 02/25/15 18:08:44.101 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-25 at 18:08:39 now: 2015-02-25 at 18:08:44 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f867680>
06 02/25/15 18:08:44.187 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_nextCheck was: 2015-02-25 at 18:08:44 now: 2015-02-25 at 18:08:49 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f867680>
50 02/25/15 18:08:44.188 luup_log:230: GCal3 V 1.2B:Next check will be in 5 sec on 2015-02-25 at 18:08:49 <0x2f867680>
06 02/25/15 18:08:49.101 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-25 at 18:08:44 now: 2015-02-25 at 18:08:49 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f867680>
06 02/25/15 18:08:49.189 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_nextCheck was: 2015-02-25 at 18:08:49 now: 2015-02-25 at 18:08:54 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f867680>
50 02/25/15 18:08:49.190 luup_log:230: GCal3 V 1.2B:Next check will be in 5 sec on 2015-02-25 at 18:08:54 <0x2f867680>
06 02/25/15 18:08:54.101 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-25 at 18:08:49 now: 2015-02-25 at 18:08:54 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f867680>
06 02/25/15 18:08:54.214 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_nextCheck was: 2015-02-25 at 18:08:54 now: 2015-02-25 at 18:08:59 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f867680>
50 02/25/15 18:08:54.216 luup_log:230: GCal3 V 1.2B:Next check will be in 5 sec on 2015-02-25 at 18:08:59 <0x2f867680>
08 02/25/15 18:08:57.321 JobHandler_LuaUPnP::HandleActionRequest device: 206 service: urn:srs-com:serviceId:GCalIII action: GCalCheck <0x325a8680>
08 02/25/15 18:08:57.321 JobHandler_LuaUPnP::HandleActionRequest argument DeviceNum=206 <0x325a8680>
08 02/25/15 18:08:57.322 JobHandler_LuaUPnP::HandleActionRequest argument serviceId=urn:srs-com:serviceId:GCalIII <0x325a8680>
08 02/25/15 18:08:57.322 JobHandler_LuaUPnP::HandleActionRequest argument action=GCalCheck <0x325a8680>
08 02/25/15 18:08:57.322 JobHandler_LuaUPnP::HandleActionRequest argument rand=0.2834179020163041 <0x325a8680>
06 02/25/15 18:08:57.323 Device_Variable::m_szValue_set device: 206 service: urn:srs-com:serviceId:GCalIII variable: gc_NextEvent was: Fatal error - access token now: Checking ... #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x325a8680>
06 02/25/15 18:08:57.323 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 <0x325a8680>
02 02/25/15 18:08:57.368 ZW_Send_Data node 12 USING ROUTE 3.0.0.0 <0x2c467680>
06 02/25/15 18:08:59.101 Device_Variable::m_szValue_set device: 206 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-25 at 16:55:27 now: 2015-02-25 at 18:08:59 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f667680>
50 02/25/15 18:08:59.102 luup_log:206: GCal3 V 1.2B:Checking semaphore <0x2f667680>
06 02/25/15 18:08:59.120 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-25 at 18:08:54 now: 2015-02-25 at 18:08:59 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f867680>
50 02/25/15 18:08:59.174 luup_log:206: GCal3 V 1.2B:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2f667680>
50 02/25/15 18:08:59.176 luup_log:206: GCal3 V 1.2B:Semaphore file returned 206 <0x2f667680>
50 02/25/15 18:08:59.223 luup_log:206: GCal3 V 1.2B:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2f667680>
50 02/25/15 18:08:59.226 luup_log:206: GCal3 V 1.2B:Device 206 claimed semaphore <0x2f667680>
50 02/25/15 18:08:59.228 luup_log:206: GCal3 V 1.2B:StartMin is 2015-02-25T00:00:00.000Z StartMax is 2015-02-26T20:08:59.000Z <0x2f667680>
50 02/25/15 18:08:59.228 luup_log:206: GCal3 V 1.2B:End of day is 2015-02-25T23:59:59 <0x2f667680>
50 02/25/15 18:08:59.229 luup_log:206: GCal3 V 1.2B:Function: requestCalendar <0x2f667680>
50 02/25/15 18:08:59.229 luup_log:206: GCal3 V 1.2B:Function: get_access_token <0x2f667680>
01 02/25/15 18:08:59.229 LuaInterface::CallFunction_Timer-5 function GCalMain failed [string "local GCAL_VERSION = "V 1.2B"  ..."]:227: attempt to concatenate field 'access_token' (a nil value) <0x2f667680>
06 02/25/15 18:08:59.431 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_nextCheck was: 2015-02-25 at 18:08:59 now: 2015-02-25 at 18:09:04 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f867680>
50 02/25/15 18:08:59.432 luup_log:230: GCal3 V 1.2B:Next check will be in 5 sec on 2015-02-25 at 18:09:04 <0x2f867680>
02 02/25/15 18:08:59.519 ZW_Send_Data node 12 USING ROUTE 3.0.0.0 <0x2c467680>
06 02/25/15 18:09:04.102 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-25 at 18:08:59 now: 2015-02-25 at 18:09:04 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f867680>
06 02/25/15 18:09:04.186 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_nextCheck was: 2015-02-25 at 18:09:04 now: 2015-02-25 at 18:09:09 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f867680>
50 02/25/15 18:09:04.187 luup_log:230: GCal3 V 1.2B:Next check will be in 5 sec on 2015-02-25 at 18:09:09 <0x2f867680>
06 02/25/15 18:09:09.101 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-25 at 18:09:04 now: 2015-02-25 at 18:09:09 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f867680>
06 02/25/15 18:09:09.188 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_nextCheck was: 2015-02-25 at 18:09:09 now: 2015-02-25 at 18:09:14 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f867680>
50 02/25/15 18:09:09.189 luup_log:230: GCal3 V 1.2B:Next check will be in 5 sec on 2015-02-25 at 18:09:14 <0x2f867680>
06 02/25/15 18:09:14.101 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-25 at 18:09:09 now: 2015-02-25 at 18:09:14 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f867680>
06 02/25/15 18:09:14.196 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_nextCheck was: 2015-02-25 at 18:09:14 now: 2015-02-25 at 18:09:19 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f867680>
50 02/25/15 18:09:14.197 luup_log:230: GCal3 V 1.2B:Next check will be in 5 sec on 2015-02-25 at 18:09:19 <0x2f867680>

or lock on "checking"  :-\

Code: [Select]
02/25/15 18:24:48.266 luup_log:230: GCal3 V 1.2B:Next check will be in 5 sec on 2015-02-25 at 18:24:53 <0x2f0f5680>
06 02/25/15 18:24:53.101 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-25 at 18:24:48 now: 2015-02-25 at 18:24:53 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f0f5680>
06 02/25/15 18:24:53.180 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_nextCheck was: 2015-02-25 at 18:24:53 now: 2015-02-25 at 18:24:58 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f0f5680>
50 02/25/15 18:24:53.181 luup_log:230: GCal3 V 1.2B:Next check will be in 5 sec on 2015-02-25 at 18:24:58 <0x2f0f5680>
50 02/25/15 18:24:54.101 luup_log:204: GCal3 V 1.2B:Delay = delayedstart <0x2ecf5680>
50 02/25/15 18:24:54.101 luup_log:204: GCal3 V 1.2B:Checking semaphore <0x2ecf5680>
50 02/25/15 18:24:54.126 luup_log:204: GCal3 V 1.2B:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2ecf5680>
50 02/25/15 18:24:54.127 luup_log:204: GCal3 V 1.2B:Semaphore file returned 206 <0x2ecf5680>
50 02/25/15 18:24:54.151 luup_log:204: GCal3 V 1.2B:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2ecf5680>
50 02/25/15 18:24:54.152 luup_log:204: GCal3 V 1.2B:Device 206 blocked semaphore request from device 204 <0x2ecf5680>
06 02/25/15 18:24:54.153 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 <0x2ecf5680>
06 02/25/15 18:24:54.153 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 <0x2ecf5680>
06 02/25/15 18:24:58.101 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-25 at 18:24:53 now: 2015-02-25 at 18:24:58 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f0f5680>
06 02/25/15 18:24:58.178 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_nextCheck was: 2015-02-25 at 18:24:58 now: 2015-02-25 at 18:25:03 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f0f5680>
50 02/25/15 18:24:58.179 luup_log:230: GCal3 V 1.2B:Next check will be in 5 sec on 2015-02-25 at 18:25:03 <0x2f0f5680>
06 02/25/15 18:25:03.101 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-25 at 18:24:58 now: 2015-02-25 at 18:25:03 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f0f5680>
06 02/25/15 18:25:03.179 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_nextCheck was: 2015-02-25 at 18:25:03 now: 2015-02-25 at 18:25:08 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f0f5680>
50 02/25/15 18:25:03.179 luup_log:230: GCal3 V 1.2B:Next check will be in 5 sec on 2015-02-25 at 18:25:08 <0x2f0f5680>
50 02/25/15 18:25:04.100 luup_log:204: GCal3 V 1.2B:Delay = delayedstart <0x2ecf5680>
50 02/25/15 18:25:04.101 luup_log:204: GCal3 V 1.2B:Checking semaphore <0x2ecf5680>
50 02/25/15 18:25:04.127 luup_log:204: GCal3 V 1.2B:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2ecf5680>
50 02/25/15 18:25:04.128 luup_log:204: GCal3 V 1.2B:Semaphore file returned 206 <0x2ecf5680>
50 02/25/15 18:25:04.152 luup_log:204: GCal3 V 1.2B:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2ecf5680>
50 02/25/15 18:25:04.153 luup_log:204: GCal3 V 1.2B:Device 206 blocked semaphore request from device 204 <0x2ecf5680>
06 02/25/15 18:25:04.153 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 <0x2ecf5680>
06 02/25/15 18:25:04.154 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 <0x2ecf5680>
02 02/25/15 18:25:04.258 ZW_Send_Data node 11 USING ROUTE 255.152.193.190 <0x2bcf5680>
06 02/25/15 18:25:08.101 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-25 at 18:25:03 now: 2015-02-25 at 18:25:08 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f0f5680>
06 02/25/15 18:25:08.178 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_nextCheck was: 2015-02-25 at 18:25:08 now: 2015-02-25 at 18:25:13 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 __LEAK__ this:20480 start:4034560 to 0x1b54000 <0x2f0f5680>
50 02/25/15 18:25:08.179 luup_log:230: GCal3 V 1.2B:Next check will be in 5 sec on 2015-02-25 at 18:25:13 <0x2f0f5680>
06 02/25/15 18:25:13.101 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-25 at 18:25:08 now: 2015-02-25 at 18:25:13 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f0f5680>
06 02/25/15 18:25:13.188 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_nextCheck was: 2015-02-25 at 18:25:13 now: 2015-02-25 at 18:25:18 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 __LEAK__ this:4096 start:4100096 to 0x1b64000 <0x2f0f5680>
50 02/25/15 18:25:13.189 luup_log:230: GCal3 V 1.2B:Next check will be in 5 sec on 2015-02-25 at 18:25:18 <0x2f0f5680>
50 02/25/15 18:25:14.101 luup_log:204: GCal3 V 1.2B:Delay = delayedstart __LEAK__ this:8192 start:4108288 to 0x1b66000 <0x2ecf5680>
50 02/25/15 18:25:14.101 luup_log:204: GCal3 V 1.2B:Checking semaphore <0x2ecf5680>
50 02/25/15 18:25:14.126 luup_log:204: GCal3 V 1.2B:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2ecf5680>
50 02/25/15 18:25:14.127 luup_log:204: GCal3 V 1.2B:Semaphore file returned 206 <0x2ecf5680>
50 02/25/15 18:25:14.151 luup_log:204: GCal3 V 1.2B:Command ls /etc/cmh-ludl/GCal3/GCal3.sem returned 0 <0x2ecf5680>
50 02/25/15 18:25:14.152 luup_log:204: GCal3 V 1.2B:Device 206 blocked semaphore request from device 204 <0x2ecf5680>
06 02/25/15 18:25:14.152 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 <0x2ecf5680>
06 02/25/15 18:25:14.153 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 <0x2ecf5680>
06 02/25/15 18:25:18.101 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_lastCheck was: 2015-02-25 at 18:25:13 now: 2015-02-25 at 18:25:18 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 <0x2f0f5680>
06 02/25/15 18:25:18.190 Device_Variable::m_szValue_set device: 230 service: urn:srs-com:serviceId:GCalIII variable: gc_nextCheck was: 2015-02-25 at 18:25:18 now: 2015-02-25 at 18:25:23 #hooks: 0 upnp: 0 v:(nil)/NONE duplicate:0 __LEAK__ this:28672 start:4136960 to 0x1b6d000 <0x2f0f5680>
50 02/25/15 18:25:18.191 luup_log:230: GCal3 V 1.2B:Next check will be in 5 sec on 2015-02-25 at 18:25:23 <0x2f0f5680>
« Last Edit: February 25, 2015, 01:20:42 pm by minimoibientot »

Offline minimoibientot

  • Sr. Newbie
  • *
  • Posts: 30
  • Karma: +0/-0
Re: GCAL3 - V 1.1 Released
« Reply #302 on: February 25, 2015, 01:19:08 pm »
Code: [Select]
os.execute( 'reboot' )
and returned in order

Offline Stuart

  • Moderator
  • Hero Member
  • *****
  • Posts: 728
  • Karma: +71/-2
Re: GCAL3 - V 1.1 Released
« Reply #303 on: February 25, 2015, 03:47:32 pm »
file installed
thank you

I watch the logs

Ok - I made a small change that will fix one part of the problem - a symptom.

What's happening is that sometimes the plugin is unable to get an access token from google and that was causing the plugin to crash some time later.  I've fixed that behavior.  If it fails to get a valid token it will retry after 60 seconds.

Maybe now we will get to the part of the code where it tells us why it was not getting an access token.

Try this update

EDIT: removed attachment
« Last Edit: February 25, 2015, 08:56:49 pm by Stuart »

Offline minimoibientot

  • Sr. Newbie
  • *
  • Posts: 30
  • Karma: +0/-0
Re: GCAL3 - V 1.1 Released
« Reply #304 on: February 25, 2015, 04:00:09 pm »
thank you for your speed

I just set up

Offline Stuart

  • Moderator
  • Hero Member
  • *****
  • Posts: 728
  • Karma: +71/-2
Re: GCAL3 - V 1.1 Released
« Reply #305 on: February 25, 2015, 08:56:08 pm »
thank you for your speed

I just set up

Added a front panel message if there is an error
« Last Edit: March 24, 2015, 04:50:13 pm by Stuart »

Offline minimoibientot

  • Sr. Newbie
  • *
  • Posts: 30
  • Karma: +0/-0
Re: GCAL3 - V 1.1 Released
« Reply #306 on: February 26, 2015, 12:15:06 pm »
file installed
 ;)

Offline Stuart

  • Moderator
  • Hero Member
  • *****
  • Posts: 728
  • Karma: +71/-2
V1.2 Beta with add event to Calendar
« Reply #307 on: March 05, 2015, 06:19:02 pm »
This release (V1.2B) rolls up some minor corrections and better handling of iCal date format.

The BIG news is that I've added the capability to create events in google calendar - it leverages the authentication already built into GCal3 - so there is no additional login / credential checking etc.

The attached 3 files (S_GCal3.xml, I_GCal3.xml and GCal3.lua) update V1.1 from the marketplace.  Several things to note:
(1) This only works when the plugin is associated with a google calendar NOT an iCalendar (i.e. do not use the iCal reference to a google calendar)
(2) You need to make sure that your calendar sharing is set so that service account can Make Changes to events

Here's an example of how to create an event - there are three mandatory inputs startDate, endDate and title - description is optional.  Be careful to preserve the JSON structure.  The example shows one event inside the  [] but the code will handle multiple events [{event1},{event2}, ....... ,{eventn}].
title and description can have the optional [start,end] offset and the {parameter} attributes that are recognised by GCal3.
startDate and endDate MUST be in the form yyyy-mm-ddThh:mm:ss for local time OR  yyyy-mm-ddThh:mm:ssZ for utc.  No other representations are allowed
The parameter passed into the  luup.call_action call must be an array of the form
ArrayName.CalendarEvent as 'CalendarEvent' is the name of the parameter that the plugin is expecting e.g.' Event.CalendarEvent' in the example below.

Please provide feedback !

Code: [Select]
-- Sample code for adding event
local GCAL_SID = "urn:srs-com:serviceId:GCalIII"
local GCAL_DEV = 3    -- The GCAL device number
local startDate = os.date("%Y-%m-%dT%H:%M:%S", os.time()+(1*3600)) -- plus one hour
local endDate = os.date("%Y-%m-%dT%H:%M:%S", os.time()+(1.5*3600)) -- plus 1.5 hour
local title = "TEST[-5,-5]"
local description = "MyDescription1{event parameter}"
local Event = {}

local event1 = '[{"eventName":"' ..
               title
               .. '","eventStart":"' ..
               startDate
               ..'","eventEnd":"' ..
               endDate
               .. '","eventDescription":"' ..
               description
               .. '"}]'

Event.CalendarEvent = event1

local resultcode,_,_,_ = luup.call_action(GCAL_SID, "AddEvent",Event, GCAL_DEV)
« Last Edit: March 24, 2015, 04:52:02 pm by Stuart »

Offline CudaNet

  • Beta Testers
  • Hero Member
  • *****
  • Posts: 1401
  • Karma: +42/-11
  • Chimichanga !
Re: GCAL3 - V 1.1 Released
« Reply #308 on: March 09, 2015, 06:18:02 pm »
Haven't had a chance to load this yet, too many projects on going at work. Will hopefully have some free time mid to end of week so I'll be able to provide input then. Quick question though, I see there are mandatory input fields, are there any optional ones (e.g. "Where") ?

openLuup, AltUI, Zway and HomeWave, enough said...

Offline Stuart

  • Moderator
  • Hero Member
  • *****
  • Posts: 728
  • Karma: +71/-2
Re: GCAL3 - V 1.1 Released
« Reply #309 on: March 09, 2015, 07:18:03 pm »
Haven't had a chance to load this yet, too many projects on going at work. Will hopefully have some free time mid to end of week so I'll be able to provide input then. Quick question though, I see there are mandatory input fields, are there any optional ones (e.g. "Where") ?

For now - I just just used the same fields that GCal3 knows about / uses / exports  -- start, end, title and (optionally) description.
Partly it was my thinking that the events added to the calendar might be future events that GCal would react to.
There is nothing to limit that -- so if other fields had appeal - then I could add them (assuming we did not get carried away :-))
I think keeping it in the context of home automation probably keeps the number of fields fairly small.

Offline CudaNet

  • Beta Testers
  • Hero Member
  • *****
  • Posts: 1401
  • Karma: +42/-11
  • Chimichanga !
Re: GCAL3 - V 1.1 Released
« Reply #310 on: March 10, 2015, 01:18:43 pm »
Sounds good Stuart, I have no doubt that the provisions you made will suffice (agree totally with what comes up goes down, nice an simple...). I just need to think about how I'm going to re-tool for upstream...

Haven't had a chance to load this yet, too many projects on going at work. Will hopefully have some free time mid to end of week so I'll be able to provide input then. Quick question though, I see there are mandatory input fields, are there any optional ones (e.g. "Where") ?

For now - I just just used the same fields that GCal3 knows about / uses / exports  -- start, end, title and (optionally) description.
Partly it was my thinking that the events added to the calendar might be future events that GCal would react to.
There is nothing to limit that -- so if other fields had appeal - then I could add them (assuming we did not get carried away :-))
I think keeping it in the context of home automation probably keeps the number of fields fairly small.
openLuup, AltUI, Zway and HomeWave, enough said...

Offline TwannieM

  • Hero Member
  • *****
  • Posts: 522
  • Karma: +3/-2
Re: GCAL3 - V 1.1 Released
« Reply #311 on: March 12, 2015, 03:39:27 am »
Good morning Steward

I noticed the pluging always gives me a Cridentials error after rebooting the luup.
Is there a way around this?

Offline Stuart

  • Moderator
  • Hero Member
  • *****
  • Posts: 728
  • Karma: +71/-2
Re: GCAL3 - V 1.1 Released
« Reply #312 on: March 12, 2015, 09:22:00 am »
Good morning Steward

I noticed the pluging always gives me a Cridentials error after rebooting the luup.
Is there a way around this?
It depend on what you mean by a 'credentials error'.  If you reboot luup then the plugin has no authentication token (I only keep it in memory) and so it must get a new token.
With gc_debug = 3.  The following log message is normal. Ignore the "GCal3 V_TEST"

"GCal3 V_TEST:Function: get_access_token"
"GCal3 V_TEST:Token Info request status: HTTP/1.1 400 Bad Request"
"GCal3 V_TEST:Getting a new token"
"GCal3 V_TEST:Got new token"

Also tokens expire after 1 hr - so the above log entry would also appear.

If you are experiencing something else - let me know with fuller details.
 


Offline becky

  • Jr. Member
  • **
  • Posts: 74
  • Karma: +3/-0
Re: GCAL3 - V 1.1 Released
« Reply #313 on: March 13, 2015, 02:17:14 pm »
I just have to tell you that as a mom that relies on her Google calendar a LOT, this is my absolute favorite plug-in. I'm really impressed with the thought that went into it.

Offline Stuart

  • Moderator
  • Hero Member
  • *****
  • Posts: 728
  • Karma: +71/-2
Re: GCAL3 - V 1.1 Released
« Reply #314 on: March 13, 2015, 02:38:33 pm »
I just have to tell you that as a mom that relies on her Google calendar a LOT, this is my absolute favorite plug-in. I'm really impressed with the thought that went into it.

Thank You !  You made my day !

It takes a village! -- I simply took the original work that others had started, updated it a bit and shamelessly added the ideas of many more.