Announcement

Collapse
No announcement yet.

Bricked two SqueezeAMPs - how to recover?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #31
    Yep, that was it. I booted to recovery mode, went into the NVS editor, fixed the argument, and it's working now. Thanks for all of the help...definitely would have been a lot less of a slog if I'd gotten a different serial adapter much earlier!

    For reference, the problem was here:
    I (3443) console: Running command autoexec1 = squeezelite -b 500:2000 -d all=info -C 30 -W -n Attic -o I2S 192.168.10.40

    This should have been:
    I (3443) console: Running command autoexec1 = squeezelite -b 500:2000 -d all=info -C 30 -W -n Attic -o I2S -s 192.168.10.40
    Last edited by benh; 2023-01-26, 19:05.

    Comment


      #32
      Originally posted by benh View Post
      Yep, that was it. I booted to recovery mode, went into the NVS editor, fixed the argument, and it's working now. Thanks for all of the help...definitely would have been a lot less of a slog if I'd gotten a different serial adapter much earlier!

      For reference, the problem was here:
      I (3443) console: Running command autoexec1 = squeezelite -b 500:2000 -d all=info -C 30 -W -n Attic -o I2S 192.168.10.40

      This should have been:
      I (3443) console: Running command autoexec1 = squeezelite -b 500:2000 -d all=info -C 30 -W -n Attic -o I2S -s 192.168.10.40
      This brings us back to the fact that the system shouldn't reboot when squeezelite bails out; it should instead send an air message to the UI and stay there.
      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!

      Comment

      Working...
      X