(01-09-2025, 01:24 PM)GeeM Wrote: "coming soon" about 6 months ago, then full silence from the admins/devs/team is surely not a good sign
It looks like we have to look for other solutions for 2025 models...
It's fair point, I created the expectation by saying "soon" ;-). The trouble is, from the outside, you have no idea of the task and effort to solve the problem. For the 2025 SPA models, the issue is not a big one. It could seem like it's a simple task to update OrBit, that it must not be a priority.
That's not the case. What has happened, is Volvo has introduced an entirely new security access mechanism, after 27 years of the old one! It's a huge change. And a big task to get over. The effect on the 2025 SPA models support is small, but the solution is also key to any possible support of the new SEA and SPA2 models.
It's not on the "downhill" part yet, reverse engineering new bits can be a task of unknown time an effort to solve, which is why "soon" is probably the wrong term. It was a bigger challenge than even I had thought. Once the engineering part is done, then implementation will be something more manageable and to have a timeline... i.e. on to the coding, testing, release etc.
If someone else solves it sooner, fair play to them...if that someone is reading this drop me a line support-at-<spaycetech-dot-com>!