I have installed the Google Calendar Scheduler and Google Calendar Presence Simulator through PaperUI. The former was either installed a week or so ago, or was installed by default, I don’t remember. The latter was installed recently.
I tried setting everything up according to the Wiki instructions, but it will not work.
I obtained the credentials successfully, made a new calendar called openhab, and put all the credentials and information in gcal.cfg (leaving filter and refresh commented out). I expected the log output with instructions and code, but have grepped and found nothing. So continuing, hoping it would appear after a while, I put the calendar name in gcal-persistence.cfg. I created a gcal.persist file in persistence/ with the following content:
I added an item in an item file: Switch PresenceSimulation "Simulate presence" <man_3>
I created the group gPresenceSimulation and added an item to that group.
The expected message in the log still has not appeared, and nothing is being logged to my calendar.
I tried uninstalling Google Calendar Scheduler with PaperUI, hoping that I could install again and everything would work, but when I try to uninstall it, the spinning icon never stops spinning. The log outputs nothing, and if I refresh the UI, it’s still installed.
Right now I’m out of ideas. Does anyone have any suggestions on how to proceed?
This is probably because of the dependency gcal persistence has on gcal. I suspect that as long as gcal persistence is installed, you won’t be able to uninstall gcal. I’d suggest you uninstall gcal persistence until you get gcal working. The fewer moving parts, the better.
As for gcal, I would suggest you try stopping/starting gcal while tailing the openhab.log file. That way you’ll be able to see what gcal logs at startup. You also could try putting gcal into debug mode to see if it provides any clues.
I see nothing, so it’s not installed. Strange that PaperUI claims that it is installed. How do I resolve this strangeness? Perhaps it’s as easy as installing it through the console? I’ll see if I can figure out how to do that.
Ok, I tried to install with the console, and got an error message. But then PaperUI started showing it as not installed. I installed it with PaperUI, and got no log output. I tried stopping and starting and changing logging in console, as shown above, but log still shows nothing.
But now, at least the console says it’s installed too:
openhab> list -s | grep gcal
229 │ Active │ 80 │ 1.11.0 │ org.openhab.io.gcal
This is a bit confusing. I would expect it to output the instructions and code in the log now. The cfg files are still there, unchanged, with all the information.
But when I display the whole log i find plenty of gcal related loggings, but not the instructions.
I think this is because openhab restarted teh bundles after isntalling and so the logg was lost
Trying grep again after a while shows a little more.
I don’t. No errors after I removed and reinstalled. Your error is likely because you don’t have it installed (before installing it after you got that message). And then there’s this:
openhab> feature:list | grep gcal
openhab-persistence-gcal │ 1.11.0 │ │ Uninstalled │ openhab-addons-2.2.0 │ Google Calendar Presence Simulator
openhab-misc-gcal1 │ 1.11.0 │ x │ Started │ openhab-addons-2.2.0 │ Google Calendar Scheduler
So gcal is clearly installed. But it behaves weird. No log output when stopping and starting, and not the expected log output with the code as described in the Wiki.
persistence-gcal depends on gcal. But gcal alone should produce a log message with instructions and a code to use to grant openhab permissions to read and write my calendar. But it doesn’t.
At a minimum, you should be seeing this when you tail -f /opt/openhab2/userdata/logs/openhab.log (or wherever your openhab.log file is in your installation).
I understand. But it’s not happening… I get no error messages in the console, but there are no new entries produced in the log either. It’s like the binding is completely dead. I used the openhabianpi image, so I can’t really imagine having done something terribly wrong during installation.