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 crestron.com/developer 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
