jfh

c4Forums Member
  • Content count

    986
  • Joined

  • Last visited

  • Days Won

    18

jfh last won the day on January 6

jfh had the most liked content!

About jfh

  • Rank
    Control4 Guru
  • Birthday

Profile Information

  • Gender
    Male
  • Location
    Colorado
  • Interests
    I enjoy finding new ways to make my Control4 system useful and would love to learn more about how C4 works.

Recent Profile Visitors

1,205 profile views
  1. Go to the Monitering tab on the left, find the garage door and click the Properties page. Enter your userid in the correct field, hit SET to the right. Repeat for the password, repeat for the other door(s). Then go to the Actions page and click get Devices (I forget the exact text)
  2. HouseLogix driver working after update to 1.5 I have polling set at 60 seconds. What do people suggest? I have lights that show whether doors are opened or closed, which is why I poll so frequently. Does the door status automatically update when the door opens or closes? If so, then maybe I don't need to poll so often.
  3. It looks like the HouseLogix driver was updated to version 1.5 on 1/30/17 to support API changes. Looks like I am on version 1.4. Will update here after my dealer updates the driver. (Just forced an auto update check - didn't download the newer version of the driver)
  4. Would you mind asking him exactly what he did?
  5. Using the Houselogix driver, I get a similar request rejected message but with [string "Lua Code"] : 368: invalid character at value start: < (ReceivedAsynch) at the end. Sure seems like a problem with the HouseLogix driver. I've opened up a ticket, but haven't heard anything.
  6. I think autocorrect tripped you up. You have the HouseLogix MyQ driver and it's working now, but wasn't before? What did you do to get rid of the error? Is there a new driver version that needs to be installed?
  7. I have the same problem with the Houselogix driver
  8. I started doing this until I realized it was a duplication of effort. I deleted all the variables and just check/change the state directly with the specific experience. It made a lot of things simpler, though it was a lot of work because a lot of the on/off type experiences were dummy generic light switches (Chowmain driver). Now the things that don't make sense as "lights" are experience buttons under watch or listen or, for state variables I want to monitor or change, in a dummy room called System.
  9. When using Chowmain Experience buttons - when programming, does turning on a button function the same as setting the device on variable to true? If am using conditionals under Device On to see if a button is on or off, but using the on/off device specific function to turn a button on or off. Is this the proper way to do this?
  10. Discover Devices alone did not work for me. I had to go to My Control4, deselect/save and reselect everything. Then after Discover devices everything was fine. i was also migrating from an 800 to an EA5 at about the same time, so it's possible that's why I needed the unselect/select in addition to discover. But I don't understand how CLOSE is going to work if the new VS driver doesn't have a CLOSE event.