Updating to use new WEC feed?

[garethhowell]

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?

[Marthyn]

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.

[garethhowell]

I only found out at Portimao. It seems to be using authenticated websocket calls. I developed a simple python app to read the timing feed and control a Hue bulb so it displayed the race_state (green, yellow etc). Silly I know but I could do it. I tried scraping the new site but no dice. From: Marthyn Olthof ***@***.***> Reply to: Marthyn/timing_lemons ***@***.***> Date: Friday, 18 June 2021 at 09:18 To: Marthyn/timing_lemons ***@***.***> Cc: Gareth Howell ***@***.***>, Author ***@***.***> Subject: Re: [Marthyn/timing_lemons] Updating to use new WEC feed? (#20) 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. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#20 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAEQKNTZZPUBCQLKYMNHOSLTTL6MBANCNFSM464LF2KQ>.

[Marthyn]

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.

[MarcusP-P]

@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.

[garethhowell]

Unfortunately, I put it to one side and never came back to it. The Prologue feed is redundant, I think they just forgot to take the site down. Now that you’ve nudged me, I’ll take a look today and see if I can crack the websockets interface. Unfortunately, I think it is authenticated, but I’ll take a look. Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: MarcusP-P ***@***.***> Sent: Saturday, August 14, 2021 3:29:18 AM To: Marthyn/timing_lemons ***@***.***> Cc: Gareth Howell ***@***.***>; Mention ***@***.***> Subject: Re: [Marthyn/timing_lemons] Updating to use new WEC feed? (#20) @garethhowell<https://github.com/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. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#20 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAEQKNQGP2AIBOK7PXXA6RLT4XIH5ANCNFSM464LF2KQ>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>.

[garethhowell]

@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.

[MarcusP-P]

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.

[garethhowell]

Thanks. I didn’t get around to looking on Sunday - I was too busy with other stuff. I’m not going to have a chance to dig into this before the weekend either, so it will have to be deferred for a while. Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: MarcusP-P ***@***.***> Sent: Sunday, August 15, 2021 7:32:40 PM To: Marthyn/timing_lemons ***@***.***> Cc: Gareth Howell ***@***.***>; Mention ***@***.***> Subject: Re: [Marthyn/timing_lemons] Updating to use new WEC feed? (#20) 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. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#20 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAEQKNT6LE4T4JEXRHRTFM3T5AB4RANCNFSM464LF2KQ>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>.