agent_katerB
So, first of all, this solution will be cleaner and easier if you could power the first Shelly all the time and wire the switch into the switch input. But if that’s not possible, you can still make it work.
If you can wire the Shelly for permanent power, I think you can even make it work with the original Shelly firmware. It can call webhooks so the first Shelly can call the HTTP API of the second Shelly. I didn’t try it out though.
Otherwise you’ll have to flash Tasmota: Original Shelly series Shelly Plus series
Then you can configure the first Shelly to periodically (e.g. every 55 seconds) call Tasmota’s HTTP API on the second Shelly and use PulseTime on the second Shelly to turn off after 1 minute.
Do you need email in/out or are you ok with people having to log in?
That will consume almost all processing power if it’s CPU-only and is a very slow process.
This is a complicated topic and the terminology is a bit ambiguous.
Yes, non-hardware-accelerated transcoding is slow and will consume the CPU.
However, you don’t necessarily need an external GPU to do hardware-accelerated transcoding. When you use Intel QuickSync for example, the codec hardware is part if the CPU. On the other hand it is only in CPUs that have integrated graphics, so you could still say the transcoding is done “by the GPU”, just not the additional one that you put in. In fact, putting in a dedicated graphics card often disables the integrated graphics and you have to use tricks to re-enable it before you can use it for transcoding again.
No backup no mercy. It’s really not different than with any other drive. In this case it’s even in the name, “Drive”, but it’s the same with Dropbox, S3 and all the other cloud storages. Make backups guys.
Telegram is known for being open source, but since it isn’t, you can’t self-host it. Does that count in the sense if your question?