ANNOUNCE: Squeezelite-ESP32 (dedicated thread)

[Paul Webster]

I have just installed 546 on SquezeAMP.
First thing I noticed is that the usual list of nearby WiFi access points is not shown.
It has connected to the one that I had configured - so maybe not showing the others while connected to the configured one is reasonable but in that case then perhaps the text should change.

[MumPf]

Hi
I‘ve sometimes a unintentionally and not reproducible reboot of my board. It looks, that the board works without reboot, if I turn off the bluetooth in this section:




I've a AI-Thinker-ESP32AudioKit-V2.2 and nothing in jack, only 2 speekers on amp, a rotary controller 3 buttons and a I2C display.

And I‘ver several devices paired with this board (Smartphone, Tablet, PC) and it could be, that they connect this board in background, while it plays a radio-stream.

I disable bluetooth and it plays many hours without rebooting, when I enable bluetooth it reboots sometimes after 5 min., sometimes after 1 h.

It’s not a great problem, I can enable bluetooth if I need it, but perhaps you can find the solution in the code...

Many thanks to all for the great work
Wich all a great 2021

This bug is still alive with V546

[chill]

I have just installed 546 on SquezeAMP.
First thing I noticed is that the usual list of nearby WiFi access points is not shown.
It has connected to the one that I had configured - so maybe not showing the others while connected to the configured one is reasonable but in that case then perhaps the text should change.

I updated to 546 about 90 minutes ago. It connected to my wifi immediately. I did not notice whether the list of other access points was initially empty. However, when I check now I can see a list of nearby access points as usual. It's been playing solidly since I updated.

[Grumpy Bob]

I updated to 546 about 90 minutes ago. It connected to my wifi immediately. I did not notice whether the list of other access points was initially empty. However, when I check now I can see a list of nearby access points as usual. It's been playing solidly since I updated.

Likewise - no issues seeing other access points. My SqueezeAMP had been on 542 (I think) and had been experiencing fairly frequent wifi disconnect-reconnects. 546 seems stable so far (about 2h).

Currently my SqueezeAMP is seeing service inside a pair of ancient PC speakers in my newly established home office space, and (perhaps bizarrely) connected via an Access Point in my garage.

Robert

[Paul Webster]

I just forced a refresh at the browser (Chrome on Windows) and it resolved the listings of WAPs for me.

[sle118]

This bug is still alive with V546

I can look into this issue if I am able to reproduce. Do you have a github account? If so, please go ahead and create an issue and describe the steps I would need to take to make that happen. Also, posting your NVS content might provide some additional insights

[sle118]

Currently my SqueezeAMP is seeing service inside a pair of ancient PC speakers in my newly established home office space, and (perhaps bizarrely) connected via an Access Point in my garage.

Robert

If this is the access point with the strongest signal, then that would be logical (maybe the speaker enclosure is shielding the signal coming from certain directions... For example if the front plate is metal?). Make sure that the system tab's WiFi configuration is set to comprehensive scan. Fast scan will randomly pick the first access point that sends a beacon when the WiFi stack goes up.

[MumPf]

I can look into this issue if I am able to reproduce. Do you have a github account? If so, please go ahead and create an issue and describe the steps I would need to take to make that happen. Also, posting your NVS content might provide some additional insights

#67

[Grumpy Bob]

If this is the access point with the strongest signal, then that would be logical (maybe the speaker enclosure is shielding the signal coming from certain directions... For example if the front plate is metal?). Make sure that the system tab's WiFi configuration is set to comprehensive scan. Fast scan will randomly pick the first access point that sends a beacon when the WiFi stack goes up.

I didn't mean to suggest this was the wrong AP - quite the contrary, it is the one I wished to use! I just thought it a little amusing I had a nice AP from my garage, where I need it for running Zwift on an iPad Pro. That AP is much closer to my home office than my router, as we have a long, thin house.

Very pleased with the SqueezeAMP device.

Robert

[CJS]

As @sle118 mentioned, we have moved to an updated espressif framework and tweaked one parameter and so far, I've been playing for more than 2 hours with version 546 without any issue while before, with 542, I could not get more than 10 mins. My local builds were fine because, (thanks Murphy's law) my framework version was a snapshot the day before espressif made a change that created an issue with one config parameter (and probably a few other things) while @sle118's one was taken a few days later...
Anyway, if you could try 546 and give us feedback, that would be highly appreciated.

After flashing my SqueezeAMP with FW 546 and doing a power cycle I performed a wifi stability test by playing a radio stream. The test was done with Bluetooth disabled.
The result is that during the test time of over 16 hours I did not get any disconnect, as illustrated by the SqueezeESP32 status page and radio stream play time in the screenshot below.
So wifi stability of FW 546 looks quite good. Thank you philippe_44 and sle118 for this great effort!

[Grumpy Bob]

Likewise - no issues seeing other access points. My SqueezeAMP had been on 542 (I think) and had been experiencing fairly frequent wifi disconnect-reconnects. 546 seems stable so far (about 2h).

Currently my SqueezeAMP is seeing service inside a pair of ancient PC speakers in my newly established home office space, and (perhaps bizarrely) connected via an Access Point in my garage.

Robert

My SqueezeAMP has been playing an audio stream for nearly 20h now without interruption, 546 seems very stable.

Robert

[philippe_44]

My SqueezeAMP has been playing an audio stream for nearly 20h now without interruption, 546 seems very stable.

Robert

[mboxler]

Scan I2C bus for devices (Advanced)

Can anyone verify if this works? I'm playing around with a Merus amp. I need to check/change some of it's registers, but the Scan I2C bus for devices shows nothing. I also get nothing while an I2C display is attached and working. Shouldn't the display show up in the scan, and if so, can someone verify that the scan shows a connected display?

Running fw: I2S-4MFlash.546.master-cmake

Thanks, Mike

[ElFishi]

Can anyone verify if this works? I'm playing around with a Merus amp. I need to check/change some of it's registers, but the Scan I2C bus for devices shows nothing. I also get nothing while an I2C display is attached and working. Shouldn't the display show up in the scan, and if so, can someone verify that the scan shows a connected display?

Running fw: I2S-4MFlash.546.master-cmake

Thanks, Mike

Executing

0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- 3c -- -- --
40: -- -- -- -- -- -- -- -- 48 -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

------------------------------------------------------------------------------------
Detected the following devices (names provided by https://i2cdevices.org/addresses).
60 [3ch]- SSD1305 SSD1306 PCF8578 PCF8569 SH1106
72 [48h]- PCA9685 INA219 PN532 TMP102 INA260 ADS1115
------------------------------------------------------------------------------------

[mboxler]

Executing

0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- 3c -- -- --
40: -- -- -- -- -- -- -- -- 48 -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

------------------------------------------------------------------------------------
Detected the following devices (names provided by https://i2cdevices.org/addresses).
60 [3ch]- SSD1305 SSD1306 PCF8578 PCF8569 SH1106
72 [48h]- PCA9685 INA219 PN532 TMP102 INA260 ADS1115
------------------------------------------------------------------------------------

Thanks! This is all I get with a connected and working SSD1306 display

Executing

0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --