Setting Piston State vs using a PUSH notification

#1

1) Give a description of the problem
I can make either of these happen but so far do not understand why I would use one vs the other. They both appear to do pretty much the same. I read the wiki post on Set Piston State but it just said what you could do with it. It did not actually define what the commend is and what it is for.

2) What is the expected behavior?
Trying to understand the difference in use cases for these 2 actions.

Thanks,

#2

Set piston state will give you detailed information on the dash board.
Push notification goes to your registered phone.

I use piston state to get some info without needing to go through the logs.
I use push notifications to get info (changes, warnings etc) when I’m not around.

Here is what I see (Red and gray details about what happened and when happened)

28%20AM
Screen Shot 2020-01-25 at 10.46.28 AM.png734×676 65.4 KB

#3

@ike2018 said it well. Using the piston state provides some quick debugging information sometimes if a piston doesn’t run or what it did the last time it ran. Things I don’t want a message about every time but might want to know if something went wrong. You can set it to anything so it can be very convenient if used.

#4

That gets annoying very fast:)) Been there done that:)

#5

Best to use the following if using the new app (not the classic)–> Send Push notification and store in Messages

#6

This would seem to be the key difference, which makes sense. I will do some more playing. Learning fast but still drinking from the fire hose.

And yes to @jkp …I have a few of those stored in messages.

Once I get comfortable that things are running the way I want, then I will start trimming the notifications.

Thanks all for the quick responses.

#7

My two cents?

  • “PUSH Notifications” are for when I need to be aware of something NOW
  • “Piston State” is when I want a quick overview of all of my pistons and devices
  • “Log to console” is when I need detailed information for a single piston