Hi Nikoraes, thanks for that, would you know how I could access the analog input? Set a voltage using a DtoA converter or something? Or could the Koppler emulate an eBus thermostat?
Many thanks
Hagrid.
(Edit - I was trying to respond to Nikoraes’ reply to me from 6 days ago, the message threading is not how I intended)
@Tomek Your item definition is wrong
It should be this (check the set definition):
Number e_HC1_curve “HC1 Heating curve[%.1f]” {ebus=“id:heating.temp_hcurve, cmd:heating.temp_hcurve, dst:15 , refresh:300, set:heating.set_temp_hcurve.temp_hcurve”}
In my case there is also only one decimal. So I would think a step of 0.1 would be better jn your sitemap.
@hagrid67 Of course you could try to emulate the ebus thermostat by sending the b5 10 commands. The ebus coupler is quite expensive, but even if it wouldn’t work you would be able to read some useful commands so it wouldn’t be a complete waste.
Please note that most of these commands still need to be included in a configuration file for this binding.
For the analog input you need to check the installation manual first. I have an analog input on pins 7,8,9 but I’m not sure if they all have them. I also couldn’t find which voltage is expected. To test, I would first try with a manual potentiometer.
To control the boiler you could then use a spi digital potentiometer for example (on arduino or directly on a rpi). I’ve done this for an extract fan and its doable, but a lot of work.
Buying a vrc470(f) would probably be a lot easier and more reliable…
I think the values are never set by the ebus binding, but openhab set the new value automatically. openhab core change the value if you press a switch, not the binding! So after a while the binding refreshes the value from the heating unit and sets the value back to the right value.
I would check the timing for collision detection, this is time critical. The ethernet coupler has a higher delay than the serial coupler.
I created a binding with timing infos in the log files. So please try this Version an modify your logback.xml file.
Maybe there are some retries etc. But you can see that my develop computer need about 10ms for the collision detection. Not optimal, my serial adapter need less than 5ms. But it works.
Could you send me than the full log from start (max. 10min).
Hello @csowadaopenhab.pdf (53.9 KB)
Its my log. I have to change .log tp .pdf because log file can’t be upluaded
Let me know if its OK
One more thing. I tray to check all command from JSON configuration for vaillant-vrc430
and most of them works fine
HC1 Heating curve - as I mentioned I can read value but can’t set
HC1 Day set point - not work I can’t read and I can’t set value. The strange is that I can’t find this entries in https://github.com/john30/ebusd-configuration/blob/master/ebusd-1.x.x/vaillant_de/470.csv
As I understand I should look for "“0D 27 00” data (read) and “0E 27 00 00” (set) but I can’t find it.
(The HC1 Night set point works fine)
Regards
Tomek
I tested a few set items again. I never noticed because I don’t change it remotely very often, but I have the same issue with the heating curve. The value indeed gets overwritten again. I thought it had worked some time ago, but apparently now it doesn’t. I checked the configuration again but I can’t find any error.
Does this work with ebusd for you?
For the programs I can confirm this works as I use it every day.
Changing the day and night set points works as well, but only without decimals.
I am using the USB ebus coupler from the same supplier.
In the ebusd csv files you need to look for 2700. The rest is on different lines. It’s called hc1daytemp there.
@nikoraes
Which version ebus bindig do you use ?
I openhab.cfg have you following entries?
ebus:parserUrl=platform:/base/…/configurations/ebus-config.json (vrc430)
ebus:parsers=custom
I also analysed your log and it looks good, similar timing than my ethernet connection. All send tries where successful, no retries, no collisions.
For me it is important to know if the binding in general has problems or only some commands are not processed by the heating unit. As I understood @nikoraes right, other set commands are working.
Great:)
I modify ebus-config.json ( change Set HC1 Day Setpoint and HC1 Day Setpoint to Id’s from Hc1ManualOPRoomTempDesired) and it works
Many thanks and I wish You Marry Christmas
OK
These are my files: items, json,sitemap, and bindings
I also modify openhab.cfg
ebus:parserUrl=platform:/base/…/configurations/ebus-config.json
ebus:parsers=custom