My Remote 3 was working pretty consistently for a month but in the last few days it has required a daily reboot. Remote 3 running 2.7 and two docks (one charging on WiFi, one non-charging on ethernet) running 0.8.
All 3 days the remote is left on the charging dock overnight. Upon launching an activity the next day, the activity immediately fails. The first time it happened, I simply rebooted the remote and it didn’t fix it. After rebooting both docks, worked fine for the rest of the evening. The next day, same error. Rebooted both docks and remote, worked. Same thing on the third day.
If it happens again, I can try and reboot the docks one at a time to see if the problem is isolated to one of the docks but thought I’d post here.
I have seen similar behaviour but not as consistently as yours. Did you check in the web configurator if the docks were online when this happened? My blaster had gone offline and I think that was causing me the issue. I find I have to reboot the docks about once a week which is not ideal.
I should say that kennymc.c advised that I should try adding in the dock their custom URLs. Since I did this I have not had the problem reoccur but it hasn’t been a week yet so lets see.
I have the same issue, where I have to reboot one remote daily as it won’t start an activity when picked up from the dock. The reboot always fixes it and it has nothing to do with the dock since I have no IR in use - it’s all network-controlled. The weird part is that this doesn’t happen on my second remote. Both are R3s running 2.7.0 and have very similar configs(only TVs are different).
Thanks everyone. I checked tonight and everything worked without a reboot but just in case I went into my router and gave the remote and two docks static IPs and then went into the existing docks in the web configurator and added the WebSocket URL to the “Custom URL” fields. Both docks disconnected and then immediately reconnected so hopefully all is good now. I’ll monitor and report back.
is your wifi signal weaker where the remote that wont start is? Also is it locked to an AP? I had a similar issue which for now at least seems to have stopped since I forced the remote to use the 2.4Ghz band, locked it to the nearest AP and added in the custom URL in the web configurator.
Thanks. That is a good point - the remotes used to connect to 2.4G before the upgrade and now connect at 5G(I’m using DFS channels). I will force them on 2.4G to see if that resolves the issue. I’ll leave locking to an AP as final resort since I’d like them to migrate if the closest AP goes down.
All worked fine yesterday but upon trying the remote this morning, it failed. This time a reboot of the remote (not the docks) solved it. So, unfortunately, manually adding the docks didn’t solve it.
My AP is only about 15 feet away. There should be no issues with signal strength. I just changed the WiFi band from Auto to 2.4 in the remote settings. We’ll see if that works.
Apart from locking to the AP (which as you say at 15 feet shouldnt really be required) the only other thing I can suggest is do you have the ‘Keep WiFi connected in Standby’ set on in the Power Saving settings?
Are you using Android TV integration by chance? I had this issue as well, but uninstalling the integration and reinstalling the custom driver fixed it. Looking at the git repo for it, there are a few pull requests to address a few related issues with freezing / crashing, but they have not been merged yet.
I’m having the same issues. The Remote 3 and the Dock are losing the connection to the WLAN/LAN. Most of it the connection can’t reestablished so I need to reboot Remote and/or Dock.
Sometimes just opening the WLAN settings on the Remote can fix this but this is a really rare luck.
The Dock is connected via LAN, Remote via 2,4 GHz WLAN, the distance to the WLAN AP is 1,5m up to max. 4m in the same room. Everything is controlled with IR, except the TV.
Switching to the current Beta FW 2.7.0 didn’t help. With this problems I can’t retire my Harmony Ultimate yet.
Do you have the ‘Keep Wifi connected in Standby’ option selected in the power saving setting? Also have you assigned the remote and the dock static IP addresses and added the custom URL to the dock configuration? (ws://fixed IP addres/ws)
I immediately noticed the dock 3 behaving this way when I set it up initially. My dock 2 does not behave this way. I would go into the web configurator and dock 3 was constantly reconnecting. What solved it for me was REMOVING the custom URL. Delete it entirely. Reboot the dock. Mine has been stable for weeks now since removing it. My dock 2 had a custom “web socket” URL forever though. I removed it from all docks. I’m using static DHCP for all devices.
“Keep Wifi connected in standby” is enabled. I think thats also some reason for that strong battery drain.
Remote and Dock are getting their IPs from DHCP but I’m losing the connection even without expiring the lease-time multiple times. I try to assign static IPs.