Is your feature request related to a problem? Please describe.
I have an ESP32-backed device (reTerminal E1002), and I want to have it deepsleep for periods at a time. But I also want my HA to queue an image for the device, such that I can arbitrarily call drawcustom, and send an image off - then when the device reconnects, HA will serve it that desired image.
Describe the solution you'd like
I imagine that drawcustom (And anything else) first queues an image in a "desired image" sensor for my OD device. For always on devices (powered, not deepsleep configured, nRF devices, ..), the sending can immediately begin. Once the sending is complete, the "current image" sensor can be set to what is.
For deep sleeping devices however, the image is not sent immediately. It is instead stored persistently in HA, and then when the sleeping device connects, the desired image is sent out. Once complete, the current image sensor updates.
We should also add other sensors, like "image queued: true", or "image last updated: "
Describe alternatives you've considered
I could invert the control, so the moment "last updated" is activated, I have an automation that tracks my own custom "desired image" (possibly in the form of ODL), and sends that off.
Additional context
N/A
Is your feature request related to a problem? Please describe.
I have an ESP32-backed device (reTerminal E1002), and I want to have it deepsleep for periods at a time. But I also want my HA to queue an image for the device, such that I can arbitrarily call
drawcustom, and send an image off - then when the device reconnects, HA will serve it that desired image.Describe the solution you'd like
I imagine that
drawcustom(And anything else) first queues an image in a "desired image" sensor for my OD device. For always on devices (powered, not deepsleep configured, nRF devices, ..), the sending can immediately begin. Once the sending is complete, the "current image" sensor can be set to what is.For deep sleeping devices however, the image is not sent immediately. It is instead stored persistently in HA, and then when the sleeping device connects, the desired image is sent out. Once complete, the current image sensor updates.
We should also add other sensors, like "image queued: true", or "image last updated: "
Describe alternatives you've considered
I could invert the control, so the moment "last updated" is activated, I have an automation that tracks my own custom "desired image" (possibly in the form of ODL), and sends that off.
Additional context
N/A