Jump to content


c4Forums Member
  • Content Count

  • Joined

  • Last visited

  • Days Won


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. @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...
  2. 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.
  3. 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
  4. 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/
  5. 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...
  6. Looks like I have a control4 bingo! Ha ha ha! 🤪 while the ui customization seems nice, if that’s all that 3.0 brings for now, no hurry to upgrade for most current long time customers given the expense of new hardware and the pain of incompatibilities...
  7. The netflix bug exposed a flaw in the mediatek network/media controller chip used in the yamaha receivers (rx-v673 in my case). My guess is that the v475 and 575 use the same chip as the 673 (all of which have no built in wifi). The 677 has built in wifi, so may be using a newer version of the same chip. I think that the 1079 may use a different chip entirely (a yamaha guy told me that some newer models did change from mediatek, but i don't recall which models - the '9' at the end of the model number may be significant, but i may be mistaken). So, if the issues are happening because of the use of the mediatek network chip, your only option would be to get a receiver that used a different component. Unfortunately, just buying a 'new' model won't assure this of being the case, as even current model denon/marantz (and pioneer, etc) receivers use it. Sadly, from yamaha's side, they pretty much wrote the netflix issue off on netflix instead of acknowledging that it was their fault (or the fault of their supplier) caused by not handling the bad network packet gracefully, so I wouldn't hold my breath expecting a solution from them unless you can completely isolate the problem and document it for them to reproduce...
  8. Did you get a chance to run a wire trace? what symptoms do you see when the amps crash? Is it that they drop off the network? Can you ping them or do they show up in a map of network devices? How do they recover from the crash (by themselves, by power cycling, etc)?
  9. From my experience, the problem that i encountered was only caused by the ios netflix app, and would occur just by launching the app. The android app worked fine, and did not have the issue. Just make sure you have the latest versions and you should be fine regarding that as a cause.
  10. Well, for me, i have a network cable run to the projector, but not serial or ir, so just a choice. One advantage of ip is you can then use another app to access and control the projector, which you can't with serial (or, i can use the jvc ir remote). Not necessarily an advantage, but just an alternative means to control. I do have extra wires run to the projector, so could do serial, but ip should work fine - that is, unless there's a c4 bug that needs fixing (not sure yet) I had an older rs55, and with the c4 jvc driver circa 2012, it worked like a charm. With the 2016 jvc, c4 released a new driver, and i figured that it would work better than the old one. Silly me... I plan to go back to the old driver (since the ip control commands have not changed), and then update it as needed (the new jvc driver does support some additional control commands, but easy to add to the old driver).
  11. vitali - Thanks. Bummer. The older JVC driver worked great with an older JVC projector, so I know it's possible to use Ethernet reliably. Will have to look into it further...
  12. I'm using a 2016 JVC projector and controlled with C4 (2.8.2) over ethernet, and since day 1 when I set it up with the latest JVC projector driver, C4 would show the status of the device going between "online" and "offline" status. When the projector is offline, it won't respond to commands, so won't power on when instructed to, and won't power off (or do anything else when in the offline state). Doing a trace of the driver, C4 is sending a "ConnectionStatusChanged" proxy command telling the driver that the projector is offline, so the driver tries to reconnect. However, when I run a PING loop over the network to the projector, the PING never drops and stays steady, indicating that the projector never physically drops the network connection. As a test, I tweaked the JVC projector driver to ignore the offline status message and always show the projector as being online, and now the projector responds 100% to C4 control. I don't think this is a driver issue, but seems to be an issue with the underlying proxy code that is reporting the network status. Anyone else have an installation with a JVC projector and having similar problems?
  13. FYI - Netflix did indeed release a fix for the bug that they had with their iOS app, and released it into the wild. There are two ways to get it: (1) launch the Netflix iOS app, and it should download the updated settings that it needs, or (2) download the iOS app update that was released today (8.3.0), which will also force an update to their settings and correct the bug. To ensure that you have the updated settings, if you tap the menu button in the upper left-hand corner of the Netflix app, scroll to the bottom, and check the version number, it should show at least "4.2.10-1" after the app version number. You should now be able to use the Netflix iOS app without causing the network functionality in the Yamaha receiver (or others) to crash... Hopefully this will fix at least one of the networking issues that Yamaha has.
  14. Not necessary. They are currently working on a fix, and I just tested it and confirmed that it works - both my Yamaha and Marantz receivers stay good. I am not sure exactly how the fix is rolled out, but expect it to be released very soon. I'll report back when I hear it's been deployed (it may be as early as tomorrow). Your tests do seem to confirm that the Pioneer receivers do use the same chipset as the Yamaha and Marantz/Denon, so I am confident that the fix will work those as well.
  • Create New...