I know some have an android simulator of some kind, but when I do presence sensor testing, I will use an open close sensor and if it turns true, then I go back and replace it with the presence sensor. Or use a virtual switch to simulate.
So basically I canāt simulate it because of actively being present is what your saying I think.
Did you enable Oauth?
The screenshots you are referring to are from the dashboard view. On the main CoRE app pageā¦at the top it says CoRE Dashboard. Click that, and you can view the pistons laid out as you see posted here.
Not that I am aware of without that android simulator, which I donāt have.
You can only put in one sensor and send your wife on a beer run; purely for testing purposes only though.
Just replace the presence condition with a simulated switch. When you get the piston working like you want with that, you can swap in the presence condition.
Oopsā¦ just saw that Brian already said the same thing. 
ok so I set up If living room motion changes then turn on
using entry light to 50%
it appears to work but the current evaluation says false so maybe Iām misunderstanding something.
now I should be able to change the motion to a presence and it would act the same as motion correct.
My goal seems simple I want an entry light to come on when my wife or myself arrive but not if one is already there
I then want that light to dim down in off postion in 10 minutes unless the switch in changed during the dimming process
This my first attempt at using core.
As of now the light comes on with a routine but I want it to dim to off after arriving plus canceled if manually pressed
Not sure but I believe Transition to color is a hardware function implemented by the driver (DTH). Is it a full circle or an empty circle? Full dot/circle means the function is emulated by CoRE. Also, if it is emulated by CoRE, it is async, meaning it does not delay the rest of the commands by its own duration. Perhaps change the 15-25 wait with 45-55 seconds to account for the 30s used by the transition?
I believe CORE is looking for the events. So if your sensor hasnāt left / returned hard to see it work.
Use virtual switches or presence then replace with real thing once your done testing.
I donāt think the testing porting of core works very well.
As for what people are posting some are screen shots of the app screen.
Like this:
Others are screen shots of the Web interface.
Like this:
To get the second dismay type. In the app at the top it says āCore Dashboard Tap to showā. It will open in a browser window. Tap on of your pistons and it will look like the second image. Tap the camera in the top right to capture an image of the screen.
Hope that helps.
There are a lot of examples in this thread along those lines. Just go back to the beginning and search.
Please donāt take this the wrong way, but I think you should start out with some simpler pistons until you get the hang of how CoRE works. While not difficult, it is a bitā¦ different, and takes some getting used to. Iāve only been using it a week or two, and have learned an immense amount just from reading this thread. And obviously, I still have a lot to learn.
Itās incredibly powerful, and there are usually 10 different ways to get to where you want to go, although some are better than others.
2 Likes
Local variables, no prefix. For a global variable, you prefix it with @
Thanks. Sorry I meant @ for global variables. Its system (non-editable) variables that start with $ correct ?
1 Like
ok great thanks that explains the screen shot. Like I said Iām really new to all this and donāt have the logical mind set of a developer so a lot of this is hard for me to grasp but Iām working on it. My end goal seems like a lot of and and ifs buts and levels. (i.e. foreign language). Iām the guy that can build your house and run wires and fix your plumbing.
I have been reading a lot. (4 hours just yesterday) but the organization and going though 5000 post to find that one little thing is very poor and difficult do understand when a person has such little experience and is exactly a techy I would think there would be an organized area of apps and functions with in the CoRE community
2 Likes
Youāll get it, CoRE is very complicated and can be overwhelming. Just start with the basic part of your idea, and improve it in steps. In the process youāll expose yourself to more and learn more.
Iām still trying to wrap my head around core. I do industrial maintenance, work with PLC and logic and it still confuses me. Because CoRE is so advanced there are many ways to accomplish the same thing. Sometimes itās just twisting how your thinking to make it work
When your stuck just ask. Everyone here wants to help. Thatās the great part about this forum.
1 Like
Thatās another āBADā part of this forum the information is scattered among various conversations going on at the same time. The search function will sometimes get you close just have to keep trying different searches.
The same questions get asked alot because of this disorganized format. Just how it is.
Is it possible to run a piston by using a URL? if so what would such a URL look like?
True. I wish there was a dedicated forum for CoRE. I have 3 or 4 unanswered questions up there ^ that are just lost in the noise.
4 Likes
Yeah, the url would be the dashboard url, but replace /dashboard with /execute/
is obviously the name of the piston you want to run. You can also pass that as a post form data, pistonName=
It looks like that will return Away = true if EITHER ag or kg is not presentā¦not both. In other words, one could be present but it would still change to Away. Is that your desired result?