ANNOUNCE: Squeezelite-ESP32 version 2.x

[philippe_44]

> Can someone explain to me the advantages of CSpot over LMS plugin
> Spotty.

My 2c:

Pro CSpot:
- hopefully more robust Spotify Connect mode
- no odd volume sync side effects
- works without LMS

Pro Spotty:
- UI on both Spotify app and SB Control points
- better integration and switching between Spotty streaming modes
- Library integration with My Music and/or other music services
- available for any SB player

[philippe_44]

ANNOUNCE: Squeezelite-ESP32 version 2.x

After a long pause, @sle118 and I are happy to have released the first version 2.x. It is what has been hidden under test for a while under the name cmake-4.3 (you still see that in the "FW Branch" section). This is still early stages, but it's probably good enough for a first release. Updates include:

- support of Ethernet and rewritten Wifi/Network manager
- build-in support of Spotify (through cspot project)
- improved webUI
- update to espressif's 4.3 esp-idf framework

Version 1.x (cmake) is now in maintenance mode which means only major issues will be backported). The SqueezeAMP batch that I'm currently building, will ship with 2.x (cmake-4.3)

You can go back and forth between releases 1.x and 2.x, but I still strongly suggest that you have the capability to do a local update using USB-to-uart in case things go wrong.

[mherger]

ANNOUNCE: Squeezelite-ESP32version 2.x

Installed just fine and continued playback as usual. The only odd
observation after two minutes: it picked up a new IP address, I didn't
reach it using the browser history any more :-). I guess that's due to
the new networking stack?

[mherger]

ANNOUNCE: Squeezelite-ESP32version 2.x

Two more minutes: Spotify wouldn't connect. Using the Mac desktop
version of Spotify the speaker icon would stick blinking at the bottom -
which usually means it's trying to connect. And the iOS Spotify app
would keep saying "Connecting..." while playback comes out of some
random other device (not the phone).

[Cadster]

no more ticking sounds!

Thanks Philippe, no more ticking sounds in my audiokit ESP32-A1S with the AC101 DAC, Great release!

[philippe_44]

Two more minutes: Spotify wouldn't connect. Using the Mac desktop
version of Spotify the speaker icon would stick blinking at the bottom -
which usually means it's trying to connect. And the iOS Spotify app
would keep saying "Connecting..." while playback comes out of some
random other device (not the phone).

Could you provide some logs ?

[philippe_44]

Two more minutes: Spotify wouldn't connect. Using the Mac desktop
version of Spotify the speaker icon would stick blinking at the bottom -
which usually means it's trying to connect. And the iOS Spotify app
would keep saying "Connecting..." while playback comes out of some
random other device (not the phone).

And Spotify has been giving me a lot of heartburns, but although the current version still crashes from time to time, it should play “most of the time”

[mherger]

ANNOUNCE: Squeezelite-ESP32version 2.x

> Could you provide some logs ?

I'm sorry to ask... how would I get them?...

One other observation, related or not: the web UI would never show the
Spotify bitrate. I can select a bitrate, apply it, device restarts,
setting is gone (or not shown correctly). Might be a UI glitch.

[sle118]

> Could you provide some logs ?

I'm sorry to ask... how would I get them?...

One other observation, related or not: the web UI would never show the
Spotify bitrate. I can select a bitrate, apply it, device restarts,
setting is gone (or not shown correctly). Might be a UI glitch.

you can activate telnet from the web ui's system tab. Then with telnet you'll have the logs. Alternatively, you would need a USB to serial adapter.

As for the bitrate, could you please give me some more details on the issue? This might be something I have to fix.

[mherger]

Ok, that already was useful to me: "Cannot use CSpot sink while LMS/BT/Airplay are controlling player". So stopped LMS playback. But no dice. It basically ends with a bunch of these:

E ShannonConnection.cpp:77: Shannon read: Mac doesn't match

I wonder whether this is related to the fact that it's getting a new IP all the time...

[sle118]

Ok, that already was useful to me: "Cannot use CSpot sink while LMS/BT/Airplay are controlling player". So stopped LMS playback. But no dice. It basically ends with a bunch of these:

E ShannonConnection.cpp:77: Shannon read: Mac doesn't match

I wonder whether this is related to the fact that it's getting a new IP all the time...

Not sure what you mean by '"it's gettin a new IP all the time". No matter how many reboots I do, I still get the same address each time.

As for the bit rate problem, I was able to reproduce it and will have a look.

[mherger]

As for the frontend: when I load the page, it always shows the "---" placeholder. I can then select a bitrate, apply it (SqueezeAMP reboots). But when I reload the page, it shows "---" again.

config.json would always return "format: 1". I don't know whether this has anything to do with the bitrate, but I didn't find any bitrate related info in there.

        "cspot_config": {
            "type": 33,
            "value": "{\"deviceName\":\"squeezelite-esp32\",\"format\":1,\"volume\":32767}",
            "chg": false
        }

[mherger]

ANNOUNCE: Squeezelite-ESP32version 2.x

> Not sure what you mean by '"it's gettin a new IP all the time". No
> matter how many reboots I do, I still get the same address each time.

I got three different today so far.

[sle118]

> Not sure what you mean by '"it's gettin a new IP all the time". No
> matter how many reboots I do, I still get the same address each time.

I got three different today so far.

Assuming that the MAC address doesn't change (which would be very unusual and somewhat unexplainable to me), it looks like your DHCP server likes to cycle through its range of addresses?

[mherger]

ANNOUNCE: Squeezelite-ESP32version 2.x

> Assuming that the MAC address doesn't change (which would be very
> unusual and somewhat unexplainable to me), it looks like your DHCP
> server likes to cycle through its range of addresses?

I've only seen this with Squeezelite-ESP32 since the upgrade. I noticed
because I used to address it using its IP address - which I knew by
heart, as it never changed before. Some other devices have been using
the same IP for _years_, without telling the router to assign them that
address.

But don't worry about this too much. It might have been a fluke. I'll report
back if I experience it again.