Authorize.js just hangs

[pierreode]

Following the guide for installation, I get the credentials.json file and have it in the correct directory. This is confirmed by removing it and receiving and issue when I run node authorize.json and getting an error.

My issue is that when I have my Desktop app credentials file in the correct location, and the Calendar api enabled on my account, when I run node authorize.json via my terminal, nothing happens. It just sits there for hours. I don't get any sort of feedback.

I have installed the latest version of MM and the module. And sort of direction would be great to troubleshoot where I might be going wrong.

[randomBrainstormer]

Hi @pierreode, the module now should open a browser directly in the raspberry pi, maybe you are connecting through SSH hence can't see the browser opening. Try using VNC or connecting the keyboard directly to the PI, and let me know if that's the case, I do think the documentation needs a bit update to clear this part!

[pierreode]

Ah!! Yea I am connecting via SSH, that will be the issue. Using a pi I already have setup in another part of the house! I will look into the VNC route!

I will make a new comment once I get it sorted

[randomBrainstormer]

Thanks! In the meantime I'll add this bit to the documentation

[pierreode]

Install VNC on Rapberry Pi via SSH was a great help. Thanks @randomBrainstormer for the guidance!

[jkaberg]

EDIT: Noticed the comment in README, sorry :-) However still an issue, AFAIK in current state you're only able to use this module if MM is running in an desktop environment.

@randomBrainstormer I do think this should be more clear (browser part), running MM in an docker container (serveronly mode) this is obviously not trivial nor self explanatory. Looking into this right now, but I do think changes should be made to accommodate this approach

[randomBrainstormer]

@jkaberg We used to have command line based authentication which was ideal for server-only setups, however, it continously gave us authentication issues and required a lot of "delete token, sign in again" hence we changed to the current approach which was more stable. I think we could eventually support both ways (command line auth and browser auth) but would require some work.

For now try using the VNC option. If there aren't any big support request I could try to include this in the future, Pull Requests are also welcome :D

[jkaberg]

@randomBrainstormer very understandable. My usecase involves using server-only (in an docker) to host MM on my NUC. In turn I (chrome)cast MM to an screen.

This might very well be the "unconventional" way, and for now I found a way around it 😄 (I now use the normal calendar module)