开云体育

?

Is this what you are talking about?

?

Cheers,

?

Michael . . .

Sorry to resurrect an old thread but I'm in the same situation. Just dusted off vs2008 but it won't create the .clz file. Were you able to find a solution?

?

Any console command will do.? Examples would be

ECHO ON

DHCP

EST

?

I usually ssh into the TSR310 from my host Linux laptop instead of using toolbox.?? I issue an "ECHO ON" command so I can see what I am typing when using ssh.? When I set up the TSR310 offline site, I set up the TSR310 all through an SSH connection and TSR-310 would respond to something like EST within a few seconds.? When I got to the job site, that same command would take 30 seconds to respond or not at all.? Client has a lot of IOT stuff on his main network.? After setting up a separate VLAN and SSID for the TSR310s, the TSR-310s started to responding to SSH commands quickly again.? And after doing the other things I specified, the TSR-310s appear to be working properly.

?

The AV stuff (Theater and another room) is on a CP3.? There is also a Crestron Home CP4R with an NAX audio distribution (No TSR-310s on the CP4R).? Interesting to note that client has a number of Rokus in the house.? Two of those Rokus are pulling all the streams from the pair of NAXs.? That resulted in those Rokus constantly having 54mbps of NAX multicast traffic going to each of them all the time.? The other older Rokus in the house do not do this.? At least one of the Rokus pulling the NAX streams does have a problem with overheating.?? Not sure how I am going to fix the issue.? Ideally, it would be best to keep the Rokus from requesting the NAX streams but I see no option in these Rokus to stop this action.? Tried assigning different multicast addresses to the NAX but no change -- these Rokus will just start requesting the streams again.? Really weird.? If anyone has any suggestions, I would appreciated it.

?

Steve

?

?

Not that I have found.

?

Website has control4 and a third party has created a Crestron Home driver, but no SIMPL

On Thu, Jul 25, 2024 at 01:19 PM, Michael Caldwell-Waller wrote:

The advice of "Have a separate SSID" is probably better translated as "Don't depend on our device to pick the right AP when more than one of them is serving the same SSID".? That means, make it so the device's selection of SSID served by one single AP takes all the guesswork out of AP selection, because you've made it a sure thing.? Does not mean a single device must be alone on the SSID.

?

Lately my strategy for setting up a robust network includes having SSIDs meant for computers and phones (these roam well) on multiple AP's, and then have hidden SSID's?that are unique per AP that I use when I want to force a dumber device to use a specific AP because I know its permanent location.? The crucial factor is using a unique?SSID per AP for this purpose (and not per remote).? (I hide these per-AP SSID's because they're confusing to the end user, but... be aware that hidden SSIDs perform even worse for roaming purposes if multiple AP's are serving them, the broadcasts are important for roaming to work cleanly, so... only use this idea for one SSID per AP)

?

Michael,

What do you think of the idea that I mentioned where you have (Hidden SSID) across the system (ex: CrestronTSRs) so that you only have one SSID to maintain for the TSRs, but have MAC# assignments for specific TSRs to Specific APs so that they won't roam??

The one that I use is WIFIDIAG.

It does a wireless network diagnostic scan.

?

same issue here with "too many requests" error message on the error log..

?

any update guys?

nf

On Thu, Jul 25, 2024 at 01:09 PM, Steve Kuehn wrote:

1) The TSR-310 cannot handle a lot of network chatter.? An easy way to tell if it is getting overwhelmed is to SSH into TSR-310 and issue a few console commands

Steve, can? you share those console commands with us?? TIA

On Thu, Jul 25, 2024 at 11:35 AM, Brian Matson wrote:

Our biggest headaches deal with the smallest jobs that end up being Crestron Home.

I usually don't get involved with them until there are problems, which lately there always are.

?

Biting my tongue!...:)

?

Having done some lower level WiFi development on integration of non-Crestron devices, I think I could safely share the following about what someone might mean?by having separate SSID's?so you can judge for yourself whether this is necessary.

Okay, I know I am jumping in a little late in the game here, but here is my 2 cents worth.

?

1) The TSR-310 cannot handle a lot of network chatter.? An easy way to tell if it is getting overwhelmed is to SSH into TSR-310 and issue a few console commands.? If you find it is sluggish to respond, well there is your indicator that it is overwhelmed by network chatter.

?

2) The TSR-310 seems to attach to the first AP it sees rather for looking for the AP with the strongest signal.? I've seen it attached to a very distance AP when there is a AP less than 5 feet from it.

?

3) I had recently had a job with an existing TSR-310 with firmware v2.001.0134.001 and added another TSR-310 with firmware v2.001.0186. The one with newer firmware had issues with taking 30 seconds to reconnect to the WIFI if it had been left off dock for a while even though the release notes for v2.001.0186 says it corrects for slow reconnect issues.? I landed up downgrading the firmware to v2.001.0134.001.? It has been a few weeks since I did that and, at least so for, haven't notice any reconnect issues. I am keeping my fingers cross that this fixed the issue.

?

4) The "wifisetup forget" command may take a day before it actually stops connecting to the old SSID.? That makes it very difficult to see if setting of a separate VLAN/SSID for the TSR-310 actually makes a difference.

?

In the end, I am landing up creating a single SSID that all the TSR-310 connected to, putting that SSID on its own VLAN to reduce network traffic, and limiting the SSID to just a few selected APs so the TSR-310 won't attempt to connect to a weak AP.? And I am not using the latest and greatest firmware anymore until I can confirm that firmware is stable.?

?

Of course, forget about putting the TSR-310 on its own VLAN if you are using Crestron Home.? Your only hope here is to putting the entire Crestron system on its own VLAN along with anything that Crestron Home needs to discovered such an Sonos.? Then enable IGMP snooping on your switches and APs to help cut down on network chatter.

?

?While I love the TSR-310, it is crazy that I have to jump through loops to get them to work properly.

Thanks for chiming in everyone.

?

We do exactly what you all do, and for the most part, the remotes work most of the time.

We used to use the 2.4 GHz band but changed to the 5 GHz band with the later firmware updates.

I can only assume that Crestron is recommending it because there is less congestion and interference.

?

Our biggest headaches deal with the smallest jobs that end up being Crestron Home.

I usually don't get involved with them until there are problems, which lately there always are.

With CH, it seems like all of the CS authentication and hostname stuff just complicates it even more.

When you add in VLANs ... ugh!

?

It just baffles me how Crestron has all of these "best practices", but no actual document that details them.

Maybe we just need more "Do Guides"!!!!

Guys

?

AVA has an API and the dynamic wheel can be controlled. If you have a dealer relationship with them you can request the API and do it, I praise you in advance, for I have the desire but not the time.?

?

We've built many systems with TSRs, and felt the pain.?

I have implemented a single side per remote (TSR-FAMILYRM) for example, using 2.4 on a single nearest AP.?

?

1 for each AREA capable of serving one or more remotes.?

?

We use a single band SSID on 5g (and now 6g)strictly for the owners mobile device connectivity and the allocate 2.4 to a general utility network.... So the 5g band doesn't lose an antenna in dedicating to a separate SSID.?

?

It's been nearly flawless since we started doing it this way... I have a couple homes now with Unifi Wifi 7 running and seems to be still solid as a rock.?

On Wed, Jul 24, 2024 at 09:23 PM, ckangis wrote:

The support person, if he/she actually said this, should be fired.

Or at least taken off the line and re-trained. Particularly to not answer a question unless they are sure about the answer...

So if its only pulsing once in debugger than the presets module is working.? correctly. I would check your IR module and set it to Pulse Only no repeats, or run your signals thru a One Shot. What is the device you are controlling?

We do as CK has listed, although usually we have been using 2.4 just for that extra bit of range- I wouldnt think the speed difference of 5ghz is necessary for these. Along with the newest firmware they seem to work very well that way even with sevaral remotes on the dedicated SSID. The notion of a separate SSID for each remote is ludicrous and I agree that person should get the boot. This type of shit is why I cant stand their tech support sometimes- all the misinformation handed out on a daily basis is insane.?

Hi,

?

I am curious does anyone have any experience using Extreme Networks WiFi access points.? ?I am looking to add a WiFi 7 offering and the Extreme Networks the AP5020 on paper looks better than the high end Ruckus and Aruba WiFi 7 offerings.? ?Any feedback good or bad is greatly appreciated.? ?Also, interested if you are working with Extreme Networks what has your support experience been.

?

Thank you

Bryan

Boy, I feel your pain!!!? And I wish it was just the TSRs!....:(

?

Hopefully Dave H will chime in tomorrow, but here's a couple ideas:

- You do not need a separate SSID for each remote - The support person, if he/she actually said this, should be fired.

- Yes, the new FW wants (prefers?) 5g only

- The 'old' best practice was to have a dedicated 5g SSID on each AP (FamilyTSR, MBedTSR, etc.) and lock each remote to just a single AP/SSID. This is still what Crestron would recommend, I think. In this scenario, you could have multiple TSRs connected to the same AP/SSID. They just could not roam, which is the key issue

?

*** Regarding the 3rd point which is still hard to manage, It was suggested that instead we set up a single 'system-wide' 5g SSID say "CrestronTSRs" and then set the Wifi/Network so that specific TSR MAC addresses would be locked to specific APs. i.e. All TSRs are connected to "CrestronTSRs" but the Family TSR can only talk to the Family area AP, MBed TSR only to the MBed Area AP, etc.

NOTE: I have not done this yet, nor have I dug in to understand how it would be done (I'm sure its pretty simple).

?

This would be the best scenario I think as I just had a site that was having battery issues with a couple of key remotes. Moving other unused remotes to these key areas was a B***H because I had them set for specific AP/SSID combos.? And of course this is especially difficult with the TSRs remotely (Site is 7.5 hrs away, round-trip).

Having to just reconfigure the AP/MAC# references would make this MUCH SIMPLER...

?

I look forward to others weighing in also...