Writing values to Vitotronic

jimSelf · September 21, 2017, 9:22pm

Hi there,
I have the Vitotronic binding running for months and it is working very well for reading values into OpenHab. I always thought, the binding is not for writing to the Viessmann device, but now I recognized, that the LEDs are blinking, when I hit a button in OpenHab. The logs also indicate, the values was successfully written on the bus. But on the Viessmann device, this is not reflected and after the next reading from the device (every 60s) I can see, the values are set back in OpenHab as well.
Specifically, I want to change the party mode, the save mode and operation mode.
Is there anything, I need to set on the device or in OpenHab to write those values?

Thanks

portboy · September 26, 2017, 10:36pm

Same here. I’m not able to write. Not with protokoll 300 or KW.

This binding has so much issues …

portboy · October 3, 2017, 9:24pm

I’m still working on this issue.
This is the tracert-log-output if I try to set the partymode:

23:20:51.776 [Thread-22] DEBUG de.myandres.optolink.SocketHandler run - Execute Thread for: 'set circuit1:partymode ON' 23:20:51.777 [Thread-22] TRACE de.myandres.optolink.SocketHandler exec - Queue Command: |set| 23:20:51.777 [Thread-22] TRACE de.myandres.optolink.SocketHandler exec - param1 : |circuit1:partymode| 23:20:51.777 [Thread-22] TRACE de.myandres.optolink.SocketHandler exec - param2 : |ON| 23:20:51.778 [Thread-22] TRACE de.myandres.optolink.Config getThing - get thing id: circuit1 23:20:51.778 [Thread-22] DEBUG de.myandres.optolink.Viessmann300 setData - Set Data for address 2303 .... 23:20:51.779 [Thread-22] DEBUG de.myandres.optolink.Viessmann300 transmit - Send Data to OptolinkInterface 23:20:51.780 [Thread-22] TRACE d.m.optolink.OptolinkInterface write - TxD: 41 23:20:51.781 [Thread-22] TRACE d.m.optolink.OptolinkInterface write - TxD: 06 23:20:51.781 [Thread-22] TRACE d.m.optolink.OptolinkInterface write - TxD: 00 23:20:51.782 [Thread-22] TRACE d.m.optolink.OptolinkInterface write - TxD: 02 23:20:51.782 [Thread-22] TRACE d.m.optolink.OptolinkInterface write - TxD: 23 23:20:51.782 [Thread-22] TRACE d.m.optolink.OptolinkInterface write - TxD: 03 23:20:51.782 [Thread-22] TRACE d.m.optolink.OptolinkInterface write - TxD: 01 23:20:51.782 [Thread-22] TRACE d.m.optolink.OptolinkInterface write - TxD: 01 23:20:51.783 [Thread-22] TRACE d.m.optolink.OptolinkInterface write - TxD: 30 23:20:51.863 [Thread-22] TRACE d.m.optolink.OptolinkInterface read - RxD: 06 23:20:51.864 [Thread-22] DEBUG de.myandres.optolink.Viessmann300 transmit - Data to OptolinkInterface sended [OK] 23:20:51.864 [Thread-22] DEBUG de.myandres.optolink.Viessmann300 resive - Get Data from OptolinkInterface ... 23:20:51.864 [Thread-22] TRACE d.m.optolink.OptolinkInterface read - RxD: 41 23:20:51.879 [Thread-22] TRACE d.m.optolink.OptolinkInterface read - RxD: 05 23:20:51.880 [Thread-22] TRACE d.m.optolink.OptolinkInterface read - RxD: 01 23:20:51.881 [Thread-22] TRACE d.m.optolink.OptolinkInterface read - RxD: 02 23:20:51.882 [Thread-22] TRACE d.m.optolink.OptolinkInterface read - RxD: 23 23:20:51.882 [Thread-22] TRACE d.m.optolink.OptolinkInterface read - RxD: 03 23:20:51.883 [Thread-22] TRACE d.m.optolink.OptolinkInterface read - RxD: 01 23:20:51.895 [Thread-22] TRACE d.m.optolink.OptolinkInterface read - RxD: 2F 23:20:51.895 [Thread-22] DEBUG de.myandres.optolink.Viessmann300 resive - Data from OptolinkInterface got [OK] 23:20:51.896 [Thread-22] TRACE de.myandres.optolink.Viessmann300 resive - Dump Data (No. decimal hexadcimal binary) 23:20:51.896 [Thread-22] TRACE de.myandres.optolink.Viessmann300 resive - [0] 001 01 00000001 23:20:51.897 [Thread-22] TRACE de.myandres.optolink.Viessmann300 resive - [1] 002 02 00000010 23:20:51.897 [Thread-22] TRACE de.myandres.optolink.Viessmann300 resive - [2] 035 23 00100011 23:20:51.897 [Thread-22] TRACE de.myandres.optolink.Viessmann300 resive - [3] 003 03 00000011 23:20:51.898 [Thread-22] TRACE de.myandres.optolink.Viessmann300 resive - [4] 001 01 00000001 23:20:51.898 [Thread-22] DEBUG de.myandres.optolink.Viessmann300 setData - Data for address 2303 got 23:20:51.898 [Thread-22] TRACE d.myandres.optolink.ViessmannHandler formatValue - Formating.... 23:20:51.900 [Thread-22] DEBUG de.myandres.optolink.SocketHandler run - Thread for: 'set circuit1:partymode ON' done

So no error. But the partymode wasn’t set
No matter if I use KW or 300 protokoll.

any hints?

hotte37 · January 28, 2018, 8:15pm

Hello,
I have the same issues with the optolink adapter and i am waiting for some progress in solving the problem. On Github i found commits from O.B. from 26.02.2017 that claim to solve the write problem but they are not merged into the main branch.
Unfortunately it seems, that the optolink adapter is no longer under development and there will be no new release.
Am I wrong?