[Feature Request] Ability to Include Header Information in Image Tiles

Here is the request:
It would be useful to be able to include HTTP(s) header information as part of the data used by the image tile. Even if it was a "secondary" input under an advanced section or such, or an entirely new tile. Header information such as tokens or cookies could be entered (or populated by a driver).

Reasoning:
More and more of the APIs and systems I access are requiring a cookie or authentication token to poll any data from them. This even applies to local ones on the network. While it is easy enough for a driver to handle that and include it in the Params of an httpGet (or similar command) there is no way to get an image onto an image tile at this time that requires such information. To my knowledge drivers still cannot write files to the file manager, so a driver cannot pull the image in and store it in a local location for the image tile to use (127.0.0.1 etc...). So if the image tile could include that header information (especially if it can be populated from a driver to keep the cookie/token up to date) that would alleviate the problem.

I did handle this for local purposes in my Google SDM API App/Drivers for Nest cameras... stored the raw base64-encoded image in an attribute (could also use state), then used an App endpoint to render the image back for a local dashboard tile.

Text we can do, images and other binary data, not so much…

I had not even heard/noticed about the text. That could be useful at some times (for enhanced logging, some of the APIs can produce text logs beyond what the log window can show)... but images is what I really want.

So this is a (hopeful) workaround to it.

@dkilgore90: I know some people have worked around it with apps or getting the file onto another device that can receive it... I just think that including the headers would make life a lot easier for these scenarios. Plus, I can write drivers... but I am not so much into the apps.

I put the routines in a driver for demonstration purposes, but really expect that most developers would copy the methods they needed.

https://raw.githubusercontent.com/thebearmay/hubitat/main/fileMgr.groovy