BluOS Player firmware 4.0.4 update
Answered
Hi Tony,
My 3 Pulse Flex speakers have just updated themselves to BluOS 4.0.4, while my two Powernodes have remained at BluOS 4.0.2. Curious.......
While the 2 Powernodes are still accessible via the usual BluOS apps, the 3 Pulse Flex speakers are not accessible. All the five devices are, however, still fully connected to my WiFi network,
I have had to factory reset the 3 Pulse Flexs to get them to connect again to the apps. Please note that after I did the initial version 3 to version 4 firmware update, none of the players would connect to the apps and I had to factory reset all 5 of them to get my system up and running again!
Any suggestions as to why this strange behaviour is happening? This will be rather tedious if it happens after every update!
-
Official comment
After an update it sometimes happens that the router needs a reboot. Switch off router and all devices, after 5' restart router, when fully on line restart devices one by one. Restart app. This is faster than factory reset and usually is sufficient.
-
Hmmm......does three times out of three, so far, count as "sometimes", I wonder?
I have a router with a separate multi-disk mesh WiFi system to reboot.
This router, etc, rebooting shouldn't be necessary!
0 -
This router, etc, rebooting shouldn't be necessary!
You'd be surprised. Count how many IoT devices in your home. Many IT professionals recommend you should be getting in the same habit with your home router as you do with lint traps in your dryer (weekly) and batteries in your smoke detector (every 6 months). Many recommend a monthly reboot of your home router to ensure proper cache, latest DNS resolution changes and clearing internal Network Allocation Tables which can become corrupted.
It's also a great idea to review your home networking documentation to see about DHCP reservations for many of your devices to a) make restart of outages faster and b) slow NAT corruption.
0 -
I personally never had to do the reboot procedure but my system is maybe too simple: Noide2 + Node2i.
Router is no mesh just a Fritz!box. Multicast is rather demanding on the network as I understand.
0 -
This router, etc, rebooting shouldn't be necessary!
So, for three years or so, it hasn't been necessary to reboot the router, etc......so why now?????
0 -
Something is very wrong with the network code of blue os. Really it is the only hardware i own which is this problematic in my home net. And i run a well configured bare metal pfsense, not some cheap ISP router.
If in every 2nd topic the solution is to reboot router one could come to the conclusion something with the own product could be wrong in this regard.2 -
BluOS doesn't use a cloud to store user data or IoT devices to ensure real-time syncing. Since we do not down-sample music, as a result we do admittedly create extra traffic which can be misinterpreted. It sounds like you can check this easily then. Check your log files of pfSense to see where your traffic is being blocked internally and why your devices cannot sense Multicast Traffic. I'd start with your IGMP settings.
If you'd like some assistance with this, our Support Crew can help by e-mailing them at support@bluesound.com and they can arrange an appointment.
0
Please sign in to leave a comment.
Comments
7 comments