Question about a delay or failure of signal


#1

I have a very basic piston to turn on or off a Hue bulb in my pantry, using a door sensor .
Door open =light on
door closed = light off simple eh , but here is the problem .

sometimes the light won’t come on or turn off even though on the ST app sensor open/closed is immediately shown every time without fail ( i’ve stood there opening and closing the door)
I would’ve thought that as the sensor is reporting correctly in the app that the signal to turn on/off the bulb would at least work every time .
Is there anything i can put in the piston to prevent a failure like this

TIA


#2

I’m not sure why that would be.
I have a similar simple piston and it works within 0.5secs. Quicker most times.


#3

Please upload a green snapshot.


#4

This happens to me since I have an access point that is close a hue bulb. If it happens that the APs channel is close to the one in use by the zigbee channel then my hue bulbs become unresponsive. I had to keep my AP on a specific channel instead of auto to make sure that my zigbee signal to the bulb doesn’t get flooded.


#5

It is hard to diagnose what your issue is because you are not providing everyone with a full picture.


#6

Not to turn anyone away from WebCoRE, gd forbid! I have this simple setup you explained on my closet door. For this particular instance I use the SmartThings built in app called ‘Smart Lighting’ (formally Lighting Director). They say that EVENTUALLY lighting rules using this app will be available locally even when the hub is offline.


#7

i have also noticed that in the ST app sometimes that the bulb is showing on but isn’t and vice versa really doing my head in


#8

Tried Smartlighting it was even more unreliable


#9

I think i have solved it with this little piston , only time will tell

Edit Nope … back to the drawing board


#10

When you use the SmartThings app to manually turn on and off the bulb how responsive is that?


#11

Very hit and miss too but a bit more so than the WebCore