Did anybody else’s CoRE randomly stop working about a week ago? I’ve tried updating the app in my IDE, but that didn’t fix the problem. Any guidance would be helpful. Thanks!
1 Like
Step 1: Open CoRE
Step 2: Rebuild all pistons
Step 3: test pistons to see if they are working
If not working
Step 4: open each piston not working
Step 5: rebuild piston individually
Step 6: stimulate piston
that should do the trick.
Yeah I wish I could do that. I can’t even open the SmartApp - when I click on it, I get the loading wheel and it never opens. I’ve tried installing it again through the Marketplace, but all that does is add more unopenable CoRE apps.
What version did you update to?
1 Like
Copied and pasted from the source code - v0.3.15f
EDIT: Realized this was an outdated version…updated my source code and things are running smoothly again. Thanks for that!
2 Likes
Question. Location tracking in ST has become quite cumbersome.
Is there a Core piston that I can setup to use Away Assist to trigger away mode in ST as opposed to using ST Mode to trigger Nest Away?
Quite often, I have a problem even getting into the SmartApp. It spins about 15 or more times, and then gives me the error message,
“You are not authorized to perform the requested operation”.
Then, I close it, and try again.
Sometimes it takes a few tries, but other times, I can sit there doing the same thing (I know, I’m insane) for a few minutes with no luck.
Then…it will finally let me in without doing anything different.
Is this just because of the known problem and impetus for creating the new version, or might something else be going on here?
How many pistons in CoRE do you have?
I had so many pistons the app would not open. I had to split them into 12 different installs of CoRE.
1 Like
I don’t recall exactly at the moment but I think it’s in the high tens…like 50-70.
How many are you doing in each instance of CoRE?
I started having trouble around 40. I have since split my pistons across a bunch of installs. If you want to have more than one install you have to change the following line to “false”.
1 Like
Awesome! Thanks.
So, for you, how many is the cutoff before you split?
By the way, I just checked (when I got in after trying for about 10 minutes), and it says I now have 86 running Pistons. lol
Also, how do you deal with updates? Do you just download the code, modify and re-publish each time?
I just looked to be more accurate with my info. I am at 16 CoRE installs. The most pistons any install has is 20 right now. Basically I am just splitting up instances based on functionality and rooms. For example here are some of my instances:
CoRE - Basement
CoRE - Master Bedroom
CoRE - Master Bathroom
CoRE - Shades
CoRE - Vacuums
CoRE - Remotes
…
I have one CoRE instance interact with other instances via Routines or Momentary Buttons.
For example, in one instance I have a piston that monitors activity on my first floor over a short period of time. If there is no activity (motion, contact sensors, power meters) during that period of time (5 minutes or so) it turns everything off. I have a piston in that same instance that monitors Momentary buttons. When the button is pushed via another CoRE install it fires off the piston.
As for updates I download via GIT integration and just make the code change manually before I publish. I published once or twice without making the change, caused no problems.
I often had problems with pistons failing over time and needing to be “rebuilt” via the option in CoRE. With too many pistons this “rebuild” was often failing.
1 Like
You saved my sanity!!
When I built out my ‘Rules’ infrastructure, I chose to go with a naming convention that would keep Like Things close to each other, and using ‘blank’ Pistons as section headings.
When it came time to start using CoRE, I prepopulated my single instance of CoRE with blank Pistons to represent all of the potential sections that I thought I might need at some point.
Well, I just removed (via the IDE) 28 such Pistons which had no other Pistons in their respective ‘sections’ yet, and was able to get in fairly quickly (only 11 spin cycles this time).
Now, I will go about the project of figuring out how to split up my Pistons and sections into multiple instances of CoRE.
Thanks a lot for this tip!! 
Doh!
Now that I’ve made the change to my single instance of CoRE, some (all?) of my Pistons seem messed up.
Is this change something that then requires starting over on Pistons?
Deleting pistons from CoRE should have caused an issue. But…
Taking my approach does mean rebuilding each piston you have built that you want to move.
I did it one piston at a time over a few months.
What I found was…
1 - I was able to make pistons more efficient now that I am more experienced.
2 - I had combined a lot of functionality into each piston, separating to several core instances allowed me to split that functionality across pistons.
3 - I found automations I didn’t need anymore so I didn’t recreate them.
4 - As I migrated away from dependence on routines to Momentary buttons, things got more reliable.
1 Like
OK.
Every Piston in the original instance of CoRE now has a ? at the beginning of the condition line.
When I go into the condition section, the ‘Comparison’ field is blank like I’ve never done anything there.
Then, when I go into Comparison, all of the options have a ? at the beginning.
Then, most of them have the word ERROR at/near the end of the THEN section.
Any idea what I might have done, or if there’s any way to ‘fix’ it?
Then, give me your opinion on this…
If it can’t be fixed, I’m thinking I’ll just leave the original instance in place as an example of what I have before.
I’ll designate a virtual switch to be the disabler for all of the old Pistons, to make sure they’re not mucking anything up.
Build out the new instances with their Pistons.
Delete the old Pistons as I duplicate them in a new instance.
Seem good?
Have you tried the “rebuild” option for one of your broken pistons?
As for you approach to split them out, that should work.
1 Like
Ya, rebuild didn’t appear to do anything…I’m not so sure it ever has…for me.
Oh well…I’ll just be flying free for a few days until I get some time to start building Pistons in the new instances.
Thanks again for this assistance.
I’m definitely on a better path now, in multiple ways.
One thing I wish were going to be part of the new CoRE (SE) is a migration option to ‘import’ all Pistons from the old version once it’s up and running lol @ady624
1 Like
Is it possible to use another piston’s state (paused / running) as a comparison?
v0.3.169.20170104
My CoRE stopped working. I have uninstalled it from the IDE and reinstalled using the My Smart Apps-Update from Repo, Enabled QAuth. When I try and create a piston I log this error:
error java.lang.NullPointerException: Cannot get property ‘id’ on null object @ line 10797
Piston is created with no way to edit and no name. Any suggestions?