It looks like this old problem from a year ago and solved, has reared
its ugly head again.Must be in some bad code in an upgrade. Perhaps
everyone with the issue should share what version they're on?Your
solution is brilliant, by the way. Bravo!
As WillyOne stated, the problem has been repaired for some time now.
Just make sure you're not still on version 1.60.305621. If so, I forced
an update by unplugging and replugging in my hub. Or you can go here for
None of these are actual solutions. This works, however, on all of my
hubs as a fix.In Home, enroll in the firmware preview program. This
updates your firmware to a version that does not have the bug (mine is
currently 1.62.312297). By the next morni...