Remote control (ir) stopped working after BluOS 3.6.2 upgrade

Answered

Comments

22 comments

  • Official comment
    Avatar
    Tony W. - Product Support Manager

    Everyone

    Thank you for your continued patience on this matter.

    Our Quality Assurance Team has identified the root cause and our Software Development Team has provided a resolution. Look in your App for an update to BluOS 3.6.6 within the next 24-48 hours to resolve this problem.

     

    Comment actions Permalink
  • Avatar
    Marc Thach Xuan Ky

    Me too, and today I upgraded to 3.6.3 and still no joy.  This is required for my Pulse Soundbar. My remote is for a Panasonic TV TX40EX700B.  Another remote is detected (but of course it's the TV remote that is required).  There is an article about previous versions having problems with Panasonic remotes but that was fixed.  Maybe it's been unfixed

    0
    Comment actions Permalink
  • Avatar
    Dalibor Zliechovec

    I do have 2 Panasonic TV remotes I used to use with PowerNode. 

    0
    Comment actions Permalink
  • Avatar
    Anders Gerlam

    I have updated my Pulse mini with the last update, and now the Panasonic remote do not work with the speakers via IR. 

    0
    Comment actions Permalink
  • Avatar
    Wesley P.

    Since the release of BluOS firmware 3.6.2 we have had other users come to us reporting similar issues with Panasonic IR remotes. We have passed this information along to our Quality Assurance team who are currently looking into this further to provide a fix as soon as possible.

    I am terribly sorry for this inconvenience but rest assured we are working to resolve this as soon as possible.

    Regards,
    Wesley P.

    0
    Comment actions Permalink
  • Avatar
    fabaut

    Same here. Please fix it...

    0
    Comment actions Permalink
  • Avatar
    Marc Eikens

    Same here with my Powernode with BluOs 3.6.3 and a Panasonic TV Remote control.

    Strange thing is that this also happened about a year ago (after upgrading to BluOs 2.18.0)

    (which was solved with an upgrade about one week later)

     

    0
    Comment actions Permalink
  • In all honesty Marc - it is a variation of the same problem as Panasonic Remotes have a different or unusual set of codes. When we released 2.18.0 and again this time, they were not included in a general library of IR codes at time of compiling our firmware.

    Not an excuse, just letting you know what happened. 

    Thanks for your patience. 

    0
    Comment actions Permalink
  • Avatar
    Andrew williams

    I too upgraded my powernode 2i yesterday and lost the use of my TV remote a Panasonic 49 700b tried all the usual things to no avail. Hope you can get it sorted soon thanks.

    0
    Comment actions Permalink
  • Avatar
    Marc Eikens

    Thanks Tony for your answer. Hopefully you can fix it soon.

    Just an idea : it could be helpful if we, as users, could easily "downgrade" our BluOs to a specific earlier version.

    That would also give you, as "bug fixers" more time to solve the issue in a more permanent way.

    Thanks again and have a nice weekend !

    I think I will survive without a remote control for the weekend :)

     

    1
    Comment actions Permalink
  • Avatar
    Per Ahlgren

    Same problem here. This is not the first time I have problem after update with panasonic remote.

    0
    Comment actions Permalink
  • Avatar
    Andrew williams

    I've got round this for now I've got a old remote non Panasonic which I've kept from a damaged dvd player used this works fine so going to use that till a fix is found for my Panasonic remote.

    0
    Comment actions Permalink
  • Avatar
    Gabriel Zecheru

    I'm having the same issue on 3.6.3, eagerly waiting for a fix as I have the PowerNode 2i conected to myTV and now it's a pain to use.

    0
    Comment actions Permalink
  • Avatar
    ML

    Same thing with my Powernode 2i, it stopped working with panasonic, Apple TV and cable provider remotes.

    0
    Comment actions Permalink
  • Avatar
    DanieLand

    I have exactly the same problem with my remote Atoll (node2i) since version 3.6.2 and version 3.6.3 did not solve the problem ...
    I hope the next release will fix this problem.

    0
    Comment actions Permalink
  • Hi DanieLand

    Quality Assurance is reviewing and testing a recommendation from Engineering with hopes of a fix early next week. We would push sooner but QA testing does take time to ensure it has no unanticipated side affects.

    0
    Comment actions Permalink
  • Avatar
    DanieLand

    no problem, take your time, the main thing is that it works well ...

    1
    Comment actions Permalink
  • Avatar
    Jussi Rämänen

    Hi! I also have a problem using the TV remote with Node 2i. I don’t have a Panasonic TV but an LG (55UJ750V). This problem seems to affect also LG TV users. I can use the TV remote with Node 2i when the TV is off but when the TV is on, the remote doesn’t work for e.g. controlling the volume of TV. I have connected my TV to Node using an optical cable. I really hope you fix this soon as it’s really annoying and inconvenient to have to separately adjust the TV volume using the BluOS app..

    0
    Comment actions Permalink
  • Avatar
    DanieLand

    Hello, I just update 3.6.6, my remote Atoll works again. Thanks to the developers

    1
    Comment actions Permalink
  • Thanks for your kind words, Daniel. I will pass them along to our team.

    0
    Comment actions Permalink
  • Avatar
    Anders Gerlam

    Hi,

     

    Now it works with my Panasonic Remote, Thanks Bluesound crew. 

    1
    Comment actions Permalink
  • Avatar
    Andrew williams

    All done thanks for the fix. 👍

    1
    Comment actions Permalink

Please sign in to leave a comment.