Mobile App

I'm trying to diagnose why all my wifi networks are showing poor health. I've yet to find documentation on health (outside of Site health), to help me understand what factors are causing poor network health.  I am using web management, not local management. Would off-line devices contribute to this health?

I've been experiencing "internet unstable" issues in apps like Zoom on wifi connected devices, which is the real symptom I'm trying to diagnose. My internet is 1 gigabit up/down, and using internet speed test I'm getting 500megabit up/down. I've also yet to find any sort of logs which could help further further diagnose issues.

Can anyone help?

Update - so I was able to deduce that the Fair/Poor health status was due to 2 APs which were down due to testing. It would be really helpful to have any sort of documentation where ever a health status is used, as in what metrics or contribute to health status (site, network, etc), in the case of network health, clients with poor attenuation.

The lack of any discernable logging here is a huge miss for Aruba IO as well. Why isn't something working with my device/network/client? Who knows?

I am closing in on 100% and can share a few things I've learned.

1. Check your network address space. My IOT network was not within the RFC1918 specifications. There may have been an IOT device trying to reach an Internet IP address that was getting caught in my own network. I'm not sure if I accidentally changed the octet or it was chosen automatically when I created the network, but it was outside of RFC1918.
2. Don't use 0 as any octet. Cisco started doing this in the 1980s and as far as I'm concerned it should be avoided. Especially when dealing with IOT networks since you're already dealing with poor drivers and such requiring you to be as legacy as possible. There is no reason anyone NEEDS to use 0, so do yourself a favor and avoid it. e.g. 192.168.0.X bad, 192.168.1.X good; 172.16.0.X bad, 172.16.1.X good; 10.0.0.X bad, 10.1.1.X good.
3. IOT devices are a problem. Create IOT2 2 GHz and IOT5 SSIDs if your devices don't behave properly on a combination SSID. (Frankly just create separate and save yourself the headache, for IOTs that is.) Use 5 GHz if possible because it's less crowded/handles conflicts better. Upgrade or replace your old tech if possible. I finally gave up my on my two sprinkler controllers after reading all the Reddit comments and getting no acknowledgement from the manufacturer that their WiFi capabilities are awful (Hunter Industries X2 + WAND cartridge and only supports 2 GHz.) One was in the garage where I have an AP25 mounted on the ceiling in line of sight, and the other was outdoors where I have an AP27 in line of sight. My AP27s are Ethernet connected.) I swapped out the garage controller with a Rachio 3 and it's solid. I just put it on IOT5. Today I'm replacing the outdoor one. Unfortunately they're not outdoor rated but Rachio sells an outdoor enclosure that you can hardwire or add a pigtail power cord (which is what I've done).
4. If you have multiple APs - I have 5 indoor and 2 outdoor - manually set the radio channels and lock the min/max radio power settings accordingly. I don''t have any information about what HPE does with this to lead me to trust it. I want full control, in absence of any information.

Bullets 1 and 2 alone boosted my health rating several points. I have about 15 CR2032 cell battery water leak detector IOT devices that come and go to conserve battery life. It would be good if the portal had a way to flag IOT devices like this so they don't impact the health scores at all or less. I am confident that after today my health score will be 100% if none of my water leak detectors were recently seen.

I hope this helps!

P.S. Looks like the portal has been updated, the app has been updated, and new firmware is available.

Yes, offline contributes.

Logs would be a huge help! I have asked them for this. We should all ask for this! I'd be happy with 24 hours, even less would be helpful!

Aruba/HPE - do yourself a favor and provide customers with tools to access diagnostic information so that we don't drive up your cost of doing business by creating support cases. You are not selling a consumer product at Best Buy. I would bet money that a good portion of your customer base are sophiscated enough to look to solve problems on their own before contacting you. So provide more technical information in the product with corresponding documentation to help explain it. How about some technical videos, too. Have a look at Firewalla. These guys have excellent documentation and videos. They also have very responsive email support.

^ This ^