Unless I'm missing something, seems kind of short-sighted to not keep a local copy of the schedule just for this very situation?
In fact, why would you even design it like this to begin with? It's not like a pet feeding schedule is dynamic data that changes every day. Makes no sense.
when I was poking at the protocol (MQTT plaintext, including the auth) given the esp32 doesn't have a RTC onboard, they would send MQTT packets with the current time and I suspect that they trigger off of those time packets rather then the software time source on the esp32.
Comments
Unless I'm missing something, seems kind of short-sighted to not keep a local copy of the schedule just for this very situation?
In fact, why would you even design it like this to begin with? It's not like a pet feeding schedule is dynamic data that changes every day. Makes no sense.
when I was poking at the protocol (MQTT plaintext, including the auth) given the esp32 doesn't have a RTC onboard, they would send MQTT packets with the current time and I suspect that they trigger off of those time packets rather then the software time source on the esp32.
Interesting! Hadn't even considered that.