Update to version 4.0 breaks functionality

[vishhvaan]

The update seems to have to have added new login to the web interface and other features. It breaks this library.

[arigit]

Landed here after all my automations with the ls50w2 broke, after several years of flawless use
Firmware 4.0 updates internal streaming libraries, adds a few new ones and drivers added "password protection" to the device portal. I don't see any 'password' setting in the updated app that exposes some these features

[arigit]

Now if you manually navigate to the speaker (http://1.2.3.4) you can access a menu that triggers a "First Time Setup" and asks to create a password. Not sure though the password is related to the breakage since I still see some status (input status) displayed in HA

[N0ciple]

I will check if it is possible to adapt the library to still perform actions once the password is setup and known

[N0ciple]

Ok the password stuff is quite strange. If you type the password once on a computer, it seems to grant you access to the setting page, even if you wipe your cookies or even change browser. I wonder if they whitelist the IP.
But that is not the real problem, the real problem is that they changed some GET requests for POST requests.
This should be relatively simple to fix.
Good news is that you apparently don't need the password to perform these requests (but maybe you still have to set it once).

[N0ciple]

Oh boy, that was easy.

I just changed all the all the functions that set something to now use a post request instead of a get request.

[N0ciple]

Looking at the release notes here makes me think that at the moment only the LS50W2 have this new feature and that the other speakers still uses the old GET only api.
I will try to do something quick and dirty to support the "legacy" mode for models that have not been updated yet.

[arigit]

Ok the password stuff is quite strange. If you type the password once on a computer, it seems to grant you access to the setting page, even if you wipe your cookies or even change browser. I wonder if they whitelist the IP. But that is not the real problem, the real problem is that they changed some GET requests for POST requests. This should be relatively simple to fix. Good news is that you apparently don't need the password to perform these requests (but maybe you still have to set it once).

I can confirm that the changes work just fine without setting the password for the first time in the speakers, I am positive on that. Also, it continues to work flawlessly after setting it. I believe there are a few new features in this firmware (sleep function) - it's mentioned in the release notes.

Thank you @N0ciple for the super fast response on this and the great work