Differences

This shows you the differences between two versions of the page.

--- livebox:google_calendar [2011/12/17 19:26] – brett
+++ livebox:google_calendar [2013/12/27 21:41] (current) – minerva9
@@ Line 2: / Line 2: @@
 {{ :livebox:google-calendar-logo-150x139.png}} Google Calendar xAP daemon.
+<note warning>Around mid Dec 2013, something changed in Google space which stopped this HAH component from finding any events. This might be due to Google moving from V2 of their Calendar API to V3. Until such time as rework can be done, please consider using cron instead.
+</note>
 This program will monitor a calendar and produce an xAP payload every minute for as long as the activity is running.  The password, once entered, will never be again displayed on the web GUI, this is for security reasons.  However, it can be reset by simply entering another.
@@ Line 22: / Line 26: @@
 {{:livebox:googlecal.jpg|}}
+===== Scheduling events =====
-}===== Scheduling events =====
 An entry is setup in the calendar using the following fields.  This example will send the text //"Hello World"// to the LCD.
@@ Line 99: / Line 95: @@
 </code>
-It is up to the alias scripts running with [[hah_plugboard#alias_interpreter|xap-plugboard]] to determine what action to take.
+It is up to the alias scripts running with [[hah_plugboard_v2]] to determine what action to take.  See twitter for an example of an [[twitter#alias_interpreter]] that can be used by google calendar too.
 ===== Recording events =====
-The Google calender daemon can also act as a service.  This mean it will accept an xAP payload and create a calendar event.
+The Google calender daemon can also act as a service.  This means it will accept an xAP payload and create a calendar event.
 Header information
@@ Line 154: / Line 150: @@
 ===== Troubleshooting =====
-I start up google calendar in debug mode and it won't connect !
+I start up Google Calendar in debug mode and it won't connect!
 <code>
 # xap-googlecal -i br0 -d 7
@@ Line 178: / Line 174: @@
 </code>
-Make sure your CLOCK on your livebox has correctly been set by NTP.
+Make sure the CLOCK on your Livebox has correctly been set by NTP.