Anyone else getting double notifications?


#21

For what it’s worth, I always combine these two triggers in the same piston:

IF Bulb1's switch changes to on
    Then do cool stuff
END IF

IF Bulb1's switch changes to off
    Then do other stuff
END IF

My logic is, even with only a single one of them in a piston, the piston still fires at both events. So combining them both in the same piston effectively turns two triggers into one.
(although the conditions still controls the logic flow)


Just make sure that the two blocks are separate from each other.
(do not nest these triggers)


#22

So I modified it and it seems to be hit or miss on whether the double notifications come through (sometimes they are, sometimes they aren’t.) I think the device is sending the command twice so fast, the piston isn’t always catching it in time…


#23

I cannot tell from the screenshot, but both WITHs that contain a WAIT need to have TCP set to Never.

Other than that, it looks solid.

I would turn on Trace, and set Logging to Full and let her run for a bit.


Observation:
Your latest piston should notify your device once via ST app, and another identical worded notification via your email app. This means, at a quick glance, it will appear as if you got two of the same notifications. Maybe change the wording on one of them to stand out a bit?

Also note that emails have a strict daily limit, whereas PUSH notifications do not.
(With a daily limit less than 50, I reserve email notifications for rare or precious alerts)


#24

You’re right, when I re-did this, I forgot to set the TCP back. I did that now and sometimes it’s double notifications, sometimes not. I guess I’ll just leave it the way it is, as this doesn’t occur that many times, but I was just curious why I was getting them. Yes, 2 different notification types, but I was getting the double notification even without setting up 2 different ways to be notified…


#25

This is to be expected without all of my recommended changes.


After making the changes, (and pausing the old pistons), if you are still getting double alerts then I would need to see the latest piston, with Trace turned on, and a Full log with errors to go any farther.


#26

Thanks