Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Read and write schedule (enhancement) #119

Open
Eugen4 opened this issue Dec 24, 2024 · 2 comments
Open

Read and write schedule (enhancement) #119

Eugen4 opened this issue Dec 24, 2024 · 2 comments
Labels
enhancement Something to improve or enhance VitoWiFi

Comments

@Eugen4
Copy link

Eugen4 commented Dec 24, 2024

Installation specifics

  • Heating type: Vitotronic 200
  • Protocol: P300
  • Board: ESP8266 (Wemos D1 mini)

Symptom

What happens? I wasn't able to read and write schedule for water heating
What would you expect? Add function to the library for simplify read and write schelude info to Viessmann

Extra info

ESPHome provides such possibilities:
Schedule plans info: https://deploy-preview-2737--esphome.netlify.app/components/optolink.html#schedule-plans
Code reference: https://github.com/80morpheus/esphome_optolink/blob/optolink/esphome/components/optolink/helpers.cpp

Some usefull info from here openv/openv#282

 * ## Unit: CycleTime
 * Desc: 1 byte coding of the switching times.
 * The switching times are divided into 10 minute steps and coded
 * this saves space.
 * The upper 5 bits represent the hours, the lower 3 bits the number
 * share of 10 minutes
 *
 * MSB LSB
 *      +---+---+---+---+---+---+---+---+
 *      | h4  h3  h2  h1  h0 | m2-m0 * 10|
 *      +---+---+---+---+---+---+---+---+
@bertmelis
Copy link
Owner

Can be implemented. Could you remind me in a week or so? I'm enjoying some time off 🎄.

@bertmelis
Copy link
Owner

I don't use this feature myself so I'm not really familiar with the schedule.

A single schedule is encoded by a series of 8 bytes with each byte representing a time (rounded to 10 minutes). So for one day you can define 4 periods (time on + time off = 2 bytes). A whole week needs 7 * 8 bytes = 56 bytes, as referred to on the Home Assistant page.

I don't know if a single time entry can be read or written or the whole schedule (56 bytes) need to be requested.

So my main question: How would you use the schedule?

@bertmelis bertmelis added the enhancement Something to improve or enhance VitoWiFi label Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Something to improve or enhance VitoWiFi
Projects
None yet
Development

No branches or pull requests

2 participants