Another thing I would like to suggest is to have the option to save both sent and received images locally on the phone or tablet. Now they are overwritten with each new notification from HASS or picture sent from device.
What is the use for the gallery when I only see the latest versions of these images?
I know there are ways around that by having HASS store them otherwise for keepsake, but it would be a welcome addition.
Or even some kind of sequential way for the naming convention of the files, so they are not overwritten?
I had a long debate with myself about this
But at the end I considered the following:
Image archiving is something you would want to do where you have the resources to do so (server side, as you said)
Zanzito is meant to be lightweight: archiving and managing maybe hundreds images would be complicated…
The gallery serves to have the situation under control at glance: like the rest of Zanzito, it’s about real time interaction.
But, if you have different image sources in HA, you can setup different notifier components, with fake device names, and then add a custom picture report for each of them: that way, at least, photo notifications from different sources wouldn’t overwrite each other.
First of all, there’s a bug in the address validation code, so thank you!
Zanzito was supposed to check the host name before attempting a connection, but it didn’t work.
The fix will be in the next release.
Second, yes, without http:// or https://, just the server name, and check SSL connection in the prefs