cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Unable to determine connection band and signal strength for some devices

SIGHUP
Contributor
Contributor

There are multiple devices connected to my WiFi Extender running firmware version r5.16.1-R-2011329-PROD-1

For some devices I am able to see the band (2.4GHz, 6GHz or whatever) and also the signal strength (dBm).

I attach 2 images. They show one device where the band and signal strength are given and another where these data are absent.

Why would some devices show these statistics and others not?

Screenshot 2026-10-07 at 17.49.11.pngScreenshot 2026-10-07 at 17.48.55.png

8 REPLIES 8
JimM11
Maestro
Maestro

@SIGHUP Where is the device connected too, the Hub or the Extender?

The extender (as per the first sentence in my question)

@SIGHUP If you take the MacBook Air down to the EE Hub is it still the same with N/A?

I'm not going to do that because that's not what my question is about. I want to know why it shows n/a for both metrics when connected to the extender

I imagine N/A means exactly that - the data isn't available.

I'd be surprised if it's intended and doubt it has anything much to do with the device in question. It suggests the hub is either struggling/timing out when trying to retrieve the data, or the data is completely missing for some reason. FWIW, I've seen the same myself on occasion.

@SIGHUP - does the problem exist when checking the new Beta view?

@SIGHUP OK no problem.👍

I wonder if it's possible to get a definitive answer to this.

It seems odd to me that the data are (apparently) unavailable for just one of the connected devices (there are 7 at the time of reporting this issue). 

Worth emphasising that there are 2 MacBooks connected to the extender but only one of them reports n/a for these two interesting statistics.

@SIGHUP - did you check to see if the behaviour is the same in both Hub Manager views (current and Beta)? Is there any change to the behaviour if/when the hub and extender are restarted?

If your findings are anything like mine then the issue doesn't tend to be persistent and I'm fairly certain it's not always the same devices I notice it happening with.