Oops sorry @KolfMAKER I didn’t get the ‘light pipe’ thing. I do now (hopefully) 
Regarding Testing of PV1 with @mclarkdev Latest Software, absolutely no bugs to report right now :). However I have been using it sporadically which is actually a good test for such a device. Just Wakes Up and does the job asked 
Just one note I have in mind that if the Production Device is with configurable buttons (=HTTPAPI commands) then it needs to be accompanied with good and clear advice about which HTTPAPI commands are suitable for the device. For example a list of recommended tested and validated commands. Accompanied with a disclaimer for the rest; someone will always find an obscure command that doesn’t really work. This could then become an “apparent” bug in the NVS unit but in reality it is a limitation or oversight on the HTTPAPI side.
I am happy to prepare the list and test with multiple sources e.g. NAS, USB, Spotify, Tidal, Deezer etc.etc. This is really just testing the “httpapi” instructions but the Clients/Purchasers will probably only see this side and won’t even know what an “httpapi” is !!
This is the sort of scenario I envisage
Anyway I will carry out the the tests and report back. It is certainly not a bad test for the Unit & Software as a button pressed is a test in itself. And the more buttons pressed means tested more and more.
I am thinking it is really nice to make a super flexible unit for the educated but however keep it simple for most folk. Maybe we could even have a command filter @mclarkdev that only allows tested and validated httpapi commands.
Anyway just thoughts for now. The proof is in the testing
So finally Questions about Testing Table (exclude Configuration & Multiroom for now):
Q Any other sources / inputs / services to include ?
Q. Any other httpapi commands of interest for this device ?
Many Thanks in advance, Kevin