We are just about to release version 2 of our Pentair IntelliCenter module which was a SIMPL+ module rewrite in SIMPL#. That task alone was a fun challenge and we were about to release that version until we decided to wrap in the Crestron Home components in the same library that plays with SIMPL Windows. It’s taken me about a month – from not knowing anything about extensions, to about to release the Pentair IntelliCenter Driver. While I don’t have any code that I can share, I started off following the Create an Extension Driver section of the SDK documentation with the goal of just having a button do something on the CP4-R, and worked out from there which I think would be good for someone starting out. It wasn’t until I didn’t understand one of the steps that I referenced the samples. While the samples do compile and run(I think I actually ran them once when Lincoln had enough of me screaming at the CP4-R in a WTH moment) I only use them for reference material. The process was certainly A LOT of trial and error.? Documentation is ok, there is a lot of reading between the lines, and a lot of going may places on the SDK site to put the jigsaw puzzle together.

?

Jay I know you know your way around Visual Studio, but for anyone else reading this, if you haven’t really played with SIMPL# and/or SIMPL#Pro and you’re trying this out, be prepared for steep uphill battle.

?

Caleb

?

Caleb Radecky | Manager, Online Products & Services
Crestron Silver Certified Programmer | DMC-D-4K | DMC-E-4K
ControlWorks Consulting, LLC | Crestron Services Provider |
D. 440.771.4809 | O.440.449.1100 X1109 | F.440.449.1106 |

?

From: [email protected] <[email protected]> On Behalf Of jbasen
Sent: Wednesday, February 17, 2021 21:17
To: [email protected]
Subject: [crestron] Crestron Home Driver Using the Driver SDK

?

I've had a request to port the Weatherflow Tempest weather station driver I wrote to Crestron Home.? How bad can it be.? So, I downloaded the driver SDK from and got it installed on my laptop.? Then I started to try and dig in.? Crestron supplies a bunch of sample projects so I figured that was the best place to start.? I could find a nice simple sample and then start digging through the code and the help files to see what is going on.

Now my understanding is that a driver for an extension device, like a weather station, is the easiest type of driver to create so again, how bad can it be.?

So, I look at the extension driver samples and there is one for a door lock.? Opening up the sample Crestron has chosen to include every possible bit of functionality you can think of for a door lock.? It includes access list support, jam support, and the list goes on.? All that extra functionality in a sample that you are using to try and just get started with something new obfuscates the underlying structure you are trying to understand.

When I want to start learning something new I want to start at the "see spot run" level.? As stupid simple as possible.? Once I have a clue I can take baby steps and move onward to something a bit more complex.? Now a door lock isn't like trying to learn to speak English by trying to read "War and Peace" but with all the added functionality Crestron included it is certainly at the level of a novel by Earnest Hemingway.?

So, this saga finally brings me to my question.? Does anyone, who has gone down this path before me, have a really, really, really basic example of an extension driver they are willing to share?? Something at the level of controlling an IoT relay from Crestron home where all you can do is turn it on/off.?

Thanks in advance for the help.

Jay