Bad WLAN connection with Remote3

I just received my Remote3 and the trouble already starts :frowning:

I have been able to enable my WLAN (Ubiquiti AccessPoints spread over several places in my house, using WLAN 2,4/5GHz WPA2) on the remote and the doc. The Dock has a really good connection (-48dBm), but the Remote3 is not managing. The remote is choosing not the nearest AccessPoint and has always bad till no WLAN connection. It is impossible to open the Web-Configurator. Even when having the RC close to the Dock or placed in the Doc for charging, WLAN is not enabled properly.

Is there any hint about how to improve?

Config of the RC is still set to standard - no devices etc configured yet.

Thanks

I had a similar experience and in the end forced my R3 remote to the 2.4GHz channel which has been much more reliable.

1 Like

Hi,

that‘s what I already tried as well (selecting 2,4GHz only in the settings dialogue of the remote). But it dies not help.

This maybe worth a try - I have Active Wifi scanning set on in the settings and set to 12s. I am also using Unifi APs.

Will you be using the remote in multiple rooms? If not, try locking it to the nearest access point

It will be used in several rooms.

I found the issue: Remote3 is unable to work with WLAN channels like 13. I changed the channel to 1 and now it works.

Which firmware? From the updates 2.7 and up should support channel 12&13. I did not test. Channel 1 is not the best channel. If you do not have many neighbors 6 would be better perhaps not for the rem6 it other devices.

Ralf

The remote is showing 2.6.12 and no update is show up, when checking for newer versions. How crazy, not supporting all typical channels.

Are you sure you have a Remote 3 and not Remote Two? Because for Two the latest version is 2.6.12

If you have R3 enable beta updates. Lastest for R3 ist 2.7.3.

Ralf

Yes, I am sure having a Remote 3. I just received it yesterday and it has the slider in the lower section of the display and the wireless charging pad on the backside.

About beta-version: Will all channels up to 13 be supported or only specific ones?

How can I enable beta-versions?

Do I get any other issues with going for beta?

Is there somewhere a change-log where I can check, what is fixed (for official releases and beta-versions)?

Hi,

Slider can be configured in 2.7.3

I think starting with 2.7.0 alle channel up to 13 are supported but no WPA3

In the settings, update you can enable beta

I didn´t notice any problems with 2.7.3

Change.log is on discord in a beta channel

Ralf

Remote 3 is making me crazy. I now set one accesspoint to Channel 6. The Remote3 is configured to 2,4GHz only. I mapped the Remote to this dedicated accesspoint. And it is nearly impossible to configure the remote via web. The connection gets lost several times within a minute and the browser is just showing:

In my Ubiquiti admin-panel I can see it as well: WLAN connection, if connected, is excellent (-48dBm). But still connection is instable:

how do you manage a stable connection?

Is remote in dock?

It is happening in the dock as well as outside.

When outside, I have it in my hand and it is turned on all the time (display is showing content).

Perhaps create a simple activity with “prevent sleep" then I can configure even without being in the dock.

How can you tell that the connection is dropping? If it’s happening in the web configurator, try temporarily disabling the firewall on that device.

I now have installed the latest beta (2.7.3). The Remote3 now seems to be able to connect to any of my AccessPoints (several Ubiquiti UniFi AC-Pro and AC-HD) - independent to the channel (Remote3 set to 2,4GHz only). Dropping connections seem to be an issue on Windows PC, only. iPad and iPhone are not facing this problem - at least not on such frequency. On a Windows-computer it is impossible to configure the Remote3. I already disabled Firewalls, Virus-scanner, … - no improvement. I tried different browsers as well - Chrome & Edge.

Does anybody have an idea?

How are you accessing the configurator? With the ip or the .local domain? Try to use the IP as this is more stable in most networks.