Can someone tell me how to put a Pulse M into factory reset mode?

Answered
Bryon Black

I can not seem to get my Pulse M to do a factory reset, I have been using the steps below...but it does not appear to work, is there a different protocol for the Pulse M????

Thanks in advance. 

:

Steps to Factory Reset:
1. Disconnect the PULSE M from electrical power.
2. Wait 30 seconds.
3. Reconnect the power.
4. Once the LED turns Red, press and hold the PLAY/PAUSE button. The LED will immediately turn Green and
then back to Red - continue to hold the button for 30 seconds.
5. After 30 seconds, the LED will begin to blink red – then release the button.
6. All customization to the PULSE M will be removed and restored to factory settings.
IMPORTANT Removing your nger from the PLAY/PAUSE button at any time before the LED begins ashing red will
cancel the factory reset and leave the PULSE M in Upgrade Mode. Just start the steps again to factory reset it.
You will know the factory reset is successful if the PULSE M returns to Hotspot mode (wireless connection - the LED
will turn solid green). If it is connected to your network through a wired Ethernet connection, it will simply connect as if
it was a new player (LED will turn solid blue).
0

Comments

7 comments

Date Votes
  • Official comment
    Seppi Evans
    Hi-Res

    It’s the timing of when you place your finger, try a litter earlier or later and keep it held until it blinks.

  • Bryon Black

    Seppi- 


    Thanks for the hint. 

    I am not seeing it ever turn Green at the beginning, just Red. It does blink read (step 5) after 30 secs of holding. 

    Releasing the button the Pulse then goes through what appears to be a reboot, and then ends up Solid Green and is discoverable as a new device. 

    Next issue is that adding it as a new player, ends with an error on the iPhone during the reconnection to wifi. And the device is still not showing in the players tray. :|

     

     

    0
  • Seppi Evans
    Hi-Res
    • Edited

    Sounds like it did factory reset, can’t check the sequence on my Pulse M due to its being on its own network and loosing everything if I reset it but it did factory reset before Christmas without a problem.

    On the iPhone if the M does show as a hotspot in preferences with a default name then it’s 100% factory reset.

    If unable to complete setup run an Ethernet lead from the M to your Router just on a temp basis, the LED will turn Blue and you then be able to finish configuration / adding Wi-Fi credentials .

    Have to ask why did you have to factory reset?

     

    EDIT

    If you are still having issues in the BluOS App Please select Settings, Send Support Request so the Bluesound Support Crew can review the log file and take a closer look. If you cannot do this then use email support@bluesound.com

    0
  • Bryon Black
    • Edited

    Seppi - 

    Thanks for your help.

    Why system reset?? I belive my router did an automatic upgrade that caused the Pulse M's to not reconnect. My other Bluesound devices (Soundbar + Subwoofer - hardwired ) and Mini 2i wifi were connected as was a Hub, which is connected hardwired. 

    The M's would not connect nor would they reinstall via the iPhone app. Rebooting them they appeared not to get a dhcp address via wifi, they would via ethernet. So I figured it best to do a system reset and start from scratch. 

     So #1 Pulse M would not provision, using wifi nor would it fully provision (show up in the bluOS app). After a full reset of the #2 Pulse M, and connecting it via ethernet it completed install / provisioning and then began to work again. 

    #1 Pulse M would connect via ethernet but would not connect via wifi. I review my network logs and noticed that #1 showing an odd behavior getting DHCP. It makes a request for DHCP and the DHCP server would give the wifi interface an address (192.168.111.35 for example), then #1 would assign what I think is a local IP address to the interface on a address  in the 10.10.1.x network. My DHCP server then reported that the device is on an invalid network using an address like 10.10.1.118. If it was connected via ethernet the DHCP was assigned from the 192.168.111.x network and ithe Pulse would work wired. 

    In order to fix the issue with the wifi provisioning of DHCP after a lot of trail and error, I ended up rebooting the router. That seemed to clear the issue with DHCP, and a proper IP address was supplied and the device did not try to assign a local IP. From there I was able to do a reinstall using ethernet and then moved to wifi and the unit is now working again. 

    This took place over a course of days, and dozens of power off, wait 30 secs or wait 5 mins, power on, try some stuff, repeat... 

    I think the DHCP cache got corrupted and it would assign an address to the wifi interface of the device but for some reason it erred out, and then the device assigned a local ip address (10.10.1.118 example), which was not reachable. Once rebooted the DHCP cache was rebuilt and the DHCP ip address was able to be provisioned without error. 

    Luckily i have a good deal of experience with networking and having the ability to review the router logs and and seeing network traffic of the working dev ices and comparing that traffic to the non-working Pulses, was key to trouble shooting the issue. If I did not have visibility to the logs and network traffic the resolution of this could have taken a long time or forever, or I might have gotten lucky and rebooted the router at some point and stuff magically worked again. 

    Anyway, thanks for your help, and perhaps my experience is helpful to others in the community. 

    -bb

    0
  • Seppi Evans
    Hi-Res

    I suspect that you were plagued with a duplicate (or more) IP addresses. Routers unfortunately loose their memory of which IPs have already been issued during a reboot so when a device asks for a new IP the Router blindly hands out one that not in its opinion in use but was issued before the reboot and you end up with two devices with the same address.

    A client requests a new IP but if there are two devices with the same IP concurrently the reply could go to the wrong client and the original client requesting the IP does not hear back from the Router gives up and self assigns and IP.

    Long term creating reserved IPs on your Router for your Bluesound devices should stop this happening again.

    0
  • Bryon Black
    • Edited

    Hey Seppi-

    Follow up. 

    Over the past couple of days I went about reorganizing my DHCP leases and creating reserved IPs for a variety of devices including all my new bluesound components. As I went about the re-org, putting each devices MAC address into the reserved list, the same behavior as i experience previously occurred where when the Pulses when they are connected wirelessly, they would get a DHCP address from my router from the 192.168.111.x network, and then immediately get another address via DHCP on the 10.10.1.x network and then nothing would connect of show up in the BlueOS app. 

    Frustrated, I did what worked form me previously, I turned the whole mess off waited and turned everything back on which cleared the issue last time but this time no joy... every time a BlueSound device tried to connect wirelessly it would first get a 192.168.111.x network address then immediately get pushed another address from the 10.10.1.x network. I kept thinking it was some kind of Bluesound issue until I noticed my Apple watch exhibiting the same exact symptoms in the DHCP log. 

    Note: this behavior happened to devices that had reserved DHCP entries (addresses). So regardless of having a reservation for an IP on the 192.168.111.x network  the 10.10.1.x address would be sent and override or break the DHCP address of the device making the request. 

    That got me thinking there is another DHCP server on my network...but where????

    First thought was iPhone and iPads, mine all have the ability to be wifi hotspots and a I recently turned on my iPhone hotspot to support another activity and I had not turned it off. While on the right path that, the iPhone and iPads were not the devices issuing dhcp. 

    I looked a bit more carefully at the DHCP traffic in my firewall and noticed where the 10.10.1.x DHCP was coming from (10.10.1.254), this told me that another device was a DHCP server, a quick look at the devices connected to my router, I noticed the funky little hockey puck LED lighting controller blinking quietly next to the router. I unplugged it and then rebooted the whole mess without the LED lighting controller and suddenly and happily everything started to get DHCP from 192.168.111.x and the address assigned was not overwritten.  All the BlueSound stuff started to show up and started to work as before, wirelessly. :) :) :) 

     

    So it appears now once and for all, everything is working, and everything is now on reserved IPs via DHCP. :) 

    1
  • Seppi Evans
    Hi-Res

    Great catch there! I have had this in corporate environments previously with two DHCP servers running but the IP address range was the same and just the gateway entry was different so was very hard to figure out. Someone had brought a Unix box in from home and plugged it into the LAN without realising what services were running on it.

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post