Jump to content
C4 Forums | Control4

rosenqui

c4Forums Member
  • Posts

    57
  • Joined

  • Last visited

Posts posted by rosenqui

  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. 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.

    IMG_20191205_154115.jpg

    IMG_20191205_152935.jpg

    IMG_20191205_154046.jpg

  5. 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.

  6. 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.

  7. 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?

  8. 44 minutes ago, JoelC said:

    @rosenqui Unfortunately, push notifications are not supported on the Amazon fire tablets. Amazon uses a different push notification service than Google. Currently, we don't have plans to implement Amazon's push notification service in the Android app.

    Good to know - thanks. At least I know it's not something I misconfigured.

  9. On 10/2/2019 at 11:30 AM, JoelC said:

    Amazon got back to us. They did something on their end and the Control4 OS3 app is now live on their app store.

    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?

  10. On 6/7/2019 at 7:39 PM, JoelC said:

    ...
    Also, VPN does work on Android as long as the app has connected one time.
    ...

    That's only true if WiFi happens to be active 🙍‍♂️. If you're out & about and not connected to any WiFi, but have your VPN active and tunnelling over the cellular IP network you get:

    Unable to Connect

    Please join a WiFi network connected to your system, or contact your dealer to enable Anywhere Access through 4Sight.

  11. I've got an HC800 running 2.8.2 that I'd like to get upgraded to 3.X. I'm requesting rough estimates for a remote upgrade - please specify if the estimate is in USD or CAD (I'm in Canada).

    The red-button UI is configured to display on the living room TV at the moment, but we never use it so it can be deleted.

    I have a bunch of Sonos devices but we always control things via the Sonos app. The Sonos involvement of C4 is mainly some programming on keypad buttons to start a zone playing a streaming radio station. The main thing it looks like I'll have to give up is the old Sonos announcement capability - I'm currently using it to play a doorbell sound in certain zones without killing the current audio source.

    I don't have any C4 touchscreens, just Android devices and a bunch of SR-250 remotes.

    Feel free to post publicly or DM me with a price if you're able to help out.

    Thanks in advance,
    Eric in Ottawa

  12. For those (like me) who find this thread when doing a Google search for ELK-930 AND Control4, I wired mine up this way based on the above advice:

    OUT  <----->  +12
    NEG  <----->  SIG <--+
                         |
                  GND <--+ 10k resistor

    I added a doorbell contact device to the project and then connected it to CONTACT 1 on the HC800.

     

    I found the /var/log/debug/driver_event.log file helpful to tell if the controller was seeing any change in the signal. If so, you get events like this (assuming the device is named "Doorbell"):

    2015-05-07 08:14:48 -0400 home-controller-800-XXXXXXXXXXXX [3462] INFO: Driver Fan Speed Controller(94) fired event Unknown(4567)
    2015-05-07 08:14:48 -0400 home-controller-800-XXXXXXXXXXXX [3462] INFO: Driver Keypad Dimmer(250) fired event Unknown(4568)
    2015-05-07 08:14:51 -0400 home-controller-800-XXXXXXXXXXXX [3462] INFO: Driver Doorbell(396) fired event Unknown(1000)
    2015-05-07 08:14:51 -0400 home-controller-800-XXXXXXXXXXXX [3462] INFO: Driver Doorbell(396) fired event Closed(2)
    2015-05-07 08:14:51 -0400 home-controller-800-XXXXXXXXXXXX [3462] INFO: Executing command (EXECUTE_MACRO) on driver Macros(260)
    2015-05-07 08:14:51 -0400 home-controller-800-XXXXXXXXXXXX [3462] INFO: Driver Macros(260) fired event Unknown(4)

    I did this to get only the Doorbell events since you tend to get a lot of activity from switches etc. in that log file:

    /var/log/debug# tail -f driver_event.log | grep Doorbell

    So far I haven't had any false positives or missed button presses, but I'll keep an eye on it. If anyone else has wired theirs differently I'd be interested to hear how you wired it & why.

×
×
  • Create New...

Important Information

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