[Saswell SEA801-Zigbee/SEA802-Zigbee] Please add support for weekly schedule #7080

soeren-a · 2021-04-14T21:02:36Z

Please add support for weekly schedule settings for the already supported Saswell SEA801-Zigbee/SEA802-Zigbee radiator valve.

What happened

With the current implementation there is no way to change or set the weekly schedule of the device. This is possible for other Tuya radiator valves but not for this one. There is no way to set the schedule on the valve.

Debug info

Zigbee2MQTT version:
Adapter hardware: CC2538
Adapter firmware version:

github-actions · 2021-05-20T00:02:50Z

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

soeren-a · 2021-05-21T19:04:48Z

It would be great if you could add the ability to change / adjust the weekly schedule. Thanks.

JohnRabbit1 · 2021-06-09T13:35:55Z

I have eceived this thing yesterday and have made the following for the schedule.

What you can do is the following:
Topic: zigbee2mqtt/yourdevice/set
Payload: see attachment

thermostaatjson.txt
dayofweek 1-7, 1=sunday
transitionTime: minutes after midnight

github-actions · 2021-07-11T00:01:27Z

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

kr0ner · 2021-09-07T21:21:05Z

I have eceived this thing yesterday and have made the following for the schedule.

What you can do is the following:
Topic: zigbee2mqtt/yourdevice/set
Payload: see attachment

thermostaatjson.txt
dayofweek 1-7, 1=sunday
transitionTime: minutes after midnight

Did this really work for you? I've tried it with the SEA802 and it does not seem to do anything :/

JohnRabbit1 · 2021-09-08T08:40:23Z

Yes sure it works. I have a couple of 801/802 thermostats here and programmed all of them that way.
If you are using nodered: I have attached a little flow wich does the trick for a complete week.
flows.txt
Rename flows.txt to flows.json (I cannot upload a json file)

kr0ner · 2021-09-08T08:46:09Z

Yes sure it works. I have a couple of 801/802 thermostats here and programmed all of them that way.
If you are using nodered: I have attached a little flow wich does the trick for a complete week.
flows.txt
Rename flows.txt to flows.json (I cannot upload a json file)

That is good to know :) thanks for the hints 👍

@JohnRabbit1 : seems that (at least for me) the week starts on monday, that's why I did not see anything ^^ offset by +1

Appart from that your solution works. Thank you :)

machv · 2021-10-15T14:03:19Z

Thank you for this tip. Maybe it can be added to the documentation page for this TRV?

And BTW is there any way to get currently configured schedule from TRV back?

I tried to send MQTT message to /get with payload {"weekly_schedule": ""} but it didn't work.

In device file (https://github.com/Koenkk/zigbee-herdsman-converters/blob/master/devices/saswell.js) I noticed that in fromZigbee section is tuya_thermostat_weekly_schedule, but I am not sure whether it is actually working.

Chekedaudau · 2021-10-27T20:33:34Z

Is there any chance to put this scheduler config in the gui of zigbee2mqtt?

maz3max · 2021-10-28T00:16:09Z

Is there any chance to put this scheduler config in the gui of zigbee2mqtt?

I would really appreciate this as well! Also, I took a look inside the code and wonder if the device can actually sync time?
It uses ignore_tuya_set_time which suggests that is doesn't get the time but I might be wrong.

Do you know more? @drzony @Koenkk

drzony · 2021-10-28T00:19:01Z

@maz3max Time setting is handled by a separate event https://github.com/Koenkk/zigbee-herdsman-converters/blob/28f1f8d4cb600fbeaa9432bb3df65a332c38f4c7/devices/saswell.js#L31

maz3max · 2021-10-28T00:21:19Z

@maz3max Time setting is handled by a separate event https://github.com/Koenkk/zigbee-herdsman-converters/blob/28f1f8d4cb600fbeaa9432bb3df65a332c38f4c7/devices/saswell.js#L31

Ahh, thanks for clarifying!

kr0ner · 2021-10-28T04:06:59Z

A good alternative might be https://github.com/nielsfaber/scheduler-card
I initially modified it so that it creates a scheduling JSON based on GUI input and sends it to the devices via MQTT -> zigbee2mqtt. Then I went back and let the scheduler-component manage everything from Home Assistant.

Chekedaudau · 2021-10-28T07:59:46Z

A good alternative might be https://github.com/nielsfaber/scheduler-card I initially modified it so that it creates a scheduling JSON based on GUI input and sends it to the devices via MQTT -> zigbee2mqtt. Then I went back and let the scheduler-component manage everything from Home Assistant.

The advantage for me with a scheduler direct on the radiators would be that it would even work if home assistant or zigbee2mqtt is not available for whatever reasons. There are other TuYa radiators where this config is possible in zigbee2mqtt. For example https://www.zigbee2mqtt.io/devices/TS0601_thermostat.html

geigervibe · 2021-11-09T11:12:49Z

I tried to set more than 4 transitions per day but without luck.

I got the following error in the logs and I wonder, if this is really a limitation of device or if the z2m-integration is limited:

Zigbee2MQTT:error 2021-11-09 09:12:06: Publish 'set' 'weekly_schedule' to 'zb_thermostat_t2' failed: 'Error: Too more transitions provided. Provided: 6 but supports only 6 for device zb_thermostat_t2'

when I publishing the following:

{
  "weekly_schedule": {
    "2": {
      "dayofweek": 2,
      "mode": 1,
      "numoftrans": 6,
      "transitions": [
        {
          "heatSetpoint": "15.5",
          "transitionTime": 480
        },
        {
          "heatSetpoint": "9.0",
          "transitionTime": 540
        },
        {
          "heatSetpoint": "25.0",
          "transitionTime": 600
        },
        {
          "heatSetpoint": "20.5",
          "transitionTime": 660
        },
        {
          "heatSetpoint": "22.5",
          "transitionTime": 670
        },
        {
          "heatSetpoint": "7.5",
          "transitionTime": 720
        }
      ]
    }
  }
}

Has somebody an idea about this?

kr0ner · 2021-11-09T11:17:06Z

I tried to set more than 4 transitions per day but without luck.

I got the following error in the logs and I wonder, if this is really a limitation of device or if the z2m-integration is limited:

Zigbee2MQTT:error 2021-11-09 09:12:06: Publish 'set' 'weekly_schedule' to 'zb_thermostat_t2' failed: 'Error: Too more transitions provided. Provided: 6 but supports only 6 for device zb_thermostat_t2'

when I publishing the following:
{
  "weekly_schedule": {
    "2": {
      "dayofweek": 2,
      "mode": 1,
      "numoftrans": 6,
      "transitions": [
        {
          "heatSetpoint": "15.5",
          "transitionTime": 480
        },
        {
          "heatSetpoint": "9.0",
          "transitionTime": 540
        },
        {
          "heatSetpoint": "25.0",
          "transitionTime": 600
        },
        {
          "heatSetpoint": "20.5",
          "transitionTime": 660
        },
        {
          "heatSetpoint": "22.5",
          "transitionTime": 670
        },
        {
          "heatSetpoint": "7.5",
          "transitionTime": 720
        }
      ]
    }
  }
}
Has somebody an idea about this?

It always has 4 slots. If you provide e.g. 2, 3 and 4 will be set to 2;)

drzony · 2021-11-09T11:17:27Z

@geigervibe The log message is incorrect, the device supports only 4 slots

geigervibe · 2021-11-09T11:27:05Z

Thanks for clarification... While I was googling for it, I saw some examples of more than 4 slots for other thermostats. So I was unsafe about this model. Thanks...

iksrd · 2021-11-12T19:02:15Z

I have a similar problem. I send the schedule, but nothing happens. Tell me what I'm doing wrong

{
"weekly_schedule": {
"1": {
"dayofweek": 7,
"mode": 1,
"numoftrans": 4,
"transitions": [
{
"heatSetpoint": "21",
"transitionTime": 240
},
{
"heatSetpoint": "22",
"transitionTime": 480
},
{
"heatSetpoint": "22",
"transitionTime": 1080
},
{
"heatSetpoint": "21",
"transitionTime": 1320
}
]
},
"2": {
"dayofweek": 7,
"mode": 1,
"numoftrans": 4,
"transitions": [
{
"heatSetpoint": "21",
"transitionTime": 240
},
{
"heatSetpoint": "22",
"transitionTime": 480
},
{
"heatSetpoint": "22",
"transitionTime": 1080
},
{
"heatSetpoint": "21",
"transitionTime": 1320
}
]
},
"3": {
"dayofweek": 7,
"mode": 1,
"numoftrans": 4,
"transitions": [
{
"heatSetpoint": "21",
"transitionTime": 240
},
{
"heatSetpoint": "22",
"transitionTime": 480
},
{
"heatSetpoint": "22",
"transitionTime": 1080
},
{
"heatSetpoint": "21",
"transitionTime": 1320
}
]
},
"4": {
"dayofweek": 7,
"mode": 1,
"numoftrans": 4,
"transitions": [
{
"heatSetpoint": "21",
"transitionTime": 240
},
{
"heatSetpoint": "22",
"transitionTime": 480
},
{
"heatSetpoint": "22",
"transitionTime": 1080
},
{
"heatSetpoint": "21",
"transitionTime": 1320
}
]
},
"5": {
"dayofweek": 7,
"mode": 1,
"numoftrans": 4,
"transitions": [
{
"heatSetpoint": "21",
"transitionTime": 240
},
{
"heatSetpoint": "22",
"transitionTime": 480
},
{
"heatSetpoint": "22",
"transitionTime": 1080
},
{
"heatSetpoint": "21",
"transitionTime": 1320
}
]
},
"6": {
"dayofweek": 7,
"mode": 1,
"numoftrans": 4,
"transitions": [
{
"heatSetpoint": "21",
"transitionTime": 240
},
{
"heatSetpoint": "22",
"transitionTime": 480
},
{
"heatSetpoint": "22",
"transitionTime": 1080
},
{
"heatSetpoint": "21",
"transitionTime": 1320
}
]
},
"7": {
"dayofweek": 7,
"mode": 1,
"numoftrans": 4,
"transitions": [
{
"heatSetpoint": "21",
"transitionTime": 240
},
{
"heatSetpoint": "22",
"transitionTime": 480
},
{
"heatSetpoint": "22",
"transitionTime": 1080
},
{
"heatSetpoint": "21",
"transitionTime": 1320
}
]
}
}
}

kr0ner · 2021-11-12T19:29:47Z

I have a similar problem. I send the schedule, but nothing happens. Tell me what I'm doing wrong

"dayofweek": 7
Copy & Paste error 😅

gomble · 2021-12-29T21:55:09Z

hello did someone find a solution ? Will this be in the gui in the future ?

hannah52 · 2022-01-14T09:32:02Z

hello did someone find a solution ? Will this be in the gui in the future ?

You could try proposed solution.
In my case I can set only 3 days max at a time . Thus I put 3 days msg + 3 days msg +1 day msg into zigbee2mqtt/[device Friendly Name] topic.

I suggest you to try with 1 day of week and check if schedule works for you.

But it looks like something was broken in 1.22.2 release. Now scheduler applies with time offset. I think it's better to use 1.22.0 or 1.22.1

JohnRabbit1 · 2022-01-14T10:03:16Z

Hi,
Yesterday, I tried to change my weekly schedule in version 1.22.2. Yes you are right: something has changed. The days are shifted somehow. Previously day 1 was monday. Now day 1 is tuesday. And so on. day 7 is monday. I don't have problems to set 7 days in one time.

gomble · 2022-01-14T10:04:41Z

yes the same problem. Is it not possible to configure this on the gui ?

JohnRabbit1 · 2022-01-14T10:26:30Z

No, not at this moment. I program the device in node-red with z2m node. It is a simple JSON structure which is injected in a z2m node.

KardinalReusen · 2022-10-04T10:29:00Z

I have eceived this thing yesterday and have made the following for the schedule.

What you can do is the following: Topic: zigbee2mqtt/yourdevice/set Payload: see attachment

thermostaatjson.txt dayofweek 1-7, 1=sunday transitionTime: minutes after midnight

Is it possible to deactivate / delete the weekly schedule of the device instead of changing it? And how can I do it?

JohnRabbit1 · 2022-10-04T11:08:31Z

You can set system_mode to off. -------- Oorspronkelijk bericht --------Van: KardinalReusen ***@***.***> Datum: 04-10-2022 12:29 (GMT+01:00) Aan: Koenkk/zigbee2mqtt ***@***.***> Cc: JohnRabbit1 ***@***.***>, Mention ***@***.***> Onderwerp: Re: [Koenkk/zigbee2mqtt] [Saswell SEA801-Zigbee/SEA802-Zigbee] Please add support for weekly schedule (#7080) I have eceived this thing yesterday and have made the following for the schedule. What you can do is the following: Topic: zigbee2mqtt/yourdevice/set Payload: see attachment thermostaatjson.txt dayofweek 1-7, 1=sunday transitionTime: minutes after midnight Is it possible to deactivate / delete the weekly schedule of the device instead of changing it? And how can I do it? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

KardinalReusen · 2022-10-04T12:35:04Z

I would prefer operating in system_mode auto (for being able to regulate the temperature) without having a built-in schedule because it is disturbing the settings I set in HA manually . Is that possible, too?

JohnRabbit1 · 2022-10-04T12:53:22Z

I am not familiar with HA. But what you can try is the following: there is a button on the device with tekst: auto/manu. Select manu: you will disable the built-in schedule. HA can change settings then. Never tried that. Reason fort hat is that I want all my devices operate independent from the automation system. In my case: when Openhab/Nodered fails (cann’t remember when that was the case) the buit-in schedule continues. So i am using the automation system purely for programmig the devices and switching on/off Van: KardinalReusen ***@***.*** Verzonden: dinsdag 4 oktober 2022 14:35 Aan: Koenkk/zigbee2mqtt CC: JohnRabbit1; Mention Onderwerp: Re: [Koenkk/zigbee2mqtt] [Saswell SEA801-Zigbee/SEA802-Zigbee] Please add support for weekly schedule (#7080) I would prefer operating in system_mode auto (for being able to regulate the temperature) without having a built-in schedule because it is disturbing the settings I set in HA manually . Is that possible, too? — Reply to this email directly, view it on GitHub <#7080 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUNJAKNFNVBZHQJ7MHQ232LWBQQAHANCNFSM426EV4TQ> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AUNJAKIRIFGEGMQUWFBK7K3WBQQAHA5CNFSM426EV4T2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOJOB4JIY.gif> Message ID: ***@***.***>

KardinalReusen · 2022-10-04T13:24:08Z

I am afraid, but I don't have this button on my SEA802. I assume you have a SEA801?

KardinalReusen · 2022-10-04T13:32:00Z

Maybe I found a solution here: Link. I will try it as soon as I get home.

drzony · 2022-10-04T13:52:23Z

@KardinalReusen In Home Assistant:
Auto - Based on temperature, but temperature is set based on schedule
Heat - Based on temperature, no schedule
Off - Idle
Below is SEA802 set to maintain 20*C at all times

JohnRabbit1 · 2022-10-04T13:55:54Z

Good to hear. You can also try this: system_mode: heat Van: KardinalReusen ***@***.*** Verzonden: dinsdag 4 oktober 2022 15:32 Aan: Koenkk/zigbee2mqtt CC: JohnRabbit1; Mention Onderwerp: Re: [Koenkk/zigbee2mqtt] [Saswell SEA801-Zigbee/SEA802-Zigbee] Please add support for weekly schedule (#7080) Maybe I found a solution here: Link <https://community.home-assistant.io/t/how-to-delete-factory-set-temp-schedule-from-t0l0-tuya-sea802-z01-radiator-valve/390286> . I will try it as soon as I get home. — Reply to this email directly, view it on GitHub <#7080 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUNJAKJ67GHGLPLUYNMVX73WBQWVXANCNFSM426EV4TQ> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AUNJAKLD5CVTTB36MJJ57SLWBQWVXA5CNFSM426EV4T2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOJOCPOTQ.gif> Message ID: ***@***.***>

KardinalReusen · 2022-10-04T14:33:42Z

@KardinalReusen In Home Assistant: Auto - Based on temperature, but temperature is set based on schedule Heat - Based on temperature, no schedule Off - Idle Below is SEA802 set to maintain 20*C at all times

Now I finally understand how it works! Many thanks. I will set the mode to heat.

soeren-a added the problem Something isn't working label Apr 14, 2021

github-actions bot added the stale Stale issues label May 20, 2021

github-actions bot removed the stale Stale issues label May 22, 2021

github-actions bot added the stale Stale issues label Jul 11, 2021

github-actions bot closed this as completed Jul 18, 2021

machv mentioned this issue Nov 18, 2021

Zigbee2MQTT Version 1.21.2-dev & Homeassistant Generic Thermostat & Hama 00176593 & Zigbee2Mqtt do not work - need help! #9185

Closed

SnakeZi mentioned this issue Apr 11, 2023

_TZE200_gd4rvykv not working #16966

Closed

AdamHyski mentioned this issue Oct 19, 2023

Update SEA801-Zigbee_SEA802-Zigbee.md Koenkk/zigbee2mqtt.io#2278

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Saswell SEA801-Zigbee/SEA802-Zigbee] Please add support for weekly schedule #7080

[Saswell SEA801-Zigbee/SEA802-Zigbee] Please add support for weekly schedule #7080

soeren-a commented Apr 14, 2021 •

edited

Loading

github-actions bot commented May 20, 2021

soeren-a commented May 21, 2021

JohnRabbit1 commented Jun 9, 2021 •

edited

Loading

github-actions bot commented Jul 11, 2021

kr0ner commented Sep 7, 2021

JohnRabbit1 commented Sep 8, 2021

kr0ner commented Sep 8, 2021 •

edited

Loading

machv commented Oct 15, 2021

Chekedaudau commented Oct 27, 2021

maz3max commented Oct 28, 2021

drzony commented Oct 28, 2021

maz3max commented Oct 28, 2021

kr0ner commented Oct 28, 2021

Chekedaudau commented Oct 28, 2021 •

edited

Loading

geigervibe commented Nov 9, 2021

kr0ner commented Nov 9, 2021

drzony commented Nov 9, 2021

geigervibe commented Nov 9, 2021

iksrd commented Nov 12, 2021

kr0ner commented Nov 12, 2021 •

edited

Loading

gomble commented Dec 29, 2021

hannah52 commented Jan 14, 2022 •

edited

Loading

JohnRabbit1 commented Jan 14, 2022

gomble commented Jan 14, 2022

JohnRabbit1 commented Jan 14, 2022

KardinalReusen commented Oct 4, 2022

JohnRabbit1 commented Oct 4, 2022 via email

KardinalReusen commented Oct 4, 2022

JohnRabbit1 commented Oct 4, 2022 via email

KardinalReusen commented Oct 4, 2022

KardinalReusen commented Oct 4, 2022

drzony commented Oct 4, 2022 •

edited

Loading

JohnRabbit1 commented Oct 4, 2022 via email

KardinalReusen commented Oct 4, 2022

[Saswell SEA801-Zigbee/SEA802-Zigbee] Please add support for weekly schedule #7080

[Saswell SEA801-Zigbee/SEA802-Zigbee] Please add support for weekly schedule #7080

Comments

soeren-a commented Apr 14, 2021 • edited Loading

What happened

Debug info

github-actions bot commented May 20, 2021

soeren-a commented May 21, 2021

JohnRabbit1 commented Jun 9, 2021 • edited Loading

github-actions bot commented Jul 11, 2021

kr0ner commented Sep 7, 2021

JohnRabbit1 commented Sep 8, 2021

kr0ner commented Sep 8, 2021 • edited Loading

machv commented Oct 15, 2021

Chekedaudau commented Oct 27, 2021

maz3max commented Oct 28, 2021

drzony commented Oct 28, 2021

maz3max commented Oct 28, 2021

kr0ner commented Oct 28, 2021

Chekedaudau commented Oct 28, 2021 • edited Loading

geigervibe commented Nov 9, 2021

kr0ner commented Nov 9, 2021

drzony commented Nov 9, 2021

geigervibe commented Nov 9, 2021

iksrd commented Nov 12, 2021

kr0ner commented Nov 12, 2021 • edited Loading

gomble commented Dec 29, 2021

hannah52 commented Jan 14, 2022 • edited Loading

JohnRabbit1 commented Jan 14, 2022

gomble commented Jan 14, 2022

JohnRabbit1 commented Jan 14, 2022

KardinalReusen commented Oct 4, 2022

JohnRabbit1 commented Oct 4, 2022 via email

KardinalReusen commented Oct 4, 2022

JohnRabbit1 commented Oct 4, 2022 via email

KardinalReusen commented Oct 4, 2022

KardinalReusen commented Oct 4, 2022

drzony commented Oct 4, 2022 • edited Loading

JohnRabbit1 commented Oct 4, 2022 via email

KardinalReusen commented Oct 4, 2022

soeren-a commented Apr 14, 2021 •

edited

Loading

JohnRabbit1 commented Jun 9, 2021 •

edited

Loading

kr0ner commented Sep 8, 2021 •

edited

Loading

Chekedaudau commented Oct 28, 2021 •

edited

Loading

kr0ner commented Nov 12, 2021 •

edited

Loading

hannah52 commented Jan 14, 2022 •

edited

Loading

drzony commented Oct 4, 2022 •

edited

Loading