There have been many posts related to the seeming flakiness of web hooks, and I’ve certainly had my share of struggles with them over the past couple of weeks. Callbacks not being executed, rarely callbacks being executed multiple times for a single publish command (I mean the ENTIRE SET of callbacks being called repeatedly), and worst of all a webhook simply not working anymore and unrecoverable even after reboots, delete and re-create, only to be eventually brought back randomly one day for no reason.
This was all for the matter of learning. I was using the famous get_weather webhook and correlating some of the received data with some local sensor data, and then posting both to Librato. So just a slight variation on the tutorials. Simple enough stuff. But combining the behaviors above with some difficulties I’ve been having with deep sleep mode, and I just didn’t have time to troubleshoot everything at once.
So I removed any reference of the get_weather webhook from my program and at this point am only reading sensor data and posting it to Librato. And so far that has been reliable - no GET hook being published to (that seems to be the source of trouble).
BUT…and this is a BIG but…can someone explain to me why suddenly the get_weather callback is now being very reliably triggered, every 1 minute or so (a periodicity I’ve never used)? I see it on my dashboard. The active program is neither subscribing to nor publishing to that web hook (I didn’t delete the webhook itself), yet it is being triggered! It has been FULLY deleted from my program, and a new program is flashed to the chip. That program is reliably reading and posting sensor data to Librato. The weather data is no longer being posted to Librato, but it IS being triggered according to the dashboard.
Why!!! I’m so confused.