c4Forums Member
  • Content count

  • Joined

  • Last visited

  • Days Won


Cinegration last won the day on May 8

Cinegration had the most liked content!

About Cinegration

  • Rank
    Control4 End User

Contact Methods

  • Website URL

Profile Information

  • Location
    Denver, CO
  1. Houselogix supporting 3rd party drivers?

    Being a Control4 dealer (Diamond Level) and developing drivers since 2009 I wanted to put my 2 cents in. The main thing I've seen over the past 8 years, is products and solutions adapting to make the smart home experience better. I see Platform providers (Control4, Savant, Crestron) continually upgrading their user experience. This in turn requires the other manufactures to modify their approach at the solution. Both companies want to provide the best experience for their customers and this is where development companies come in. What a specialized development company brings to both parties is knowledge and speed. Knowledge in what each platform is doing, the benefits of the new user experiences they are bringing and the skills to make the new interfaces link with a manufactures particular hardware. Developers also bring speed. Companies have many layers of management and corporate goals. What a development company like Cinegration, Domosapiens or Chowmain brings is the ability to get an actual software product created, developed and distributed without the overhead and time it takes a typical company. What development companies have been missing has been a complete developer and dealer driver management system like DriverCentral. DriverCentral is it's own company (Not a development company or subject to similar fates like previous marketplaces). It was developed specifically to provide a vast array of tools both to the dealer and to the developer so each side can get to work on what they do best. Being a Control4 dealer and Developer gave us a unique insight into the issues and long term repercussions of smart software. The single biggest thing we saw was the 'marketplace' should not be controlled by a development company. Support. There is an understated assumption that support is always available. It's not, and good people and great support are hard to find. Since most of us development companies are only a handful of people (it's three of us at Cinegration for example), answering the 45-60 help desk tickets that come in is almost impossible. We subsidised this by selling our software through DriverCentral and using their help desk system. They have a full time tech support person on staff that is Control4 certified for the sole purpose of helping our dealers. Existing licenses. Development companies change distribution channels. That happens as new marketplaces with better tools and features come out. DriverCentral created an importation tool that allows them to upload any existing marketplace license table into theirs and give dealers the ability to manage those drivers on their customers systems. Do you need to have your stuff moved over? No. Should you, do you still have an iPhone 4? Future. We at Cinegration always want to provide the best solution for the hardware and software we can. To make that possible, new tools and systems had to be created. DriverCentral is just another way to move the customer experience into the future. Change sucks... and without it nothing exciting would ever happen. The key is making sure it goes as smoothly as possible and we feel DriverCentral can provide that to our customers both now, and 4 or 8 or 10 years from now.
  2. New Driver: Battery Agent

    On the 260 issue, we've found that the Control4 does not transmit the % correctly to director. The driver simply 'receives' the level from director then processes. If we get incorrect data, we process incorrect data. From testing we found that the 260's do not transmit their 'correct' % until you click on the driver in composer and wake up the remote. This 'forces' the remote and director to re-sync. We're testing some options as to how we can work around this. Are your units battery or charger based? All the other items (locks, shades, ca devices etc...) all correctly do what they are supposed to do from our testing. It's just the SR remotes that we've seen this issue. Thanks!
  3. New Driver: Battery Agent

    Hi! Sorry about the late responses. We are moving all our drivers to tomorrow. this has already been installed in the new release. We'll send out an official press release tomorrow. Thanks!
  4. New Driver: Battery Agent

    We use Control4's email notification in our driver. We do not offer a smtp server/push notification on this driver. In order for the driver to 'notify you' you would need to purchase 4Sight. This also gives you access to Alexa and other emails + remote login. the driver handles all the notifications automatically, just need to pay for the email service and it will work. Thanks!
  5. DoorBird Integration Driver Now available!

    I think you can. The 'tab' that is removed in HE is Connections and that's not used in this situation. Note: my explanation only explains how to change the video feed. Remember that you will also need to create an intercom group (put two touchscreens in it), assign that intercom group to the doorbird and Re-enable SIP (which sets all the settings you just changed). All of this you should be able to do with composerHome. Note: we only offer support to dealers but if you're computer savvy and like reading you should be fine. The driver download has pdfs and documentation that explain these areas. Thanks and have a great weekend!
  6. DoorBird Integration Driver Now available!

    There was a recent doorbird firmware that changed a security validation. We released an update the next day with the update and if you have auto-update, no further action is required. Thanks!
  7. DoorBird Integration Driver Now available!

    This is as designed. The reason is because a doorbell push is a 'broadcast' call to all touchscreens in the home. Once a call is accepted, the video is initiated. The doorbird's camera is only capable of handling 2 video streams at the same time. This means if you have more than 2 touchscreens in a home, the video must come 'after' the call is accepted. However, if you want to have the image show up before answer (i have 3 touchscreens at my house so i do this), you can specify 2 touchscreens and convert the video feed for the doorstation call to 'alternate camera'. This makes the video come 'with' the broadcast call thus allowing you to see who's at the door before pressing answer. Manually calling the doorbird will work from all touchscreens. Hope that helps explain it better and sorry about the confusion. This change in video is done under the intercom proxy of the doorbird in system design. If you change you need to refresh navigators for the effect to happen. Thanks!
  8. DoorBird Integration Driver Now available!

    Make sure you have the communications agent added then try it again. If that doesn't we have live chat available to help you out. Thanks!
  9. ROBLOX is written in lua My kids have already started learning lua because of that. So for me that was really awesome... and for all the reasons Ryan already said
  10. New Driver: Battery Agent

    Ah! sorry about that. Yes i can add that in tonight. Are there any others?
  11. Multiply same devices driver

    You can only bind one serial device at a time. What are you trying to do? if you need to have many devices talk to one serial you will need to make a cloud driver and connect via bindings or another in bound function. Good luck!
  12. New Driver: Battery Agent

    Note: Card access/Control4 wireless relay devices are line powered only. the contact sensor is battery powered. Thanks!
  13. New Driver: Battery Agent

    Try this version. So, Control4 decided to change the c4z file name of the card access devices (from cardacess_ to control4_). I've updated this and added in Axxess. Let me know. Change log (has not been posted to houselogix server btw)  Version 1003 (5.2017) Added support for escaped characters in the name Added extra verification of 0 or nil value variable returns. Example: yale Doorlock initially transmits 0 level. Driver will now wait 5 minutes then ask again. If it’s still 0, driver will notify user of low battery state Added support for these devices axxess_contactsensor.c4i axxess_motionsensor_MS-C4ZB-11.c4i axxess_doorbell_DB-C4ZB-11.c4i cardaccess_sensorbridge_ZGB20.c4i contact_cabridge_water.c4i contact_cabridge_micro_dws.c4i control4_wirelesscontact.c4i Thanks! battery_agent.c4z
  14. New Driver: Battery Agent

    What devices do you have that use batteries? I thought we captured all of them but may have missed some of them.