@ckangis, I haven't heard anything like that. There is a requirement to use the tsr-310_3.000.0010.puf FW with the latest version of CH or vice-versa. I'm pretty sure I saw that somewhere recently. That could be what your network guy was referencing and possibly related to the chipset.
?
I also have several sites where I can't get TSR-310's working reliably. I've tried everything I can think of, even dedicating an AP to the remote and still no luck. What's strange is that I have tons of these remotes in the field but it's only certain sites that have issues with, seemingly no commonality. I have a long case open with TB regarding one of these sites with the behavior you are reporting, along with full lock ups, to the point they have to be rebooted. Here's what I've tried, all with no luck:
?
Multiple versions of FW (to include current)
Locking a TSR to an AP (in Ubiquiti AP settings)
Removing common SSID from TSR and using a separate SSID, dedicated ONLY to the remote
Adding a dedicated AP, with the TSR as the only client?
Remove Hostname and adding a direct IP address for setup/connection to the processor
Setting 5ghz only on the TSR
Setting 40MHz width max on AP
Turn voice control off (which seems to keep getting turned on)
?
I can't recreate the issues off site, even with the same remotes. What's even stranger is that for one site I gave my customer 2 brand new remotes on his nightstand as a test because of this issue. When one locks up, the other is still usable so I'm at a total loss because there's no errors logged or anything definitive. My case has been open for months now with TB and we're no further along.
?
@Steve Kuehn, have you seen any downsides to rolling back FW?? I don't think I've rolled FW on these previously, only updated. At this point I'm ready and willing to try anything though.
