Power comparison with Vector 3 Pedals

I have similar results on my power2max and 2t. About 5% off , whole range.

Yep, same here - Neo 2T vs Assioma Favero Duo... 4-5% off (Favero reads higher). I thought it was related to the fact that Favero (just like Vector) measures at the pedal and there is no efficiency loss through the drive train, where Neo 2T measures.

I have readed older neo models reviews and they are much closer against pedal based and spider based powermeters.

Maybe it is just a matter of new firmware? The current one is already quite "old" in comparison of other releases for their other products.

This is a known issue and covered by GPLama on youtube. All we can hope for is a new firmware to fix the problems or at least get 2T in line with the original Neo which is way more accurate.

Same here, Neo 2T vs SRAM Red Quarq. About 2% to 5% off.

www.zwiftpower.com/analysis.php?set_id=9791

Oh yeah? What known issue? What is your source for this information?

Neo 2T is very comparable to the original Neo. I'm not sure what you're on about, but I think you are mistaken.

I'm sure you're familiar with Shane Miller (aka GPllama)
He's had his Neo for years and finds it to be an extremely accurate unit. He has tested a Neo 2 (also accurate) and a 2T (reading much lower and inconsistent at different flywheel speeds) as well. He also tested the Neo Bike and found it to be as accurate as the original Neo. 2T was the only issue.
He has a very repeatable test procedure that he applies to all power meters and trainers. His findings reflect what you'll find a lot of users also report on several riding forums. Also lines up with my experience as well.
He's also been to Tacx headquarters and discussed his findings with the team.

Unless there's a few dozen people with the issue and it's not such a wide range of units, it's a firmware issue that is in progress to be fixed.

I think you are 100% incorrect about Shane Miller's reporting. If you're talking about issues with 2T before it was even released, those issues were resolved with firmware version .31

Update your references. You don't know what you're talking about.