Motion Sensor Fuel Stream

#21

Not sure with ady missing in action. Just a good rule of thumb is to be very selective as to what name you want because you cannot change it once created. (you can change the name in the piston, but that will only make a new data point. The old one will linger and clutter your screen) This is why I do all my testing in the ‘zz’ container, and only move it to the proper container once I am 100% happy with it.

I have also been known to ‘re-use’ old data points when testing, so as to keep my list nice and lean.

#22

OK thanks - will do. I’m making progress on my piston. To avoid angled lines above you added a wait and a second write to the fuel stream, but the second value is ‘$0’ rather than ‘0’, what does that do?

#23

My example above only use 0 and 100. There is no symbol before the number.

When the event happens, I set the OLD number first, wait 2 seconds, then set the NEW (accurate) number to avoid the angled lines.

This method works great for ‘binary’ type events. (yes or no)
(sunUp, moonUp, windowOpen, doorOpen, userPresent, etc)

Many other events work better angled since it is really a gradual shifting of data.
(temperature, humidity, barometric pressure, wind MPH, cloud coverage, river depth, etc)