Closed jochen-rath closed 6 months ago
Hey folks, I'm working on the S3 version of the Louder ESP board, and very much look forward to having squeezelite-esp32 support for it. I tried to do the same as @jochen-rath and apart from the absence of Bluetooth found a few more issues. Long story short, it doesn't work currently.
S3 has a more usable PSRAM, that supports a faster interface. It has a built-in debugger right via the USB port, which is a fantastic option for developers.
I'm willing to send a few board samples to the developers who are ready to look into the S3-related issues and perhaps add official support. The board itself uses a TAS5805M DAC that is already supported and works off USB (with a 5W output power limit) or an external power source (driving 2 channels 20W each)
The missing autoexec key is fine. It's just standard behavior where during boot, the system checks for autoexec=1 to see if it should execute the start sequence. Then from there it will execute in sequence autoexec1, autoexec2, etc. The warning here is merely an indication that there is only a single autoexec to run (squeezelite).
As for not connecting to the media server, your logs seem to be showing that an attempt is made
[00:04:24.067] notify:228 notified server 192.168.0.140 hport 9000 cport 9090
I (29968) network_status: LMS IP: 192.168.0.140, hport: 9000, cport: 9090
[00:04:24.187] notify:228 notified server 192.168.0.140 hport 9000 cport 9090
I (30088) network_status: LMS IP: 192.168.0.140, hport: 9000, cport: 9090
Can you confirm that the issue isn't on the server side? for example a firewall issue, etc.
In this moment, I run the squeezelite command manuelly via idf.py monitor.
squeezelite-esp32> I (29888) squeezelite_cmd: Calling squeezelite
Your mentioned log occurs after the manuelly running of the squeezelite command, when esp32-s3 connects to the lms. Only after this connection is established, I can play music. But this connection doesn't occure automatically on start up.
[00:04:24.067] notify:228 notified server 192.168.0.140 hport 9000 cport 9090
I (29968) network_status: LMS IP: 192.168.0.140, hport: 9000, cport: 9090
[00:04:24.187] notify:228 notified server 192.168.0.140 hport 9000 cport 9090
I (30088) network_status: LMS IP: 192.168.0.140, hport: 9000, cport: 9090
=== END OF LOG ===
Because the esp32-s3 can connect to the LMS, I don't think, it is a firewall problem.
Thx for the explanation of the autoexec warning. I will look again for another problem.
I have ordered an esp32-s3 so I can test myself
The workaround of manually adding
"autoexec": "1",
to the NVS worked for me (with the exact same issue).
So I have 2 autoexec keys in my NVS:
{
"autoexec": "1",
"autoexec1": "squeezelite -o i2s -s x.x.x.x -b 500:2000 -C 30 -d all=info -n \"speaker-name\"",
}
This fixed it for me.
Wow, thank you very much. This solved the issue. Now it works on my ESP32-S3
Hello I try to run squeezelite-esp32 on a ESP32-S3-WROOM-1 board.
Describe the bug
After booting the ESP32-S3, the board can not connect to my LMS-Server. On "idf.py monitor" it gives me the message: W (2938) config: Value not found for key autoexec When I connect to the ESP32-S3 with the "idf.py monitor", I can manually run the command "squeezelite -s Servername -n ESP" and connect my ESP32-S3 device to my LMS-Server. Than I can play music over a connected IS2 DAC.
Preliminary Information
Hardware Details
Please describe your hardware setup:
NVS Settings
Example Log
Here's an example log for reference. Make sure to obfuscate sensitive information like Wi-Fi passwords, MAC addresses, and change IP addresses to something more generic.
sdkconfig
Issue Description