Advanced mutli schedule management

[cedricbarbecue]

Hello,

I just discovered this great integration this morning.
I don't really know how or why but I didn't come across it several months ago when I decided to switch from Netatmo to SONOFF TRV zigbee with full management via HA.
Not having found an integration for my needs, I did it myself via a few automations.
I find almost everything I want in "versatille thermostat" except the "simple" management of a complex schedule (an idea that comes directly from what the Netatmo app offers).

I took the time to read your documentation but I have the feeling that it is not possible via "versatille thermostat"

I need/want to be able to manage three schedules (work/in_holiday/friends_at_home) to set the target temperatures according to the rooms (13), times and days.

Having a good knowledge of Google Sheets, I host my schedules on a sheet that I convert into a large json that I retrieve as a sensor via the HA REST integration. Then I send the different schedules to my valves.

Afterwards, my algorithms are quite simple and clearly less advanced than what "versatille thermostat" offers.

In any case, my boiler self-regulates "a little by itself" and the heating is already much better managed than via my previous Netatmo configuration.

In short, is it planned to one day be able to integrate this type of schedule management into the integration instead of the "scheduler" integration which does not really allow the same thing ?
By the way, do you have any ideas so that I can do without my Google Sheet? I haven't found anything very practical for storing table-type data.

[jmcollin78]

Wahouuuu, this is really a great achievement.
One think missing on Versatile Thermostat is the capability to have an kind of internal scheduler and you have the idea. I love it.

It was not planned until today because developping a scheduler is something very hard and there is already a Scheduler in HA which is very complete ( but complex to use). Your case can be fully implemented with the Scheduler (see https://github.com/jmcollin78/versatile_thermostat/blob/main/documentation/en/additions.md#the-scheduler-component) but this is not a straighforward task.

I will this post for a eventual futur improvement. How do you do the integration of a json planning into a sensor with HA ?

[cedricbarbecue]

I agree that it could be done with the scheduler component but I will require a lot of work to be set and also for modification.
On my sheet if I want to create a new schedule I "just" need to add the name of the schedule then copy paste an other schedule then do the wanted modification.

Here is a copy of my sheet
Please ask my write right if you need more access

With app script directly on google sheet I can expose an endpoint with the json. I used this tutorial to do the implementation

function doGet(e) {
  const jsonValue = SpreadsheetApp.getActiveSpreadsheet().getSheetByName("Planning json").getRange("D1").getValue()
  return ContentService.createTextOutput(jsonValue)
}

With the Rest sensor integration I can create a sensor on HA

sensor:
  - platform: rest
    unique_id: heating_schedule
    resource: https://script.google.com/macros/s/AK....6/exec
    name: Heating schedule
    json_attributes_path: "$.data"
    json_attributes:
      - schedules
      - rooms
      - plannings
    value_template: "{{value_json.checksum}}"
    timeout: 60

Then I'm using an HA automation that check the checksum data of the json (use as the sensor state)
If the value change I do a loop on each room then send the schedule to each valve

As you can guest all my scripts have a strong dependency to what I want to send to the SONOFF TRV
I'm using the valve with their own schedule in System mode auto

I'm using the system mode heat only when I want to force a target temperature

I did that because at the beginning of my work I want to ensure that even with no access to the Zigbee network the valve could open an close automatically. This is done on the Netatmo valve (very useful because they could have some connectivity issue during some minutes/hours)
I think that isn't very smart because :

• the Zigbee network with the valve is very good
• It is a extra step that can be confusing and doesn't really improve anything

[jmcollin78]

So nice. I have created an issue to keep the idea and transform this into an eventual new feature