My Aeotec Dual Nano Switch doesn't seem to be evaluating Switch ON correctly

#1

I’ve been having some difficulty figuring out why my floods won’t turn off after motion detected and a 6 minute wait. I believe it is because checking its Switch state is coming back Off, when it is On.

After a 6 minute wait here, the Piston state is “Piston state: At 12:19… After 6 minute wait, switch was already OFF…sunlightScale0to4: 2”. I know I could just go ahead and turn it off regardless of state, but I would like to sound a chime if the lights went from On to Off.

download%20(2)
download (2).png1178×1143 123 KB

When editing the piston, nothing is desplayed for state of the device:

Capture

The IDE doesn’t show a Switch property.

Capture2

So might this be my problem here… The piston is not able to check the device Switch state?

#2

If you run it again, turn on Logging to FULL. Then you’ll be able to see what the state of the switch was determined to be when the condition is evaluated.

#3

I’ve had it running FULL today, just didn’t know exactly what to look for.

That condition was false all day, until the point I forced it to true. So, yeah, looks like I can’t ask for the switch state.

The parent device does have a switch state, but I’ve been a little confused since I got it as to what that means. If I switch that on, both associated lights come on. I can still switch the child devices on individually, but I guess I can’t query the switch state of the child device. Looks like I can query the power draw, but I’m not sure how often that is updated.

Perhaps (thinking out loud) I need to share the parent device to webcore? Not sure what that would buy me though.

#4

Yeah, you can post the logs you get and we can have a look at them.

But yeah…from what you’re saying…it’s looking like something which might be a bit of a challenge to get working. I don’t have any of those devices so I can’t speak to the specifics of them. Hopefully others will come along with a bit more insight.

But like I said, you can post the logs and we can look at them. That tells quite a bit about what’s happening.

#5

When I saw that condition #62 was never true I started to catch on.:slight_smile: I’m assuming that I can’t grab the switch state and will move on without it. Seems silly that I can set it, but not get it. I could set another value that contains the switch state but I don’t think it’s worth the trouble at this point.