# Device naming question
**URL:** https://community.cambiumnetworks.com/t/device-naming-question/108787
**Category:** ePMP
**Created:** [September 2, 2026, 3:14pm UTC](https://community.cambiumnetworks.com/t/device-naming-question/108787 "2026-09-02T15:14:40Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@MiahSchaller](https://community.cambiumnetworks.com/u/MiahSchaller)
#### Post date: [September 2, 2026, 3:14pm UTC](https://community.cambiumnetworks.com/t/device-naming-question/108787/1 "2026-09-02T15:14:40Z")
> [@chain problems on 4 series](https://community.cambiumnetworks.com/t/chain-problems-on-4-series/108396/8):
>
> We had some problems with this and it ended up having to do with characters being used in the device name. We simplified things and it started displaying properly.
Just ran into this issue today and had to strip the `( )` out of the device name to get it to show up properly. Should be great fun to rename all of the SMs in our deployment that have those characters…
---
### Author:  [@aka](https://community.cambiumnetworks.com/u/aka)
#### Post date: [September 2, 2026, 5:28pm UTC](https://community.cambiumnetworks.com/t/device-naming-question/108787/2 "2026-09-02T17:28:19Z")
Hello @MiahSchaller,
could you tell more on which exactly issue you had? Which device and FW?
Thank you!
---
### Author:  [@MiahSchaller](https://community.cambiumnetworks.com/u/MiahSchaller)
#### Post date: [September 8, 2026, 5:09pm UTC](https://community.cambiumnetworks.com/t/device-naming-question/108787/4 "2026-09-08T17:09:46Z")
We had a 4600 that was running 5.10.4 firmware with two connected 4625 SMs on that same firmware. SMs and AP were updated to 5.11.0 and afterwards, the SM that had ( ) in the name reported the IP address as 0.0.0.0, Device Name as Unavailable and SM Distance as N/A similar to what mksistemi had noted in their images on their post. Rebooted the devices with no change. Saw the post from Eric Ozrelic later on in the thread about characters in the device name possibly causing an issue; after removing the ( ) from the name of the SM that did not report properly, it showed the proper information again.
Cant repost because the body is too similar to the post I deleted???
---
### Author:  [@aka](https://community.cambiumnetworks.com/u/aka)
#### Post date: [September 9, 2026, 12:21pm UTC](https://community.cambiumnetworks.com/t/device-naming-question/108787/5 "2026-09-09T12:21:30Z")
Hello @MiahSchaller ,
please give the full non working name example so I can try to reproduce it.
We had some fixed regarding hostname before but they are note related to brackets. It can be something else.
> [@MiahSchaller](#):
>
> Cant repost because the body is too similar to the post I deleted???
Unfortunately, the measures against bots and spammers can sometimes affect normal users. Once in a while it bumps me too…
---
### Author:  [@MiahSchaller](https://community.cambiumnetworks.com/u/MiahSchaller)
#### Post date: [September 9, 2026, 3:37pm UTC](https://community.cambiumnetworks.com/t/device-naming-question/108787/6 "2026-09-09T15:37:17Z")
Device name was **Conboy\_Michael(27843)**. Now named **Conboy 27843** and it shows up properly.
---
### Author:  [@aka](https://community.cambiumnetworks.com/u/aka)
#### Post date: [September 9, 2026, 6:25pm UTC](https://community.cambiumnetworks.com/t/device-naming-question/108787/7 "2026-09-09T18:25:19Z")
> [@MiahSchaller](#):
>
> Conboy\_Michael(27843)
Thanks — that clarifies it! This turns out to be a symptom of a broader issue, which has already been fixed in the 5.13.0 release.
---
### Author:  [@MiahSchaller](https://community.cambiumnetworks.com/u/MiahSchaller)
#### Post date: [September 11, 2026, 4:00pm UTC](https://community.cambiumnetworks.com/t/device-naming-question/108787/8 "2026-09-11T16:00:50Z")
Any more explanation? I don’t see anything related to a 5.13.0 release and 5.12.0 was just released.
---
### Author:  [@aka](https://community.cambiumnetworks.com/u/aka)
#### Post date: [September 15, 2026, 10:05am UTC](https://community.cambiumnetworks.com/t/device-naming-question/108787/9 "2026-09-15T10:05:30Z")
5.13.0 is in progress and may be released after 5.12.1, which is already published as beta.
Unfortunately, I can not provide any accurate ETA at the moment.
Thank you!