Jump to content

brente

c4Forums Member
  • Content Count

    94
  • Joined

  • Last visited

  • Days Won

    2

brente last won the day on April 14 2016

brente had the most liked content!

About brente

  • Rank
    Control4 End User

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

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

  1. It seems as though it is the same data from the 2017 hack that pulled the user info from this web site...
  2. @c4009 - I am not familiar with the use of “*” in front of “STAY” feature and don’t see any reference to this in the nx8e or keypad manual. From your description, it sounds like doing “*STAY” will bypass all of the internal sensors except one, but still set the alarm for instant Mode (as STAY does, versus EXIT mode) - I’ll have to try this on my panel to see if that works (wonder what zone type value determines this?). if correct, from what I am aware of, there is no way to do this from the Control4 security UI. I am not familiar with alarm.com and any functionality that they offer. Sorry. You can manually bypass zones from the c4 ui through the Function button, but it won’t let you “unbypass” zones that are automatically bypassed when arming the through STAY - it will only let you bypass additional zones that are not automatically included already.
  3. Hi - unfortunately, from my experience with the 584 driver, you can’t access this functionality from c4 programming (Or a macro) directly. I’d have to double-check, but I believe that the driver does support and use this internally (I think by the functions capability as you saw - that capability emulates the interlogix keypad functionality), but you’d need to use LUA programming to access it and/or expose for c4 programming (non-trivial) - it is not exposed outside of the driver currently. May not help you, but a couple of things: - the 584 driver supports the ability to bypass an open zone automatically IF you have the automatic bypass setting enabled on the panel (the 587 driver did not). You can see this with an open zone by attempting to arm the panel from the c4 ui (can’t use an interlogix touch panel to do this), the c4 security panel driver will report a zone is open, and if you continue the arming process then the 584 driver will automatically bypass that open zone - when the error is displayed, you can manually close the zone, then arming will continue without bypassing the zone. However, you won’t be able to know whether the zone was bypassed or not beyond arming time. - if you want to bypass a specific zone automatically when arming, you can also set the appropriate property for that zone in your panel settings (e.g., automatically bypassing internal motion detectors when arming for STAY mode) - this is a function of the panel and not c4 (you may use this already). Still, not exposed programmatically. myself, I just manually bypass a zone when needed using the panel...
  4. Attached are the full 584 driver instructions that are included with the "NX-584 RS-232 Automation Module" driver (the settings that @sweeper154 posted above are included in this documentation) - note that these instructions are also viewable from the Documentation tab for the 584 driver in Composer Pro or Composer HE. The instructions call out all of the panel/module settings that the driver expects. Changing the panel settings does require some knowledge - be sure to note current settings before changing in case you run into issues. You can find instructions on how to change the panel settings in the 584 module instructions or with in the nx8e instructions. Some things to be aware of: - the 584 driver reads all of the zone information (number, type, description, etc.) from the panel in several ways: when the driver is first installed, by using the action button, or when the controller is restarted. You can try the action button to refresh the zone information without restarting the controller. - if you have the panel settings correct and the zone count shows in composer (pro or HE), but the zone names are not displayed as they are on the keypad, you may need Control4 to fix this on your controller. It seems as though the driver (and older versions) doesn’t clean itself up completely so leaves data on the controller that can’t be removed by simply deleting the driver and restarting the controller. I did not have this problem going from the 587 driver to the 584 driver, but @Scrib ran into this, but I’m not sure exactly what Control4 did (they knew what needed to be done and it was quick). - if you turn on logging on composer, you should be able to watch the status messages that the driver generates as it processes the zone information read from the panel to aid in troubleshooting. - after the zone information is read correctly, you will be able to bind sensors to the zones to use the open/closed state for programming. once everything is up and running, it works well... documentation.rtf
  5. @sweeper154 - since you have an nx-8e, assuming you’re using the built in 584 functionality? (Instead of the external 587 module). Ensure that you’re using the 584 driver per above. For panel settings, check the driver documentation for the default panel settings to use (which include baud rate, etc) - I believe you can see this from composer HE in the documentation tab for the driver, or your dealer can send to you. If you were using the 584 driver before upgrading, the driver should still function fine in the latest os3 update. If settings are right and it’s still not working, then their may be a driver issue on your controller - another user had that problem and c4 support fixed it (hopefully you won’t have to do this though).
  6. Have your dealer search for the "NX-584 RS-232 Automation Module" driver - that should show up in their Composer Pro. It is compatible with OS3+
  7. Not sure what's wrong, but I was using the AV7702 driver ("receiver_Marantz_AV7702_serial_ip.c4i") with an AV7702 for years and it worked great. When I replaced the AV7702 preamp with an AV7705, I kept the AV7702 driver in place as the functionality didn't really change, and I have no issues with volume control over IP. So, might want to try one of the older drivers. Also, see that you're using the EU version of the driver - no idea how it differs from the regular driver... edit: I'm using the AV7702 driver under 2.10.6 and it works great. No idea if issues exist for higher C4 versions...
  8. Great. Be sure to follow the instructions included with the driver for the panel settings. Reach out if you have any trouble
  9. It depends on what cable you have connected to your c4 controller (on my system, I actually have a null modem cable plugged into my controller). The 584e has a male db9 connector, so at least that side needs a female side. If you don’t need a cable, you can also go with a null modem adapter that fits in line with the cable.
  10. @Scrib it's relatively straight forward. With the 584e connected to the system, just entering and exiting programming mode on the NX panel should add the 584e to the system (you don't need to remove the 587e - just disconnect it) - note that there is a delay after exiting as the panel checks for devices. In programming mode on the NX panel, you need to set it up per the 584e driver instructions (the instructions tell you settings to use) - there are only a few changes compared to the 587e configuration. Note that the driver says to disable any unused partitions/zones as otherwise they will show up in the C4 interface. The instructions say that a NULL modem cable is needed - not sure that's the case with the 587e, but I had to change my wiring to get the 584e to work with my cable (so, I'm thinking that the 587e didn't need a null modem cable). When all connected up, the 584e driver will report "Driver Initializing" while it reads in the partition/zone information from the panel. If you turn on trace Log Level in the Properties page of the 584e driver you can see the communication between the panel and the driver as the initializing process works - if you don't see any activity, then I'd check your cable... the 584e installation manual should come with your 584e and has the installation instructions to follow. You can find it here too: https://www.surveillance-video.com/media/lanot/attachments/customimport/NX-584E-Installation-Manual.pdf Reach out if you have questions...
  11. @ERDrPCI agree with you that running the programming after an event occurs (e.g., weather alert event) would be the most efficient way to check the zones. I have an idea about getting the open zone names as you need, but need to find time to mess with it. Give me a week or so and I'll let you know what I come up with...
  12. Not sure that the integration is any better from the 587e driver to the 584e, but here's some of what I see (may be incomplete): - when the 584e driver is put into an appropriate Log Level, you can see that the driver has access to all of the panel events/messages and will log/display all the alarm panel events that it sees, BUT not all of these events are exposed outside of the driver - after the 584e driver queries the panel and adds the zones to the system, you can connect contact sensors (or other) to the 584e driver. The sensors will show the open/closed state of as reported by the panel. You can then use the individual sensor state to trigger programming or to query the open/closed state. - the partition OPEN_ZONE_COUNT variable will indicate the number of zones that are open when arming is attempted. If zero, then all closed. if greater than zero, then something is open. - the "Arm Failed" partition event will be triggered if a zone is open when arming is attempted. The driver, however, will not report back what zone is open. You could (manually) query each zone to see which one (or more) are open if this event is triggered. You could create a programming macro that would add all open zones to a variable, and then use that variable to report open zones. - the "Disarm Failed" partition event is NOT triggered if an invalid alarm PIN is entered to disarm the alarm. I'd say this is a BUG in the 584e driver. As a workaround, you could watch the DISPLAY_TEXT partition variable for a change to the string "Operation Rejected by Panel" which is the error message displayed when an invalid code is entered. - the alarm arm/disarm panel will allow logging of the arm/disarm event and will report that a PIN was used, but will not display the actual PIN used (it's obscured) - (per above) if an invalid PIN code is entered, DISPLAY_TEXT partition variable for "Operation Rejected by Panel" which is the error message displayed when an invalid code is entered - when an alarm is triggered, the DISPLAY_TEXT variable (and panel display) will not report which zone causes the alarm to be triggered. The "OPEN_ZONE_COUNT" will indicate the number of zones open. as said above under "Arm Failed" partition event, you could have some code to manually check each zone and store their state in a variable to then report which zones triggered the alarm - could be the same programming macro code so would only have to code it once. UPDATE: the DISPLAY_TEXT variable does show the zone that caused the alarm, but the value stored in the variable changes very quickly so odds are if you try to display the contents, it won’t show the value as expected - you can reproduce this by using programming to show the value when it changes (e.g., include it in an email or a notification). - the ALARM_STATE partition variable does not appear to indicate whether an alarm has occurred or not. BUG. I'd think that it should, assuming that the variable is used to indicate the state of an alarm - its not documented in the driver so it's purpose is unclear. UPDATE: this variable seems to indicate whether the panel is in an alarm state (set to 1 for true), or not (set to 0 to false) So, while the driver doesn't make it easy to get access to the panel details, you could probably accomplish a lot of what you want with some work (a lot of work) by adding extra programming to the project. Too bad that the driver isn't more robust to simplify the reporting of the type of information that you are asking for. No idea if any of the other panel drivers report that information either.
  13. coming from a 587e, the 584e works great with the NX8. One thing to be aware of is that the 584e requires a NULL modem cable, whereas the 587e uses a straight through cable. Going from the 587e, you will also end up removing all of your contact sensor bindings from the project as the 584e driver will query the panel/keypad directly and pull all zone/partition information and settings and will not use the separate contact sensor bindings that the 587 driver needed... correction: you don't need to remove your existing contact sensors and can bind them to the 584e driver if you want to use their state to program against
  14. On iOS 13? If so, seems to be a known touchid bug in iOS... https://9to5mac.com/2019/09/30/ios-13-iphone-touch-id-login-bug/
  15. This might help you... Depending on the actual driver that you are using, you may be able to display panel information through the email agent or the push notification agent by using text like this in the message body to reference the alarm variable state info such as: ${ROOM->SECURITYSYSTEMNAME::ALARM_STATE} ${ROOM->SECURITYSYSTEMNAME::DISPLAY_TEXT} ${ROOM->SECURITYSYSTEMNAME::TROUBLE_TEXT} Where "ROOM" is the name of the room that the security panel driver is assigned to, and "SECURITYSYSTEMNAME" is the name of the driver as used in the room - replace this text with the names from your project. The DISPLAY_TEXT variable should show the same information that would be displayed on a keypad panel, and the TROUBLE_TEXT would show any trouble messages that the panel reports. Depending on the version of the driver and security proxy used, you should be able to view the panel UI through the control4 user interface to view the alarm system state, then cycle through and display messages that would show on a keypad. So, if you're trying to arm the alarm, you should be able to see the alarm state to indicate if a contact is open and which one it is. If, however, you want the security panel zones to appear in the Control4 ui under Security->Locks & Sensors so that you can view the state of the actual sensors, then you do need to add a contact to each of the appropriate rooms and bind them to the security panel driver as lippaVisual says. If needed, you could probably check each contact sensor to see its state, but I found the just using the DISPLAY_TEXT variable close enough for my use...
×
×
  • Create New...