Jump to content
C4 Forums | Control4

IntrinsicGroup

c4Forums Member
  • Posts

    219
  • Joined

  • Last visited

  • Days Won

    7

IntrinsicGroup last won the day on March 1

IntrinsicGroup had the most liked content!

1 Follower

Contact Methods

  • Website URL
    www.intrinsicdev.com

Profile Information

  • Interests
    Driver Development, Software Development, Problem Solving

Recent Profile Visitors

2,302 profile views

IntrinsicGroup's Achievements

  1. This is a vehicle specific driver BUT we are currently reworking the driver to make it an official solution, and we're also working on power wall integration as well as part of that.
  2. We haven't received an update from Control4, however, Chamberlain have confirmed their long term support for our integration to them, which Control4 stated was their main concern. Everyone who has installed the driver over the last few weeks has done so without any issues, hence we have removed the disclaimer.
  3. I don't believe alerts are sent from the driver so it's possible this is part of the block by C4 but hard to say for sure. It may be isolated to your system. If you'd like to submit a support request we can see if it's anything we can help with.
  4. Glad it's working well for you... thanks, the more support we have from dealers regarding this unprecedented situation the more likely we are to get it over turned.
  5. If the driver was installed you should be fine. The driver is available for sale on our website for those that have installed it and still need to obtain a license. If you experience any issues please submit a support request on our website.
  6. Yes, there are no issues with the driver or our relationship with Chamberlain. Control4 have chosen to forcibly block this official integration. This is now sadly a legal matter. If you install any other platforms their drivers are on the way. RTI is launching today and others will follow shortly.
  7. Yes, so long as it was installed before Control4 forcibly blocked it you'll be fine. This isn't a driver issue. If you attempted to install it after they imposed the block you can contact us for a refund or hold off to see if Control4 provide us with any more information.
  8. We have undertaken testing this morning and it appears Control4 have taken the regrettable step of blocking new connections of the driver at some point during the night (note we are UK based). Existing integrations are still working without issues. We assume Control4 will clarify the situation at some point. This is now with our legal counsel and we have no further information we can share at this time.
  9. We need to be a little careful what we say here. None of us were in the room when the Clare Controls discussion was undertaken. From our experience though if two publicly traded companies have a contract for services between them and one company suddenly stops providing a service there’s only really two options: 1) They are in breach of the contract, which normally leads to damages being paid; or 2) The contract period had already ended, so the services were shut off because there was no obligation to provide them. One point we can comment on (as it's publicly visible) is that on my last count there were over 40 drivers for Control4 on Driver Central that are $150 or more. Some are more than double our driver price and some do include a license fee/tribute for the manufacturer's API, they just don't necessarily declare that. It's becoming more and more common for cloud services to require some kind of financial compensation (indeed Control4 are introducing that policy themselves) so I believe we will see this happening more and more with drivers in the future.
  10. Control4 did give their blessing for this driver, they advised they weren't pursuing a relationship with Chamberlain, gave us email addresses for their contacts at Chamberlain and wished us luck with the integration. Our understanding is Jesse Smith doesn't use any cloud based drivers, he is not singling out this one specifically, but either way nobody has to install any of our drivers. They are there to provide an option and give dealer's/end-users choice. This is an official integration. If Control4 can provide us with the reason they object to it we'd be happy to attempt to alleviate their concerns.
  11. We appreciate the support. Our company ethos is to be very open - if there's a problem, we don't cover things up. (it's how you deal with the problem that is important!). Intrinsic is part of a larger company and our Group CEO (a former lawyer) is directly involved in this. All integrations go through our legal team before launch, so we're confident on the legalities of this integration. We can't comment on the specific relationship between myQ and Control4. We do believe the basis of the announcement to be fundamentally flawed: - Snap instructed us to get an agreement with myQ before they would let us launch this driver - The agreement covered longterm support - Snap are aware this driver covers longterm support - Chamberlain are committed to supporting the CI market and fully endorse this driver There's no problem with the driver, which is still functional, and has the support of the Control platforms who are also launching it.
  12. We can confirm that there's no legal basis for it, as if there was, that would stop all garage door openers (ratgdo, tailwind etc) from being able to integrate with the system. There's no copyright issues or safety concerns, and there's no memory leaks or malware either - Several Snap employees are even using it in their own houses.
  13. There are no issues with the driver or our relationship with Chamberlain. If Control4 forcibly block the driver we will issue refunds to those that have purchased it as a good will gesture and seek legal means to recover our losses. This is completely beyond our control, and beyond the control of Control4 dealers alike. This concerns us, and should concern all users, dealers and third party developers. As mentioned above, there are significant legal implications should Snap block a driver (the way the driver works would mean they'd have to push software on every users controller without their consent = not legal and support call headache for dealers). Which other brand/manufactuer will they choose to forcibly block next? It is a very slippery slope, will competing audio brands be next? Other brands that have publicly changed their API or have hardware that is flakey? Perhaps they are only singling out Chamberlain for now, but given Control4 in April 2021 stated "Good luck working with Chamberlain... I hope it works out for you" it seems unlikely Chamberlain will be the last victim.
  14. Jesse Smith's post on Facebook sums up this situation. There are significant legal implications should Snap block a driver (the way the driver works would mean they'd have to push software on every users controller without their consent = not legal and support call headache for dealers). Snap are fully aware that this contract with Chamberlain includes long terms support for the CI market, so we can only speculate there is something else behind the announcement.
  15. Yes, as above driver limit is currently 12. This can be extended for additional devices if required but myQ thought more than 12 was unlikely.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.