PumpUpVolume

I don't have a device handy that I can use for a site survey, so I'll try channel 11 for now and plan to do another site survey asap. I don't believe I have any 11 b devices, so I'll try 11ng; I suppose if I have a b device, I'll discover that quickly enough as it will stop working with the new settings. Power level is a set level. It is set to full. That is not a modulating level. The only other options are half, quarter, eighth, minimum. I've attached a screenshot of the new settings.

I only have one (1) WAP at this time (plan to add one or two more in the future, but only need one now), so no option to block NEEO on other WAPs. How do I disable "sleep mode"? I haven't put a router behind the ISP router because it forces double NAT, which I'd prefer to avoid.

See the attached screenshot for current radio configuration settings. You can see that it is already set to a 20mHz bandwidth. Are there any other settings you recommend checking or changing? The screenshot shows the configuration that has been in place for months - with terrible performance from the NEEO.

Also note that another member said (above), "we couldn’t get them to work at all with ubiquiti"; you seem to have had a different experience with ubiquiti.

I am not blocking anything on the WiFi network. I am not using multicast filtering. Router is supplied by ISP and is in minimal/default configuration with all radios turned OFF. The router is the very widely deployed Bell Home Hub 3000. Netgear Prosafe 28PT GE POE SmartSwitch is pretty much out of the box configuration; nothing fancy going on here... it's pretty much running as an unmanaged switch. Netgear Prosafe WAC720 access point is also minimal configuration with unique SSID for each 2.4 and 5.2 GHz bands. These are the only two access point radios active in the house. Nothing fancy going on here either. If I run a speedtest to my ISP through all devices (access point, switch, and router) using OOKLA from an iPhone I get a consistent 250 - 300 MBPS from much further away than where the NEEO is used. I have ~20 devices on the network, but most are connected by ethernet; there is only very light use of the WiFi netwok in the house as all high demand end points have ethernet connections. The rest of the 20 devices perform flawlessly. The NEEO is a nightmare. Thoughts and ideas are welcome and invited !

Your description of what happens with a dedicated 2.4GHz SSID perfectly describes my current state. It doesn't sound a like a good investment to add a parallel network only to experience more of the same.

I have unique SSIDs for each of my channels. I do not have a common SSID for the two bands. There is only one 2.4GHz access point and one 2.4 GHz SSID in my house and that is what the NEEO uses. I do have a 5.2 GHz access point, but it has a different/unique SSID.

I got the same advice - to make sure it is in 2.4 GHz. The NEEO doesn't have a 5.2 GHz radio, so what else would it be on? Seriously. I have a RSSI of -41 db (as reported by NEEO in the Settings section), which is laboratory perfect conditions for a WiFi connection. It is not a weak connection issue; something else is going on.

That does sound like a very similar if not identical scenario. I have very similar proximity to my WiFi access point (with -41 RSSI, which is stellar) and if I speed test my WiFi when the NEEO is acting up, I get ~300Mbps on an iphone standing further away. I also experience the spurts/periodic issues. It can work OK for a period of time and then it works badly for a period of time and then get to the point where it barely works or doesn't work at all. Have you tried seeking a resolution through the Control4 Customer Advocacy service?

The NEEO firmware version is 1.71.3-30626811. Is that the current version? The Netgear WAC720 access point supports one SSID for 2.4 GHz and one SSID for 5.2 GHz (there are unique SSIDs for each band and it is the only operating access point in the home right now). I would need to install another access point immediately adjacent to the existing one to add an SSID. That is not an ideal scenario from a bandwidth conflict management perspective. Why would I need a dedicated SSID for the NEEO; the access point is currently serving a dozen or so devices between the two frequencies... it should be able to handle a much greater number.

I have had a NEEO remote for approximately a year, when it was supplied with a new EA3 processor and system installation. Since new, we have continuously experienced network connectivity issues between the NEEO and the Control4 EA3 processor. The connectivity issues present as lag (e.g. 2 second), spinning wheel, and a couple of errors including the one shown in the attached screen shot. Our NEEO remote is used in very close proximity to a high quality, business class WiFi access point (Netgear Prosafe WAC720). Signal strength is stellar (RSSI reported by the NEEO is -47) and I don't experience connectivity or throughput issues with any other devices connected through the access point; in fact, I have stellar network performance with other devices. The network is configured with Cat6 wiring and a gig switch (Netgear 28PT GE POE Smart Switch). The EA3 is connected by ethernet to Netgear Prosafe switch. When the NEEO remote acts up, I have tried various things to get it temporarily working again, including rebooting the NEEO, the WiFi access point, and the EA3 processor. At times, each of those have seemed to work temporarily, but that might be just coincidence because sometimes waiting a brief period of time caused the problem to temporarily resolve itself. We get all sorts of weird behaviour on the NEEO. For example, right now I'm trying to enter the "Settings" screen. when I click Settings, I get the spinning wheel for 30 seconds and then it goes back to same menu I started with. Click settings again, spinning wheel for 30 second and back to the same menu I started with. But, do this four times and on the fourth attempt it actually goes into settings. I would appreciate any insight or suggestions as to how to get the NEEO working such that it provides a decent user experience. As presently working, it is a terrible user experience.

I have confirmed that there is a viable workaround for this issue. If one switches the "Simple IP Control" setting on the TV to ON - without making any changes in Control4 (i.e. leave C4 configured for Web API), it will prevent the TV from dropping the ethernet connection. The working theory is that the ethernet network adapter in the TV has a Wake On LAN issue when put in the low power state associated with "Simple IP Control" switched to OFF (and TV is powered OFF). The implication of switching "Simple IP Control" to ON is the TV will consume a bit more power when the TV is powered off because the network adapters are left in a higher power state than with that setting in the OFF position. Note: Sony has confirmed to me that they have not addressed this issue in a firmware update at this point. The issue is still under investigation.

@dw886: Could you please be more specific as to which setting you are suggesting changing? Are you suggesting changing from Web API control to Simple IP? Or something else? The problem does seem to be sleep/power related as the TV never loses connection when it is powered on.

I have the same issue that is being discussed in this thread. A Sony XR55A80J with a Control4 EA3 processor and NEOO remote. Periodically - approximately once per day - the Sony XR55A80J TV drops the network connection and Control4 is unable to control the TV. The TV is connected with a Cat 6e ethernet cable to a gig switch. When I run the TV's network diagnostic utility, it reports: Cable OK; LAN OK; Internet Failed, but the error state will eventually progress to Cable OK; LAN Failed; and Internet Failed. The TV claims to be unable to communicate with the router, the other 20 or so devices on the network are not experiencing any issue. The issue can be temporarily resolved by restarting the TV. When the TV is in this state it will not respond to a PING command from a PC. The TV is set to use DCHP, but the TV's IP address is reserved in the router. I have temporarily removed the network switch and replaced the cable and that did not make any difference - same behaviour... TV loses the network connection about once per day. TV is set to use Web API with Control4.