Sign in to follow this  
Followers 0
wpervaiz

zap coordinator vs. zigbee server?

22 posts in this topic

hey guys,

what is the difference between a zap coordinator, and a zigbee server??

if i have an hc-200 and an hc-300 installed in my project, which should act as which??

thanks!

Share this post


Link to post
Share on other sites

are you runngin 1.7 or 1.8(zigbee pro)?

in 1.7, one control4 system can be used one or multiple zigbee servers. NO ZAP was introduce at the time.

in 1.8, one control4 system can be use only ONE zigbee server in any HC-class controller (you CANNOT use HTC or MC as zigbee server). An addition of ZAP(Zigbee Access Point) help extend the radio signal of the closest NODES.

You can run both zigbee server and zap in one HC controller but not hc1000

If you want to upgrade zigbee into zigbee pro devices, you need an additional zap in the system or a USB upgrade. In your case you should be fine to upgrade because you have hc-200 running as ZAP

You can use HTC or MC as ZAP but not HC-1000 because it does not have zigbee radio.

I would use HC-300 as zigbee server, and HC-200 as ZAP in your case.

someone can chime in if I missed anything.

Share this post


Link to post
Share on other sites

It depends, but more than likely you'd have one running each, and preferably the one running zigbee coordinator would NOT be running navigator.

Share this post


Link to post
Share on other sites

Interesting post - given that it is ZP, which of the two should run director and navigator?

assuming both controllers are also streaming audio?

Share this post


Link to post
Share on other sites

So if i have two TVs, how does this sound:

Hc1000: director

Hc300: Zserver, Navigator

Hc200: coordinator, Navigator

Is there any reason I would want the zserver, and zap coordinator swapped with each other? (i.e. so that hc300 runs coordinator, and hc200 runs zserver?)

thanks!

Share this post


Link to post
Share on other sites
Put COORDINATOR on the HC1000.

Coordinator requires a zigbee radio. ZServer can run on the 1000 though.

Share this post


Link to post
Share on other sites

Well. put the big resource hog that doesn't require the zigbee radio on the HC1000. Everyone calls it something different anyways. It's one of those tow processes you listed, but the name varies depending on who you talk to.

Share this post


Link to post
Share on other sites
Well. put the big resource hog that doesn't require the zigbee radio on the HC1000. Everyone calls it something different anyways. It's one of those tow processes you listed, but the name varies depending on who you talk to.

It's zserver - that was the big benefit of being able to put the zserver process on the HC1000 a couple releases back, as previously it was required to run on the same controller as zigbee server.

Share this post


Link to post
Share on other sites

Zserver and director on the 1000, ZAP coordinator on the 300 and the 200 would run navigator and act as a zigbee access point(ZAP). The most efficient way to set it up and use of system resources.

Share this post


Link to post
Share on other sites

Names always stay the same as they are directly named in system services as such and in tools/network and in the zigbee setup wizard. They are standardized names. If someone is calling them different names please do yourself a favor and do not let them set up your mesh.

Share this post


Link to post
Share on other sites

Joe, can you summarize what goes on what in a single post here- I'm confused and in a tough spot currently with severe mesh problems- thanks.

Share this post


Link to post
Share on other sites

How's that 2.0.x working out for you? No severe mesh problems over here on 1.7. Still rock solid dependable - no reboots required.

Share this post


Link to post
Share on other sites

^Yeah, it's something beyond the norm. We're working on it as I write this. Basically, been working for awhile trying to get a multi-level house to "resonate" with Zigbee. It's tough architecture that's pushing us to the limits.

Edited by Controlfouruserguy

Share this post


Link to post
Share on other sites
Joe, can you summarize what goes on what in a single post here- I'm confused and in a tough spot currently with severe mesh problems- thanks.

this is how i set it up:

Hc1000: Zserver, director

Hc300: Navigator, zap coordinator (multiple)

Hc200: Navigator, zap coordinator (multiple)

looks solid for now

thanks guys!

Share this post


Link to post
Share on other sites

^you should only have one coordinator unless you have a really really large house and some nodes too far away to hop and communicate with the original coordinator. You can have multiple zaps which may be what you were trying to say.

Share this post


Link to post
Share on other sites

How important is it to have Zserver, coordinator and all ZAPs tied into just one switch (no switch cascading)?

Share this post


Link to post
Share on other sites

Preferred, not required.

I know that is vague, but so is the situation. (i.e. what switches, what router, how many?)

Brent

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0
    • 12 Posts
    • 1110 Views
    • 7 Posts
    • 81 Views
    • 12 Posts
    • 762 Views
    • 1 Posts
    • 33 Views
    • 1 Posts
    • 57 Views
    • 9 Posts
    • 113 Views
    • 3 Posts
    • 133 Views