Delay before first report

[agentgonzo]

Is it possible to (optionally) make the ispindel do it's sleep/delay before sending the first message?

It connects straight away as soon as I turn it on after charging. Given it's not floating in the beer at that point, it reports a wild number for the angle/gravity. Which then makes all my charts scale unnecessarily to take account of a huge or tiny SG value.

It would be nice if I could turn it on, drop it in the fermenter, then have it send it's readings once it's settled

Thanks

[ErikdBr]

I just delete the 1st reading from BrewSpy.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[gizmocuz]

I think this is a very interesting request. If you are using it to report to InfluxDB/Grafana/MQTT, you just can't delete that initial value
A setting where you can specify a 20 second delay fixes this

[thegreatgunbantoad]

It kind of feels like the fix here needs to be in the server/cloud side, this is a flaw of those tools. Brewfather does not have that problem, perhaps these other tools should be allowing deletion of data points or attaching the device after it is in place.

[ErikdBr]

It kind of feels like the fix here needs to be in the server/cloud side, this is a flaw of those tools. Brewfather does not have that problem, perhaps these other tools should be allowing deletion of data points or attaching the device after it is in place.

Agreed, BrewSpy doesn't have that problem either, just delete any datapoints you want.

[thegreatgunbantoad]

#644 is sort of not dissimilar. If there were an option to stop sending when fully upright(ish) or horizontal(ish) it would solve both of these issues.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[thegreatgunbantoad]

I might have about 70% of a work up going, just need to find my spare unit to play with now by brain is getting back in action. Doesn't action it but hope full;y this will let you set the bounds: https://github.com/thegreatgunbantoad/iSpindel/tree/add-angle-bounds

{Edit: I've been a bit messed about by new blood pressure meds so I haven't been looking at this and probably won't for a little while yet.]

[agentgonzo]

As menioned above, brewspy may allow you to delete things, but the first datapoint is almost always invalid as it is in your hand after you've flipped the power button. It doesn't make sense to get everyone to go and delete the first datapoint when invalid anyway... much easier to just not send it in the first place.

[ErikdBr]

Well, that 1st datapoint is very handy to confirm everything is working. If you flip the powerswitch and you don't get that 1st datapoint and throw it in your brew and it doesn't work what then?

You don't want to automate everything is my 2 cents (and of the rest of the programming world)

[agentgonzo]

True. I hadn't though about just the signal as being useful. I find that first datapoint throws off all my autoscaling graphs and is counter productive. I always check for the blue flash to know it has sent the signal.

It would be nice as a config value to optionally send the first datapoint or not.

Gravitymon has a nice feature where it won't send out-of-range signals, or if the accelerometer is indicating that the tilt is unreliable/moving.