Google Calendar has stopped working.
Hi my google calendar has stopped working; it had been running my central heating for the last 2 weeks with no problems. Luckily I have left all the old CH controls in place.
I do not see the aliasmsg arrive at the HAH. All other functions are fine (Twitter Cron etc etc). I can send a requirement to google cal and it is registered in the calendar. Heartbeat is seen.
I normally send a “relay 2 on” Alias msg for 3 minutes to ensure operation.
I know I could use cron, but the GoogleCal GUI, using different colours makes it easy for the other half to see what is going on.
I have probably fiddled with something, but for the life of me cannot see what. I have now exhausted my limited knowledge on how to move on and resolve the problem.
What I have done is
Reloaded known working backups.
Performed a Clean build
Started from a virgin ini and rebuilt my configuration.
Created new GoogleCal account
Tried setting the calendar event aliasmsg time 1 hour before and 1 hour after real time just in case there is a problem with time zones.
Below is a log/debug file hopefully someone will be able to tell me if they can see any problems.
# xap-googlecal -d 6 -i br0
Google Calendar Connector for xAP v12
Copyright (C) DBzoo 2009-2010
[inf][init.c:118:discoverBroadcastNetwork] br0: address 192.168.1.87
[inf][init.c:130:discoverBroadcastNetwork] br0: netmask 255.255.255.0
[inf][init.c:137:discoverBroadcastNetwork] Autoconfig: xAP broadcasts on 192.168.1.255:3639
[ntc][init.c:54:discoverHub] Broadcast socket port 3639 in use
[inf][init.c:55:discoverHub] Assuming a hub is active
[ntc][init.c:64:discoverHub] Socket port 3640 in use
[ntc][init.c:64:discoverHub] Socket port 3641 in use
[ntc][init.c:64:discoverHub] Socket port 3642 in use
[ntc][init.c:64:discoverHub] Socket port 3643 in use
[ntc][init.c:64:discoverHub] Socket port 3644 in use
[ntc][init.c:64:discoverHub] Socket port 3645 in use
[ntc][init.c:64:discoverHub] Socket port 3646 in use
[inf][init.c:66:discoverHub] Discovered port 3647
[inf][googlecal.c:461:main] Connecting to google
[inf][filter.c:34:xapAddFilter] section=xap-header key=target value=dbzoo.livebox.GoogleCal
[inf][filter.c:34:xapAddFilter] section=xap-header key=class value=google.calendar
[inf][filter.c:34:xapAddFilter] section=event key=title value=XAP_FILTER_ANY
[inf][filter.c:34:xapAddFilter] section=event key=start value=XAP_FILTER_ANY
[inf][filter.c:195:xapAddFilterAction] section=event key=start value=XAP_FILTER_ANY data=0
[inf][tx.c:19:xapSend] send
xap-hbeat
{
v=12
hop=1
uid=FF00DA00
class=xap-hbeat.alive
source=dbzoo.livebox.GoogleCal
interval=60
port=3647
pid=192.168.1.87:337
}
[inf][tx.c:19:xapSend] send
xap-hbeat
{
v=12
hop=1
uid=FF00DA00
class=xap-hbeat.alive
source=dbzoo.livebox.GoogleCal
interval=60
port=3647
pid=192.168.1.87:337
}
Many thanks in advance.
Google have recently been testing out a new version (v3) of their calendar API. Their testing has broken the v2 API on previous occasions and there is one report of a similar issue today.
Since nothing else has changed, I'm guessing that the problem might well be at their end.
Brett can possibly look under the bonnet to check the actual response stream from Google.
Always good to have a workaround/alternative comms channel. You can ask Google Calendar to send an SMS message at the start of an event. If you have SMS feeding into your HAH, that might be a decent fallback.
Cheers,
Derek.
Must admit I never got this to work reliably.
debug used to say no events when I knew there were some. I had to set 10-15 min long events to ensure at least one got through.
So it worked sometimes but mostly not, I moved to cron and find this very stable. You can still setup endpoints for heating on/off times and have a script update the cron file for you. This allows the other half to see what's happening via a gui displaying the endpoints.
would be good to understand the googlecal issue but it was wasting too much of my time messing with it, I gave up.
Garry
I'm with Garry on this one. I never really got google calendar to work effectively. I gave up on it more than 2 years ago and have use cron ever since. That said, obvously my experience is way out of date, but I've never really felt the need to try it again.
I use googlecal for nightlight scheduling. It's been fine for around a year.
Was away from home in the week so don't know exactly when it stopped working, but it didn't work last night.
Had a chat with Brett this morning (well, evening for him), he will have a look & see what is going on. I do like the nice UI on Google Calendar & also the ease of use on mobile devices.
Really should script up something to catch the falling/rising light level from a roomNode and do control that way. This would save playing with the calendar events as the seasons change.
I can confirm it is no longer working.
Hi
I'm not great on the old linux stuff and forget vi commands each time I return, consequently I put together a little vb app. I have added Cron to it.
I can email it if anyone is interested.
Really should script up something to catch the falling/rising light level from a roomNode and do control that way. This would save playing with the calendar events as the seasons change.
@Derek: there is a sample called: automaticLightsApplet.lua combined with sunForecastApplet.lua whcih does something close its driven from the actual sun up/down times for your long/lat.
Brett
Or IFTTT will post a tweet at sr/ss
Hi Magill, as a fellow VB coder i would love to give your app a go
cheers - Andrew
How busy is this forum this weekend!? Any correlation to the fact it's Xfactor final weekend :)
Glad to see people getting back into all things HaaH, interesting to see what others are up to!
Garry
Garry could be.....
either that or its dark and cold out and its the time of year to catch up on these neat little projects :)
Andrew
Kema,
Increase to debug level 7 (max) you might get more useful information back.
Brett