Hi Uwe
Sorry, I made a mistake by renaming the channel. Please download it from here and try again.
https://github.com/frami/org.openhab.binding.wr3223/releases/download/V2.5.8.1/org.openhab.binding.wr3223-2.5.8-SNAPSHOT.jar
wr3223:controller:local:summerBypassActivationTemperature content_copy
Number:Temperature
Thanks Michael,
the channel is now available. But apparently the parameter Es does not accept the data, as displayed in the logfile.
I’m trying to write 21°C, but the WR3223 keeps 18°C.
With our WR3223 I can write and read the parameter. But I see no effect and in the manual and in the menu of the WR3223 controller I don’t find a parameter “BypassOff”. Do you have a EWT? We don’t have one and I’m not sure, if the parameter Es not belongs to EWT.
Our WR3223 is from the year 2011. Do you have a newer one?
My WR3223 dates from 2007. And yes, I do have a EWT.
Anyway, thanks a lot for trying. Actually my bypass is currently decoupled from the WR3223 controller and handled by a Shelly 1. In case of you beeing successful, I would have reverted to the original wiring. Now I just keep it as it is and have full control of the bypass.
Kind regards
Uwe Drost
Hello!
First of all thanks to everyone for the work done, especially to Michael.
I’ve had no clue about openhab, but when I bought a Schwoererhaus last year, I challenged myself with controlling the heating of my home with openhab in order to reduce electricity costs.
As far as I am, I have a Raspi 4 running with the latest stable release of openhab, I have a Xiaomi Sensor for temperatur and humidity in the living room connected by bluetooth LE sending data via a MQTT broker and I have the WR3223 ventilation controller Binding running, but the Schwoererhaus control device still connected. I get a bunch of data, but I am also noticing that I’m missing some relevant:
additional_heater_relays is reacting when I switch the additional heater open (@ control device) but additional_heater_status and additional_heater_open don’t change state.
heat_pump_status is NULL, heat_pump_open is ON and heat_pump_activate is OFF, regardless of which is shown at the control device. If I change the desired temperature at the controll device, so the little heatpump lite switches off, there seems to be no change of state at any of the these items.
evu_blockade doesn’t change state when EVU is actually blocking, so I’m a little bit worried about all the error contacts may be not showing what they should.
By the way, is there a handler in this binding for the message to change the filters? Or is there an other way to get this message when the controll device is removed?
Maybee all mentioned works as it should, as soon as I remove the control device, what is going to be my next step.
My next idea is to setup rules for switching the temperatur and ventilation level according to a timescale and additionally to switch on the additional heaters for one hour in the morning bevore usual waking up time (which is not possible to setup with the controll device).
Therefore, I would appreciate any references/tips for this…
So far,
best wishes to all of you…
J.
Hello Jan
I’m not sure, if it helps to remove the control device. The reading of the different parameters should work independent of the control device. Can you check your log file for messages from “WR3223Controller”? For example, it should have some from the start of the plugin like this:
2020-12-22 21:56:31.385 [INFO ] [internal.controller.WR3223Controller] - Connected to WR3223 over serial port /dev/usbWr3223. 2020-12-22 21:56:31.431 [WARN ] [internal.controller.WR3223Controller] - Command Ta is not supported by the controller. 2020-12-22 21:56:31.543 [WARN ] [internal.controller.WR3223Controller] - Command Tf is not supported by the controller. 2020-12-22 21:56:32.087 [WARN ] [internal.controller.WR3223Controller] - Command T1 is not supported by the controller. 2020-12-22 21:56:33.173 [WARN ] [internal.controller.WR3223Controller] - Command T7 is not supported by the controller. 2020-12-22 21:56:33.285 [WARN ] [internal.controller.WR3223Controller] - Command T8 is not supported by the controller. 2020-12-22 21:56:34.483 [WARN ] [internal.controller.WR3223Controller] - Command RA is not supported by the controller. 2020-12-22 21:56:34.595 [WARN ] [internal.controller.WR3223Controller] - Command D1 is not supported by the controller.
This messages shows which function are not supported. Our ventilation is basic, without heat pump and without heater. But I know that other users, can use this function.
For the message to change the filters, I just add a recurring event in my calendar. The control device is doing the same. If you would like to do it with Openhab, you can write a rule which change a state of an item to show it’s time to change the filter.
Best regards,
Michael
Hello Michael and thanks for your reply.
Here is what the log states at the start of the plugin:
2020-12-23 11:14:57.860 [WARN ] [internal.controller.WR3223Controller] - Command Ta is not supported by the controller.
2020-12-23 11:14:57.963 [WARN ] [internal.controller.WR3223Controller] - Command Tf is not supported by the controller.
2020-12-23 11:14:59.178 [WARN ] [internal.controller.WR3223Controller] - Command T4 is not supported by the controller.
2020-12-23 11:14:59.433 [WARN ] [internal.controller.WR3223Controller] - Command T6 is not supported by the controller.
2020-12-23 11:14:59.725 [WARN ] [internal.controller.WR3223Controller] - Command T8 is not supported by the controller.
2020-12-23 11:15:00.754 [WARN ] [internal.controller.WR3223Controller] - Command SP is not supported by the controller.
2020-12-23 11:15:00.901 [WARN ] [internal.controller.WR3223Controller] - Command RA is not supported by the controller.
2020-12-23 11:15:01.048 [WARN ] [internal.controller.WR3223Controller] - Command D1 is not supported by the controller.
2020-12-23 11:15:01.232 [WARN ] [internal.controller.WR3223Controller] - Command D2 is not supported by the controller.
2020-12-23 11:15:01.342 [WARN ] [internal.controller.WR3223Controller] - Command D3 is not supported by the controller.
2020-12-23 11:15:01.932 [WARN ] [internal.controller.WR3223Controller] - Command LR is not supported by the controller.
2020-12-23 11:15:03.711 [WARN ] [internal.controller.WR3223Controller] - Command SM is not supported by the controller.
2020-12-23 11:15:03.856 [WARN ] [internal.controller.WR3223Controller] - Command SN is not supported by the controller.
2020-12-23 11:15:04.003 [WARN ] [internal.controller.WR3223Controller] - Command DA is not supported by the controller.
2020-12-23 11:15:04.149 [WARN ] [internal.controller.WR3223Controller] - Command DE is not supported by the controller.
2020-12-23 11:15:06.062 [WARN ] [internal.controller.WR3223Controller] - Command WS is not supported by the controller.
2020-12-23 11:15:27.103 [WARN ] [internal.controller.WR3223Controller] - The control device is active! Openhab can only control the WR3223, when the control device is removed. (Bedienteil)
As you see, all of that with the control device still conected.
Regarding the filter message, I thought this routine would be a little more complex than just counting round about 2 mounth… 
Thanks so far,
best regards,
Jan
Hello Jan
The reason why you don’t get the head pump and heater status is, that the command “Ta” is not supported. For not showing the EVU status, there is the not supported command “Tf” the reason.
2020-12-23 11:14:57.860 [WARN ] [internal.controller.WR3223Controller] - Command Ta is not supported by the controller.
2020-12-23 11:14:57.963 [WARN ] [internal.controller.WR3223Controller] - Command Tf is not supported by the controller.
My WR3223 never supported this commands because it is very basic without heat pump. Maybe @c214 can help you. He has implemented this feature.
Best regards,
Michael
Hello Michael!
Best wishes for 2021 first.
And thanks for your reply.
I will try to contact @c214 soon to see if he can tell me how to implement this feature. Without theese status informations controlling the heating just with the raspbi will probably not work.
Could the issue, that the controller is not supporting the command “Ta” and „Tf“ may be caused by my Reichelt USB to TTL converter (RPI USB TTL: Raspberry Pi - USB zu TTL, 0,9 m, PL2303HX bei reichelt elektronik)?
All the best for the new year again, even to all others reading this,
best regards, Jan
Hello Uwe,
did you get a order number from hermes?
How much is the price for the original Hermes cable and interface device?
Thanks and kind regards,
Daniel
Hallo Michael,
ich hätte Interesse, das WR3223 Binding als OH3-Addon zu nutzen.
Daher wollte ich fragen, ob Du vorhast, das Binding auch für OH3 zugänglich zu machen?
Viele Grüße,
Daniel
Hello Daniel,
Artikelnummer 3266
60 Euro + shipping (Switzerland 32 Euro)
Best regards
U. Drost
Thank you! 
Hello Daniel
I createt a pre-release of the plugin for OH3. I’m not testet it, because my setup at home still use OH2.5.
Best regards
Michael
Thanks for your great effort here.
I just ordered the serial adapter cable from the manufacturer.
Is it possible to switch Kühlfunktion on/off?
Thanks
I don‘t know. I don‘t have an integrated heat pump.
Kind regards
Uwe Drost
I also don’t have an integrated heat pump, but the necessary channel exists. See channel ID “cooling_mode” under GitHub - frami/org.openhab.binding.wr3223 at feature/oh3-upgrade
my controller states “Status: unkown” in the Things-Section.
How can I determine if I really have a connection issue?
btw: my “Bedienteil” (Touch-Display) is connected to X1. So you cannot have both type of controllers: serial and X1?
I’m also trying to get this thing to work.
Have you tried to ssh into your open hab?
ssh -p 8101 openhab@YOUROPENHABIP
enter your password and type bundle:list
Check if the status of openHAB Add-ons :: Bundles :: WR3223 Binding is Active.
In my case a dependency / bundle was missing. I think it was openHAB Core :: Bundles :: Serial Transport
Yeah, I think it’s there although my terminal is cutting half of the info:
235 │ Active │ 80 │ 2.5.0 │ openHAB Core :: Bundles :: Seri
236 │ Active │ 80 │ 2.5.0 │ openHAB Core :: Bundles :: Seri
237 │ Active │ 80 │ 2.5.0 │ openHAB Core :: Bundles :: Seri
I’m using this cable and connected it like described
https://www.delock.de/produkte/G_83786/merkmale.html?setLanguage=en
But status says: Status: UNKNOWN
In openhab.log I can find
2021-08-31 20:46:17.487 [INFO ] [internal.controller.WR3223Controller] - Connected to WR3223 over serial port /dev/ttyUSB0.
but also
021-08-31 20:48:21.405 [WARN ] [mmon.WrappedScheduledExecutorService] - Scheduled runnable ended with an exception:
java.util.ConcurrentModificationException: null
at java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1561) ~[?:1.8.0_292]
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482) ~[?:1.8.0_292]
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472) ~[?:1.8.0_292]
at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) ~[?:1.8.0_292]
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) ~[?:1.8.0_292]
at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:566) ~[?:1.8.0_292]
at org.eclipse.smarthome.io.transport.serial.internal.SerialPortRegistry.getPortProvidersForPortName(SerialPortRegistry.java:86) ~[?:?]
at org.eclipse.smarthome.io.transport.serial.internal.SerialPortManagerImpl.getIdentifier(SerialPortManagerImpl.java:85) ~[?:?]
at org.openhab.binding.wr3223.internal.client.SerialWR3223Connector.connect(SerialWR3223Connector.java:45) ~[?:?]
at org.openhab.binding.wr3223.internal.controller.WR3223Controller.initConnection(WR3223Controller.java:314) ~[?:?]
at org.openhab.binding.wr3223.internal.controller.WR3223Controller.run(WR3223Controller.java:136) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_292]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) ~[?:1.8.0_292]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) ~[?:1.8.0_292]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) ~[?:1.8.0_292]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_292]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_292]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_292]
I’d appreciate any help on this. Thanks!