New user struggling with automating switch with presense

[JDRoberts]

To use CORE, you will need two threads.

The first thread is the peer assistance thread. This is where the core experts hang out. People there will be happy to help you with any core questions. (Core calls an individual rule a “piston”)

CoRE - Get peer assistance here with setting up Pistons

Welcome to the CoRE Logic Thread. Here you will find many community members that are more than willing to help you with the Logic and Programming of your Pistons. **There will be another thread for “How are you using CoRE?” and “How are you using the CoRE/AskAlexa integration?”. So, this is the place to ask your questions and the place to get the answers.

And here is the author’s thread where you will get the code for core.

[RELEASE CANDIDATE] CoRE (Community's own Rule Engine)

UPDATE DEC 19 2017: If you are still using CoRE, please update to the latest version as soon as you can. Here’s what changed: v0.3.16e.20171219 - RC - Replaced recovery safety nets using unschedule() with a much more optimized method that does not affect ST as much as unschedule() does This is important as CoRE has been identified as a major choke point on a certain method that it uses (ST describes that as expensive in their documentation. As it turns out, it is. With ST’s help, CoRE is now able to recover from timeouts much faster and with a lot less resources than by using its own recovery safety net. You should also consider moving on to webCoRE instead, as CoRE is no longer actively maintained and only gets critical updates. Thank you Continuing in the BETA process of CoRE (mil…

Again, core is very powerful, but also very complex. Feel free to ask for any help you need, including just explanations of how CORE works. But ask those questions in the peer assistance thread.