Glow IHD disconnects/reconnects from WiFi roughly every 10 mins

mtrmtr
in Glow IHD/CAD

While updating my Syslog server for my home network I noticed that for a very long time the Glow IHD has been following a pattern on connecting to WiFi and then disconnecting after about ten minutes and then shortly after reconnects.

I have four UniFi APs covering my home (channel overlap isn't an issue) and have tried moving it to another AP model and checked settings to ensure its not from the AP side and I cannot see any cause. The GlowIHD has an excellent signal as the nearest AP is in the same room and its the only 2.4Ghz device connecting to that AP.

Is this part of the firmware design?

Note: I did consider an Ethernet IHD recently but their dependency on online configuration was a showstopper for me.

Share on Twitter

Comments

  • coradiacoradia

    I’m seeing the same behaviour with my Glow IHD on UniFi.

    Over the last 48 hours, UniFi recorded 289 disconnections, almost exactly every 10 minutes, and it normally reconnected about 12 seconds later.

    This doesn’t look like a coverage or roaming problem in my case:

    • Signal stayed between −52 and −65 dBm
    • Wi-Fi satisfaction averaged 99.94%
    • It remained on the same AP and 2.4 GHz channel
    • Minimum RSSI, fast roaming and BSS transition are disabled
    • WPA group rekeying is disabled
    • DHCP lease time is 24 hours

    I found a potentially important second factor in my case. UniFi’s separate security-category content filter was blocking DNS requests to cce0ecf008d1.cad2.sensornet.info, which appears to be one of the IHD’s Hildebrand/Glow services. The separate Security Filtering policy includes more granular categories, such as Parked Domains, Empty Domains, DGA Domains, Unreachable Domains, Phishing, and Malware.

    UniFi identifies the Security Filtering policy as responsible for the blocked DNS request, although it doesn’t report which individual category matched.

    I had previously tried to allow the base domain in that security rule, but accidentally entered sensortnet.info instead of sensornet.info. I’m going to correct that and watch whether the ten-minute disconnection cycle stops.

    If it continues after the domain resolves normally, the extremely precise 600-second cadence would seem to point towards a Glow firmware timer or connectivity watchdog rather than an access-point problem. I’ll report back once I’ve tested the corrected exception.

    Share on Twitter
Sign In or Register to comment.