Feature/support ctlv2 #266
Conversation
janphkre
force-pushed
the
feature/support-ctlv2
branch
from
5521b60 to
066bb36
Compare
janphkre
force-pushed
the
feature/support-ctlv2
branch
from
066bb36 to
c7b76b8
Compare
|
You removed (commented) SFMode. It dies not work on 720. Do you know the new address for SFMode? |
|
It is not necessarily a different address, the 720 might be using a different datatype for it, as it is using different data types for the timeslots. Since i still do not know what SFMode is, I can not find out which value is there to be expected for it under which condition. However, every commented line that has the name "Unknown*", is a value that i was able to observe on the bus without actively probing for it. Maybe it is one of them. |
There was a problem hiding this comment.
See janphkre@2a08b2e#commitcomment-91984115
the comment is in the Unit column. changing the ,at the end of the line to . changes the number of columns in this line.
|
try for ctvl2 so vrt 380 2022-12-08 15:12:37.029 [main notice] ebusd 22.4.v3.16.2-200-ga8ca21f541 started with auto scan on device 192.168.0.54:3333 |
|
Great enhancement, thanks for the contribution @janphkre I'm also using a SensoConfort 720 (wireless) |
|
Tks for work : now my file ctvl0:
Entity for thermostat is : temp setpoint = hc1actualflowtempdeisider ? but only read mode |
I noticed some issue with the line below the one you commented and fixed those in both de and en. I hope it is the issue you mentioned, because i couldn't see an issue with the line you mentioned in a csv editor. |
In your example the first command has an issue: I was able to write to the second slot if this first command contains the total amount of slots that shall be set / active: I don't know if this "array size" actually does something on the second and third slot, but it has to be specified for all commands. However, I noticed a problem with the hwcTimer: In the message definition for |
My configuration is the same, execpt for z2Timer and z3Timer, so I'd guess that you only have one zone configured and that is where the difference is resulting from. But still it is a mistery to me what this command does, but i guess that is okay for the time being: |
For me the ctlv2 shows up as follows: To answer your question:
The
The mode of the thermostat can be read out through the fields |
@janphkre fixed the comment issue in 40632c9 what do you see in the following lines? |
i try your config 👍 read scan config file vaillant/15.ctlv0.csv for ID "ctlv0", SW0313, HW9103 in mqtt i found :
for study and improve what do u suggest me to start. Itry with your modify z1ActualRoomTempDesired change to respect manual setting temp room on vrt 480 actual temperature room vrt480 i think |
|
Now i want try with mqqt havac code `climate:
|
@LukasGrebe |
@1achy |
|
Thanks for this PR. Most items work on my 720/2 but I had to change and do you haven an idea on how to write the timeslots? |
|
Hi, I also have this senso comfort and it is found as 15.ctlv2. How can I force ebusd to load this 15.ctlv2.csv? Just tried I downloaded the repository, took 08.hmu.csv, 15.ctlv2.csv and 26.vr_71.csv in etc/ebusd/vaillant. I took memory.csv, broadcast.csv and _templates.csv in /etc/ebusd. |
I create a csv for the Hydraulikstation, see my post or my github repository |
I've changed it to a HEX:2 - and then I'm able to set the schedule with the following (I think that' what you've meant with 'value explicitly'): I'm aware that it's not elegant - but I don't know ebusd that well and this solves my issue - what do you think about that solution? I've noticed another thing - when updating the configuration value - I have to do a forced read before I'm getting it back |
|
Have the same issue as @SzosszeNET Most of the values are not reported. |
|
created a PR @janphkre janphkre#1 |
|
Does anybody know whether it is possible to set multiple heating time slots simultaneously?
Can I somehow combine this into one message? Otherwise I would have to execute quite a lot of write commands whenever I want to change the temperature. |
duplicate lines deleted
|
@john30 what is hindering the merge? The requested change was implemeted both files have the same length now. I would argue that hundreds of users are waiting for this integration, because it's a very common thermostat. |
|
@majuss - maybe ppl having life? Doubt John gets paid to to this and even if he was this a little respect goes a long way. Was lucky found this PR - you can clone it, point your ebusd to it and works, sure not having to do it would be easier, but not everything is perfect. |
|
@SzosszeNET I'am sorry that it came around as negative. It was meant to be a neutral comment and the question how we can help. |
|
Edit - was too hasty, looks like it works now I think this functionality gets broken by #316 somehow. Just tried ebusctl info HMU loads but the CTLV2 CSV does not |
|
I used this mod and to continue is WORK !!!!!!!! I use personal config 👍 I attach : BACKUOP CARTELLA IN WWW ebusd_mod_ctlv2.zip Picture config for use personal config WORK. ALL:
|
|
@1achy seems only to work with ctlv0 I have a ctlv2 and it doesn't work :( Still no timers etc. and a lot of commands that couldn't be processed. I'am using ebusd addon in HA version: 23.2.6. Is 24.1 necessary for this fix to work? EDIT: Tested it with 24.1 still same behavior. I want to desperately set a cc.Timer but still no luck. Wenn I change the time on the panel some unknown MS commands pop up, maybe related to that, maybe not. The cc Timer topic is never created in MQTT. 
|
Which configuration settings did you choose? If you choose the automatic configuration from john30 you should check the 15.ctlv2.csv for your "missing" timers. Not all timers are available here. I copied the repository from to my local system. |
|
Okay I used this repo not not the link provided by @1achy. When I try to set a timer like this: I get: With this config, ctvl2 is not loaded at all. |
Are you able to read (not write) the timer slots? |
|
So I got it running but the timers are not threre with your config. It's somewhat creepy that the only config which works with one of the most used thermostats is from a random dude in an alreaedy merged PR. |
I do not see any differences for the timers in the files from @1achy and the other repository. But at the end, if it works now, all is fine. |
|
So I have them now but I still can't set anything:
But: gives me: 2024-11-20 19:28:38.644 [mqtt error] write message ctlv2 ccTimer.Monday0 not found Writing via ebusctl: So the ccTimer.Monday without the 0 is there. And below is the config, but I absolutely don't understand what it's expecting as input? Without : I always get "ERR: end of input reached" 
|
e.g. 3 time slots for Monday: The write commands without a temperature require the following template ( Have a look also here, this has been asked before... john30/ebusd#1365 (comment) |
|
Hi @chrizzzp how can I send these three consecutive timeslots via MQTT? I used your command, they didn't give me an error in the logs, but still nothign changed:
|
Did you check the correct template is present ( And make sure Once you have this established you can update the ccTimer over MQTT. I think for your case you will have to write the timers for all days (unless you have a separate automation for each day). So you would publish seven MQTT messages (e.g. in Home Assistant by a script) with the following topics and payloads: This should not take longer than 1-2 seconds (never checked this). BTW: I think there also other means to activate the circulation manually, e.g. with a multi-purpose-input which can be configured for the circulation pump in the regulator. So you would have to connect e.g. a Shelly actor to this input.
|
|
Sadly I dont have the element A quick lookup gives me this: I added the line to the template and used you script. No error but also no change :( I don't want to buy a shelly which is dependend on wifi when the control unit should be able to handle it. |
Yes you have, but in your CSV the corresponding definition is
Did you try to write the timer by ebusctl? Are you using local CSVs or from an online repository? |
This feature provides most functionality for a vaillant VRC720/2 sensoComfort control panel. (https://www.vaillant.de/heizung/produkte/witterungsgefuhrter-regler-sensocomfort-179200.html)
The configuration is based on the previous "700" generation.
For the first parts the old generation continues to work and the time slot behaviour had to be altered, as mentioned in #241.
Currently I only have 3 Zones, HWC and CC configured, so I can not provide the commands for ventilation (Using System schema 2)
The installation manual mentions that all the provided commands support 3 timeframes, but ventilation supports 12.
There are two things to note: