Jump to content
c4forums | The Control4 Community

brente

c4Forums Member
  • Content Count

    97
  • 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. Not sure if many others are still using the iOS control4 for OS2 app, but I've noticed that with iOS version 2.10.17 there is a noticeable 6-7 second delay when trying to activate a video device by tapping the device icon in the lower left corner of the Control4 UI after switching away from the Control4 app to use another app on an iOS device. Not sure if it's an iOS 14 issue, or a bug in the Control4 app, but it's 100% reproducible. Oddly, it doesn't seem to happen with an audio device (e.g., sonos). I've submitted feedback for the Control4 app beta via iOS TestFlight, but haven't seen any
  2. Darin - I never noticed this before (probably just never encountered this scenario), but here’s a UI display bug with the latest Control4 os2 2.10 app on iOS... When using the Control4 app on an iPad Pro, if the app is open in horizontal position and the security proxy is open, then the user switches to another app by swiping up from the bottom, then launches the Control4 app again, the Control4 app thinks that the orientation of the iPad Pro is in vertical mode instead of horizontal mode. Repro 100% Steps to reproduce: - orient the iPad to horizontal mode - launch the Contr
  3. @c4009 Looking into this, I learned that on the NX8/NX-8E panels the "*" key allows access to secondary arming settings (along with secondary functions, which I was aware of). So, using "*STAY" enables "Night Mode" for Stay and arms all zones (including interior zones), and "*EXIT" enables "Silent Exit" for Exit/Away arming. These aren't called out in the Interlogix manuals. Examining the Control4 Interlogix 584 driver, I saw that the current driver provides access to the secondary Silent Exit arming setting (as "Silent(Away)"), but not the Night setting. Interestingly enough, the
  4. It seems as though it is the same data from the 2017 hack that pulled the user info from this web site...
  5. @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. Sor
  6. 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
  7. 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 se
  8. @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
  9. 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+
  10. 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
  11. Great. Be sure to follow the instructions included with the driver for the panel settings. Reach out if you have any trouble
  12. 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.
  13. @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
  14. @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...
  15. 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
×
×
  • Create New...