So to follow up,

For some odd reason, 1-11 now shows up on 2.4GHz in the software controller. This means I can use 1 and 11, the best channels in my locale right now.

For 5GHz, I am still limited to 2 channels for 80GHz when I should be able to select from 6 here in NZ.  I do not see a DFS option in the controller, is why I am missing those other channels?

@Fae why am I missing DFS?

I'm currently reverse-engineering the channel selections issue, somewhat slowed down by tp-link's attempt to obfuscate the java code.

The bold ones are available for me to select in the controller. The others are not exposed due to requiring DFS. Why does NZ region not have the DFS option available?

country:554
5180,30140,00,17,10,7
5200,50140,00,17,10,7
5220,30140,00,17,10,7
5240,50140,00,17,10,7
5260,30340,42,24,17,14
5280,50340,42,24,17,14
5300,30340,42,24,17,14
5320,50340,42,24,17,14
5500,30340,42,24,17,14
5520,50340,42,24,17,14
5540,30340,42,24,17,14
5560,50340,42,24,17,14
5580,30340,42,24,17,14
5600,50340,42,24,17,14
5620,30340,42,24,17,14
5640,50340,42,24,17,14
5660,30340,42,24,17,14
5680,50340,42,24,17,14
5700,30340,42,24,17,14
5720,50340,42,24,17,17
5745,30140,00,30,23,23
5765,50140,00,30,23,23
5785,30140,00,30,23,23
5805,50140,00,30,23,23
5825,10140,00,30,23,23

Now to map the file to the below function.

 private static List<RegionWireParam> a(Integer var0) {
      ArrayList var1 = new ArrayList();
      InputStream var2 = b.class.getResourceAsStream("/region/REG_DOMAIN5.region");
      if (var2 == null) {
         a.error("Failed to load REGION_5G_FILE");
         return var1;
      } else {
         BufferedReader var3 = null;
         InputStreamReader var4 = null;

         Object var6;
         try {
            var4 = new InputStreamReader(var2, "UTF-8");
            var3 = new BufferedReader(var4);
            String var5 = "";
            int var27 = 0;

            label174:
            while((var5 = var3.readLine()) != null) {
               String var7 = "country:" + var0;
               if (var5.lastIndexOf(var7) >= 0) {
                  String[] var8;
                  if (var5.lastIndexOf("empty") > 0) {
                     var8 = null;
                     return var8;
                  }

                  while(true) {
                     if ((var5 = var3.readLine()) == null || var5.lastIndexOf(":") >= 0) {
                        break label174;
                     }

                     var8 = var5.split(",");
                     ++var27;
                     int var9 = Integer.parseInt(var8[0]);
                     RegionWireParam var10 = new RegionWireParam();
                     var10.setChannelName(a(var9) + " / " + var9 + "MHz");
                     var10.setMaxTxPower(Integer.valueOf(var8[3]));
                     var10.setSupport40(b(Integer.parseInt(var8[1], 16)));
                     var10.setValue(var27);
                     var10.setFr(var9);
                     var10.setcFlag(Integer.parseInt(var8[1], 16));
                     var10.setdFlag(Integer.parseInt(var8[2], 16));
                     var1.add(var10);
                  }
               }
            }

Digging deeper, it seems that on rebooting the AP it states to the controller it's a USA model, how do I fix this?

It also says it doesn't support DFS, I guess that is why the option for DFS in the controller is not visible.

NOTE : Region 841 is USA.

2021-10-18 00:06:48 [discovery-handler-pool-1] [INFO]-[SourceFile:126] - May be invalid upTime for mac E8-48-B8-B3-26-32, oldUpTime 0 days 00:08:14, reportedUpTime 0 days 00:01:20, discoveryMsg EapDiscoveryBody(deviceInfo=com.tplink.omada.device.message.discovery.eap.EapDiscoveryDeviceInfo@1829495[name=EAP245-E8-48-B8-B3-26-32,model=EAP245,modelVersion=3.0,firmwareVersion=5.0.3 Build 20210604 Rel. 51934,hardwareVersion=3.0,specialModel=<null>,upTime=0 days 00:01:20,ip=192.168.93.67,cpuUtil=0,memUtil=42,wirelessLinked=false,factory=false,additionalProperties={txRate=1152, rxRate=864, mask=255.255.255.0}], deviceMisc=com.tplink.omada.device.message.discovery.eap.EapDeviceMisc@3659af[support5g=true,support11ac=true,supportLag=false,supportMesh=1,customizeRegion=841,minPower2G=6,maxPower2G=24,minPower5G=6,maxPower5G=24,supportChannelLimit=<null>,channelLimitMode=<null>,supportDfs=0,lanPortsNum=<null>,lanVlanPorts=<null>,lanPoePorts=<null>,supportRoaming=1,additionalProperties={maxTxPower=0}], controllerSetting=com.tplink.omada.device.message.discovery.eap.EapDiscoveryControllerSetting@a57be5[controllerId=90f93dc254d8ff7dd92e7e76c07f624d,additionalProperties={}])

@Fae some assistance required, please.

Hmm, so it seems NZ directs you to AU site and this offers the US firmware, has my device now been locked to US region, how to change it?

Thanks,

WelshWizards

Well not good news, had a chat with support it seems they are locked to US version. 

I have reached out to local support/sales here in NZ/AU to give them a change, else they will be going back as not fit for purpose.

Anyone else experiencing this issue here?

Hi @Fae 

Well this is not the confirmation I wanted. I really don't get why tp-link would do this. Very much shortsighted behavior, NZ is not USA.

I now have to return my AP's and switch to my supplier and buy something that just works, what a pain.

Suffice to say I will not be entering the tp-link ecosystem for managed WiFi or switches now, in no way can you describe the EAP245 v3 as SMB grade equipment.

Regards,

WelshWizards

@Fae 

So further investigation shows that this is an artificial limitation in your firmware, I am running OpenWRT on it and can see the missing channels.

Now its time to dig deeper, no warranty void sticker to stop you from opening this device up, which is nice

Below is the Serial port header,

There are two sets of Pads that need to be bridged

R237 to be bridged

Bridge R225 (hidden under the can on the rear of the board)

Ew, this board wasn't cleaned well after being made, leftover flux can be seen.

The aim of the game is to depersonalise this board, make it forget all about the USA.

So to Follow up,

It is possible to change your US region locked device back into the EU region,  and this opens up the DFS channels that should be available in NZ.

MTD3 partition holds the information that determines the region/country code. I will be working on a method to automate this.

@WelshWizards 

Any luck on this? If you bridge them, as you posted above, what will happen? I AM SO CURIOUS ABOUT THIS.

@John1234 

Sorry John, what do you mean by bridge them?

@WelshWizards 

Do you need to solder them together and run something to enable the missing (DFS) channels?? Your previously posted pictures