Marthyn/timing_lemons

Updating to use new WEC feed?

Opened this issue · 8 comments

Thanks for creating this app, @Marthyn , I used it a lot last year.
Now that WEC have moved to a new timing site that seems to use websockets to retrieve the timing data, are there any plans to update this app?

Hi Gareth!

I haven't looked at this in a few months, I usually only take a look around Le Mans. So by then I will definitely have a look. Perhaps if I have time during the Monza event I can take a look already, had no idea they changed their architecture. Thanks for letting me know.

That's actually a fantastic idea! I also got HUE lights, would be awesome to have that indication. If the whole timing source is behind an authenticated source it might be difficult or even impossible to keep this project working. It was based on the premise that the feed was a public JSON file.

@garethhowell, is there any chance that you managed to grab any details of the endpoints? I want to get a head start on an app to access it, so I don't need to do as much coding while the sessions are on. I think the JSON is stuck on the prologue.

@MarcusP-P No way of accessing the feed at the moment. Hopefully, it will be live tomorrow during the test session. I'll look then.

It looks like they use socket.io to communicate. the protocol is described at: https://github.com/socketio/engine.io-protocol/tree/v3

It starts of with a https connection, and the server will send you an sid. You can then upgrade it to websockets using the sid. There is no auth. Alternatively, you can use https with the sid, and get the data too.

Unfortunately, the sid expires after about 25 seconds, so you'd then need to get a new one.