Any updates? The latest firmware update has notes that UC is aware of the issue and to contact UC customer Support. I don’t want to send my remote in for an unspecified time for a software bug. UC needs to fix the issue.
With my first R3 I did not have any of these issues.
I received a second R3, that one also is taking actions on its own while having exact same config as the first one.
Weird…
Not so weird as the error is random.
Touché
I hope that bug will be fixed soon.
I’ve noticed that the issue seems to occur often if I turn of an activity and then put the remote into the dock for charging. It also happens sometimes randomly when the remote is lying on the table sometimes, but this seems to trigger the issue really often.
Had issue again with the volume slider yesterday, remote on surface, again noticeably warmer than usual, slider jumping up and down. switched to a different activity and back and all was well (no reboot). R3 with Yamaha AV amp RX-A1080 via HomeAssistant IP control. It’s now fine as I type. For me its more of a small inconvenience than an every day problem (so far…) 2.8.4 firmware
So my first remote never had the issue. My second remote which I own now for a couple of weeks had it a few times right from the start.
Then I noticed my second one also wakes up screen and I got the screen turning green with lines. On the remote, so not webconfigurator, I disabled “Keep WiFi connected in standby”. That did not help because still it was waking up screen. So I turned off the remote completely to prevent it do go wild. A day later I turned it back on and, again on the remote directly, enabled “Keep WiFi connected in standby” again.
That was a couple of days ago, since then I have not noticed yet the screen waking up, did not have a green screen and did not have ghost touches. Yet.
As the issue is random, I still expect it to turn up again but I also have some false hope that by disabling “Keep WiFi connected in standby” direcly on the remote, turning it off, turning it on and enabling “Keep WiFi connected in standby” again directly on the remote might have somehow exorcised the ghost?
How much time do you have on average between ghost/screen issues?
I have “wifi connected in standby” OFF, not touched this setting at all.
I probably see the issue maybe twice a month and for me it’s only been the slider.
Most of the time mine is cold to the touch but when the slider is moving around by itself it is noticeably warmer. Its also been on a flat surface untouched for a few mins when Ive noticed the issue
These random display activations are caused by the Keep WiFi connected in Standby setting as this enabled Wake on LAN on the remote.
This is a different issue and most likely caused by a bug in the WiFi chip firmware if you can rule out that no other device in your network woke up the remote. It also happens with R2 wich is not the case with the ghost touches and display artifacts. UC is aware of this and in contact with manufacturer. Unfortunately debugging is very difficult ([bug] Possible fix for recurring wakes of remote · Issue #646 · unfoldedcircle/feature-and-bug-tracker · GitHub)
My power saving settings as follows
“Keep WiFi connected in standby” Disabled
“Wakeup sensitivity” Medium
“Display timeout” 1 min
“Sleep timeout” 20mins 31 seconds
So what you’re saying is this remote was over engineered to the point of making it not work. My 10 year old Harmony remote doesn’t have this issue, my $10 universal remote doesn’t have this issue. Unfolded needs to get this figured out and excuses of debugging are tough and it’s random are not valid excuses. Ghost touches for me occur 2-3x a day. It’s a great remote when it works. But it’s really embarrassing when your $400 remote changes the programming while watching and you have to explain that to everyone.
The issue wll probably need to be fixed in the closed source firmware by the WiFi chip vendor itself. As these wake-ups are random it’s hard to track down the real cause. UC will probaly won’t be able to fix this without the help of the manufacturer and in the past they have not been very fast in communicating with them. There could be similar reasons why the ghost touches and display artifacts after wake-up have not been fixed yet.
As every network configuration can be different it’s simply impossible, especially for small startups like UC to test every possible combination in advance. Markus (Head of software) has shared some details about this and other bugs on Discord a while ago. You also find more in-depth details about bugs on GitHub.
I don’t spend time on the GitHub, nor do I have time to. All of the excuses and kicking the can down the road don’t fly with me. As the business that provided the product, it’s on Marton and UC to get the issue fixed with their vendor or provide refunds for producing a lemon. As a business making money is nice, but you have the responsibility/liability to produce what you took money for. Blaming the vendor doesn’t absolve you from the blame or responsibility to get the issue fixed.