Getting the ‘notify me when’ notifications when I’m home too, even though I have this unchecked. Only have away and night checked. Is it a coincidence that his just started happening to me yesterday, same time as all as you guys? I’m in the UK too. Clearly a problem their end
I really wanted to buy sirens for this system, but if this keeps happening, that’s not going to happen unfortunately:(
I’d like to add my voice to this as well!
Been having the same issues as everyone else, I’m based in the UK and didn’t change anything. I’ve opened a support ticket and Matthew responded to say it’s a known issue and they are looking into it.
It doesn’t affect the security of my house, as I have a cat that would trigger the sensors constantly on her way in and out so I don’t use it for security. Just frustrating when the bedroom lights come on 3 times in the night!
Thanks for the update @Jonathan_Rider, it’s good to hear that someone at SmartThings has actually acknowledged there is a problem that they’re looking into. All updates so far have been pretty generic, asking for examples, etc, so this is encouraging.
Many thanks,
Richard
I’m having the same problem. Routines running in the wrong modes; as do Webcore pistons relying on mode restrictions. Hope we find a solution soon, my setup depends heavily on modes.
Before this, these routines were rock-solid.
I’m in the UK.
Wynand
I wonder whether it has anything to do with sunset. Most of my mode issues seem to fall apart when that is involved.
My system is in home mode however I have sonos speakers setup to play a fire alarm in away mode when internal motion sensors detect motion. This worked perfectly for months but has now gone nuts.
Just not reliable. Sombody has messed up big time. Just happened to happen when I went on holiday and left the mother in law at home for two weeks with all hell braking loose!
also based in the UK
Hi all. Just a quick update to say I heard from Ellen from support last night:
Hi Richard, thanks for your reply and I’m so sorry for the long delay getting back! I’ve been making noise about this issue and our teams are still investigating, but beyond that, I don’t have an update just yet. I’m sorry about the seemingly slow going, but we often aren’t able to give timelines for a fix when it’s being actively worked on to avoid setting any incorrect expectations if additional testing is needed. If you can encourage forum members to also send their logs to the support team, more information is always a huge help and I’d appreciate it.
Let me know if when you see any recent occurrences of the issue and I’ll report on our investigating teams for further investigation, I’m sorry again for the wait on this.
So please continue to send in your logs of when this issue occurs including SmartApp name, date, time, what mode you were in when it triggered and what mode(s) it should only trigger in.
The strange thing is that I have not had any routines trigger in the wrong mode since Tuesday morning and I don’t know why. They haven’t told me they’ve made any changes or found the cause, etc. So maybe they’ve changed something on my hub? But then wouldn’t they tell me to check if the problem is still happening? Very odd. Anyway I know everyone on here is still seeing the issue so until I see confirmation and acknowledgement from support that they’ve fixed it for everyone I’ll have to assume I’ve just been lucky for the last few days and the issue could happen again at any time.
Just in case they’ve changed something on my hub to fix this my hub firmware version is 000.019.00017 - is this the same as everyone else’s?
For me all this started happening on 21st November, before which my system was working perfectly. I reported the issue on the 22nd November, and started this thread on 24th November, shortly after which I finally got a response from Ellen on Twitter on the same day. Pretty much nothing else has happened since then, other than reporting back all my examples as and when the issue occurred, and receiving replies from Ellen almost every day to advise they are still investigation and thanking me for my help. And I’ve not seen the issue again since the 28th November, while you guys are still seeing it. All very odd.
UK based as well, also had the same but only seemed to affect me randomly for a few minutes each day. Sadly those few minutes are during the night and causes my bedroom lights to come on full (motion set to be ignored if the mode isn’t evening), it hasn’t done it for the last few days but it could be that i’ve learnt not to move as much in my sleep!
I’ve been away since I first posted on here about this. It is still playing havoc with pistons and other routines based on modes also it appears that virtual switches are ineffective some of the time to stop lighting coming on in the middle of the night. Last night was the occurrence Friday 1st of December, finally paused the Piston to stop it keep waking us up at 1.14 am. All were fine until last week. Wife is getting very annoyed and wants it all ripped out! Hopefully smartthings will find a fix soon. Current firmware version 000.019. 00017 and I’m also in the UK.
Just coming along to say “me too!” and thank you for saving my sanity.
I’ve got a motion sensor and light in my bedroom, which has been coming on during the night, despite an “only when Home (not Night)” restriction, which has been driving me nuts.
I’ve put together a WebCore piston to log the mode changes, and, just to be contrary, it’s not logging any unexpected changes. And the false activations of the bedroom light have stopped. But I’m fairly sure that’s just a coincidence, because now I’m getting spurious motion alerts from my camera instead…
(Spurious in the sense that there’s genuine motion, but it should be ignored due to the mode settings.)
From the logs I was getting on the bedroom light, it seemed that the the mode was changing from Night to Home (or, very occasionally, Away), and then the motion was triggering. About 15 seconds later, the mode was changing back to Home, and this would turn the light off again. Nothing was logged by SmartThings itself, just the WebCore pistons.
I’m actually happier about the situation with the camera, because WebCore is not involved: this is just coming from Smart Home Monitor, so it’s all withing Samsung’s domain, and there’s no third party components they could potentially blame.
SHM is a mess lately, at least for me. It’s driving me crazy!
I’ve had to unplug the hub and rip out the batteries as the wife was getting very annoyed. Back to dumb home here for a while, which is better than a schizophrenic home. Hopefully they can figure this out soon but we can’t afford to just keep letting it screw up for them to collect data.
No word from support since Friday, and my system is still stable for no apparent reason since 28 Nov after first reporting this issue on the 23 Nov, while I see all yours are still misfiring all over the place, so not good and for all I know my issue may come back any time.
In the meantime it seems SmartThings are oblivious to half their users having useless systems that are having to be unplugged and they are rolling out yet another unrelated firmware update! The least they could do is post something on here and maybe even on their status web page to acknowledge they have a problem affecting some on their users! Not good SmartThings, please communicate with your user community!
Hub Firmware Update
Hello,
Between Monday, December 4, 3:00 PM GMT and Tuesday, December 5, 12:00 AM GMT, we will automatically update your SmartThings Hub v2 to the latest firmware (version 0.19.19). Your Hub will briefly go offline as it reboots and applies the update; most customers will experience less than one minute of downtime. This update will provide the following improvements:Fix frequent disconnects for users with an offline Hue bridge
Fix disconnect issue for some users with video cameras
This update only applies to the Hub v2 in all regions. Additional versions of the SmartThings Hub and works as a SmartThings Hub will not receive an update at this time. You can confirm your Hub has updated as described in “Is my Hub’s firmware up to date?” and see additional details about these changes in this community post.Thank You,
SmartThings Team
Yes disappointed to see a unrelated firmware update coming out when people are having these issues. My system I think is more stable but I’ve edited routines to prevent the spamming so not 100% all is back to normal.
Also never had a response bar the auto response to my email to raise the ticket.
Hmmmm. I wonder if it will include undocumted fixes? Might have to plug mine back and just wholesale delete routines then rebuild after some testing that won’t get me out out out of the house by annoying the wife.
Hi Richard
Exactly same issue for me. Awaiting feedback from ST support. I’ve left notes in my IDE to point them to the problem routine.
The issue only applies to a routine which is set to trigger during Night Mode, but is now randomly triggering during Home mode.
The routine is that, when there is motion, mode is Night, and Lux is less than 30, lights should come on for 2 minutes.
The effect of the issue is to switch off lights in the middle of the evening when Mode is Home (the lights switch off after the 2 minute timed period)
I got so fed up with this that 7 days ago I swapped Night for Away mode in the suspect routine (Note: Away mode is not active in my setup). Since then no more phantom switching (though that routine is effectively disabled now due to Away mode not being active on my hub)
I’m UK based.
Dave
Hi all,
I am experiencing the same issues, and have actually opened a separate topic with a more detailed description. (see here, also UK based)
One important hint / quick fix: It seems that all the issues only occur for SmartApps on the SmartThings platform. I have recreated some of the (mode dependent) functionalities in SmartRules (which also runs the routines in the SmartThings cloud), and all of them have performed reliably (so far… 
)
Let’s keep fingers crossed and see what the firmware update will do… 
Last night, my Schlage Connect door lock(s, I have two) unlocked by itself, after an hour and a half, after I’ve got home. When switched from Home, to Night mode.
What if it happens, when we are not home?
Take the door locks out of the Routines or Pistons until they fix the issue.
Or put a sign out front that says “Free stuff, come inside” 