Skip to content
HearingTracker
Log in

Phonak Audeo Lumity L90-R region update

This topic is closed.

11 replies1.3k viewsLast reply

Link to this topic
Edited

Ok, some things have changed, and here are some people who helped me :slight_smile:
I have a pair of Phonak Audeo Lumity L90-R, firmware 1.0.5.0. The origin is a Nordic country, Norway.
I also need to put my settings on them, changing language to english, even if now I use them occasionally with the help of manual settings in the my Phonak application.
But it seems that Phonak limits access to programming in my country, my audiologist not being able to connect them to Target, not even after the help requested from the IT department, all legal, obviously. The message contained something like “a software update is needed to be able to start connecting”
So I have to buy the Hardware with my own money.
At the moment, I found a used Noahlink wireless on ebay for a pretty good price, but the seller still hasn’t confirmed which model it is.
Then, on aliexpress I have a very good offer of a new Noahlink wireless device, but I don’t know how I will register the product, especially for support or the eventual warranty.
I have some doubts and maybe you can help me, enlighten me.
First: are the devices connected to Target checked in the Phonak database and blocked if they are not from the specific region? Is this blocking only on the respective connection, temporary, or can it be permanent?
Two: when I connect to my device, will I be able to upload the received from my audiologist without the need to connect to the Internet?
Three: How do I identify the generation of the Noahlink device? As I understood that this year Himsa has a new Noahlink model, but I don’t know what product code it is. The one on aliexpress looks like this: HIMSA II K/S, model CPD-1 and date of manufacture 15.04.2022.
14

4 people in this conversation6 min readJump to latest
@CoS said:

But it seems that Phonak limits access to programming in my country, my audiologist not being able to connect them to Target

It’s not possible to block as such, your Audiologist doesn’t know/how to use target.
Doesn’t matter what country you brought them in.

@CoS said:

The message contained something like “a software update is needed to be able to start connecting”

Yes so if your were programmed in a later version of target then you need to use that version or later, your Audiologist should of known this, a very simple update using targets built-in updater would have solved your issue.

@CoS said:

At the moment, I found a used Noahlink wireless on ebay for a pretty good price, but the seller still hasn’t confirmed which model it is.

Doesn’t matter, if it’s a Noahlink wireless programming device it’ll work on your HAs, you don’t want a NOAHlink! Be careful with the wording.

This is the one you want.

https://www.himsa.com/products/noahlink-wireless/27

@CoS said:

but I don’t know how I will register the product, especially for support or the eventual warranty

You do not need or want to bother with this, just use it, Noahlink wireless is plug and play.

@CoS said:

First: are the devices connected to Target checked in the Phonak database and blocked if they are not from the specific region?

Definitely not, it doesn’t matter if you buy from USA the UK or AUS the Noahlink wireless programming device will work.

@CoS said:

Two: when I connect to my device, will I be able to upload the audiogram received from my audiologist without the need to connect to the Internet?

Yes absolutely no problem, it’s stored in the HAs chip. No internet needed.

@CoS said:

Three: How do I identify the generation of the Noahlink device? As I understood that this year Himsa has a new Noahlink model

No need to worry about this, the newer model will be backwards compatible, the latest version is NOT going obsolete.

Again this is the one.

https://www.himsa.com/products/noahlink-wireless/

@tenkan said:

Yes so if your HAs were programmed in a later version of target then you need to use that version or later, your Audiologist should of known this, a very simple update using targets built-in updater would have solved your issue.

It’s getting very interesting, thank you!
After you helped me with the Target, I played a little with it and noticed what upgrade or update means.
From what I observed during the connection, only the device on the right HE succeeded in connecting, the other one not being recognized, later without success for both HE.
He definitely had the latest version of Target installed, 8.1.2, but at one point, I saw that even version 7 was running.
Since I didn’t anticipate what was coming, I didn’t think to keep a lot of details, but being quite skilled in the way software works, I saw that the Target was launched separately, from the desktop, but also from the software NOAH (am I right?), or from there the “associated” Target is launched, in her case it is Target 8.1.2.
Finally, having all kinds of software on the laptop desktop, so different, it would be difficult for me to say very precisely.
I will talk to her (my Audi) about this aspect and find out how to identify the software variant with which the devices were programmed, to make another attempt next week.
Probably is need for a Target version downgrade.
She is a very good audiologist, but she doesn’t seem to have knowledge of these things, which is a bit unpleasant, but she should understand and be explained at the company training, being even a big one in the country, with national coverage.
In addition, I understood from the audiologist that I do not have to pay for the import of some settings from the current Bolero/Naida devices and the settings inherent in the Lumity family

@tenkan said:

Doesn’t matter, if it’s a Noahlink wireless programming device it’ll work on your HAs, you don’t want a NOAHlink! Be careful with the wording.
This is the one you want.
Noahlink Wireless – HIMSA

No, I’m just referring to Noahlink wireless programming device only.

I will leave the discussion open until I solve the case.
Thank you for the pertinence of the statements, warnings and the tip with the Traget variant for HE update.

@CoS said:

From what I observed during the connection, only the device on the right HE succeeded in connecting, the other one not being recognized, later without success for both HE.

To get connected you have to press the button I believe on your .

For me, I have to open and close the battery doors as I have disposable.

Sometimes both or one will connect without doing that. If they don’t connect, the Audi will have to follow what on the screen to get them to connect.

@Zebras said:

Sometimes both or one will connect without doing that. If they don’t connect, the Audi will have to follow what on the screen to get them to connect.

Hmm… Good point…
I remembered that she stopped/started them only once, with the same error message.

Yeah that pairing mode is only 2 to 3mim as well ! Unbelievable they wouldn’t know this?

I’ve bought hearing aids from USA, Spain, Australia, Switzerland and New Zealand and have never had an issue when programming.

I wonder if factory resetting then would work? It may not but that’s how I start before I program my .

For Luminty at least Target version 8 is needed.

  • Target 8.0.1 were the first version, released Q3/2022
    first update
  • Target 8.1.0 , released 4/2023
    this got an additional minor update
  • Target 8.1.0.944 , released 5/2023
    then a minor bug fix update
  • Target 8.1.1. , released Q2/2023
    the latest is
  • Target 8.1.2.1196

Normaly you should be able to programm Lumity regardless of the Target 8 version

Not.
The audiologist is in a different city than my home and I have my job in another location, a triangle, so it is more difficult to travel.
For now, I will contact him by phone in the following days, depending on his availability.
Until then, I’m staying on the Naida/Bolero pair.
I have enough patience.
Thank you for your interest :slight_smile:

Bad news. Very bad news.
It seems that @tenkan somehow “felt” things and on Tuesday morning I actually found out why there is some non-involvement and avoidance of solving the problem.
This is because I had learned about the connection and solution options and I had decided to contact the audiologist for a later session, but I was called and warned that any attempt to schedule me would be refused!!!
I tried to close the discussions definitively, still requesting to receive the settings for the initial devices in pdf format by email, but I was met with another, aggressive refusal.
The rights of the company over the is invoked, without taking into account that there would be no audiogram without the patient. But I will be careful to make complaints where necessary for abuse of position.
In the meantime, I found a company that accepted this for a fee, on Wednesday. I had a rather tiring journey, and I went through the “hard forks” of testing from scratch for tonal, vocal audiogram, impedancemetry, etc…
And the settings were made very quickly and then exported to my email.
So it is possible!
What I didn’t like is that experience in the profession of audiologist is essential for a good result, being able to use the knowledge to the maximum to make a less performing device give everything it needs.
It’s just that, in my case, I have to wait a little longer and go to an additional adjustment, because I wasn’t as lucky with this.
All the fun? 50 Euros.
That’s it for now.

Related discussions