Jump to content

bnet

c4Forums Member
  • Content Count

    60
  • Joined

  • Last visited

  • Days Won

    3

bnet last won the day on May 21 2019

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. seen 3.2.1.586045-res in some of my driver logs. release notes on dealer portal go up to 3.1.3. composer update goes up to 3.1.3. didn’t find anything on this forum or google. anyone else seen a 3.2.x?
  2. hmm, heat and aux control seem like pool 101 stuff. does the jandy driver have conditionals for the aux relays? pentair does not - drives me crazy i can't query the driver for an aux state.
  3. there is enough head scratching for all the players here but generally, my issues with c4 relate more to functionality: -aside from a few bugs, the pool proxy generally needs updating. variable speed pumps, specialized lighting, chlorinators and chemical samplers are not that uncommon but not naturally supported by the proxy. an update to thermostat_v2 style extra would be nice step in the right direction. -the c4 driver has some questionable implementation. 15+ query commands cycling every 30is seconds is probably not necessary (in fairness, not all of these make it to the bus as the iLink gobbles some up). no retry when a command fails (there are ACK and interface busy replies that could, but are not, used keep a msg from going into a black hole). -as much as i want to fault the iLink, i'm not so sure. i have not seen a command go out successfully that wasn't acted on by Pentair. iLink's primary issue is that in an effort to simplify inner-connectivity, it has lost all but the most basic functionality. -the Pentair bus is busy and a mess. there is clearly 3rd party hardware branded as Pentair that speak their own language and have their own packet structure mixed in with native Pentair packets. but again, i have yet to turn on a pump or flip a aux/relay on my intellitouch and have the system not act on it. the overall issue seems to be that when you layer abstraction on abstraction on abstraction, something will get dropped.
  4. my current pentair integration is probably the weakest and least reliable component in my setup. part of the issue is the c4 pentair driver (functionality and including an issue or two i have with the c4 pool proxy) and part the pentair iLink. this is what you do, or more specifically, what i'm doing: i wrote a pool proxy driver "bPentair" (not released) with the ability to directly read/write to the Pentair serial bus. disclaimer is that i have an intellitouch, not an intelliconect, but the intelliconect uses the same serial connection to talk to other pentair equipment. by going direct, you can bypass MQTT (your entire network really) and not get caught by a change in pentair's MQTT interface and not require a separate box as noted above. of course, you will need a serial connection between your c4 controller and pentiar but everyone added that during construction, right! also would need a $10 rs485<->rs232 protocol adapter and because i'm running this on my development ea1, i needed a $15 3.5mm to rs232 adapter. also, as noted above, a direct connection gives you access to everything on the bus - iChem, iChlor, detail pump info, etc. you can not get this info from iLink ($200) but can via pentair's screenlogic2 ($500+). but even then i'm not sure you can get the info into/do anything about it in C4. as an example, the screenshot is real/live data. perhaps when bPentair get a little further along, i can look at the differences between intellitouch and intellicenter and intelliconect.
  5. @alanchow - thanks for info. technically it checks (obviously, your doing it) but it does not seem to pass my sanity check: i'll add some profiling code but best guess is that 80%+ of the processing time on my main page is in/on C4:GetProjectItems() - even passing all the filter flags i can it is an expensive call. i'm not serving rich content or streaming anything - just generated html with a style sheet and javascript. there are no static pages or content i've stashed on the controller. even the icons are served by ngnix, not the driver. no matter where the html is generated, i will still need to call GetProjectItems so the above "negotiated settlement" is a work-around for a negligible portion of the processing load. in fact, there is likely an extra step - encoding GetProjectItems's output before shipping to client - no one should have to deal with that xml directly. so when the dust settles, i'll still have a process (same driver), listening on the controller (same port), serving content (maybe begins with a "{" instead of "<html>"), talking to a client (same browser, javascript/ws vs http get). i haven't implemented it so i could be very wrong (am i?), but the before looks very similar to the after. but, if this is where they have drawn the line, so be it - on to v2
  6. hmm, where to start... should i give an example of another driver listening on a server port? multi-x rf repeater, virtually any ip-based driver... or should i list some C4 network APIs that are provided specifically create client/server interactions? C4:CreateNetworkConnection(), C4:GetNetworkConnections(), C4:ReceivedFromNetwork() or about 15 others or should i copy/paste the server sockets example directly from C4's API documentation... so many options
  7. yup - hacked. so hacked i even added C4:RenameDevice() to their documentation while i was in there so everyone else can hack. that's the actual API call if you want me to look it up for you.
  8. by my read, does not violate the licensing agreement
  9. Rename your Control4 devices without Composer… or programming! Use bRename’s internal web server to view your devices, rename them and refresh your navigators. Accessible from a standard browser or a touchscreen navigator. Installers - perfect for clients who have changed the spelling of their children's names 3 times. It was a "Bathroom", a "Vanity", a "Toilet" and now it’s a "Powder Room"? Homeowners - change that "Bedroom" to an "Exercise Room”, then change it again and again and the next one again and again – all without involving your dealer. It is your system, make it perfect. https://bnet4solutions.com/brename/ Was $50, is $50, will be $50
  10. You can commit or hedge but can’t do both. Otherwise, it is really a payment plan not a subscription.
  11. in january, i started offering license subscriptions for bMyQ and bRoomba. each are currently priced at $12.50 per 3 months if a software/driver solution is the route you want to take. copy from my site's FAQs: What Are License Subscriptions? BNet Solutions now offers the bRoomba and bMyQ drivers on a subscription basis. Instead of a one-time purchase, you are billed at a regular interval (usually quarterly) for the use of these drivers. All billing transactions are handled by PayPal and are “friction-less”. You may choose to continue the subscription for as long as you like for cancel it at anytime. Once cancelled, the driver will continue to function until the expiration of the current subscription period and then will be deactivated. Why Only Offer Subscriptions for bRoomba and bMyQ? The rebuke to these drivers is that they rely on unsupported cloud services / APIs to function and that a change to that infrastructure could cripple the functionality of these drivers. If you are a “Dumpster Fire” prophet, do not buy these drivers. I wish you well on your integration efforts but know that there are NO official APIs available for 3rd party integrations. If you want to integrate MyQ or Roomba hardware into your automated home, but want to hedge on a full license purchase, perhaps a subscription is right for you. See the bRoomba and bMyQ product pages for more details on pricing and terms.
  12. Pleased to announce the bRename driver is available! Rename your Control4 devices without Composer... or programming! Use bRename's internal web server to view your devices, rename them and refresh your navigators. Accessible from a standard browser or a touchscreen navigator. A win for installers and homeowners! Visit https://bnet4solutions.com/bRename for the bRename driver and documentation. Enjoy!
  13. 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?
  14. 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.
  15. Wires are cheap, run them everywhere - future proof/what ifs/what could be.
×
×
  • Create New...