Jump to content

bnet

c4Forums Member
  • Content Count

    48
  • Joined

  • Last visited

  • Days Won

    3

bnet last won the day on May 21

bnet had the most liked content!

1 Follower

About bnet

  • Rank
    Control4 End User

Contact Methods

  • Website URL
    https://bnet4solutions.com

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. So with all the talk about supported drivers, unsupported drivers, official APIs, unofficial APIs, companies merging or going out of business, it occurs to me that there is an alternative driver development/sales business model that would mitigate the medium to long-term risk of purchasing drivers. To date, we are based on a lump-sum, everything up-front purchase model. You buy the driver and hope that everything that driver touches internally (control4, hardware, etc) and externally (cloud services, APIs, etc) doesn't change, break or get discontinued. If it does and your lucky, you upgrade. If your unlucky, and there is no upgrade path - you are stuck or you buy another driver to replace the old one (if one exists). The alternative driver business model looks like a subscription. Technically, I'm not sure if it is a subscription, a lease, limited license, whatever. No matter, the concept is the same: you pay a recurring fee to use the driver. And you pay it as long as you want to use the driver. Driver breaks, a better one comes along, you no longer use/need it - stop the subscription. Other side of the coin is that if you stop paying, the driver stop working. As a consumer/home owner, the incentives are all in the right place - build a good product, keep it current and I'll stick with you. It keeps developers honest by giving you an out with limited sunk cost. As a driver developer, it is more work. We have all built some form of payment infrastructure - we would need another. Our driver architecture would need updated to handle the on/off nature of subscriptions. What is the market price of a driver subscription anyway? $1, $2, $5, $10 per month? per quarter? annually? Technically speaking, this model has some challenges - all are, I believe, solvable. The infrastructure can be built out, friction-less, recurring transaction services exists. The challenge is one of mindset and adoption. So, TECHNICAL ASPECTS ASIDE, thoughts on the driver subscription business model?
  2. re polling interval - short answer: there is no technical limitation long answer: Polling is a balance between keeping the driver’s device status up to date vs overloading the MyQ API. I have seen other apps poll as frequently as every 5 seconds –a setting that would seem to get your implementation banned (by mac/ip) within short order. 1-minute intervals seem reasonable but any feedback on this subject is welcome. re authentication action - on other drivers i had initially done away with the authentication action design. the issue was that, believe it or not, not everyone knows or enters their u/p correctly the first time. when the driver fails to authenticate after the u/p is fat-fingered a few times, the account can get lock. so, i've been using the read / aim / fire method for authentication. it is an extra step but only done once so i hope its not too much of a distraction. that's the reason anyway - perhaps a poor design choice.
  3. Wires are cheap, run them everywhere - future proof/what ifs/what could be.
  4. And it took you 10 mins to call it a “hack” Another non-answer answer
  5. I tell everyone the deal before I sell it. It's a customer's decision at the end of the day. But I give them all the info they need to make an informed decision I missed the part where you actually answer the question - you call my work a “hack” and at the same time profit on another identical “hack”. Does “all the info they need” include your financial arrangement with DC because you are clearly motivated to put the customers’ interests ahead of your own.
  6. Absolutely true - and if there was a published API, bMyQ would be using it as would the DC driver I’m sure. But there is not and so this is what we have.
  7. What is your cut of MSRP? 20% per “hack”? Or are we witnessing true, authentic altruism at work here?
  8. Perhaps he should post a financial disclosure next to his guarantee
  9. As did many of us. Partly why bMyQ is priced more “reasonably”
  10. I would always choose a hardwired/local solution over a wireless/cloud solution - just not an option for everyone. That is why we have options.
  11. What is your problem? I didn't think this would be so controversial - it is a $75 driver for a garage door. We are not saving the world here. Don't want to use a driver, then don't but not everyone has the wires in place or wants to solder. Maybe you can come down off your pedestal long enough to post the "guaranteed support for eternity" statement for your services? I'll take notes and you can go back to throwing rocks...
  12. And what makes your unofficial API usage any better? Like i said on the other thread - you want C4 to control your MyQ devices you can use a soldering iron or a driver. If/when there is an official API, I'll use that. Between now and then, this is the method we have if you choose the driver path. But since you asked, I guess the real difference is that I built a home with Control4 and use/depend on my drivers everyday. If/when a driver stops working, I'll be here to fix it.
  13. I feel "hack" is a bit strong - i would suggest "reverse engineered". Some may even take offense to their working being called a "hack". Whatever you want to call it, if you want Control4 to control/monitor your MyQ devices, you have a driver or a soldering iron - choose your hack.
  14. Your "instant" answer is going to be a contact sensor - there is no publish/subscribe or websocket service available from MyQ. So, bMyQ gets its device state via the only method possible - polling. Currently configurable between 1 and 10 min increments. bMyQ does have a nice feature that keeps the device state current after issuing a command - see the polling discussion notes in the documentation for more detail.
  15. When you have a driver that stops working and you write drivers, well... you start a new project. So, I'll throw my hat into the HL MyQ driver replacement ring - check out bMyQ at https://bnet4solutions.com
×
×
  • Create New...