{"id":1816,"date":"2023-04-17T12:08:39","date_gmt":"2023-04-17T12:08:39","guid":{"rendered":"https:\/\/www.creatingsmarthome.com\/?p=1816"},"modified":"2024-08-14T11:21:38","modified_gmt":"2024-08-14T11:21:38","slug":"home-assistant-setting-up-time-schedules-to-shelly-devices-gen1-and-gen2","status":"publish","type":"post","link":"https:\/\/www.creatingsmarthome.com\/index.php\/2023\/04\/17\/home-assistant-setting-up-time-schedules-to-shelly-devices-gen1-and-gen2\/","title":{"rendered":"Home Assistant: Setting up time schedules to Shelly devices (gen1 and gen2)"},"content":{"rendered":"\n

Since my transformation to dynamic electricity prices are ongoing, I need to try to tackle up all the corner cases that comes with it. In previous article<\/a> I introduced more advanced cheapest hours automation that can handle devices which can be transferred to use the cheap electricity.<\/p>\n\n\n\n

Anyhow, some devices (like the water boiler<\/strong>) are still too much dependant of the system failures! Let me give you an example: My Unifi devices<\/a> are automatically updated every night at 01:00 and that might cause my WiFi network to go offline for few minutes. And my water boiler is controlled with Shelly EM3<\/a> that uses Wifi.. do you already guess where this is going? If the cheapest hours begins at 01:00 AND<\/strong> Unifi update happens, no control signal will be transferred to the Shelly and water boiler won’t start heating at all for that night. I think I would REALLY<\/strong> get some feedback from my wife if there’s no hot water for the upcoming day \ud83d\ude00

Well, I think I’ve found a solution for this corner case as well. Shelly supports internal schedules, but unfortunately Shellys Home Assistant integration<\/a> is not supporting them at the moment. However, we can use custom HTTP or MQTT commands for that. <\/p>\n\n\n\n

So here’s the plan what will happen after this enhancement: <\/p>\n\n\n\n

    \n
  1. Next day electricity prices are received and calculated by cheapest hours automation<\/a><\/li>\n\n\n\n
  2. Home Assistant will send command through to set the next active schedule to the Shelly directly<\/li>\n\n\n\n
  3. Shelly will handle the relay switch when the time is right<\/li>\n<\/ol>\n\n\n\n

    In this way we get rid of the dependency with Home Assistant, WiFi and Shelly. Of course there’s a possibility that during the set schedule sequence, the WiFi is down or Home Assistant is broken (never happened though). But on such special case, Shelly would use previous days schedule, so water would still be heated, even though it might not be the cheapest price at the moment.<\/p>\n\n\n\n

    Create functionality to set the schedules<\/h2>\n\n\n\n

    Shelly Gen 1 and Gen2 are totally different from each other by the software. Therefore I’ve made actually two guides how to achieve schedule settings: one for gen 1 and one for gen 2. For exact list of devices that are gen 1 can be found from Shelly official website<\/a>. If the device you are using is not listed, the device is most probably gen 2.<\/p>\n\n\n\n

    So depending of your Shelly device, jump either into Shelly Gen 1<\/strong> or Shelly Gen 2<\/strong> part of this article!<\/p>\n\n\n\n

    How-To: Shelly Gen 1<\/h3>\n\n\n\n

    First generation Shelly devices only supports settings changes by HTTP POST<\/strong> commands and MQTT is (mostly) just receiving data. So for this operation we can’t use MQTT, but have to rely on HTTP REST requests instead. <\/p>\n\n\n\n

    For the REST commands to work, a static ip needs be set to the Shelly device used. Static ip<\/strong> can (usually) be set from your network router, so please see the manual of the network router used. Once the IP is set as static, mark it down somewhere. We will use it on next step.<\/p>\n\n\n\n

    Rest commands<\/a> can be used by creating e.g. rest_command.yaml<\/strong> file and adding the commands into. Just remember to include the file in the main configuration.yaml<\/strong> file by adding ‘rest_command: !include rest_command.yaml’<\/em> -line into it.<\/p>\n\n\n\n

    Now that the Shelly is ready and we have the support to add rest command, let’s create one <\/a>to to do what we want to:<\/p>\n\n\n\n

    shelly_set_schedule:\n  url: http:\/\/{{deviceip}}\/settings\/relay\/0\n  method: POST\n  payload: 'schedule={{schedule}}&schedule_rules={{rules}}'<\/code><\/pre>\n\n\n\n
    In the url we need to set the Shelly endpoint<\/strong> that receives the command, using parameter ‘deviceip’<\/em> in here that will later be provided by the automation. <\/p>\n\n\n\n
    Depending on your Shelly device and usage, you might want to change relay number to something else (at the end of url line). I’m using Shelly EM3 that has only one relay, so I’m using relay index 0.<\/p>\n\n\n\n
    Second is the method. POST is generally used to change data<\/strong>, so that’s what we are using now.<\/p>\n\n\n\n
    Third is the payload<\/strong>. We want to set schedule<\/strong> (on \/ off) and rules<\/strong> (times) and those comes in as parameters from Home Assistant automations later on. <\/p>\n\n\n\n
    Rules needs to be in format HHMM-ddddddd-ff<\/strong>:<\/p>\n\n\n\n