Osram Lightify Randomly Turns On

#1

I posted this same request on the main SmartThings community forum, but that was to try and do something within CoRE. Now that I’ve moved over to WebCoRE, I wondered whether any of you guys might have a few better ideas!

Essentially, it’s a well known problem that Osram Lightify bulbs have a habit of just turning themselves on randomly. The solution is apparently to update the bulbs firmware - but I’ve done that and they still come on. I’ve lost count the number of times, I’ve woken up and the the corner lamp in the living room has been turned on without my knowledge!

So… do any of you know of any possible ways of turning the lamp in question off automatically?

I can’t really do it between two points in time, because say one of us is up late with the lamp on for a genuine reason - I don’t want it to turn off automatically.

Bit stumped!

#2

I did something similar for when we are away. I had someone else come into my home to feed the cat but they forgot to turn off the lights. I’m a noob so I’m sure there is a better idea out there but what about doing the 2 points in time but wait for 30 mins? So mine is only when all away if a light changes to on, wait for 30 mins and turn off the whole house light?

#3

do you have a motion sensor in the area that you could use to turn off light say 30 mins after last motion?

#4

The only motion sensor I have in my setup is in the hallway (outside the main living room) so I don’t think that is an option. I could go out and buy another one but it seems a bit distrastic just to fix this issue - I might as well buy a bulb that doesn’t do this!

I suppose what I could do is… when we go to bed, we ALWAYS run a lights off routine which turns off everything in the house. When we do this, I could set it to another mode and then do as @borristhecat says and turn it off if it comes on whilst in that mode?

#5

didnt mean to suggest you go out and buy one. not knowing the setup was just asking. :slight_smile:

do you also have another routine that gets run when you are up and about and its OK for the light to be on? if yes, between the time the go to bed routine runs and this routine runs you could turn off the light if it turns on.

yes, you could do that. if you wanted to create another mode so you could turn off errant lights during that mode.

#6

that will work for when the house is in away mode. if the light randomly turns on like @Hilly_2015 posted then off course it will not help if someone is in the house the light randomly turns on.

#7

yes but if he instead puts if between time A and time B a light turns on or if he has a night mode then it would work.

#8

sure. the only caveat on those are the family would have to go to sleep by a certain time or on the second one, there would be no difference between night mode and sleep mode. :slight_smile:

if there is a going to sleep routine and woke up from sleep routine already, that would make it more flexible and convenient.

#9

sorry didn’t read your reply fully

That is what I meant he could do

@Hilly_2015 just incase it helps this is my piston

image
image.png1178×579 27 KB

I also use TrendSetter smartApp to group certain lights so RGB Bulb 8 is the whole house light which has 1st floor and ground floor grouped lights in.

#10

yep, understood.

think OP may have a slightly different issue from this use case. for OP light is turning on randomly, not that someone turned it on and left it on.

#11

If it randomly turns on though should it not still send a message to ST to say it’s turned on?

#12

even if it does, the mode may not be away. which is what i was trying to clarify with this:

#13

Think I get what your getting at :thinking:.

On a slight side note I just realized that my piston doesn’t react exactly as I want it to. If another light turn on whilst it’s timing down its restarting the 30min timer, how do I get this to just carry on rather than restarting?

#14

ok

replace everything in the then … end if block with:

with $currentEventDevice (set TCP to never and TSP to allow multiple)
   wait 30 mins
   turn off
end wth

wait your rgb bulb 8 is a group device? if yes, then do this:

with rgb bulb 8 (set TCP to never)
   wait 30 mins
   turn off
end wth

EDIT: even better change the whole piston to this:

if location mode is away (set subscription mode to always)
   if any of bulbs 1, bulbs 2 or bulbs 3 changes to on
       with rgb bulb 8 (set TCP to never)
          wait 30 mins
          turn off
       end wth
   end if
else
   with location
      cancel all pending tasks
   end with
end if
#15

Thought it was something to do with TCP but tried a few things and couldn’t get it to work, so thanks for this.

Is this what you ment?

download
download.png1178×649 99.6 KB

#16

yes, thats what i meant. does it work as you expect?

#17

Not quite, when the mode changes to away it starts the countdown even if no lights are on.

#18

hmm … sometimes nested changes to can be funky. what if you change the changes to on to is on?

if you do that you dont need to force subscription on the location mode anymore because all conditions would then be conditions and subscribed to automatically.

#19

Nope that doesn’t work :(. I also noticed that both of them still reset the timer every time a new device is turned on aswell.

#20

ok, i will try the piston later today and see if i can figure out whats going on.