Jump to content
C4 Forums | Control4

jacdx

c4Forums Member
  • Posts

    156
  • Joined

  • Last visited

Everything posted by jacdx

  1. Thanks. I'll see if I can dig up a resistor. Where would it go on the circuit? I'm using 12+ and sig on the controller. Would it bridge those at the controller? So, this issue isn't quite as cut and dry as I thought. I came into the kitchen this morning, the can lights turn on because of the motion sensor and the test light for the doorbell goes on with it!!!!! :o Surely mistaken, I turned the can lights off, doorbell light went off. Dimmed them up past 10% and the doorbell light would trigger a press and hold it until I turn off the cans. I turned the can lights on and off a few times just to make sure that I'm not crazy. And the doorbell test light would go on anytime the can lights were on. The doorbell test light is in a different room...not related in any way to my kitchen programming. Late last night when I wrote the reply, the cans were never on, since the motion programming turns on an 'evening' scene instead at night. My Elk & doorbell are high on a cabinet in the kitchen, about 4ft from a 75w halogen can light. The Elk has been just sitting out in the open while I get this figured out. So, I turn the can lights on, doorbell press triggers and holds. I go up to the Elk and put my hand over it to block the light (not touching) and the doorbell release event fires. Move my hand, the doorbell presses and holds again. I took a scrap piece of opaque plastic and covered the Elk and left it for now. Now it's acting correctly, can lights on or off. Could the Elk be light sensitive? Or is this setup so sensitive without a resistor that a nearby can light or halogen could trigger the contact via some sort of interference?
  2. Hmmm... like good wine and every girl I've ever dated, it "needed some time". We went to dinner for an hour, came back and the contact is now closed (like it should be) until I press the doorbell. The doorbell now works through C4 correctly, announcements fire correctly. Now, if I can get the announcements to work faster... Currently it takes 3 seconds from doorbell press for the sound to start. When I had the light programmed to it, it would turn on/off instantly.
  3. Hey guys, I'm FINALLY getting around to doing my Elk-930 install and I'm running into issues. So, it's a Spore LED lighted doorbell (specs here: http://sporedoorbells.com/storage/trueinfo.pdf) and I've only got one. I've got it wired up to a HC-800 contact and the Elk. I wired it all up exactly as the Elk-930 instructions say, and have looked at prior threads on here. Programming-wise, I added a Doorbell, connected it to the HC-800 contact, programmed it to play one announcement when the doorbell is pressed, and a second when the doorbell is released (for testing). That was all sorts of erratic. I could only get the announcements to fire when I was handling the Elk module and twisting screws. Then I ditched the annoucements and setup the events to turn a light on when doorbell pressed and turn it off when released. That shed some light on the subject (zing!). The light stays on constantly. Pressing the doorbell doesn't make it go off either. I've double checked and triple checked my wiring. Even swapped out the Elk module for a second one, same issue. Thought 'Invert Sensor' might help in Composer, but it didn't change anything. Without the Elk module wired, I can cross the wires connected to the controller and they behave as expected, the contact closes and the light goes on. Uncross and the light goes out. I just can't seem to get the ELK to recognize the state of the doorbell correctly. My transformer is a Broan 16.5V. I measured 19V on it. I'm thinking either the transformer is outputting too high so the Elk can't measure the voltage drop correctly...or the draw from the doorbell is too low for the Elk to detect and open contact state. Any ideas?
×
×
  • Create New...

Important Information

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