Shelly Scanner

The Shelly Scanner scheduler editor is far more flexible than the one provided by the native app—albeit at the cost of greater complexity, which I believe is nonetheless manageable even for a less experienced user.
There are actually three slightly different editors for Gen2 (plus) and later devices, for the Blu TRV, and for the Wall Display, which combines a Gen2 scheduler with a dedicated thermostat scheduler.
Shelly Scanner allows you to easily exchange individual schedule elements as well as entire groups of definitions from one device to another.

Scheduler for gen2 or later devices

As you can see from the image you can choose a time (hours, minutes, seconds), one or more days of the month, one ore more months and one or more days of the week in which the actions that are defined subsequently will be executed. In the editable fields a number represents a simple value, * indicates that the execution must always occur (in the case of the snapshot every day of the month - "Days" field) or you can indicate a range (for example, focusing again on "Days", the value 2-10 implies that the execution occurs on the days between 2 and 10 at the times, in the months and in the days of the week indicated) or an interval (for example */3 on the same field indicates "every three days" but always starting from day 1 - therefore, between the end of one month and the beginning of the next, the interval may not be 3 days; 5/3 instead indicates "every three days" starting from day 5).
Finally, the comma ',' allows you to combine the notations just presented, so 3,5,10-20 on "Days" means "day 3, day 5, and days from 10 to 20."
A group of buttons will allow you to define times with reference to sunrise or sunset; in this case hours and minutes are used to advance or delay the execution of the event.
The small pencil-shaped icon that is located above each field will allow you to conveniently define any combination of individual values and/or intervals.
The field below "days of the week" and "months" is the result of all the other time fields in the format that will then be given to the devices; it has more or less a standard format (cron) and can be edited by expert users; above all it can be copied and pasted to quickly replicate the same time definition. Here you find a detailed description; note however that the described @random is not allowed on Shelly devices.

At the bottom of each scheduled task (job), you will find two fields to enter one or more commands (Method) to execute, along with any required Parameters; this aspect is admittedly more complex than using the native app, however there is no need know the basic commands—they are suggested when you click the icon . The full list of commands is documented by the manufacturer on the Shelly API page, though reviewing it requires some effort.
The advantage of this approach is that, with some effort, you can program behaviors that would otherwise be impossible, allowing your creativity to run wild; you can find some examples here.
Next to , you'll find buttons to add or remove a command, as well as a button to execute any individual command (test).
In most cases, the commands suggested by the menu can later be modified quite intuitively; for instance, if you choose to turn on a dimmer at 50% brightness, the Method field will be populated with "Light.Set," while the Parameters field will be set to “"id":0,"on":true,"brightness":50”. Replacing "50" with another value (within the 0–100 range) adjusts the brightness, while removing “"on":true” (including the subsequent comma) changes the brightness level without altering the on/off state.
Once entered, the most common parameters can be edited via the graphical interface; an Edit option appears in the menu whenever possible; the same result can be achieved by double-clicking on the parameter field.
Please note that scenarios not supported by the native app will not be correctly recognized by it.

On the right of any job you will find an icon that has the purpose of activating or deactivating the job itself and, even further to the right, the icons, arranged vertically, which serve respectively to:

• add a new job;
• duplicate the job;
• remove the job;
• copy the job;
• paste a previously copied job.

There is still a special case to take into account; when you set the automatic firmware update from the app, a specific job is actually created on the scheduler; you will see this job like all the others but Shelly Scanner will not allow you to modify the tasks.

Blu TRV Scheduler

Much of what was said in the previous sections regarding Gen2 devices applies; however here you don't manage methods but rather the desired temperature in Celsius degrees or the valve position (from 0 to 100).

The Load ... button will load the definitions from a backup file from a Blu TRV or a Wall Display; in the latter case, you will need to explicitly specify the profile to load. All loaded definitions will be disabled by default and will only be transferred to the device after pressing Apply.

Wall Dispaly Scheduler

Shelly Wall Display has a scheduler identical to the one described in the first section and, in addition, a dedicated scheduler for the thermostat function (shown in the illustration). This is an extremely simplified version of the Blu TRV scheduler, as hours and minutes can only be numbers (no intervals, sequences, or combined values). Seconds, days of the month, and months are also not supported.
On the other hand, the Wall Display includes the concept of profiles; essentially, you can define multiple profiles, each with its own schedule. You can then activate the profile that best suits a specific situation. The Shelly Scanner editor allows you to rename, create, remove, and duplicate a profile.

The Load ... button will load definitions from a backup file from a Blu TRV or a Wall Display into the currently selected profile. In case the backup file comes from a Blu TRV some time-based definitions, which are not compatible with the Wall Display, will be ignored. If the file comes from a Wall Display, you will be asked to specify the profile to load. All loaded definitions will be disabled by default and will only be transferred to the device after pressing Apply.

General aspects

Except for activating/deactivating a pre-existing job, any other changes take effect only after pressing the Apply button.

Hint: you can open multiple scheduler windows from multiple devices and copy/paste between them.

Examples

Below are examples of definition that cannot be implemented with the native app but possible using Shelly Scanner; you can simply copy the lines you find below and paste () them into a blank schedule that will need to be activated.
Cases not covered by the native app will not be recognized by the app itself, nor will you be able to edit them from the app; however, you will still be able to remove them.

Manual controls inhibitions (buttons or switches connected to a relay) during certain hours of the day; with the following definition the manual controls will be deactivated daily at 10:30 AM (these definition should work on every 1/1PM standard, PRO, and Mini).
{"timespec":"0 30 10 * * *","calls":[{"method":"switch.SetConfig","params":{"id":0,"config":{"in_locked":true}}}]}
to activate again the commands you mast use a secon definition like this:
{"timespec":"0 30 13 * * *","calls":[{"method":"switch.SetConfig","params":{"id":0,"config":{"in_locked":false}}}]}
which, specifically, reactivates the controls at 1:30 PM.

Weekly Reboot; here on any Sunday at 0:00
{ "timespec" : "0 0 0 * * 0", "calls" : [ { "method" : "Shelly.Reboot" } ] }

Activation of webhook/action at sunrise or sunset times and/or on specific days of the week; specifically the following definition activates the action with "id":1 half an hour before sunrise on Saturdays and Sundays.
{"timespec":"@sunrise-0h30m * * 0,6","calls":[{"method":"Webhook.Update","params":{"id":1,"enable":true}}]}
to deactivate the action, for example at 10:00, you need a second job like this:
{"timespec":"0 0 10 * * 0,6","calls":[{"method":"Webhook.Update","params":{"id":1,"enable":false}}]}
The id of the actions can be easily found with Shelly Scanner: double-click on the device and click on the tab Webhook.List.