Jump to content

brente

c4Forums Member
  • Content Count

    80
  • 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. 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...
  2. 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...
  3. 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...
  4. 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)?
  5. 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.
  6. 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).
  7. 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...
  8. 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?
  9. 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.
  10. 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.
  11. No worries. I haven't used mine much either, but was testing out my projector and saw it was skipping instead of scanning. I had thought that it worked before, but must not have. Given the crappy samsung remote, I figured I would try programming my AVR remote and that worked fine. Thanks for the original driver!
  12. Cyknight - does the scan forward, scan reverse, work correctly for you with your driver? I am using version 5 of the c4i driver and was finding that they both would just do a skip forward, skip reverse, instead of a scan. I was able to program a different remote to control the Samsung, and when I captured the button commands, I found that the IR codes were these... When I edited your driver to use these new codes, it worked as expected. FYI... Scan Forward 0000 006c 0000 0027 00ae 00ab 0014 0013 0014 0013 0014 0013 0014 0013 0014 0013 0014 0039 0014 0013 0014 0013 0014 0013 0014 0013 0014 0013 0014 0013 0014 0013 0014 0013 0014 0013 0014 0013 0014 00ab 0014 0039 0014 0039 0014 0039 0014 0013 0014 0039 0014 0013 0014 0039 0014 0013 0014 0039 0014 0013 0014 0013 0014 0013 0014 0013 0014 0039 0014 0013 0014 0039 0014 0013 0014 0039 0014 0039 0014 0039 0014 089d Scan Reverse 0000 006c 0000 0027 00ae 00ab 0014 0013 0014 0013 0014 0013 0014 0013 0014 0013 0014 0039 0014 0013 0014 0013 0014 0013 0014 0013 0014 0013 0014 0013 0014 0013 0014 0013 0014 0013 0014 0013 0014 00ab 0014 0039 0014 0039 0014 0039 0014 0013 0014 0013 0014 0039 0014 0013 0014 0013 0014 0039 0014 0013 0014 0013 0014 0013 0014 0039 0014 0013 0014 0039 0014 0039 0014 0013 0014 0039 0014 0039 0014 0039 0014 089d
  13. Yeah, from reading your description, it is a different issue. as an FYI, I have the following configuration and have not experienced any problems with C4 and my Yamaha receiver: - only one Yamaha on my network (RX-V673), but also a Marantz preamp. I have had more receivers/devices, but only the one Yamaha. - default IP port on the Yamaha. using DHCP for the IP address - have an HC250 in one room against an HC800 master - I am using the "receiver_RXA710_Network_DriverWorks_DestU_US_Yamaha.c4i" driver dated 4/30/2010 creation, 2/29/2012 modified (Control4 certified on 9/8/2011 for software released versions: 2.0.6, 2.1.0) - I am currently on 2.8.2 When my Yamaha drops off the network due to the Netflix bug, C4 shows that the Yamaha goes offline and seems to batch up any commands that are intended for it (e.g., volume changes, etc.) as you see, but I can fully control anything not related to the Yamaha such as other source media commands, with no apparent impact on the HC250 or HC800. When the Yamaha goes offline, the C4 log shows "Network Connection Down." until the Yamaha starts responding again, then the command queue is sent to the Yamaha and everything is good again...
  14. It would not surprise me at all. Do you use netflix on an ios device? If so, then yep. What i am curious about is what other apps have a similiar bug for those thst don't use netflix, but are having a similar problem? I have been having network flakiness with a projector, snd it eould not surprise me that if it was affected as well. you can easily see this: - display the network screen on your pioneer that shows ip/mac/connection status - fire up netflix on an ios device and start streaming a video - watch the network screen to see if it shows a loss of connection. Should happen within 20 seconds - terminate the netflix app, and the network connection should be restored btw - the bug in netflix was introduced in February, which directly aligns with when i started having problems...
×
×
  • Create New...