Keyboard Shortcuts
Likes
Search
Moving to Crestron Home driver development
开云体育Hi, ? since KNX-support for CH is available for some time now, i?m considering adding CH to my portfolio. I?ve programmed some custom drivers for IP based devices and am considering to do the same for CH. To those of you who already do that: can you give some advice where the main differences/obstacles are compared to “traditional” driver development (i know the SDK site)? I guess the whole GUI-part needs some deeper investigation, right? ? Cheers, Thorsten |
开云体育Thorsten I wrote a detailed article on extension driver development for CH for Residential Tech Today.? You can find the article here: The article includes code snippets along with a link to a driver template that can be downloaded from my GitHub. Hope this helps Jay On 1/31/2022 4:15 AM, Thorsten K?hler
wrote:
|
开云体育That?s awesome, Jay! Just scanned through it and it seems to be exactly what i need for starters – this will definitely be my bed-time reading tonight. ? ? Cheers, Thorsten ? Von: [email protected] <[email protected]> Im Auftrag von jbasen ? Thorsten I wrote a detailed article on extension driver development for CH for Residential Tech Today.? You can find the article here: The article includes code snippets along with a link to a driver template that can be downloaded from my GitHub. Hope this helps Jay On 1/31/2022 4:15 AM, Thorsten K?hler wrote:
|
|
Nice! ?I too am interested and have been asked to write a driver. ?
?
I have .NET code of full connection/control of HAI Omni controllers and I had someone ask me to write a Crestron Home driver, googled and found your template.?
?
For the most part I understand the fundamentals, I just now have to find some extra time to start with a project to see how this all works. ??
?
What I’m still a bit unclear, since the HAI does lightings, Climate, thermostats, etc what type of driver it should follow — I’m suspecting its a "platform driver”.
?
And since it’s locally IP controlled, but not “cloud controlled” you still use the cloud connected transport, right?
|
开云体育Hi Danny, I am far from an expert on this.? I did the development and wrote
the article almost a year ago.? 1) The way I understood it was that a platform driver is for devices where there is a one to many relationship.? For example, I've thought about writing a CH driver for Shelly's lineup of smart home devices.? In my SimplWindows Shelly driver I have a communications manager module that handles bi-directional communications with all the Shelly devices and then there are individual modules for each Shelly device in your home that have inputs/outputs for controlling/feedback of an individual Shelly device.? This would require a platform driver and the added learning curve of fully understanding how platform drivers work is what has kept me from writing one.? An extension driver is for a one-to-one relationship.? For example, I wrote an extension driver to communicate with a Weatherflow smart weather station.? One module for one device. 2) From what I remember you still use the cloud connected
transport to communicate with a device on your local network.? I
believe that is exactly how my Weatherflow extension driver
works.? Whether this is really the way that Crestron intended is
another question.? But, it does work.? Hope this helps Jay On 1/31/2022 9:20 AM, Danny Mavromatis
via groups.io wrote:
Nice! ?I too am interested and have been asked to write a driver. ? |
|
Yes, you want a platform driver, and then sub drivers for each device type most likely.
One of the main issues you will hit is that extension drivers of this kind are basically extra appendages in home.? So like, you can't make a lighting driver this way that appears in the lighting load list. You can't make a thermostat driver this way that it actually believes is a thermostat. You can make the UI look exactly like the thermostat, but it won't show up in the standard thermostat group the UI provides. (or at least, as of the last SDK release you couldn't do it)? |