Jump to content

rosenqui

c4Forums Member
  • Content Count

    57
  • Joined

  • Last visited

About rosenqui

  • Rank
    Control4 End User

Profile Information

  • Gender
    Male
  • Location
    Ottawa, Ontario

Recent Profile Visitors

1,306 profile views
  1. I'm posting on this old thread again because I've been getting phantom events from the doorbell contact lately. It was working quite reliably until the last few months, and the wiring hasn't changed so I'm trying to figure out what's going on. See my post directly above for how I've wired the ELK-930 into my C4. The ELK-930 is wired like in "Method 1" from the instruction manual here. At least I think I've done it correctly that way. I've swapped out the 10K resistor to see if that will help, but I'm wondering if something else might be wrong. When I measure the voltage at the ELK-930 across the OUT and NEG terminals in an idle state (everything wired up, but doorbell button not pressed) I get around 11.5VDC and it looks like about 2.2mA. The C4 is showing the contact as "Open", so I guess the pull-down resistor is doing its job. I don't have enough hands to measure the voltage when the doorbell is pressed, but I'm guessing it goes to the full 12V are several hundred mA. I know that the open collector output on the ELK-930 can float a bit, but is 11.5VDC and 2.2mA normal? Should the voltage be lower or is the low amperage what makes the C4 see the contact as open?
  2. I guess I've answered my own question... When I went to reboot the hallway landing keypad (a KC120277) via 15 presses on the top button, it did nothing. None of the buttons responded to presses, although the backlighting worked and the status LEDs accurately tracked the load of the linked light. I flipped the breaker off then on for that circuit and the keypad buttons are working now. Best guess is that something happened around 4AM (minor power brownout or surge perhaps?) that messed up that one keypad.
  3. I woke up around 4AM today because the hallway light outside the bedroom came on. Check out the events at 03:56:11.012 and 03:56:12.641. I don't have any programming that invokes "press" or "click" on any of those buttons. The "Bedtime" keypad buttons are linked to a dummy switch named BedtimeAndArmedState, and the only programming for that is to turn it off at dawn or change the LED colour. The controller is running OS 3.1.0. 2019-12-22 03:56:09.944 -0500 hc-800 [4507] INFO: FireEvent: Driver Main Floor Thermostat(932) fired event Unknown(114) 2019-12-22 03:56:09.944 -0500 hc-800 [4507] INFO: Executing command (HOLD_MODE_CHANGED) on driver Ecobee Thermostat(931) 2019-12-22 03:56:09.945 -0500 hc-800 [4507] INFO: FireEvent: Driver Main Floor Thermostat(932) fired event HOLD_MODE_CHANGED(105) 2019-12-22 03:56:11.011 -0500 hc-800 [4507] INFO: FireEvent: Driver Upstairs Hallway(464) fired event ButtonAction(5012) 2019-12-22 03:56:11.012 -0500 hc-800 [4507] INFO: FireEvent: Driver Upstairs Hallway Landing Keypad(468) fired event Push on 'Hall'(5001) 2019-12-22 03:56:11.067 -0500 hc-800 [4507] INFO: FireEvent: Driver BedtimeAndArmedState(478) fired event ButtonAction(5001) 2019-12-22 03:56:11.068 -0500 hc-800 [4507] INFO: FireEvent: Driver BedtimeAndArmedState(478) fired event ButtonClick(5003) 2019-12-22 03:56:11.230 -0500 hc-800 [4507] INFO: FireEvent: Driver Switch(72) fired event VARIABLE_CHANGED(4568) 2019-12-22 03:56:11.393 -0500 hc-800 [4507] INFO: FireEvent: Driver Advanced Lighting(257) fired event BECAME_ACTIVE(15) 2019-12-22 03:56:11.395 -0500 hc-800 [4507] INFO: FireEvent: Driver Advanced Lighting(257) fired event BECAME_ACTIVE(45) 2019-12-22 03:56:11.396 -0500 hc-800 [4507] INFO: FireEvent: Driver Advanced Lighting(257) fired event BECAME_INACTIVE(51) 2019-12-22 03:56:11.398 -0500 hc-800 [4507] INFO: FireEvent: Driver Upstairs Hallway(464) fired event VARIABLE_CHANGED(1001) 2019-12-22 03:56:11.399 -0500 hc-800 [4507] INFO: FireEvent: Driver Upstairs Hallway(464) fired event Light Level Changed(5000) 2019-12-22 03:56:11.401 -0500 hc-800 [4507] INFO: FireEvent: Driver Upstairs Hallway(464) fired event VARIABLE_CHANGED(1000) 2019-12-22 03:56:11.401 -0500 hc-800 [4507] INFO: FireEvent: Driver Upstairs Hallway(464) fired event LIGHT_ON(5100) 2019-12-22 03:56:11.549 -0500 hc-800 [4507] INFO: FireEvent: Driver Upstairs Hallway(464) fired event VARIABLE_CHANGED(1001) 2019-12-22 03:56:11.550 -0500 hc-800 [4507] INFO: FireEvent: Driver Upstairs Hallway(464) fired event Light Level Changed(5000) 2019-12-22 03:56:12.520 -0500 hc-800 [4507] INFO: FireEvent: Driver Upstairs Hallway(464) fired event VARIABLE_CHANGED(1001) 2019-12-22 03:56:12.520 -0500 hc-800 [4507] INFO: FireEvent: Driver Upstairs Hallway(464) fired event Light Level Changed(5000) 2019-12-22 03:56:12.523 -0500 hc-800 [4507] INFO: FireEvent: Driver Keypad Dimmer(463) fired event VARIABLE_CHANGED(4570) 2019-12-22 03:56:12.641 -0500 hc-800 [4507] INFO: FireEvent: Driver Upstairs Hallway Landing Keypad(468) fired event Click on 'Bedtime'(5502) 2019-12-22 03:56:12.732 -0500 hc-800 [4507] INFO: FireEvent: Driver Switch(62) fired event VARIABLE_CHANGED(4568) 2019-12-22 03:56:13.344 -0500 hc-800 [4507] INFO: FireEvent: Driver Upstairs Hallway(464) fired event VARIABLE_CHANGED(1001) 2019-12-22 03:56:13.345 -0500 hc-800 [4507] INFO: FireEvent: Driver Upstairs Hallway(464) fired event Light Level Changed(5000) 2019-12-22 03:56:13.347 -0500 hc-800 [4507] INFO: FireEvent: Driver Keypad Dimmer(463) fired event VARIABLE_CHANGED(4570) 2019-12-22 03:56:13.642 -0500 hc-800 [4507] INFO: FireEvent: Driver Switch(515) fired event VARIABLE_CHANGED(4568) 2019-12-22 03:56:13.721 -0500 hc-800 [4507] INFO: FireEvent: Driver Keypad Dimmer(59) fired event VARIABLE_CHANGED(4568) 2019-12-22 03:56:13.830 -0500 hc-800 [4507] INFO: FireEvent: Driver Keypad Dimmer(460) fired event VARIABLE_CHANGED(4568) 2019-12-22 03:56:14.376 -0500 hc-800 [4507] INFO: FireEvent: Driver Upstairs Hallway(464) fired event VARIABLE_CHANGED(1001) 2019-12-22 03:56:14.376 -0500 hc-800 [4507] INFO: FireEvent: Driver Upstairs Hallway(464) fired event Light Level Changed(5000) 2019-12-22 03:56:14.378 -0500 hc-800 [4507] INFO: FireEvent: Driver Keypad Dimmer(463) fired event VARIABLE_CHANGED(4570) ... more light level changed events AFAIK this hasn't happened before in the ~5 years I've had the system. I'm going to reboot the switches involved and then the controller, but I'm wondering if anyone else has experienced phantom key presses like this. The click on the "Bedtime" button is especially concerning since it turns off all of the house lights.
  4. If anything is controlled via IP rather than IR, the most likely culprit is that the IP addresses changed due to the power failure and the C4 has the old IP addresses in its configuration.
  5. The item was sold on 2020-07-17. Selling a used CCZ-T1-W thermostat. The unit is in good condition... just a couple of spots of paint on the back from where it was attached to the wall. It's on firmware 3.25.27, which I believe is the latest. Asking US$50 or CAD$65 plus shipping.
  6. Yes, but only if you need a sensor object in the project for the sake of programming or binding. The issue is that the panel side of that binding doesn't even appear in Composer. If it did, then the [Add Zone Drivers] action button would/should create the contact and wire it up, but it doesn't. It only adds objects for the first 12 zones:
  7. I don't think so - I don't think the new zones even show up in the list of contact sensors until they show up in the top half of that display. A lot of zones might not have/need any bindings unless you plan to use them in automation programming.
  8. I don't have an issue with the Control4-supplied driver other than this, so I'd rather not drop another $180 on the problem.
  9. The driver is: Just to be clear, the only problem I'm having is that I can't get the top half of the security panel properties display to expand to 14 zones from the original 12. The Android C4 app and the Composer status for partition 1 know about the extra 2 zones, but I can't change their name & type since they're not in the list above.
  10. The panel is a PC1832. I'll try enabling auto scroll mode to see if that does anything. As an aside though, when my system was upgraded to OS 3.1 the security panel driver had to be completely redone (I was on 2.8 previously). I never had to do any of this stuff when the tech remotely updated my system. The newer driver pulled the zone names & types the first time through, it just doesn't want to expand the [Zones] tab portion of the properties to include the new zones.
  11. I've got one of the nice PTK5507 touchscreen keypads upstairs. The original (builder-supplied) PK5501 is down in the basement near the panel, but it doesn't get much use unless someone is doing stuff right at the panel. The touchscreen has a [Broadcast Labels] button in its installer menu. I used that as well as the *998* option and it hasn't seemed to make any difference for getting the 2 extra zones to show up in Composer.
  12. I just tried that and then did "read from panel" again... no change :-(
  13. I've got a DSC security panel using the IT-100 serial interface. It's working fine with my C4 system (HC-800) running 3.1.0, but I just added two more security zones and I can't get Composer to show the extra zones. In the panel properties I've bumped up the number of zones by 2 and added those new zones to the partition 1 list. I've clicked on the little "read from panel" button at the top right of the properties page several times and I can see from the debug log that it knows about the new zones (I went from 12 zones to 14): ReceivedFromProxy(): READ_PANEL_INFO on binding 5001; Call Function PRX_CMD.READ_PANEL_INFO() ZoneInformation:SetDataGuardFlag for Zone 1 to false ZoneInformation:SetDataGuardFlag for Zone 2 to false ZoneInformation:SetDataGuardFlag for Zone 3 to false ZoneInformation:SetDataGuardFlag for Zone 4 to false ZoneInformation:SetDataGuardFlag for Zone 5 to false ZoneInformation:SetDataGuardFlag for Zone 6 to false ZoneInformation:SetDataGuardFlag for Zone 7 to false ZoneInformation:SetDataGuardFlag for Zone 8 to false ZoneInformation:SetDataGuardFlag for Zone 9 to false ZoneInformation:SetDataGuardFlag for Zone 10 to false ZoneInformation:SetDataGuardFlag for Zone 11 to false ZoneInformation:SetDataGuardFlag for Zone 12 to false ZoneInformation:SetDataGuardFlag for Zone 13 to false ZoneInformation:SetDataGuardFlag for Zone 14 to false SecurityPanelCom_ReadPanelInfo Starting Timer: OutQueue Starting Timer: Info The mobile app shows the new zones, but just as "Zone 13" and "Zone 14". It displays their open/closed status just fine, so most of what I need is working, but the "Zones" tab in Composer never adds extra rows to its list of zones to let me edit the names and the zone types. I suspect that the zone sync from the panel isn't working 100% because the mobile app shows the default zone names rather than the names I assigned in the DSC security panel (those show up correctly on my DSC touchscreen so I know they're configured correctly at the panel). Clicking [Refresh] from the Actions tab doesn't help, nor does [Add Zone Drivers] - it just adds drivers for the original 12 zones. Any ideas on how to get the two new zones to show up in the zone list so that I can edit their names and types?
  14. Good to know - thanks. At least I know it's not something I misconfigured.
  15. I'm running the app (3.1.0.352) on a Kindle Fire HD 8" tablet. The only issue I've noticed is that the Kindle tablet shows up in the My Account / Users & Devices / Devices section of the customer web site, but not in the My Automation / Notifications / Devices section, and I don't get any notifications on the tablet. I'm getting notifications on my Android phone and they show up in the Notification History of the web site. Do I need to do something extra to get notifications to appear on a Kindle tablet?
×
×
  • Create New...