PumpUpVolume

Certainly there are indications that the NEEO is defective. The counterargument would be that doesn't make sense since the problem is made to go away by rebooting the WiFi access point. Rebooting the router doesn't fix the problem; rebooting the NEEO doesn't fix the problem; rebooting the WiFi access point, however, does make the problem go a way for 10 days or so. What I find so puzzling is why does only device/client stop working and no other devices are impacted but rebooting the access point fixes the issue. I can't even come up with a theory as to the root cause of the issue. It is a bit difficult to conceive how a defective radio in the NEEO manifests as a connectivity problem after ~10 days of use, rebooting the NEEO doesn't fix the issue, but rebooting the WiFi access point does.

I am updating this thread to note that changing the WAP 2.4 GHz channel and lengthening the guard interval on the WAP did not solve the issue. The same bad behaviour has returned. I reboot all devices and then it works fine for a period of time, but then it reverts to all the same problems ("please wait", spinning wheel, "cannot connect to network", etc). The most characteristic aspect of this problem is that it works smoothly for a period of time and then suddenly starts exhibiting issues. Once it starts exhibiting issues, the issues persist until everything is rebooted.

Answering my own question here --> Yes, it does: "and Wi-Fi 2.4 and 5GHz support with an advanced antenna array with up to 5 times stronger signal." https://www.control4.com/solutions/products/remotes/ That sounds like the answer to my woes.

Does anyone know whether the WiFi chip in the Halo has a 5 GHz radio? That would be sweet.

Will the Halo sport a better WiFi chip?

It is interesting to note that the MAC on my NEEO starts with 4C:24, which is similar to the middle one in your list above. That is, the MAC in my NEEO aligns with the one in your group that doesn't work as well. This could be random coincidence, but it does support your hypothesis that there might be two pools of WiFi chips with one pool being problematic. I'm not going to jump to any conclusions, but at the very least it is an interesting coincidence.

As indicated previously, I will conduct a new WiFi site survey as soon as I can obtain a notebook PC; I presently have access/use of several computers, but they are all either desktops or they are locked down such that I can't install a sniffer app. I have only one NEEO and only one 2.4 GHz radio in the house, so I don't have the option to try swapping between rooms, etc. This is one remote, one WAP environment. I can say for certain that the issue is not something like microwave oven interference in our case. The problem is present when the microwave is not in use. When our NEEO stops responding properly it stays in that state for hours, days, or weeks at a time. I'm never quite sure what gets it working again, but is not simply some intermittent interference issue. That would not explain that observed pattern. If it is an interference issue, the source of the interference must be something that operates pretty continuously over periods of days, which does not include a microwave oven. Our cordless phones do not use the 2.4GHz band; we have a single model of cordless phone in the house and it is the 5 GHz type. We don't have any other remote systems in the house and certainly not ones used on any continuous basis. If there is an interference issue, about the only practical source of such would be the neighboring houses on either of two sides; that is a valid possibility. At the moment, I've got my fingers crossed that the root cause of the problem was having the WAP on channel 3 and there was cross-channel interference from the WiFi in the neighbors house. Evidently, I will get more insight into this when I can conduct a site survey - I'm looking into borrowing a notebook to do this. I know what needs to be done - I have conducted site surveys before - I just don't presently have a notebook computer I can use for this purpose. The NEEO has responded well since I got the WAP reconfigured to a standard channel and extended the guard interval. I'm not celebrating yet, however, as sometimes the problem goes dormant for days or even weeks.

Well, there may be more than one issue in play, but in my case I only have a single 2.4GHz radio in the house and the NEEO can't stay connected to it and/or there is signal interference. The WAP is located within feet of where the NEEO is used. I do understand that cross channel interference is a bigger problem that co-channel interference, so maybe moving from channel 3 to channel 6 will be a solution for me, but too early to tell at this point.

That is interesting given that someone else commented that they simply couldn't get the NEEO to work with ubiquiti products. I wonder what the difference is between the configurations?

I explored the DMZ approach in great detail at one point and hit a wall. I'd need to go back to my notes to confirm, but I think the issue I ran into is this... The connection to the ISP is currently negotiated by the Home Hub 3000. I cannot see the account name and password that it uses to negotiate the connection with the ISP. I think that the ISP recognized some hard programmed identifier in the Home Hub 3000 - there is no place where an account and password is visible or can be entered; however that works is entirely hidden. If I set up another router in the DMZ then I need to have the credentials to negotiate the WAN connection to the ISP. My ISP refuses to give those credentials to me. I did find instructions on how to get this information for the Home Hub 3000 if you have device issued by Bell in Ontario. However, the Home Hub 3000 issued is Manitoba is different hardware and different firmware and none of the Ontario instructions apply to the Manitoba configuration. I have not been able to find a Manitoba version of those instructions. Thus, I hit the wall because I was unsuccessful at figuring out the login credentials. I did manage to talk to an empathic tech at Bell MTS who said to me "look, I can see you have a good technical understanding and I am confident that you will figure out how to make the connection if you plug away at it long enough. I'm prohibited from telling you how to do it, but you can probably eventually figure out on your own. However, I'm cautioning you, you will have other other problems and when you call us we will be able to see what you've done and we won't support you until you set your router back to the default configuration. We have other customers that have attempted the DMZ approach and they all have problems and we won't provide support to fix those problems." At that point I flew the white flag on the idea of a DMZ approach. If anyone on the forum knows how to set up the DMZ on a MB Bell MTS Home Hub 3000 and obtain the correct login credential, I'm interested in that information. In full candour, I doubt this is a router issue. It might be a WAP issue. I'm not about to invest energy into inserting a second router unless there is reason to believe that it is a router issue. Keep in mind, traffic between my NEEO and the EA3 processor does NOT travel through the router. That traffic goes from the NEEO --> WAP --> Smart Switch --> EA3 Processor (and the reverse). The router is the least involved actor. My router does NAT and WAN and not much more. I'm not using the radios on the router and on the LAN side there is basically a single gig line to the switch.

I did a site survey with inSSIDer when I originally installed the network, but that was a long ago and much could have changed. The only reason why I have repeated that recently is all the computers I own are desktop units, which are, for obvious reasons, a poor tool for conducting a WiFi survey. I'm working at borrowing or buying a notebook so that I can do another site survey. I know what needs to be done, I just lack the required hardware tool at the moment.

The system is now running with the modified setting: Channel 6 (fixed) 20 MHz channel width (unchanged) Guard interval = long - 800 ns Full output power (unchanged, but fixed, not modulating) so, the only real changes are channel from 3 --> 6 and Guard Interval from auto --> long - 800 ns Both the WAP and the NEEO have been rebooted and for now the NEEO is behaving. Now let's wait and see whether these changes have made a difference. I wish I had documented changes I made previously because the channel may have been set up this way previously; it might have been switched to 3 in an effort to solve the problem.

I ran tests with three channels using my iPhone and OOKLA. Here are the results: Channel 1: 52 Mbps Channel 6: 60 Mbps Channel 11: 40 Mbps

OK... I just noticed that the WAP didn't take the settings changer earlier. I've re-changed the settings and am retesting. Will post again when I've been able to test the NEEO. The SkyBell still streams with the new settings. I also need to make a correction to one thing I said before. My phone was on the 5.2 network when I ran the OOKLA test before. On channel 11 I get only 40 MBPS once I force the phone to the 2.4 network.

Also note that my location is not very polluted from neighbouring access WAPs. My iPhone shows my two networks (2.4 & 5.2) and one other network. Sometimes others will appear briefly, but there are only two houses that are within proximity to really have the potential to cause an issue. And I don't see any issues.

The radios that are built into the Bell MTS Home Hub are turned OFF (as previously noted). The Home Hub sits utility room. My WAP is perfectly centrally located and in very close proximity to where the NEEO is used. I can try a different channel, but that seems counterintuitive given that my SkyBell streams video on the current channel and the SkyBell is located outdoors, furthest from the WAP720. If any device were prone to have an issue with the WiFi signal, it would be the SkyBell.

And, I see this spinning wheel all the time - it often stays present for long pauses like 10 - 15 seconds before something else happens

I also get a "Loading Error" frequently; see attached.

Another one of the errors that I see is "Page Error". See attached screen shot of a "Page Error" after changing the WAP settings and rebooting both the WAP and the NEEO.

This is all that I see on the NEEO setting screen - there is nothing about WiFi sleep mode...

I first rebooted the radio and then I rebooted the NEEO.

And, yes, I did reboot the WAP and then the NEEO after changing settings.

Oh, and putting my ISP router into bridge mode is complicated... and the moment I do, my ISP won't support me if anything goes wrong with my IP TV, which does happen occasionally. So, going to bridge mode on the ISP router is not a practical option as it just opens up a bigger can of pain. Also, note that I don't have the common Bell Home Hub 3000 which is deployed in Ontario. I have Manitoba one which has different firmware and features. All the documentation posted online for jailbreaking the Home Hub 3000 applies to the Ontario one and not the MB one.

Changing to these settings did not work. The NEEO is presenting huge lag with the new settings. Other devices still work fine. Can still stream video from my SkyBell and still get >250MBPS through the WAP to the ISP. All devices work great except the NEEO, which is terrible.

I see only two settings that are changeable: 1) Beep when docked; 2) Adaptive Brightness. There is no setting for WiFi sleep. I'm not deploying a multi AP network for the foreseeable future. I'll deal with that issue when I get to it. My short term goal is to solve the NEEO issue.