I am trying to set up my DSC Alarm System with SmartThings and am working through the process, but don’t understand the basic process of installing a SmartApp on a Raspberry Pi.
I know the very knowledgeable community here can help. Thanks!
1 Like
You can’t. Smartapps are written in smartthings’ own variation of groovy and run in the smartthings cloud.
There are many people who will use a raspberry pi as a “man in the middle” to create an integration with some other Platform, but those cases you aren’t running the smartapp itself on the pi. Just passing information back-and-forth.
The following FAQ explains how you install smartapps to your account:
And for questions about working with the raspberry pi, check the developer section of the forum.
https://community.smartthings.com/c/developers
But you’re probably best off by going to whatever thread had the discussion of the integration that you were trying to do and just asking your questions there. 
1 Like
It’s not too difficult of a setup but you will need another piece of hardware. Details can be found here:
2 Likes
Thanks for the clarification, JD Roberts. I understand about the thread specific focus, but there wasn’t a lot of activity in this area recently, with many recent questions unanswered. So i was trying to get through this myself, just needing help with a generic Rasp Pi question.
I appreciate your input. Thank you.
1 Like
Thanks rontalley.
I have been able to set this up now…I think.
Parts of this were a bit difficult to follow, as I am new to the ST system, not real comfortable with GitHub, and not always able to bridge some of the areas of assumed knowledge in the instructions.
Thank you for your help!
2 Likes
You did way better than me. Took me 2 weeks! This was my absolute first dabble into SmartThings and it killed me.
Now looking back, I realize how easy it was but you don’t know what you don’t know.
Good job!
2 Likes
I had some help from another ST user, otherwise I would still be wandering in the wilderness…Ha.
Yes, it is just as you say: The process is relatively straightforward, but if you don’t understand the basics of say Linux , or some aspect of ST, you are going to get stuck. For instance, the question I posited here to start this thread. Also, I had to figure out what the executable file type was to even START AlarmServer. Plus, many other aspects that seem obvious now that I understand things better.
The GitHub instructions are OK I guess, but assume knowledge/experience that many (most?) of us do not have.
2 Likes
100% agree with this statement. Glad you got it worked out!
FYI, I had issues using my motions connected to my DSC Panel. They worked too good! They were so quick to report motion/no motion that ST sometimes did not even pickup on the change. I ended up making a webCoRE Piston for my motions that went something like this:
If DSC motion changes to active
Then with Virtual motion
Active
(asynchronous)
If DSC motion changes to inactive
Then with Virtual motion
Wait 30 seconds
Inactive
(asynchronous)
You get to the (asynchronous) setting by clicking on the “with” under the Action block section and then clicking the gear icon when creating the Piston. Asyn allows for each “If” block to run on its own without care to what else is going on in the Piston. You may have as many “If” blocks as you like and can put all of your motion logic in one Piston.
This allowed for a 30 second re-trigger time which helped solve some automation issues I was having. I did this for all of my motions connected to the DSC Panel. Everything else worked perfectly.
Wow, that is some advanced stuff.
I will have to look into the webCore stuff.
Thanks for the information!