Fix existing bugs and usability problems then add new features.
BeantwortetI have had my Node for about 6 months and I'm mostly satisfied with it, but it does suffer from several bugs and usability problems. I have features that I either want improved or new ones that I want added, but most of all I want the existing bugs and usability problems fixed.
Bugs and Irritations.
1, WiFi Setup, and Connection.
When you turn your Node on for the first time (or after a reset) it goes into Hot-Spot mode (status indicator green), and at this stage you use the BluOS App in your mobile device to detect the Node and select/connect it to your network. If it works, no problems, you can enjoy your Node and your music. If it doesn't work, you are in for a lot of unnecessary frustration.
Bug 1 - When you attempt to connect to your WiFi network, the Node immediately goes into connected mode and displays the blue "connected" status - even if an error occurred and connection was unsuccessful. If the connection was unsuccessful it should resume Hot-Spot mode.
Wish - Fix the bug. (Or said a bit differently - add new feature - resume Hot-Spot mode)
Bug 2 - If Node connection to your WiFi network was unsuccessful, you can't do much in the BluOS app except click the "House icon" but then it goes into an infinite loop searching for your Node. (It's never going to find it because the Node didn't revert back to Hot-Spot mode when it couldn't connect to your WiFi).
Wish 1 - Fix the bug
Irritation 1 - If you close the BluOS app down (on an Android mobile) and re-open it, it will resume where it left off and continue searching. The only way to stop the infinite loop is to find the BluOS app in your phones settings and do a "Force Stop".
Wish 2 - Fix bug 2
Irritation 2 - Re-start the BluOS app (after you have done the "Force Stop") and the app immediately starts to look for your Node. If it can't find it within about 30 seconds it stops and lets you know. So this indicates that two separate pieces of code are being used to perform the same job, but in different places within the app. One correctly drops out of the search loop if Node not found, and the other loops forever. (Programming 101 - if it's the same job - call the same code).
Irritation 3 - The only way to get your Node out of the false connected state is to perform a reset. A reset involves turning power off to the Node for thirty seconds (the Node doesn't have an on/off button) and then quickly getting your finger on the status led, before it gets to the normal startup stage. There's only a very small window of opportunity for you to get your finger on it before it boots up into its previous bugged state. If your power switch is behind the cabinet or is just that little bit too far away, you are going be in for a whole world of frustration.
Wish 3 - Allow at least another half second for user to get finger on status button.
Irritation 4 - Status LED is purple indicating the Node has timed out of Hot-Spot mode. (IE you were called away before you could finish setting it up).
I couldn't find anything in the manual that tells you what to do when the Hot-Spot mode times out.
According to support, they recommend you disconnect the power from your Node and connect an Ethernet cable from your player to the router, and then after several more steps you can disconnect the Ethernet cable. Really! Are they serious! I was expecting something along the lines of "Hold your finger on the status LED for x seconds and the Node will go back into Hot-Spot mode.
Wish 4 - Implement a software solution in Node firmware to restart Hot-Spot mode.
Irritation 5 - A recent firmware update introduced bugs that prevented connection to music shares on the connected network.
Occasionally bugs are introduced when you do updates, it happens and I get that. Except this firmware update (BluOS 3.20.21. Released October 05, 2022) was to provide "Support for Bluesound POWERNODE EDGE". Previous release notes include support for "NAD M50 CD ejecting", "Added balance trim to Bluesound POWERNODE", and "Support for Dolby Atmos on the SOUNDBAR+". I own a Bluesound Node! I don't have a POWERNODE EDGE! It doesn't have a CD! and its also not a soundbar!
Wish 5 - Only update my Node with software essential for the operation of the Node, and it's workings within the network.
Irritation 6 - Error messages (if provided at all) are close to useless.
In the above WiFi and shared folder connection issues I don't recall any error messages at all, but I did get an error message when I tried to connect the Node to the network through a newly purchased WiFi repeater. It said "error connecting to the network". I tried connecting to that repeater three times before I gave up (and each time I had to do the whole reset Node and force stop the BluOS app) - and what useful information could I provide to support? "Error connecting to the network" - I don't think that's going to be any help in diagnosing the problem.
Wish 6 - Provide useful error messages (that perhaps include error codes) - so that the support staff have a diagnostic chance.
-
Offizieller Kommentar
Hi Chris
Thanks for taking the time to write.
All your questions are in fact already answered at www.blueosund.com/setup. The issues you are describing all appear to be related to your handheld device not returning to your main network after joining the BluOS Player's hotspot network once the hotspot is collapsed.
When seeing this, it is often diagnosed by our Support Crew to be related to either a consumer having multiple home networks and their handheld device joining the wrong network or improperly configured wireless extenders in your home network. Check out www.bluesound.com/network101 for great tips on best practices for setting up not just Blueosund but many IoT devices.
In your Quick Setup Guide, also note the toll-free number for your region along with support@bluesound.com for assistance not just with setup issues but any other problems you may come across and we will be happy to help.
Post ist für Kommentare geschlossen.
Kommentare
1 Kommentar