►
From YouTube: Home automation with Hubitat and .NET Core
Description
Who doesn’t love a good DIY (Do It Yourself) IoT project? There are so many interesting things that we can do with a few components and a little creatively.
In this episode, Cam Soper comes on to show us how he automated his home with .NET Core, Hubitat, and Azure with his open source project called Puppet.
[01:00] - Taking a look at the setup
[02:29] - Triggering Hubitat events
[05:15] - Using .NET for interaction
[08:52] - The motivation behind Puppet
[13:35] - Running your own Puppet server
Puppet - A .NET Core framework for automating Hubitat Elevation
https://github.com/CamSoper/puppet
Bot Framework
https://dev.botframework.com?WT.mc_id=ondotnet-c9-cephilli
.NET Core Guide
https://docs.microsoft.com/en-us/dotnet/core?WT.mc_id=ondotnet-c9-cephilli
#dotnet #iot #azure #raspberryppi #homeautomation
A
A
Hey
everyone,
my
name
is
Joseph
Philip
and
in
this
episode
of
the
on
that
show,
I'm
gonna
have
my
buddy
cam
who's
gonna
talk
to
me
about
some
of
these
interesting
dotnet
and
IOT
things
that
we've
been
playing
around
with
sure.
So,
okay,
why
don't
you
you
know,
since
you
haven't
been
on
the
show
before
tell
us
a
little
bit
about
who
you
are,
what
exactly
you
do
so.
B
A
B
So,
first,
let's
just
this
right,
here's
this
power
so
we'll
ignore
that-
and
this
is
this
is
my
router.
So
that's
part
of
my
little
local
area
network
here
for
for
our
discussion
today,
but
the
most
important
piece
of
hardware
I
want
to
show
off
is
this
guy
right
here?
This
is
a
home
automation
hub.
This
is
made
by
a
company
called
habitat.
It's
a
habitat.
You
know,
I'm
gonna,
get
this
wrong.
Habitat
elevation,
I
think
I
previously
called
it
elevate
and.
B
B
A
B
To
move
for
the
kind
of
the
big
selling
point
for
habitat
over
smart
things
is
that
all
of
the
execution
takes
place
locally,
whereas
with
smart
things,
a
lot
of
it
takes
place
in
the
cloud,
and
you
know
for
some
of
us
home
automation,
hobbyists.
You
know
that
distinction
is
kind
of
it
can.
It
can
be
important,
depending
on
what
we're
trying
to
do.
Try
to
cut.
A
B
So
this
remote
control
is
a
z-wave,
remote
control,
yeah,
it
has,
as
you
can
see,
it
has
four
buttons
and
each
one
of
these
buttons
I
can
press
them
and
get
what's
called
a
push
event
or
I
can
hold
them
and
get
what's
called
a
held
event.
So
I
have
eight
eight
functions
that
I
can
kick
off
on
this
remote
control.
Nice
and
I
actually
use
one
of
these.
Just
like
this
at
home
to
drive
a
speaker
system
in
my
house.
Oh
no
I
use
it
to
communicate
with
folks
outside
of
my
office.
B
B
A
B
Allow
you
to
do
those
things
correct,
so
the
the
habitat
itself.
They
have
a
programming
environment.
They
have
a
you,
can
write
code
for
the
habitat
device
using
a
language
called
groovy
I
extended
using
their
api's
I
I
isolated.
All
of
the
functionality
on
in
my
home,
automation,
Network
I
made
the
hub
attack
device
strictly
a
hub
for
a
basically
a
control
point
for
all
my
devices.
No
I
don't
have
any
code
running
on
this
guy
at
all.
Okay,
I.
B
Take
that
back,
I'm
gonna
pray
any
bit
of
code
running
on
it,
but
very
little
and
all
of
the
code
that
I
used
to
drive
the
automation
of
my
house
is
net
based.
Okay.
So
what
we're
seeing
right
here
on
my
screen
is
a
dotnet
application
that
I've
written
and
it
handles
events
coming
out
of
this
hub.
So
when
I
push
button
one
here,
that's
going
to
trigger
a
push
event
that
this
that
this
button
was
pushed
and
it's
going
to
fire
off
some
code
to
make
an
announcement
over-over.
The
audio
we'll
do
that.
C
A
Awesome
I
love
that
I
love
that
so
so,
let's
talk
about
this
really
quick.
How
how
this
whole
integration
piece
happens
so
that
dotnet
code
is
not
running
on
the
habitat,
correct
right,
so
I'm
guessing
at
your
home,
there
is
a
server
or
some
device
right.
That
is
running
like,
as
you
know,
like
a
a
plethora
right.
No.
B
B
So
the
this
is
a
console
application.
It
runs
it's
just
a
straight
up,
console
app
I,
just
run
it
as
a
daemon
on
a
on
a
Raspberry
Pi,
actually
I'm
interested
in
moving
it
to
containers.
I
just
haven't
gotten
around
to
that
yet,
but
I
could
I
I
do
have
an
Ubuntu
server
at
home.
That
I
could
run
it
on
in
docker.
Just
haven't
gotten
there
now
here
it's
running
completely
on
my
surface
yeah.
A
Pi
could
be
a
docker
container.
It
could
be
running
as
a
as
a
like
a
systemd
thing
in
Linux
mm-hm.
It
doesn't
matter,
it's
essentially
just
a
service,
that's
running
and
I'm
guessing
somehow
you
were
able
to
integrate
into
the
hub
it's
at
I'm.
Guessing
you
gave
it.
You
know
when
this
event
happens,
call
this
endpoint,
so
they.
B
C
B
You
wanted
to
correct,
so
that's
the
first
part
of
it
is
controlling
the
devices
that
I've
got
attached
to
this
hub.
It's
all
through
this
restful
interface,
sure
the
other
side
of
it
is.
They
have
a
it's,
it's
undocumented
and
it's
technically
not
supported,
but
they
have
a
WebSocket
that
runs
on
the
device
to
drive
their
administration
portal
mm-hmm
and
what
I
do
in
my
code
is
I
attach
to
that
web
socket
and
I
watch
it
for
events
as
they
get
raised
yeah.
B
So,
when
I
push
that
button,
it
raises
an
event
on
the
web,
socket
with
a
little
chunk
of
JSON.
That
describes
what
happened,
yeah
and
I'm
grabbing
that
and
using
that
to
kick
off
that
will
kick
off
an
event
in
my
code
that
drives.
You
know
he
does
whatever
I've
you
know
programmed
it
to
do
in
this
book.
I
have
a
certain
assembly,
I
call
a
puppet
dot,
automation
that
it
actually
goes
looking
through
the
assembly
for
whatever,
whatever
classes
declaratively
say
they
are
interested
in
whatever
event
happened.
Okay,.
A
So
all
right,
so
let
me
let
me
make
sure
I'm
getting
this
so
WebSocket
web
socket
listening
for
various
events,
yep.
So
if
you
push
the
button
on
your
remote
control
mm-hm,
you
know
long
press
or
just
really
quick
press
right
sends
an
event.
Event
kicks
off
a
WebSocket
thing,
mm-hmm
and
then,
in
your
code,
that's
running
on
your
server.
Wherever
the
server
happens
to
be
dotnet
core
it,
you
get
a
callback.
One
of
these
restful
api
is
that'll.
Let
it
know
what
device
to
turn
on
or
turn
off
or
interact
with
well.
B
In
the
case
of
the
office
remote
stop
that
in
the
case
of
the
office,
remote
I've
got
some
attributes
here
on
my
class
here
that
say:
okay,
if
the
device,
if
the
remote
device
it
has
a
button
held
or
a
button
pushed,
we
are
interested.
This
is
declaratively,
we
are
interested
and
the
the
engine
knows
to
go
out
there
and
load
this
class
and
fire
off
this
handle
method,
sure
and
then
the
handle
method.
You
can
see
the
code
right.
There
is
pretty
self-explanatory
if
the
if
the
button
is
pushed
and
it's
the
button
one.
B
A
B
The
the
impetus
behind
this
was
actually
laziness
just
to
be
perfectly
honest
sure
as
well,
so
they
have
like
I
said
they
have
a
programming
model
fairly
mature.
It's
built
on
a
language
called
groovy
which
I
had
not
been
familiar
with
groovy
before
I
got
into
smart
things.
In
short,
at
that
it
was
all
new
to
me
and
I
just
was
not
as
effective
in
their
environment
as
I
was
in
our
beloved
dotnet
core
and
I
started.
B
A
That's
really
cool.
So
now
you
have
this
framework
that
you've
created
and
I'm
guessing
you've
probably
spent
like
months
and
months
and
months
of
time
of
trial
and
error,
and
just
try
to
figure
stuff
out.
But
now
you
have
this
code
and
I'm
guessing
it's
on
github
and
openly
available.
It
is
that
it
makes
it.
It's
probably
super
easy
now
for
you
to
add
another
device,
and
you.
B
Start
working
yeah,
so
this
is
this-
is
the
the
branch
of
my
github
repository
where
I
keep
my
my
demo
projects.
Yeah
I
have
a
separate
branch,
that's
my
house
and
and
in
fact
anybody
can
go
I
keep
it
public.
Anybody
can
go
in
and
look
at
the
code
that
drives
my
house,
I
mean
I,
don't
have
like
credentials
or
anything
safe,
but
yeah.
Essentially,
all
I
have
to
do
is
come
into
this
puppet
automation,
project
and
add
a
new
class
that
represents
that.
B
An
automation
that
I
wanted
to
do,
and
and
declaratively
again
I
say
what
devices
are
you
interested
in
and
I
have
this
hole?
This
is
a
bad
example.
I
have
another
example
here:
the
I
have
a
syntax
essentially
for
turning
devices
off
and
on
mm-hmm,
like
in
this
case,
where,
if
I
run
this
again,
what
this
code
does
is
it
responds
to
the
open
event
on
this
contact
sensor.
So
when
I
open
this,
it's
going
to
turn
the
bulb
on
right.
A
B
A
Interesting
is
that,
like
I
feel
like
they're,
multiple
events
that
happened
just
now,
mm-hmm
right,
so
you
open
the
door
right
like
you,
simulated,
open
the
door
uh-huh,
but
then
your
speaker
went
off
and
it
also
your
light,
went
on
correct
right.
So
then
I
can
have
multiple
handlers
right.
That
process
events
and
based
on
that,
like
they
can
interact
with
whatever
devices
that
are
available
through
the
habitat
mm-hmm.
B
Now
you
do
have
to
be
a
little
careful.
I
got
myself
into
a
bit
of
a
problem.
The
other
day,
my
the
front
lights
on
my
house
are
actually
a
very
complicated
program
because
they're
all
they
are
all
smart
lights
and
they're
capable
of
different
colors
and
I
wanted
to
be
able
to
manage,
like
if
I
open
the
front
door.
If
I
have
the
lights
set
to
color
like,
for
example,
a
holiday
display,
if
I
have
them
set
to
some
kind
of
color
I
want
them
to
go
back
to
a
nice
soft
white
to
illuminate.
B
You
know
where
you're
walking
and
on
you
know,
on
my
driveway
or
whatever,
but
the
logic
behind
that
is
actually
kind
of
complicated
and
I
actually
made
a
little
mistake
when
I
was
testing
the
other
day
and
created
a
recursive
loop
that
brought
the
whole
system
crashing
down,
so
you
kind
of
have
to
be
careful
about
what
you're
doing
in
this
framework.
But
but
it's
it's.
It's
been
running
in
my
house
now
for
the
better
part
of
a
year.
It's
I've
been
using
it.
A
And
so
so,
just
really
quickly,
so
this
whole
framework
that
you're
built
is
built
on
dotnet,
core
c-sharp
and
I'm.
Guessing
now
you
have
your
own,
for
lack
of
better
words
is
like
your
own
DSL
right,
like
your
own
structure
of
how,
like
you,
interact
with
these
totally
different
devices
right
yeah.
What
made
you
decide
to
do
this
like
all
side
of
laziness
right,
but
why
did
you
decide
it?
Why
did
you
decide
to
again
not
just
use
a
thing
like
smart
things
or
whatever
and
build
your
own
thing
and
online?
You.
B
A
B
All
of
a
sudden
I'm
looking
for
opportunities
to
run
that
core
on
Raspberry,
Pi
everywhere,
right
and
I've
got
I've
got
other
projects
at
my
house,
you
being
driven
by
Raspberry
Pi
in
that
core,
but
there
was
a.
There
was
a
period
of
time
there
where
I
was
just
looking
for
any
project.
I
could
build
and
run
it.
On
a
you
know,
a
tiny
credit
card,
sized
computer
sure.
B
The
the
github,
the
excuse
me,
the
github
repository
for
this
project-
I
have
a
readme
on
there
that
should
hopefully
get
you
started.
I,
don't
think
I've
updated
it
in
a
while.
So
there
might
be
there
might
be
some
discrepancies
there,
but
I'll
try
and
make
sure
this.
It
gets
updated
before
this
before
this
posts
and
if
I
fail
in
that,
please
reach
out
to
me
and
and
I'm
always
happy
to
answer
questions
sure
that
the
you
want.
The
the
repo
address.
A
Yeah,
if
you
could
like,
if
you
pop
over
in
the
repo
really
quickly
so
folks,
can
see
where
it
is
sure
and
then
what
we'll
do
is
well
like,
while
you
put
it
up
we'll
just
make
sure
that
it's
inside
of
the
show
notes.
So
if
people
want
to
come
in
and
I
can
look
at
the
code,
look
at
the
documentation
and
I
believe
you've
also
done
some
like
conference
talks
and
presentations
about
this
as
well.
A
B
A
Great,
so
again,
so
what
we'll
do
we'll
make
sure
that
the
repo
is
inside
of
the
show
notes,
and
so
everyone
could
go
in
and
try
it
out,
but
thank
you
so
much
more
like
this
like
this
is
such
an
exciting
thing
for
me,
like
every
time
I
get
a
new
toy
to
play
with,
like
I.
Could
I
can't
just
like
wait
to
to
mess
around
with
it?
So
thank
you
again
for
coming
up
thanks
for
having
me
and
thank
you
all
for
watching.
This
has
been
another
episode
of
the
on
that
show.