Improvements

[spencermehta]

I'd like to create a checklist for more things that can be added/improved about this.
If you have any suggestions please add them here.

• [x] Enable/disable tweeting
• [x] More than two tweet thresholds
• [x] Downtime
• [x] Custom hostname for pingTest() in config
• [ ] Fix issue that tweet always uses highest threshold, therefore lower threshold messages never get tweeted
• [ ] Pushbullet integration
• [ ] Tweet for downtime
• [ ] Email notifications

[sethrd]

How about pushbullet notifications for passing a threshold instead of / along with tweets?

[N4Z1T]

ISP downtime

ex: @Symphonet #internet is back! It was down for 28 minutes and 11 seconds, since 10:10:28 AM.

thank you very much for awesome work!

[spencermehta]

@sethrd Good idea. I'll have a look into how I can implement this.
@ariyako That would be possible, but you would have to set it to run at very frequent intervals to get any sort of an accurate downtime timeframe. I suppose if there is no detected connection at all, it can reduce the interval until a connection is re-established.

[spencermehta]

@ariyako I've implemented a basic downtime counter. My next goals are to allow tweeting of downtime and let the user set a custom hostname for the pingTest() in the config

[joshp23]

optional email notifications

[N4Z1T]

thanks you so much for downtime counter!.

[N4Z1T]

ping -c 1 " + hostname

Bad option -c. (Win 7)

[spencermehta]

@ariyako What version of Python are you using?

[N4Z1T]

3.5.2

[spencermehta]

@ariyako I've slightly modified the code for this. Could you try again to see if this fixes it?

[N4Z1T]

same error ping with -c come as bad option for windows os