Is XOR operator working?
I am using it to send an IFTTT maker event when a trigger (light changes to on) XOR condition (light is on)
But it’s sending the event twice. Below is the Piston.
Ignore the mode restriction, I set that to test if that was the reason for the doubling of events.
Well, each of the two condutions you have will run one IFTTT event, regardles of whether it evaluates true or false - you have both when true and when false individual actions for both conditions, hence the double event. Did you mean to have one acion for THEN and one for ELSE but instead added them as individual actions?
v0.1.10f.20160624 - Beta M1 - Fixed a problem with saving state globally (never worked) and the hue attribute 100/360 confusion. Philips Hue works, OSRAM Lightify seem to have an issue with retrieving the hue correctly, ST was informed.
I’ve been looking for a few days, how do I view CoRE’s dashboard?
Go to the ide and pull up the CoRE app and enable Oauth. Now on the smartapp on your phone, launch CoRE then you can tap the Dashboard link up top and it should load.
I realized that I had that Piston set up all wrong, so I killed it and started a new one. I think I am good now. I went with ELSE IF instead of XOR. My use case is setting up a ST dimmer to control a Wink Lutron dimmer…trying to get them synced.
Did I mention how much I love this SA? 
It appears a new problem has cropped up. This problem is not directly related to CoRE because it is happening in other apps as well. It no longer seems possible to change modes by calling routines, Attached is the CoRE app and the log results. This same problem is also found in RuleMachine so something has changed on the back end.
Edited: Executing the same routine in the SmartThings app works with no problem.
Which app is the owner of that error log? Press on the blue id to the left of the error message
Log shows it attached to the name “Mode to Away”
So I guess this is a routine problem? I went into the SmartThings Routine and it looks like all the parameters are intact. I re-saved it and it still isn’t working. It works if I execute it from the SmartThings app using the routines menu.
And it only does this if the mode is being changed in that routine?
I am not sure what you mean by "that routine"
I have several routines, two of which are “mode to home” and "mode to away"
In those routines I have it changing thermostat settings, turning off lights, etc…
When the routine is called from an app, such as CoRE it is no longer executing the routine, meaning it isn’t changing the thermostat or turning off lights, along with changing the mode from home to away. If I use the SmartThings app and tap on the routine, it will execute and do all the things it is supposed to do.
I will be away from the computer for the next several hours so I will reply to any questions when I get back. Again, this isn’t a fault of your CoRE app. I just hope it can be made to work again.
Yeah, my question is, if you have any routine that does not change modes, can you execute that from CoRE?
I just checked that, any routine execution fails. Seems to be related to ST, nothing us developers can do on our end.
Documentation says location.helloHome?.execute("Good Night!") and that’s what I do.
UPDATE: It seems to work once in a while. Most of the times, the right routine (the one selected to run) outputs an error message:
8:42:56 AM: error groovy.lang.MissingMethodException: No signature of method: script14668206705262022424921.execute() is applicable for argument types: (null, null, null) values: [null, null, null]
Possible solutions: execute(), autoExecute()
When it does work (about once out of 8 attempts), it outputs this:
8:44:31 AM: trace settings: [lockDoors:[Patio Door Lock, Kitchen Door Lock]]
8:44:31 AM: debug HH execute(), newMode: null
Note: Both logs above belong to the same routine.
@slagle @jody.albritton @Tyler
Should I open a support ticket?
Thank you
The routines bug messed with me today too. My CoRE ‘Good Morning’ routine fired right on time today, but did not change my Home mode from Night to Morning. Manually going into the ST app and triggering the Morning Routine manually had the desired effect.
Why not set the mode from CoRE directly and rely on Routines? I have a few routines but don’t use them anymore… Sounds a bit convoluted to have a smartapp ask another smartapp do something the first could have done in the first place. 
but then that’s just me?
I think back then when that was added, the list of devices was/is built around the switch capability. I guess I can make the list display devices in the same capability as the condition - and use switch for any non-device capabilities
I am trying to create a basic piston and when I try to do anything in it I get a red ‘you are not authorized to perform the requested operation.’ I enabled the dashboard and oauth, what am I missing?
