Hi there,

I'm running the latest early release of Omada controller on a Linux box.

I just want to report the fact that adopting an EAP115-Wall with latest available firmware (5.0.4 Build 20220216 Rel. 57495) breaks the beta firmware (check) feature.

After digging a little, I can provide with some information :

- Symptom is : The "Firmware beta" screens are not populated and the message "Something went wrong. Please try again later or contact our technical support." is raised.

- The server.log shows the following error : "c.t.s.o.m.c.d(): get GetTargetFirmware failed, omadacid:3aac9ec5412072656021d3e662f6932b, response:{"msg":"Parameter is invalid: hwId is blank","error_code":-20107}"

- Looking at the associated ~json request, it looks like EAP115-Wall reports with an incompatible hwId format :

hwId=v2#Z4zMrjCOxidl6ectwT6vvA==,
      compoundModel=EAP115-Wall(EU) v1.0,
      showModel=EAP115-Wall(EU) v1.0,
      version=5.0.4,
      firmwareVersion=5.0.4 Build 20220216 Rel. 57495,

compared to

hwId=v2#o0slmG0toGnWMKzQiwGcVNYNFLCuffAueJkTXK+X4AQMMQRPn3vhZNxZIsFeYJns,
      compoundModel=EAP230-Wall(EU) v1.0,
      showModel=EAP230-Wall(EU) v1.0,
      version=3.2.3,
      firmwareVersion=3.2.3 Build 20240815 Rel. 33684,

- Forgetting the EAP115-Wall make the "Firmware beta" feature to work again.

I know the feature is in beta and I don't know wether this is a known issue/limitation or not.

However, I would like to know if :

- whether a fix will appear in an upcoming release of the controller ?

- or a new EAP115-wall firmware will fix this incompatibility (as far as I know I'm running the latest) ?

- or this will be considered as a known limitation (due to EAP115-wall being considered more or less EOL)?.

Regards.