@htilburgs This is exactly what I‘m trying to prevent/workaround with this tutorial.
Using a public calendar URL allows anyone to see your calendars without any authentication at all. This way your calendars are open and accessible by anyone who knows the URL. (URLs can be crawled by machines ;))
This here is just a secure method to sync your calendars.
If you don‘t care about having your personal life available to anyone or anything, it‘s your business.
@Sammie1232 Seems like the folder and/or the file do not exist. Please create them if they are not there.
The folder needs to be owned by the current user. On a Raspi, this command would look like this: chown -R pi:pi /home/pi/.vdirsyncer
@yk Dis you activate the systemd unit for the timer? You can enable it with sudo systemctl enable vdirsyncer.timer you can also check via sudo systemctl status vdirsyncer.timer, is it’s enabled already. If so, it should work…
@showbizkid Did you create the .vdirsyncer folder first? Sounds like it is not present…
@nem1 Try to make the git pull and npm install without sudo.
You can also try to completely remove the module folder and clone it again. Sometimes this solves such problems.
I changed the module to use vbb-hafas directly instead of using the unavailabe endpoint 2.vbb.transport.rest. If you update your module, you should be able to see departures again (let’s see how long this will work…).
@AgP42: Note, that MMM-PublictransportBerlin parses VBB/Berlin-specific changes in the HAFAS-API, as @derhuerst described them here: https://github.com/public-transport/hafas-client/blob/master/p/vbb/readme.md.
If they don’t matter to you, you can leave it as it is and continue using MMM-PublicTransportHafas :)
The API is live again. Let’s see how long the new method is working… I have antoher solution on my roadmap to make this more reliable (hopefully :D)
@AgP42 The Problem was not your configuration, but the data source the module is getting it’s data from. When you get the shown error, the module was configured right.
You can find them here: https://github.com/deg0nz/MMM-PublicTransportBerlin/issues/
Additionally, you can check the avialability of the data source here: https://status.transport.rest
@nem1
This actually means what it says. VBB Data is currently not available. The API is down for some days now… The error has been reported.
You can check the status at https://status.transport.rest
Attention:
Due to changes in the API, the stationId must be a string now. If you experience errors, please check the updated readme and change your configuration to use a string for the ID.
This is also true for the directionStationId is you use this feature.
@OsCourt I think you need to use dav.php instead of cal.php on newer baikal versions. Also you need to use digest authentication with the calendar module of the mirror. It’s described in the readme of the module.