bnet

Just to put a bow on this thread - BNet Solutions is a Licensed Control4 Development Partner with full access to Composer, SDK, API docs etc. I do NOT have access to the dealer forum and have been told it is for "dealers" only. I believe the premise of the orig question is still valid - other than the dealer forum, where do Control4 driver developers discuss driver development? I'm not sure if it exists... Should we start one? Separate category on this site? Different site? Most importantly, is anyone interested? I don't need a forum to talk to myself...

Pleased to announce my Nexia driver is officially available! Thank you to my testers for their feedback - it is a better product because of you. Visit https://bnet4solutions.com for my modest but growing list of drivers. enjoy!

Thank you for the replies. I'm not interested in challenging C4's business model, looking for download links or on a C4 bash-fest - I love my C4. It is truly the centerpiece of my house. That's why I would like to fill in a few missing functionality holes and address a few driver issues. And if I make a product that someone else likes in the process, that's great. I've only been at this for a few months and my appreciation for the framework continues to grow but development has been somewhat tedious. On the upside, I really have enjoyed figuring some of this out. But... When API/Proxy docs say a functions return a string but it only ever returns nil, what am I doing wrong? Turns out, the reference docs are wrong - who knew? (Ryan knew) When my thermostatv2 driver <extras> crashes the C4 iOS, is it me, C4 iOS app, proxy driver or something else? Works perfectly on my T3s and android app but bombs my C4 iOS app every time. Has to be me, but why? Spend days on this one with no luck... What are people using for their IDE? Has anyone successfully integrated Visual Studio Code remote debugging? And a few dozen more somewhat mundane questions... I'll muddle on if need be, I just know there are smarter people who have already been down these paths... and it sounds like those paths perhaps all lead to the dealer forum. (above questions are just some examples - I'm not necessarily looking for answers just included to support the larger question) Thanks for your time.

Short question - Is there a driver development forum where I should be posting development-related question? Longer version - While there are certainly some development posts and I've incorporated several tips, the forum seem more geared toward dealer/user-related questions and composer-related programming than driver-development. I'm happy to post my development-related questions here, I just don't want to lob questions that no one else cares about... Also occurs to me that developers may feel like they are competing with each other so the spirit may not be there... Thanks!

I control my firepit from aux button on pool controller (aqualink driver). Had to install remote starter kit. Wired solution obviously...

Ready for some testers if your interested:

After a frustrating few years with my existing Nexia HVAC driver, I decided to build my own. At first in node, but a few months back I ported it over to native C4 world. After some recent refining, my hope is that there is a market for an alternative to the driver that I'm sure everyone else has also been struggling with. I've attached the driver documentation for your reading pleasure. If you are interested, please msg me. Thanks! Brian bNexia.rtf bTstat.rtf

Great! Let me polish a little and write some documentation and I'll be back with you...

I've been down this road with my HVAC installer for years and from what I'm told (and read and have slowly come to believe) - my system, like yours, is a "communicating" system and requires the trane "communicating" tstats. I've looked into all kinds of 3rd party tstats and even research a serial connection directly to the unit (there is a serial port for diagnostics) but with no luck. I'm also the victim of the houselogix driver mentioned above - they told me 2 years ago they knew about the issues and even offered a refund - should have taken it! They also said they were going to stop selling it but I see it is still available. They do have a bunch of great drivers but they acquired this driver and have no plans to update/fix it. I asked to buy it, license it, anything to try and get it working but had no luck. Not integrating HVAC into a home automation solution seemed crazy... Having never written a C4 driver and being fairly confident I didn't want to, I wrote a node.js app that I called the NGS (Nexia Gateway Server) to proxy requests from C4 to Nexia (via the TCP Command driver) that then talks to the tstats. It worked well for what it was and I've been happily using it for over year... until... Curiosity got the best of me and I recently ported it over to Control4/lua world. And now, I'm honestly not sure what to do with it. I've developed for many years but this is my first "real" Control4 driver, this is not my business or my trade but if someone wants to help me make sure it works in the real world, I would share it. It should work with any Nexia connected tstats.