RouterBOARD naming... not consistent!

Hi all,

We use an in-house App for provisioning CPEs, currently the hAP Lite model (RB941-2nD-TC). The App first identifies the device it’s connecting to, to make sure we don’t try to provision say an RB951 with the config parameters for the hAP Lite.

We have found a discrepancy in what is returned by /system routerboard print for EXACTLY the same device model, hardware appearance, etc.

In one case, it returns:

[admin@661806F7260F] > /system routerboard print
       routerboard: yes
        board-name: hAP lite
             model: RouterBOARD 941-2nD
     serial-number: 661806F7260F
     firmware-type: qca9531L
  factory-firmware: 3.33
  current-firmware: 3.33
  upgrade-firmware: 6.43.7

In another, it returns:

[admin@9D76095754E9] > /system routerboard print
       routerboard: yes
        board-name: hAP lite
             model: RB941-2nD
     serial-number: 9D76095754E9
     firmware-type: qca9531L
  factory-firmware: 6.42.1
  current-firmware: 6.43.5
  upgrade-firmware: 6.43.7

Is there a reason for this? We can account for it but we want to know if we have to expect random naming (and I have read the “how do we name stuff” thread and Wiki entry!)

The model name is probably baked in the routerboot (firmware). Upgrade it on the first device

/system routerboard upgrade

and reboot the device.

Have done so, model name remains the same. I thought it may have been in the firmware where v3.x had “old” naming and 4.x “new” based on RBxxxx, but looks to be fully baked in.

Afaik there is no way to change it. Other models like hap ac2 are similarly affected.

Not wanting to change it, just have a consistent way of identifying a router model over SSH, without complicated regex…