So I just spent the last 20 minutes RTFM'ing, and this really needs a QuickStart guide.  I have been attempting to connect to it via my phone, and I'm blocked by a wifi password.  Bluetooth is not showing anything at all, so no dice there either.  Cannot find how to use this standalone (not setting up with HA) anywhere in your documentation.  I know this is probably basic stuff, but we need to know the basic stuff somehow.  

Hey, @RocketGuy please have a look at GitHub here https://github.com/sonocotta/esp32-audio-dock?tab=readme-ov-file#squeezelite-esp32 , it has few instructions, including the default password which is squeezelite. Hope that helps

Thanks!

Thanks for the password, I was looking at the GitHub and it's way, way too much detail with not enough formatting and information prioritization.  I could not find the password anywhere on that page even after looking again.  So yeah, need a QuickStart document with just the salient details for getting up and running for most use cases, as that is definitely in TL;DR territory.  

I totally get RTFM, and I'm generally down for that, but this needs more structure as it's currently a wade fest.  This happens a lot with engineering projects, it's really difficult to maintain perspective because you're so close to it and have a ton of knowledge.  So it's advisable to get someone else as an outside pair of eyes/editor to help with formatting and organizing the documentation.  

It's clear that you've put a ton of work into this, I don't want to see it fall by the wayside just because it's inaccessible to a lot of users who aren't programmers.  

Thanks again for responding.  

You're totally right, been there. It is just hard to have the right perspective when you work this close for a long time. I appreciate any contributions here, if you can lay out at least a plan of what you'd find most useful for the TLDR doc, I promise to fill it up with the necessary details. 

Okay, so the first principle in good UX design (distinct from UI) is designing it from the user use case, not from the system capabilities or features.  So it's best to think of it as a totally separate job.  

In short, what is the user probably gonna do with this?  What do they need to do that?  And then exclude everything else.  Dave Grohl once said "think bumpersticker, not poetry" when writing a hit song, and that applies here.  Format example at bottom.  

If there are multiple use cases, fine, but clearly segregate them under their own headers so they are easy to find and use, we're spoon feeding here.  

So Quickstart: What is needed to make this work for the primary expected default purpose?  (in my case, I'd go with use my phone or computer to push music through this to a device that emits sound, or for the other models, speakers).  

1) The stuff that is really too stupid for an engineer to even think about.   Just short of how to open a bag stupid.  

-The USB-C power spec needed for the power supply, and note that its usb-c connector on the cable.  What is the power requirement?  (Link to the serial option, don't go into it here).  
-Then the audio out options in brief, mostly will this blow up a line input or not?   What is the connector spec for the audio out jack? (suggested connector type or cable is probably a good idea, not everybody is familiar with 1/8" anymore) 
-A picture of these plugged in, because it just makes everything easier and sometimes a stressed out end user suddenly loses literacy.  

2) Configuration steps to get it working for the default case:

-Again the dumb stuff, power it on first, then open phone to wifi settings.  (Some people need to know what state is safe to power up in due to magic smoke release trauma of the past.)  What cables should be plugged in first is good, if applicable.  

-Wifi Default SSID to expect, screen shot of finding it in wifi settings

-Default password, both the SSID and PASSWORD should be in a different color or otherwise emphasized to make them easy to see and clearly labeled probably on their own lines e.g.:

SSID:  [DEFAULTSSID]
PASSWORD: [DEFAULTPASSWORD]

-How to configure the device onto the user's home wifi network (I'm assuming this is a thing, I can't remember now if it's an actual feature or not).  

-Similar steps for Bluetooth setup, screenshots for iOS and Android would be good.  

And this all needs proper white space use formatting so that it's easily scanned by somebody who is just trying to get going.  Bullet point lists and one line answers basically.  Here is a simplified format example:

QUICK START GUIDE 

Use Case Section header
     -First step
     -Second step
          Important Information on its own line, e.g. ssid/password etc.
     -Third step




HTH

Thanks, really appreciate the writeup. I'll try to compile a guide after holidays when my head will be clear again.

This streamer looks really promising. I am looking forward to buy it as soon as you add the transparent panel for the display as stated above. Maybe it even has room for a SH1122 display?

Did you also think about adding an IR receiver and/or a rotary encoder to the front or do you prefer not to offer local control options?

Regards

Hey @martymcbro I know it's been a while, but the transparent panel and OLED screen are both available right now. I was thinking about rotary as well, and planning to add it at least as a header for DIY assembly in the future.

Thank you for the update. I'm still interested in a transparent panel. I've already bought a HiFi Media Link some time ago. Where can I get the panel? I didn't find it on Tindie.

https://www.tindie.com/products/sonocotta/louder-esparagus-media-center/ here it is. join the Discord to see a few more photos https://discord.gg/PtnaAaQMpS

I can't wait for you to have this readily available. I've done a deep dive on LMS and the assorted squeeze platers lately and having an "off the shelf" solution to recommend to friends is amazing. It's so hard to ask them to buy a development board without a case or any finishing. I would love a similar product with the Louder ESP32 Components as well as a line/headphone out. that would honestly make the best and coolest little desktop streamer box.