Hi Matthias,
the binding correctly sets the RS232 mode on thing initialization/dispose and by using the activation switch. This is handled the same way as in the OH1 binding. What differs from the OH1 binding is that in the old version the itam state was not updated if no correct answer was retrieved, while in the new binding the state is set to UNDEF
if the response is not matching the request. IMO this behaviour is desired, since otherwise you never know if the current state is matching the actual value in the device (besides being the only indication of a working connection).
Now it seems to be the case that the deactivation of the CC Sense doesnât work for all devices or is reactivated by the ComfoAir/CC Sense (SMHaller brought up the idea that it could be dependent on the firmware). So openHAB and CC Sense are sending and receiving data in parallel, and openHAB is not getting the requested response or is receiving a bunch of (unrequested) responses at once and not able to filter out the requested one. The latter case, which seems to be most common in your logs, I tried to improve (LINK). However, this doesnât solve the root issue of two communication paths on one serial bus and if the deactivation doesnât work due to hardware restrictions there is not much I can do about.
You can always add a relay to phisicaly connect and disconnect wires from CCEase, and you can controled it by openhab too: if you switch to binding control â open relay, else if switch to CCEase â close relay
Hi Miasko
thats the failback solution for me And an manual switch for my wifeâŠ
This will most probably also be my future setup (Another Qubino more)
I migrated to OH3 now and the binding works perfect. Even the âis_enthalpyâ channel works now, as in the V1 Binding. Thanks for the implementation of the setup values!
short update:
The next version (3.1) of the binding wil bring some minor improvements:
- channels will not update if
bindingControl
isOFF
. This omits items changing toUNDEF
if control is handed over to CCEase/CCSense - logic tries to filter requested values from responses that also contain unrequested data. This should improve the behaviour for cases where a deactivation of CCEase/CCSense (due to potential hardware restrictions as discussed above) does not work (BTW, thanks to @Matze_R and @smhaller for their testing efforts). However, a physical deactivation of external controls (e.g. by relais) is still recommended.
- some other minor fixes (see full PR #9401)
If someone is eager to have this now, JAR-file is available here: https://openhab.jfrog.io/openhab/libs-pullrequest-local/org/openhab/addons/bundles/org.openhab.binding.comfoair/3.1.0-SNAPSHOT/org.openhab.binding.comfoair-3.1.0-SNAPSHOT.jar
Hi guys,
I have the ComfoConnect LAN interface installed. Is there any possiblity to get the link to openhab? I understand that this binding here is only working with a serial port?
Hi Jan,
you are right, the current ComfoAir binding only supports serial connections. Additionally, the ComfoConnect LAN interface seems to use a different protocol, so an integration in the current binding probably wouldnât make much sense technically.
However, there seem to be some efforts on this topic and actual possibilities for integration over MQTT (1 & 2).
Hello Everyone,
in my case i have a ComfoD 350 machine. as i see the main control unit is the same as the comfoair 350. this mainboard (yellow) comes also with a rj45 connector (green), the other board is not part of my comfoD.
i know i canât control the fanlevel over rs232, as there is a 4 way switch direktly connected, but is it possible to read the values which i can see in the small display in the front over this connection.
i tried to connect to openhab as descripted above with an PL-2303 cable an an rj45 to DB9 adapter, but canât get any values in openhab. the RX and TX is crossed as i think the connector on my board has the same pins as the the board with the 9-pol connector (wich is not in my comfoD).
anyone has get the connection to work with an comfoD?
thanks.
Hi Jens,
I donât own a ComfoD but I think the pinout should be the same as for the ComfoAir, which is as shown for the RJ45 connector (from the protocol description):
Just make sure this matches the DB9 pinout (pins 2, 3, 5; +12V is not needed):
maybe swap RX and TX
BR Hans
thanks for the reply, is solved the problem, i had a shortcut in my self crimped lan cable, and afterwards i traced the serial port in openhab from the console so that openhab it self could not connect. now its working
Greetings! First of all: Thank you very much for your and everybodies effort to develop this binding - after several tries (e.g. with esphome, mqtt-python-solutions, âŠ) this binding is the first realisation, which started to function for me.
I have a WERNIG G90-380 luxe. It is connected via RS232 port and following cable: UGREEN USB / RS232 Seriell PL2303 chipset.
Other cables, e.g. DTech FTDI USB / RS232 Adapter FT232RL Chip did not work.
Running OH 4.0.1 on Raspi 4b.
After installation of the Binding and creation of items all sensors seem to wirk fine!!
But: Only the control of the fan level does not work. It seems that the control item (which uses a kind of rollershutter input from 0 - 100) is not correctly definined (? see the logs - i tried to set it to high, but update was tried to â0â) - but actualy I have no idea what to change, since everything else is working smoothly.
Wernig has 3 different levels - 0 (absent), 1 (low), 2 (medium), 3 (high).
2023-12-22 18:44:03.881 [INFO ] [openhab.event.ItemStateUpdatedEvent ] - Item 'ComfoAir_Wohnraumluftung_Steuerung_aktivieren' updated to ON
2023-12-22 18:44:04.086 [INFO ] [openhab.event.ItemStateUpdatedEvent ] - Item 'ComfoAir_Wohnraumluftung_Luftungsstufe' updated to 1
2023-12-22 18:44:04.292 [INFO ] [openhab.event.ItemStateUpdatedEvent ] - Item 'ComfoAir_Wohnraumluftung_Aussenlufttemperatur' updated to 6 °C
2023-12-22 18:44:04.495 [INFO ] [openhab.event.ItemStateUpdatedEvent ] - Item 'ComfoAir_Wohnraumluftung_Zieltemperatur' updated to 23 °C
2023-12-22 18:44:04.694 [INFO ] [openhab.event.ItemStateUpdatedEvent ] - Item 'ComfoAir_Wohnraumluftung_Abluftventilator_' updated to 15
2023-12-22 18:44:04.896 [INFO ] [openhab.event.ItemStateUpdatedEvent ] - Item 'ComfoAir_Wohnraumluftung_Zuluftventilator_' updated to 15
2023-12-22 18:44:05.102 [INFO ] [openhab.event.ItemStateUpdatedEvent ] - Item 'ComfoAir_Wohnraumluftung_Filter_Laufzeit' updated to 1648800 s
2023-12-22 18:44:05.304 [INFO ] [openhab.event.ItemStateUpdatedEvent ] - Item 'ComfoAir_Wohnraumluftung_Ablufttemperatur' updated to 19 °C
2023-12-22 18:44:06.710 [INFO ] [openhab.event.ItemStateUpdatedEvent ] - Item 'ComfoAir_Wohnraumluftung_Zulufttemperatur' updated to 19.5 °C
2023-12-22 18:44:06.913 [INFO ] [openhab.event.ItemStateUpdatedEvent ] - Item 'ComfoAir_Wohnraumluftung_Fortlufttemperatur' updated to 8 °C
2023-12-22 18:44:07.113 [INFO ] [openhab.event.ItemStateUpdatedEvent ] - Item 'ComfoAir_Wohnraumluftung_Fehler_Aktuell' updated to No Errors
2023-12-22 18:44:07.315 [INFO ] [openhab.event.ItemStateUpdatedEvent ] - Item 'ComfoAir_Wohnraumluftung_Filterfehler' updated to OFF
2023-12-22 18:44:08.911 [INFO ] [openhab.event.ItemStateUpdatedEvent ] - Item 'Systeminfo_Cpu_Load' updated to 3.9
2023-12-22 18:44:08.914 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'Systeminfo_Cpu_Load' changed from 1.4 to 3.9
2023-12-22 18:44:08.917 [INFO ] [openhab.event.ItemStateUpdatedEvent ] - Item 'Systeminfo_Memory_AvailablePercent' updated to 80.4
2023-12-22 18:44:08.961 [INFO ] [openhab.event.ItemStateUpdatedEvent ] - Item 'Systeminfo_Storage_AvailablePercent' updated to 71.7
2023-12-22 18:44:17.518 [INFO ] [openhab.event.ItemCommandEvent ] - Item 'ComfoAir_Wohnraumluftung_Luftungsstufe' received command 0
2023-12-22 18:44:17.520 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'ComfoAir_Wohnraumluftung_Luftungsstufe' predicted to become 0
2023-12-22 18:44:17.524 [INFO ] [openhab.event.ItemStateUpdatedEvent ] - Item 'ComfoAir_Wohnraumluftung_Luftungsstufe' updated to 0
2023-12-22 18:44:17.526 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'ComfoAir_Wohnraumluftung_Luftungsstufe' changed from 1 to 0
Can anybody help me please?
Newbee fault. I created an input item (knob) with min 0 and max 3 - that works fine. maybe this helps other newbees Items to enter data - Development / Add-ons - openHAB Community
Hi guys,
i have a physical button to activate the bathroom mode that activate the level 3 for 30 minutes. Is there a way to return the operating speed to the previous mode?
in those 30 minutes, even by acting on the comfoAirLevel item, it does not receive the command.
Thanks
The problem is that the highest demant wins. So for example i have 0-10V module and openhab with rs232, if i set it to level 3 with rs232 and 5V(50%) then level 3 will be active. If I select Level 0 (away) then it wil stay on 50%. if i let it drop till 0V it will stay on Level 0 becaus that will be the highest demand. Hope this will help.