No, it’s to keep the remote connected to wifi while sleeping instead of trying to reconnect once you wake it up.
Hmmm. Sounds like that would drain the heck out of battery. Where is the setting though? In the remote or UI?
It doesn’t exist on R3 yet - just R2. It will use way less battery than keeping the remote awake constantly during activity, which I have to do now to avoid connectivity issues. In the current state it’s using around 13% per hour.
Ok. Where is the setting then? I have a remote 2.
Also, you should definitely NOT need to use the keep activity awake option. That’s crazy. I have no connection issues at all. I would highly recommend using Ethernet for the dock and static IP’s for both remote and dock. Mine is solid
That is because you have a R2. R3 has a lot of issues. I’m not sure where the setting is on R2 as I don’t have one. Try the development section in the web configurator settings.
It is in the Power Saving settings, but only for the R2.
The R3 only has one increased issue compared to the R2 it is the increased battery drain. I did not notice any other difference between R2 and R3.
Ralf
If you let it sleep during an activity everything goes to hell eventually(if you rely on network controls).
I still have the connection issue. Get the message ‘service unavailable’ for about 10 seconds then the remote starts to work again. It’s really irritating and the family no longer wants to use the R3, so they’ve defaulted back to the remotes for the TV, Apple TV, etc. Please help!
Activate “prevent sleep” in each activity.
Ralf
Prevent sleep is activated. The issue remains. It’s not just the activities that are failing, it’s the standard remote buttons for a specific device also - channels, volume, home button, etc. All fail for about 10 seconds then start working again.
IR device?
It’s something with your network then. Should have absolutely nothing to do with IR. I presume you’re getting the red banner message at the top. Use Ethernet if you can. Set static IP’s to both the dock and remote.
I’m already using Ethernet. It’s a mesh network (TP-Link Deco), however both docks and the remote now all have reserved IPs. Re-booted yesterday. Same problem still exists. Getting internal server error and unresponsive red banners at different times. Seems random.
Oh yeah. I forgot that you have a remote 3. That’s your issue most likely, until the devs fix via firmware.
ah ok, so it’s a known issue with the R3? When will the firmware be released please?
Pretty sure it is, yeah. I have absolutely zero issues with the R2. R3 is coming soon, so I can’t test any differences. I believe each beta firmware states this issue, and it’s still being worked. No idea when a true fix will come.
I also get those errors all the time with my R3. I also have a mesh network (Orbi 970).
1 Like
I don’t know if this might help, however it might be worth a try. In the Deco app select the remote 3 device and turn off the “Mesh Technolgy” setting so that it stays connected to the same Deco and doesn’t attempt to connect to another one.
Forget mesh as the cause. I also have a mesh system. Try using IP for connection of dock instead of name. I think detection is done with mDNS and this can be affect by the WiFi system but not mesh in general.
Ralf