Jump to content
C4 Forums | Control4

JamesW

c4Forums Member
  • Posts

    4
  • Joined

  • Last visited

About JamesW

  • Birthday 01/21/1969

Profile Information

  • Gender
    Male
  • Location
    Denver

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

JamesW's Achievements

  1. Yes, I did recently (within the last month or two) solve the problem by installing a C4 Zigbee IO extender, Model C4-Z2IO. It isn't controlling or monitoring anything, it is just plugged into a power outlet in the garage about 12 feet from the Yale Assure SL lock. That C4-Z2IO has enabled all of the more robust communication required to lock/unlock/toggle the lock, sync the date and time, sync the user database, and sync configuration. It has been working well enough that I have been able to program some automation around checking the lock status and locking the door at a specific time each night, if it is unlocked. I also put some custom buttons on my Navigator screens to easily lock/unlock the door from the Navigators. Let me know if you have any questions and I will try to answer to the best of my ability.
  2. Could it be the age of my C4-DIM1-Z dimmers, and is it possible those older dimmers have lesser Zigbee Pro capabilities as compared to modern dimmers? In other words, is it possible my older dimmers are unable to relay larger or more complex Zigbee data packets required to do the more robust functions of the Yale Assure lock (such as locking, unlocking, toggling, user programming, lock programming, firmware update), but are still able to communicate smaller packets of data (such as basic logging and lock state information performed at the lock)? Could it be the Control4 OS version 2.10.6 has any lesser Zigbee Pro networking capabilities as compared to OS version 3.x? Are there any Zigbee network diagnostic tools or utilities that could help diagnose why the lock can communicate partially, but cannot be operated via the C4 user interface?
  3. Thanks, chopedogg88. When I search the C4 driver database for Yale Assure, I get one result for "Yale Smart Locks". Yale Smart Locks Manufacturer: Yale Model: Assure, nexTouch, Doorman Creator: Yale Modified Date: Wed Oct 16 12:30:00 UTC 2019 Device Type: LOCK Control Method: ZigBee Version: 18 Certified: TRUE Supported OS Version: Control4 OS version 2.6.0 and above Driver Type: C4Z (This driver type requires Control4 OS version 2.6.0 or higher) The driver file for this search result is yale-control4-3.c4z version 18 and that matches the driver in the project. When I search the driver database for Yale, I see there is a driver for Yale Real Living, but we are not using that one.
  4. Hello, I have a Yale Assure Lock SL, model number YRD256-C42-0BP, that is not functioning properly in my Control4 environment. Specifically, the lock only communicates and functions partially. I receive activity logging and lock state information from the lock, so it is communicating on some level, but I cannot lock/unlock it from C4 and I cannot perform lock programming functions from C4 while it is installed in the door. When the lock is removed from the door and carried down to the equipment room, it immediately functions normally. When the lock is placed back in the door, it can only communicate status, but cannot be controlled via C4. I've been working with my dealer for months to troubleshoot and they are unable to help resolve the problem. I am hoping some of the more experienced gurus here on the forums can provide some additional troubleshooting suggestions. The lock is installed in the man door of my garage, which is located behind my house. There is a C4-DIM1-Z wireless dimmer about 12 inches from the lock inside the garage, immediately adjacent to the man door. Also in the garage we have a Card Access Wireless Contact Sensor and a Card Access InHome Wireless Contact Relay. The dimmer, contact sensor, and contact relay all function as expected. The equipment rack contains (among other equipment) an HC-800 running OS version 2.10.6 and the rack is located in the basement, one level down from the garage, approximately 25 feet from the lock. We are currently using Zigbee channel 24. The lock briefly functioned properly on Zigbee channel 25 but then returned to partial communication, so the dealer moved back to the full powered channel 24. There are six light loads throughout the house, all using C4 wireless dimmers with no problem. All of the C4 remote controls function as expected, although they aren't particularly quick. In terms of troubleshooting, we have done the following: Changed the batteries in the lock (no improvement) Took the lock out of the door and carried it down to the equipment room (this worked, until the lock was returned to the door) Swapped out the Zigbee radio in the lock (no improvement) Updated the lock firmware to version 7 (no improvement) Replaced the standard Zigbee antenna on the back of the HC-800 with an extension antenna placed above and behind the equipment rack (no improvement) Changed the Zigbee channel several times (worked on channel 25 for a few days and then returned to partial communication) Changed the 2.4GHz WiFi channels on the Araknis access points several times to get farther away from the Zigbee channel (no improvement) Turned off all 2.4GHz WiFi radios in the house (no improvement) Disconnected the Araknis access point sitting on top of the rack (no improvement) Hard wired power to the Card Access Wireless Contact Sensor to allow it to function as an always-on Zigbee repeater (no improvement) We have logging set at level 5 - Trace, and when commands are issued to the lock from within C4, we can see them timing out and retrying repeatedly in the Lua Output before eventually giving up and failing. When users interface directly with the lock, or when it automatically locks itself, everything functions as expected and we see it in the Lua log. Any advice or guidance would be appreciated. As I mentioned previously, my dealer has no ideas why this is happening or how to solve it. Thank you, in advance.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.