If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
I still do not recommend to use more than 12V for casual use. The TAS produces much more heat while idle at that voltage. This is the reason why I did the boost version so that 12v is the voltage whether you use battery or wall adapter.
I know sle118 was talking about 20v, but it sounds like I should at least get a heatsink for the 16v psu i have on the way then.
It's gonna be on while i'm working from home during the day so quite a few hours, but not super loud or anything. Went 16v as I just want it to sound the best it can.
I know sle118 was talking about 20v, but it sounds like I should at least get a heatsink for the 16v psu i have on the way then.
It's gonna be on while i'm working from home during the day so quite a few hours, but not super loud or anything. Went 16v as I just want it to sound the best it can.
You can put a heatsink on the TAS and on the exposed copper pad I have added a while ago. I don’t think it’s absolutely necessary though as I don’t think 16V is needed for usual listening level.
I was able to complete more progress on the user interface today. They are dedicated mainly to configuration and status.
Configuration tab
--------------
Status tab, with gpio assignment list
LMS 7.9 - 1xRadio, 1xBoom, 5xDuet,3xTouch, 1 SB2. Sony PlayStation, Emby, Chromecast v1 and v2 and...
6xSqueezeAmp, several other ESP32-Wrover boards with jumper wires flying around, some with ethernet!
I was able to complete more progress on the user interface today. They are dedicated mainly to configuration and status.
Configuration tab
--------------
Status tab, with gpio assignment list
Looks good!
I just made the jump from make to this cmake version.
Did it via OTA update from a make recovery fw - hope that is ok and they (-> 'old' make recovery and 'new' cmake squeezelite) do not interfere with each other, right?
One thing I noticed:
Where do I setup the Bluetooth and Airplay settings in cmake Version?
I do not find anything related in 'Configuration', 'Advanced' or 'NVS editor' Tab (NVS is empty except 1 line to add new entries)
Is that due to work in progress, or am I missing something?
LMS 8.x on RasPi4 (running along with OMV and AdGuard)
Player: 5 x Squeezebox Classic, Slimp3, SqueezeAmp
2nd System: PiCorePlayer (and LMS) on Pi Zero
Looks good!
I just made the jump from make to this cmake version.
Did it via OTA update from a make recovery fw - hope that is ok and they (-> 'old' make recovery and 'new' cmake squeezelite) do not interfere with each other, right?
One thing I noticed:
Where do I setup the Bluetooth and Airplay settings in cmake Version?
I do not find anything related in 'Configuration', 'Advanced' or 'NVS editor' Tab (NVS is empty except 1 line to add new entries)
Is that due to work in progress, or am I missing something?
If there's any way you can flash with a USB dongle, I'd recommend CMake for recovery; OTA operations have been very stable for me on that release.
There shouldn't be any interference. Just remember to refresh your browser page when switching from recovery to squeezelite and vice-versa.
There are two Bluetooth settings (sink and source). Which one are you referring to?
Bluetooth sink refers to the Bluetooth being exposed, and the only setting (besides enabling it or not) is the name that's broadcasted. This now lives under "Device name", which consolidates almost all the names settings in one place. Change the name there, and Bluetooth source, network name, etc are all automatically updated at one. The only name that isn't implemented so far is the one that can be set in the Audio page (squeezelite name).
I think I should add a "service" section to centralize activating telnet, Bluetooth sink, airplay, etc.
If there's anything you'd like to see, let me know!
LMS 7.9 - 1xRadio, 1xBoom, 5xDuet,3xTouch, 1 SB2. Sony PlayStation, Emby, Chromecast v1 and v2 and...
6xSqueezeAmp, several other ESP32-Wrover boards with jumper wires flying around, some with ethernet!
There are two Bluetooth settings (sink and source). Which one are you referring to?
Bluetooth sink refers to the Bluetooth being exposed, and the only setting (besides enabling it or not) is the name that's broadcasted. This now lives under "Device name", which consolidates almost all the names settings in one place. Change the name there, and Bluetooth source, network name, etc are all automatically updated at one. The only name that isn't implemented so far is the one that can be set in the Audio page (squeezelite name).
I think I should add a "service" section to centralize activating telnet, Bluetooth sink, airplay, etc.
If there's anything you'd like to see, let me know!
Thanks for the feedback, sle118!
@philippe44:
The cmake UI in the 'Status' tab showed one occurence of my earlier reported random WiFi disconnecting:
(in this case, SqueezeAmp was on, but play was paused)
LMS 8.x on RasPi4 (running along with OMV and AdGuard)
Player: 5 x Squeezebox Classic, Slimp3, SqueezeAmp
2nd System: PiCorePlayer (and LMS) on Pi Zero
(in this case, SqueezeAmp was on, but play was paused)
If you are able to flash the development recovery (aka CMake), and remind me the device in which you are running squeezelite, I'll build you a custom version with full WiFi log verbosity to try and catch more details. Of course, a serial dongle will be needed to capture these, or at least a telnet connection which might be enough, given that WiFi reconnects. I built a telnet buffer large enough to hold lines until a connection is re-established. WiFi low level logs would give us a better understanding on what is happening to the connection.
If you can't flash CMake recovery, we can find another way to install that custom build (I would create a new Jenkins target)
LMS 7.9 - 1xRadio, 1xBoom, 5xDuet,3xTouch, 1 SB2. Sony PlayStation, Emby, Chromecast v1 and v2 and...
6xSqueezeAmp, several other ESP32-Wrover boards with jumper wires flying around, some with ethernet!
If you are able to flash the development recovery (aka CMake), and remind me the device in which you are running squeezelite, I'll build you a custom version with full WiFi log verbosity to try and catch more details. Of course, a serial dongle will be needed to capture these, or at least a telnet connection which might be enough, given that WiFi reconnects. I built a telnet buffer large enough to hold lines until a connection is re-established. WiFi low level logs would give us a better understanding on what is happening to the connection.
If you can't flash CMake recovery, we can find another way to install that custom build (I would create a new Jenkins target)
Hi sle118;
that is very kind.
I will be able to flash the new recovery, but I can do that earliest in a week.
(I need to hold a training starting monday and I am procrastinating the preparation for too long already.....)
Thanks again; I will let you know.
LMS 8.x on RasPi4 (running along with OMV and AdGuard)
Player: 5 x Squeezebox Classic, Slimp3, SqueezeAmp
2nd System: PiCorePlayer (and LMS) on Pi Zero
Hi sle118;
that is very kind.
I will be able to flash the new recovery, but I can do that earliest in a week.
(I need to hold a training starting monday and I am procrastinating the preparation for too long already.....)
Thanks again; I will let you know.
Following a recommendation on Gitter, I added a nvs parameter to disable the ESP32's wifi power save mode.
disable_ps=n to let the esp32 put the wifi radio in reduced power mode (default mode)
disable_ps=y to prevent the esp32 from using the power save mode (may help with stability)
Please try and report (no need to flash a different recovery).
There was an issue with my commit. I need to push a new one (soon). Ignore build #136 for now
LMS 7.9 - 1xRadio, 1xBoom, 5xDuet,3xTouch, 1 SB2. Sony PlayStation, Emby, Chromecast v1 and v2 and...
6xSqueezeAmp, several other ESP32-Wrover boards with jumper wires flying around, some with ethernet!
Following a recommendation on Gitter, I added a nvs parameter to disable the ESP32's wifi power save mode.
disable_ps=n to let the esp32 put the wifi radio in reduced power mode (default mode)
disable_ps=y to prevent the esp32 from using the power save mode (may help with stability)
Please try and report (no need to flash a different recovery).
There was an issue with my commit. I need to push a new one (soon). Ignore build #136 for now
I will do that.
Meanwhile, I had my system idle (power on, but stream on pause)
and teh following were the status messages:
Sometimes ~10minutes, sometimes~20, sometimes over an hour - but it seems always be multiples of 10 minutes
LMS 8.x on RasPi4 (running along with OMV and AdGuard)
Player: 5 x Squeezebox Classic, Slimp3, SqueezeAmp
2nd System: PiCorePlayer (and LMS) on Pi Zero
Sometimes ~10minutes, sometimes~20, sometimes over an hour - but it seems always be multiples of 10 minutes
I just pushed the new release. Give the new option a try.
Meanwhile, I also added a new configuration section, which allows enabling/disabling some services.
LMS 7.9 - 1xRadio, 1xBoom, 5xDuet,3xTouch, 1 SB2. Sony PlayStation, Emby, Chromecast v1 and v2 and...
6xSqueezeAmp, several other ESP32-Wrover boards with jumper wires flying around, some with ethernet!
I just pushed the new release. Give the new option a try.
Meanwhile, I also added a new configuration section, which allows enabling/disabling some services.
3 Things:
1) I can confirm that using fw development.137 and putting disable_ps to y (in NVS tab) seems to fix my WiFi dropouts. (~1 hrs test)
Thanks, sle118!
2) Odd side-note - but not important for now: I don't have the new enabling/disabling of Telnet, Bluetooth aso services in the configuration tab (As stated, I am running development.137-SqueezeAmp4MBFl) on a SqueezeAmp
3) On Gitter, you have a discussion with problems of ESP radio beeing 'too loud' ('tinfoil hats').
I can report a potentially related problem:
I have 2 AP w/ the same SSID & PW in the house, so WiFi devices can pick whichever gives better reception.
But the SqueezeAmp always connects to the AP which was farther away - even if I erased the SqueezeAmps WiFi config and 'teached' it new.
It never connected to the other AP (right next to it!). I could force it by switching the AP further away off - but as soon as I switched that on again, it connected back to that one again (the one further away).
-> So, if you could add an option to control radio power - that would be great!
Thanks again for all the great work philippe44 & you (and others) are doing here!
(SqueezeAmp enclosed in small JBL Control1 Speakers are my daily listening device in my study)
LMS 8.x on RasPi4 (running along with OMV and AdGuard)
Player: 5 x Squeezebox Classic, Slimp3, SqueezeAmp
2nd System: PiCorePlayer (and LMS) on Pi Zero
3 Things:
2) Odd side-note - but not important for now: I don't have the new enabling/disabling of Telnet, Bluetooth aso services in the configuration tab (As stated, I am running development.137-SqueezeAmp4MBFl) on a SqueezeAmp
Try doing a full page refresh : CTRL+F5 in Chrome for Windows.
Originally posted by slimhase
3 Things:
3) On Gitter, you have a discussion with problems of ESP radio beeing 'too loud' ('tinfoil hats').
I think I found an explanation. See gitter for more details. In short, the wifi client will likely connect to the AP that is on the lowest channel since the connect mode is fast scan. I'll try to come up with a Wifi config section to control these parameters and see if using "full scan" rather than "fast scan" will help
LMS 7.9 - 1xRadio, 1xBoom, 5xDuet,3xTouch, 1 SB2. Sony PlayStation, Emby, Chromecast v1 and v2 and...
6xSqueezeAmp, several other ESP32-Wrover boards with jumper wires flying around, some with ethernet!
Try doing a full page refresh : CTRL+F5 in Chrome for Windows.
I tried that. I even cleared my entire Browser cache - still, my Config Tab starts with
'Device Name
New Name....'
and nothing wrt
'Services
Telnet Server' aso
(maybe some residues from many, many reflashs? ->At some point, I should do a full clear & flash throu USB dongle....)
Originally posted by sle118
I think I found an explanation. See gitter for more details. In short, the wifi client will likely connect to the AP that is on the lowest channel since the connect mode is fast scan. I'll try to come up with a Wifi config section to control these parameters and see if using "full scan" rather than "fast scan" will help
That is really great!!
(The explanation / hypothesis holds also for my setup: The AP it connects to is using Ch1 and the 'nearer one' is running on Ch4 (which it ignores)
-> Can't wait to try out the next revision.
LMS 8.x on RasPi4 (running along with OMV and AdGuard)
Player: 5 x Squeezebox Classic, Slimp3, SqueezeAmp
2nd System: PiCorePlayer (and LMS) on Pi Zero
That is really great!!
(The explanation / hypothesis holds also for my setup: The AP it connects to is using Ch1 and the 'nearer one' is running on Ch4 (which it ignores)
-> Can't wait to try out the next revision.
It's out now. Check build #137 and follow discussion on gitter.
LMS 7.9 - 1xRadio, 1xBoom, 5xDuet,3xTouch, 1 SB2. Sony PlayStation, Emby, Chromecast v1 and v2 and...
6xSqueezeAmp, several other ESP32-Wrover boards with jumper wires flying around, some with ethernet!
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment