One of my three Flex 2i speakers keep crashing - at random
I have three Flex 2i speakers all on wifi and working great for 2 years. One of them started to fail (crash) and would not connect any more. I moved it to a wired connection and it's been fine for a couple of months, but it's still crashing randomly - it may not happen for a week at a time.
It's the most used speaker of the three as it sits in my home office - so it's turned on for most of the day. They all only stream from a local NAS SMB share. All speakers are on the latest firmware and always kept up to date.
Using /enable?log=yes I enabled log keeping and /diag?print=1 to show me the logs, I am seeing a lot of the following:
dspout: [error] /tmp/controller_socket: Resource temporarily unavailable
I have used the speaker all this week (w/c 2024-05-27) but the logs are missing out entire days:
...
May 17 12:56:18 (none) user.info dspout: [error] /tmp/controller_socket: Resource temporarily unavailable
May 29 08:21:59 (none) syslog.info syslogd started: BusyBox v1.26.2
...
May 29 08:23:59 (none) syslog.info syslogd exiting
May 31 13:34:14 (none) syslog.info syslogd started: BusyBox v1.26.2
...
The speakers are also all connected to Home-Assistant and controlled with the published API via Node-RED flows
-
Offizieller Kommentar
Hi Mike,
For 1:1 support assistance, could you please send us a Support Request through the BluOS app? By doing so, our system will conveniently include diagnostic log files from your player/s. This will help our support team quickly identify and resolve any issues with your players.
In BluOS, tap on settings then Send Support Request.
Thanks for #LivingHiFi -
Thanks Mark, I have just submitted it.
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
2 Kommentare