Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 02/03/2020 in all areas

  1. I was in a deep funk - you may have read some of my posts here about taking over a C4 install after a recent home purchase. It was a disaster - all the lights in a single room, old never-updated drivers, no real "cool" parts of c4 working .... and then Mitch saved the day. And a lot of dollars! Mitch did a great health-check, got me squared away, did some composer/HE review and set my system in tip-top shape. No more IR drivers! Roku Channels (Netflix, Hulu, etc..) right on the remote! Cool sounds play in the house when the Ring detects motion! Thanks, Mitch! Highly recommend.
    2 points
  2. Hello, I just ran into a nasty "gotcha" on my Win7 system when I installed and started to run Composer HE 3.1.1 (.569711-res). This version apparently requires the use of the secure TLS 1.2 protocol which may not be enabled by default on a Windows7 System. The symptom was "Unable to connect to project" and the error "Could not connect to director at {IP Address}". Also, the logfile in \users\{user}\appdata\Roaming\Control4\Logs will have a stack trace that looks like this: 2020-02-02 13:07:58,691 [8 ] ERROR Control4.Client.SysManager - System.Security.Authentication.Authen
    1 point
  3. the lack of clear documentation on what devices, what controllers, what os versions, what driver versions is the most confusing part of this whole thing
    1 point
  4. This happens but when the consequences are severe and identified weeks ago, developer silence is not cool. Sent from my iPhone using Tapatalk
    1 point
  5. I had the driver forget name now....geofencing.... that locked up my system, so nothing new. "followme"
    1 point
  6. While I certainly agree, there is a difference between a driver failing vs crippling a project. I know I am using a reversed engineered driver for MyQ. If and when it breaks, so be it but it will hopefully not take down my system where a dealer has to spend hours to restore everything. I'll just have look at other options for control like soldering a remote to a relay, etc. But my dealer told me it may happen, so he was up front, explained the pros and cons and I made a choice. If my dealer said the MyQ app has a chance to take your system down in "dumpster fire" fashion I may have looked
    1 point
  7. Agree 100%. I understand the issues dealers might face but don’t have a lot of sympathy for the lack of disclosure argument given how little information C4 itself discloses (at least to end users). Your “Wild West” point is key though and pretty much applies to any third party driver (hello Extra Vegtables, HouseLogix and others). As an end user (and certainly as a dealer) you have to weigh the risks of “how long will the driver work?” against “I really want this function”. I’ve had C4 almost 7 years now and seen enough to know this conflict isn’t going away anytime soon.
    1 point
  8. "Dumpster Fire" is a term coined by another developer for a driver that doesn't follow an official API. Their point being that sooner or later, it's going to have an issue, one side or the other will update and break the driver's control. The trouble is for dealers it's not always apparent if it's official API, snooped, or a hack, and the client just knows they paid for and it isn't working so it's the dealers fault. (Snooped referring to watching the communications by another app that's controlling it; as oppose to a hack which might mimic another device to fool a cloud server, ie pretending
    1 point
  9. I still don't feel this warrants hacking a controller without warning. Sent from my BBB100-1 using Tapatalk
    1 point
  10. You were in the best of hands with Mitch. Nothing intimidates him and he has such tenacity. Good for you pal. Glad Mitch got you going. Enjoy and happy automating! Sent from my iPhone using Tapatalk
    1 point
×
×
  • Create New...