I turned off the fast roaming and there is no setting for bss. It somehow has made it worse. I tried restarting the router, the remote, nothing works. It is literally useless at this point.
Unfortunately instead of making the Dock, which is always powered on, the main device that sends out all commands (not just IR), they made the remote the main device. Otherwise the remote could communicate with the Dock using bluetooth, which is much less power hungry.
1 Like
And less range. I can now control my whole house with the remote.
making the dock the primary signal source should be programmable via an update. Iām not sure if its on the roadmap
The dock will never be a replacement of the R3 as it cannot run the firmware it has complete different hardware. And dock as default which one? I have 4 in my house.
Ralf
I can +1 this topic. Not only can it take a while to reconnect to wifi, sometimes it simply doesnāt at all. In these cases I need to restart the remote to get it connected again.
Wifi is 2.4Ghz on channel 6 and no other devices have issues connecting.
I also noticed it losing connection with the dock once or twice making me need to restart the dock.
Itās an awesome remote, but these connectivity issues really need some love.
(Using an activity to prevent sleep is nice, but just partly a workaround and definitely not a solution.)
I can +1 this topic as well. It indeed can take a while to reconnect to wifi, if it does. I also need to restart often.
Itās indeed awesome, but the connectivity issues make it very hard, wil stick to my Remote Two for now!
Yes unfortunately it has made mine a paper weight. I havenāt touched it in weeks and have gone back to my old remotes. I chalk this up to a learning experience and will monitor this sub for any future fixes but I am not holding my breath. In my opinion it seems to be a fundamental design issue with the remote. The battery isnāt capable of handling full time wifi connection.
4 Likes
I was having connectivity issues with my new R3 and my Deco system as well. I think I figured out a possible solution. Go into the Deco app, click Online Clients, click the MAC address for your R3, click Mesh Technology and turn off. I also went into connection preference and forced it to a specific AP and 5ghz. I havent had any wifi connection issues since making these changes. Iād constantly have to force a reconnect to the AP. Running latest beta firmware.
Not sure if this is a WiFi issue or something else, but my Remote 3 is losing connection to the Dock quite often. I have configured a number of devices to be pure IR signals, and when doing something like āVolume Upā or āSkip Trackā, the remote throws a āReceiver is not respondingā message. There is NO RESPONSE that can be given to an IR signal, so basically itās just losing connection to the dock.
Related to this, itās crazy that it makes me acknowledge this before it will send other commands. That is, I canāt just keep hitting āVolume upā and expect the 2rd or 3rd presses to make it. Instead, I have to ACKNOWLEDGE that the one command didnāt make it, before it allows sending others. This is ridiculous. For a Volume Up command, just send it again, donāt make it a hassle to move my hands around to acknowledge and then try again.
Iām very much sharing the opinion of others here, this remote is half-baked at best. So many usability issues that I am not enjoying it.
Firmware 2.8.1 installed? In this version a command is automatically resend for up to 10 seconds if it failed.
Dock 3 a fixed IP in router? If yes connection via IP instead of mdns could be used:
Ralf
Hi @HarmonyFan : Thanks for the tips here. To answer:
Yes, I was already on version 2.8.1.
Yes, both the Dock and Remote have Static IP reservations with my router.
I think I set the dock using an Auto-discovery (?), but I just went into the configuration and made the āCustom URLā set to āws://192.168.0.12/wsā, so itāll use the IP Number. Hopefully that change will help! Canāt imagine it being a bad thing to do.
I had the exact same issue. I migrted everything to IR because I got fed up with all the ā<ā¦> not respondingā messages, thinking it was a device issue. Issues persisted after I migrated to IR / docks.
Thats why I found out itās a WiFi issue. My R3 would consistenly loose itās connection. PING times would be very high (20ms - 900ms) with high packetloss (20-30%).
I created a new SSID on my network which is only available on 2.4 Ghz and only on one accesspoint. DIsabled BSS Transitioning.
Not all my problems are gone, but the device is now actually usable!
My remote was very unstable on 5Ghz WiFi, although I had a dedicated Cisco access point for the remote only within close distance, no mesh, no other devices connected to it. Switching to 2.4 did the trick for me. I have not had a single disconnect since.
I would also like to point out that, checking the signal strength, my iPhone always gets full signal from my access point while the remote displays a much weaker signal, all other things being equal. I think the antennas on the UC3 are not up to the task - the aluminium unibody might have something to do with it.
I second the idea of a dock running the server on PoE Ethernet and connecting to the remote over Bluetooth.
1 Like
Just as a point for awareness while many R3 users report 2.4GHz being more stable I have been using 5GHz for a few months now without a disconnect so it seems to be environment dependent.
Same. The WiFi in it is very weak compared to all other devices. Iāll need to move my router to a location thatās very close to where I use the R3. It is very noticeable how poor the WiFi is from the R3 compared to all other devices. Itās a shame, because this creates a poor user experience, while everything else seems good so far.
In which case I think it is safe to advise users with problems to test both bands on different channels because, in oneās particular environment, one probably works more reliably than the other depending on WiFi settings, coverage, interference etc. I continue to experience zero problems on 2.4 while 5 was unstable despite the dedicated AP.
I have a good wifi setup at my house and when i first started setting up the remote couldnāt get a good connection selecting a wifi band and turning off auto gave me perfect signal strength and a solid connection
I thought the same and I tried the same but the remote only started being reliably connected and working well when I added another access point just a few metres from where the remote was being used.