Jump to content

Don Cohen

c4Forums Member
  • Content Count

  • Joined

  • Last visited

About Don Cohen

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
  • Interests
    Nature and Wildlife Photography, Technology of all types, Volleyball, and most recently Control4

Recent Profile Visitors

197 profile views
  1. Gotcha - thanks. Makes sense. Do you see any issue with this programming being executed every time the temperature changes? Is there any better way to address the Event side of the programming?
  2. Appreciate the reply. Can you flesh this out a bit more? I can't quite grasp what you're suggesting, and how it's different from the "If" I already have in there.
  3. Some follow-up here. Now that outside temperature is over 75, I was able to test this out a little. I manually put the Thermostat on Heat Mode, then 'Executed' the Programming to see if it switched. First, using the "OUTDOOR_TEMPERATURE_F" Variable didn't seem to work, as it remained in Heat Mode when I executed the programming. I then tried "TEMPERATURE_F" and when I executed the programming, it switched to Cool Mode. My question now is whether or not this is the 'best' way to do this. As it stands now, any time the Temperature changes, the Programming would be executed. Will this be a potential source of trouble, since there will be regular changes throughout the course of the day, although they wouldn't be frequent. Thanks. P.S. Actually, since the "OUTDOOR_TEMPERATURE_F" variable didn't seem to be the one I wanted, I need to change the Event that triggers this to be the same "TEMPERATURE_F" that did seem to work.
  4. I installed the one you linked to, several months ago, and am very satisfied with it. I'm actually using it outdoors, semi-protected, at my front door. They don't guarantee it will last for that application, but so far so good, and I have had others report long-term success with it, when outside, unprotected.
  5. I want to configure my system such that when the outdoor temperature is over 75 degrees, the Thermostat (Control4) is set to Cooling Mode, and when it's less than 65 degrees, it gets set to Heating Mode. (And I do understand there is an Auto setting that will work similarly, but for a few reasons, I'm not wanting to use this mode). There is no external temperature sensor, but the outside temperature is always shown on my T3, which I assume gets it based on the latitude and longitude in the Project configuration, or perhaps somewhere else. What I'm wanting to know is what to use as the Event to configure the programming. When I look at the available Thermostat Variables, I see "OUTDOOR_TEMPERATURE_F", "TEMPERATURE_F" and "Control4 Outdoor Temperature". I'm not seeing reference to wherever the T3 gets its temperature reading from. Which, if any, of these Variables do I use, or is there a different/better way to do this? Thanks.
  6. See my post above - I added the Universal Disney+ Driver, and using the Bravia App Selector, was able to Connect this to my Sony 900E TV. Same for a few others: Acorn, CBS All Access). As Mitch indicated above, since it involves adding a Driver, and establishing a Connection, this is a dealer function. Actually that's a guess on my part, since I haven't played with HE, but if Mitch says that's the way it is, that's good enough for me.
  7. I have no idea if this is available, or would with with your LG, but I have a Sony XBR 900E series TV, using an IP Driver to control it. The Driver had several mini drivers for some apps, but not for all of them. I searched and found Universal Drivers for what I needed (Acorn, CBS All Access, Disney+, etc.) and using the 'Bravia App Selector' was able to add these, and Connect them to any of the 15 available channels. I can access them in a Navigator, and also created Amazon voice scenes for them. So I can just tell Alexa to 'Turn on Disney+', or whatever app I want, and it loads. For me, much easier than grabbing a navigator. Again, LG might not allow this functionality, but it works well with Sony. ETA: I had another look here, since it had been a while since I set this up, and for the Sony TV, I used the "Bravia App Selector Driver" - adding one for each App I wanted to access. The instructions for the procedure are specified in the Driver. I did *not* use the Universal Drivers in this case - it was the App Selector Driver, which was then customized to access the App already installed on the TV. I did use the Universal Drivers when I added these Apps to the Roku in my Theater Room - so Mitch seems to be correct that the Universal Drivers can be used with Roku, but not with, for example, a Sony, or likely LG, TV. Just wanted to correct my faulty recollection of how I set this up.
  8. I have the DCX-3600-M and use the Scientific Atlanta Explorer 8300HD [IR] Driver, and it seems to work just fine with its built-in commands.
  9. I haven't come across that term before, but looking it up, yes - exactly! I was going to use the term 'Bonehead Programming' but your term has much more panache!
  10. I finally figured it out. I'm a bit embarrassed, but it was a result of some recently added programming. When we're watching a movie, when it's over, hitting the 'Room Off' button results in an abrupt, harsh change as the system turns off. I had previously added a Lighting Scene to slowly turn up the lights, which helps, but I wanted the sound to do the same thing, to ramp down gradually, rather than cutting off abruptly. The Driver itself isn't editable within Composer Pro to accomplish this, and not knowing how else to do this, I re-programmed the Control4 button (since it isn't used in this room). I programmed it to Ramp the AVR Volume down, put in a delay of 8 seconds, and then issue a 'Room Off' command. This aspect of it works fine. But what was happening is that the Ramping Down to 0 hadn't completed when the Room Off command was issued, and so the EA-3 continued to issue commands to ramp the volume down, and the AVR was off after 8 seconds, so couldn't respond. I changed the Delay to 15 seconds, and that seems to be enough time to ramp the volume all the way down, that programming completes, and the AVR then turns off normally. Hopefully someone can learn something from this mistake - good idea, with not so great execution!
  11. Yeah, I was thinking the same thing. Any clues on what might be going on here? I just physically unplugged and replugged the EA-3, in case that would do something more than a reboot from within. ETA: Any other troubleshooting steps to take before I call?
  12. Further follow-up: Yesterday morning, I had disconnect/reconnected to Serial 1 in Connections. Initially this resolved the problem, and it performed normally through the day and evening. I woke up this morning and checked it, and once again, it was infinitely cycling through the same sequence as reported above. I disconnected the Serial 1 connection in settings, unplugged and replugged the AVR, disconnected the Serial cable, and then replugged it into Serial 2. I made the connection to Serial 2 in Connections. No change, as soon as I enabled Logging, that same cycle was still repeating in the Lua screen. I disconnected it in Composer Pro, so no Control connection was present, physically removed the Cable from the EA-3, and that same cycle was still being generated, repeating indefinitely. What the *bleep* is going on here? Is there a physical defect in the EA-3? Is there a problem with the Driver? Remember, this problem first appeared with the original driver, which had been in place for 9 months with zero problem, same physical and logical Connection, and didn't go away when I updated the driver to a more recent version. It seems that would argue against a Driver issue, but who knows. There has not been a firmware update to the AVR since many months before this problem started. To repeat from my OP, I'm on 3.1.0, and have been since the fall. I'm hoping somebody here can provide some insight, as this is a real problem, especially when wanting to demo the system to potential customers. The lack of response is worrisome, suggesting this is such an oddball problem that nobody has seen it before, making it even harder to solve.
  13. Some follow-up here. So I watched a movie last night, and the AVR turned on and off as it should. No issues. I got up this morning, opened Composer Pro, went to the AVR, set log to Print, and found this sequence endless repeating: 07:51:43:469 SendToSerial:MV00 07:51:43:470 volRampTimerCount is : 1 07:51:43:520 VolRampTimer expired! 07:51:43:521 VolRampTimer emit! 07:51:43:523 SetVolumeMultiStep called! 07:51:43:524 SetVolumeStep direction DOWN! 07:51:43:525 SetVolumeMultiStep :: Vol stage Low! It would have gone forever, and presumably was going on throughout the night. No way to know when it started. Naturally, when I turned on a Listen session, the AVR didn't turn on, even after a couple of attempts. I then disconnected the binding to Serial 1, waited a minute, and then reconnected it. I heard the AVR turn on and off a time or two. Eventually it settled down, and the AVR was then responsive, turning on with a Listen session. The file below contains the Lua text from when the Binding was reconnected to Serial 1. Does anybody have any idea what is triggering this odd behavior? Bindings hadn't changed, or been touched, when this started happening. Defective hardware - EA-3, Cable, AVR?? The fact that Control4 was sending out that endless string would suggest something on the EA-3 hardware or OS side, since the AVR was off all night, but this is just a guess. Any suggestions on further trouble-shooting, or likely causes, etc., greatly appreciated! Serial1-Binding-Disconnected-Reconnected.txt
  14. Thanks again for the reply. Nothing for IP with the Marantz on the Network tab for connections. See the screen capture below. For the lack of anything else to try, I was thinking of plugging the cable into a different Serial port (and changing the connection accordingly). I wondered if there were something 'funky' going on in the EA-3 itself. If that doesn't fix it, then I guess the next step would be a different cable? Any other trouble-shooting tips or suggestions appreciated.
  • Create New...