To @M1dn8 @gekberlin:
As @derhuerst mentions, this feature can be implemented, but it is a bit of work… We can try this. If you have any programming skills, your contribution is more than welcome :)

To @derhuerst:
Do you think, that some other possible future services that use your API will likely use this feature? If so, I think it should be done in the API. If not, I can just throw away the entries that are not used. But as you said, determining the direction could be a bit tricky. So one would need to know the next station on the line, huh?

Hey @Tekki
Unfortunately, I’m not really familiar with the changes, that @olexs made in his MMM-PublicTransportDB module, so I don’t really know, if your config is correct. You could open an issue on his GitHub repository with the same question again. Here it is:
https://github.com/olexs/MMM-PublicTransportDB

Hey, @pauabaer
I implemented your feature request ;)
you can now exclude lines via the ignoredStations option in your config.

To all users of this module:

The transportation data in the background changed and I added support for this in the module. You should update the module asap.

You can update it with these commands in the MMM-PublicTransportBerlin-folder:

git pull
npm install

The npm install-command is very important, since the vbb-client module needs to be updated to use the new transport API.

Greetings!

As @strawberry-3-141 mentioned, the sendSocketNotification() function is called, before the callback function of your request is execuded and the content of data is created.

You could either call the sendSocketNotification() function inside the callback function of the request or put the data variable into a promise (which is a much more elegant approach and produces good-readable asynchronous code).

There are good explanations for promises, just google “promises simple explanation” (or similar).
I can recommend this one: https://coligo.io/javascript-promises-plain-simple/

Edit:
Oh, and I would recommend the Bluebird.js library for promises. http://bluebirdjs.com/

I’d really like to see some kind of ‘package manager’ for all the mirror modules. A more or less centralized solution for this would be great.

But I agree with @MichMich that npm is not really the solution for that.

I hope it’s not too late. I confirm my orders here. Mail is also already sent. @Goldjunge_Chriz

Hey, @strawberry-3-141, thanks for supporting!

@pauabaer:
currently there is no such function to filter out lines directly. Only to filter for stations, as @strawberry-3-141 mentioned. But I can implement that function if you want to have it. It’s not soo much effort I think… I can’t promise to do this fast, but I would try to find time for it ASAP.

If you want that feature, please open an issue for that on github, so I won’t forget it ^^’

@olexs
You’re very welcome :smile:
I’m happy that someone had use for it, so the code is not useless :) I already noticed the attribution in the readme and appreciated it ;) Thanks a lot

@Goldjunge_Chriz
Alright. Thats fine for me. Could you please add both mirrors to the list?

Hey, @Goldjunge_Chriz
I need two glasses, but they are each much smaller than 0.4 sqm.
Do I need to pay the price for 0.4 each or will both parts be totalized to one price?

This is what I need:

0.545x0.32 // 0.174 // Treuenbrietzen, Brandenburg // polished edges // delivery
0.63x0.365 // 0.23 // Treuenbrietzen, Brandenburg // polished edges // delivery

Both glasses together totalize to 0.404 sqm, so could it maybe totalized to one price?

If it’s possible you can put both glasses into one delivery package.

Thanks in advace!
Greetings!

P.S.: Thanks by the way, for this awesome possibility provided by you! I really appreciate that!

Okay, I think there’s a misunderstanding here.

To make things clear for the future:
The Module from @olexs MMM-PublicTransportDB is not really the same as my MMM-PublicTransportBerlin. Olexs made some changes on the original module to use the data from DB (Deutsche Bahn) while my module is just using the data from VBB (Verkehrsverbund Berlin-Brandenburg).

I think this could be the reason why the stationIds you used did not work @Jay. Since you used a stationId from VBB for DB data. I didn’t test this but maybe @olexs can make a statement to this?

Hey @Jay,
what did you have to change for the module name in the config?! o_O
I didn’t make any changes according this…

You can get valid station IDs via an easy cURL command as mentioned in the readme like this (you can do it from the mirror’s command line):

curl 'https://transport.rest/stations?query=alexanderplatz'

You just have to switch ‘alexanderplatz’ with your nearest station. This command will return all station fitting the search term.

@Advokaten
The data will be transferred, since vdirsyncer synchronizes the whole calendar data (including description, location, time, title,…). So all the calendar data you enter in your iCloud account will be synchronized to your mirror.

What you are asking depends heavily on the calendar module you are using on your mirror. I don’t think, that the default module supports this. So I think one needs to change stuff in the calendar module for this to work.

So I think what you’re asking is not really related to the syncing itself. If you’re already using the default calendar module, you already know how it looks. I didn’t change a single thing on that regarding optics. So the look is 100% similar to the default calendar module.

@Photon2000 Yeah, the problem is, that midori doesn’t support ECMAScript 6 (ES6) features. But the module is using some of them.

Unfortunately I don’t have much time in the near future to convert the module to vanilla JavaScript in ES5 for you. You could try to convert the code with a compiler like Babel. Then it should work with midori.

Hey, @poekel

after some trying on my Baikal server, I found out, that just the use of the start parameter alone is not working indeed.

However, I was able to get a request, if you add the componentType option to the request URL. You have to filter the type to VEVENT. But thats no problem, because the documentation says, that this is the only working type for export anyway.

So I got valid answers with the following URL scheme (including recognized timestamp):

https://dav.example.com/dav.php/calendars/USERNAME/calendarname?export&start=1490745600&componentType=VEVENT

@TobiasAlw Ahh, I see. Yeah, this should work. Just add all the transportation types you don’t want to see to the excludedTransportationTypes string in your configuration.

All transportation types are listed here under “other parameters”.

@TobiasAlw could you please provide a link for me? Where can I find this feature in the vbb-rest documentation?

@poekel

I will try a request with a start parameter when I’m home and test if it works with my Baikal server.

For user credentials:

Just add user and pass to your calendar config like this:

config: {
    calendars: [
        {
		url: 'http://192.168.1.xx/baikal/html/dav.php/calendars/xxxx/calendar-name?export&start=1488672000',
		symbol: 'calendar',
		user: 'USERNAME',
		pass: 'PASSWORD'
        },
    ],
}

Additionally, Baikal uses Digest authentication. To use this, you have to change the sendImmediately option in the calendarfetcher.js to false. (As I already described above)

The option is located here. The file is located in MagicMirror/modules/default/calendar/calendarfetcher.js

In a future version of MM2, there will be an option for this directly in the config file so you don’t have to change this in calendarfetcher.js. I already submitted a pull request for that.

Hey @poekel
you have to use the keyword start instead of startdate.
It’s described in the sabre/dav documentation here: http://sabre.io/dav/ics-export-plugin/

So your request should look like this:
http://192.168.1.xx/baikal/html/dav.php/calendars/xxxx/calendar-name?export&start=1488672000

You can use this URL in your MM2 config file. It returns a valid .ics file. I’m using this on my mirror too.

And please note, that your calendar-name must be the internal name in Baikal (you can look this name up in the admin settings when you edit a calendar)