updated the dvb.monitor() functionality to use webapi.vvo-online.de #30
Conversation
…nstead and thus provide more information like realtime/scheduledtime, state and delaytime as well as information on the departure platform.
|
Is there a reason why you are working on the master and not on the develop branch? |
|
Well, because I am used to it and for minor changes I refrain from using a branch. |
|
Just to let you guys know how these changes can result in some more detailed graphical view on my home automation screen, see here:
Looking forward to seeing my changes integrated :) |
|
Seems like this broke the tests, otherwise looks ok to me. @ronhippler There's still a few changes waiting in #23, including current activity. Got any ideas how to bring all of this together in a sane way? You probably have much better insight into this library than me at this point 😄 |
|
@kiliankoe Yes, the tests need to be adapted to my new changes. However, I don't have the time yet to adapt the tests. Perhaps you guys can adapt them accordingly. |
|
Maybe i replace all EFA requests with the dvb.webapi, so all requests could be used with eduroam. |
|
I can of course helo with that if youbare interested. But please first merge this PR |
|
FYI i merged the changes and published it to npm |
updated the dvb.monitor() functionality to use webapi.vvo-online.de instead and thus provide more information like realtime/scheduledtime, state and delaytime as well as information on the departure platform.
This refs kiliankoe/vvo#2