Control4 Best Practices Vol 2: Zigbee

Поділитися
Вставка
  • Опубліковано 14 гру 2024

КОМЕНТАРІ • 13

  • @CobraSurveillance
    @CobraSurveillance 2 роки тому

    (Wow you sound like Ray Romano) Great info Thank you

    • @QVisionGarage
      @QVisionGarage  2 роки тому +1

      That’s cause I am him. When I’m not acting, or writing for newsday I make UA-cam videos on niche automation systems. Appreciate the watchtime brother. What else would you like to see on control4?

    • @CobraSurveillance
      @CobraSurveillance 2 роки тому

      @@QVisionGarage Very Nice, I am new to Control4 very informational videos keep it up, knowledge is power Ray Romano you got the power LOL

  • @GODOFAI1
    @GODOFAI1 Місяць тому

    I'll love to know deep on control 4 sir and I really need Ur help sir

  • @maniakm897
    @maniakm897 3 роки тому +1

    Hello.
    I have a question about using Kwikset Signature 914 in Control4 system via zigbee.
    To control that lock via Control4 system I use Kwikset Smartcode driver (version 31). For first time I add lock to C4 system witout any problems, and can control it (open or close) via navigators. But after 1 hour pause, during which I didn't use the lock, I try to control lock again, but in this time lock did't react on my commands. To solve that problem I removed lock from zigbee network and then add it again. After these steps executing lock works again. What can be a reason of that problem ? Any ideas ?
    Firmware version of lock: 03.08.16.

    • @QVisionGarage
      @QVisionGarage  3 роки тому

      While there’s no way I can say for sure, I can tell you what it sounds like to me and what I would look at.
      A lock I believe is what would be considered an “end node” in the zigbee mesh architecture, I could be wrong but I think that is correct. Meaning it’s going to kinda wake up when it’s called to action. If there isn’t much else in the project comprising the zigbee mesh, it could just be having a hard time rejoining after going back to a sleepy state.
      I would be looking at the layout of the project the same way I described the issue in this video and if possible either reconfigure the zigbee network to have a closer point of origin for the zserver or deploy something like a ca-1 just or a motorization zserver. You could also try a zigbee extender. All in all this is really just a guess as I’ve never seen the project file or the floor plan so I can’t say with any certainty that this is the problem, I’ve used Yale C4 locks before (I think) as well as WiFi August locks and never had an issue with dropping. So this could also be hardware related, based on the description I’d be looking at the architecture of the zigbee mesh as I described above. Good luck, thanks for watching.

    • @maniakm897
      @maniakm897 3 роки тому

      ​@@QVisionGarage Thank you for your response. Actually, I have only one unit in zigbee network (it is kwikset smart lock), whick is located in 2 meters from C4 controller. If I undestand correctly, I should add one more unit with zibgee (for instance zigbee repeater) to solve that problem. Am I correct ?

    • @QVisionGarage
      @QVisionGarage  3 роки тому

      @@maniakm897 if it’s that close then range shouldn’t be an issue, I might try changing the zservers channel frequency to see if maybe that helps.

  • @maniakm897
    @maniakm897 3 роки тому

    Hello.
    I have one more question: after EA-5 controller rebooting I cannot restore zigbee connection to device. To solve this problem I should reboot zigbee device (just take off block with 4 AA batteries for 30 seconds and after this return in back in device).
    Zigbee device I use: lock Kwikset Signature 914. C4 driver: Kwikset Smartcode (version 31). Firmware version of lock: 03.08.16.
    Any ideas how to solve this problem ?

    • @QVisionGarage
      @QVisionGarage  3 роки тому

      Unfortunately brother I dont have one of these locks to further troubleshoot.
      I would probably do the following in your position, you may or may not have done these already:
      1) Check for any firmware upgrades for the lock
      2) Experiment with different zigbee channels to see if one offers a better more stable connection
      4) Reach out to Control4 for further assistance, they may request a log monitoring whats happening with the controller and the lock
      5) Reach out to the manufacturer for a warranty replacement
      I'm sorry I dont have a better answer for you, I'm afraid I havent worked enough with the product nor do I have one to mock up to try and replicate the problem.

    • @maniakm897
      @maniakm897 3 роки тому

      @@QVisionGarage thank you for your answer. Where can I check firmware upgrades for zigbee device (I did't find it Composer Pro) ?

  • @larrystotland3712
    @larrystotland3712 3 роки тому +1

    Great video except that I was under the impression that zaps where not recommended. Better to just set up another z server on a different channel.

    • @QVisionGarage
      @QVisionGarage  3 роки тому +1

      Thanks for watching brother, I think maybe the new way of thinking is leaning that way, however my years of field experience is what I rely on and because IMO there’s no substitute for proven results, I’ll continue to practice the core values that I learned when I went to the training course along with what works in the field. The real world problem I see with lots of zservers is if the end user ends up moving remotes room to room, which may not always happen but if/when it does that’s a service call. Of course every install is different and you should always test rigorously to achieve the best results, but I’ll always maintain that a controlled training environment will never be what you see out in the wild.