Did you experience this issue?

[cibernox]

Thanks to this definition I was able to control my Wolf CWL 300 excellent with MQTT though ebusd. I am planning on now creating some entities in home assistant to make it useful and easy to automate.

However I've noticed something odd. While I am able to read sensors and I can even change the fan speed (say, I go from "Reduced" to "Normal") after a few seconds, perhaps up to a minute, it reverts back to "Reduced".

Any idea why the ventilator does that?

[dstrigl]

However I've noticed something odd. While I am able to read sensors and I can even change the fan speed (say, I go from
"Reduced" to "Normal") after a few seconds, perhaps up to a minute, it reverts back to "Reduced".

Do you have a switch connected to the fan? If yes, remove it ... otherwise it will take its position for the fan speed.

[cibernox]

I do indeed have a controller screen in the wall. So you think the controller display is overriding the value I set every few seconds…

I’ll try that.

[hvorragend]

Yes, so it is.

The master remote control is flooding the bus - as far as I know - every 5 seconds.
Because I want to still use it, I've added a step switch to the CWL/Renovent device.
The step switch has a higher priority than the master remote control.

If you examine the ebus traffic, you can see that there are different devices sending the "Ventilatorbetrieb".

I've changed the ebusd-configuration - for testing purpose - to:

w,,VentilatorbetriebWrite,,,,40a1,,,,ULR,0x0=Feuchteschutz;0x00010001=Reduziert;0x00020002=Normal;0x00030003=Intensiv,,,,,IGN:1

r,,VentilatorbetriebRead,40220101,,,4022,01,,,UIR,0=Feuchteschutz;1=Reduziert;2=Normal;3=Intensiv,,FanMode

If you are using a step switch it doesn't matter what the master remote says. It is talking much, but it will be ignored by the CWL device.

[cibernox]

@hvorragend I disconnected the screen and indeed it is working!!
I was able to create in home assistant an mqtt.fan entity that allows me to set the fan speed wither with levels (0 to 3) or with presets (Low, Medium, High), and it can also turn it off (which is not really off but the lowert lever for moisture control) and ON again (which I arbitrarily decided that it turns on in "Low" by default).

It's working great!

I am also in the process of adding the rest of the sensors, at least the ones I care about because since I'm disconnecting the wall control (which was in the garage anyway and I rarely used) I want to have every possible piece of information I may care about in home assistant, like warnings about filter cleaning and such.

One setting I'm particularly interested in playing with is the Pressure Imbalance. I have a fireplace that I use occasionally and when I do, obviously the fire is consuming air from within the home. Being my home fairly new and quite air-tight, I can feel that the pressure at home gets low and cool air tries to enter in the few spots that are not completely air tight, like below the entry door. The installer back in the day mentioned that double flow mechanical ventilations like this allow to push more air in then they take out. If that is the case, it would be more efficient to make the device increase fan speed when the fireplace is burning so air goes through the heat exchange instead of letting the chill air enter below the front door.

[cibernox]

If any of you have any nice tricks/automations beside the most obvious ones (increase the speed if a CO2 sensor detects it's too high) please share.
Otherwise this issue can be closed.

Thanks again for this definition, it was a life saves. If you want I can contribute the english translation that I created.

[dstrigl]

If you want I can contribute the english translation that I created.

Your contribution is always welcome!

Regards,
Daniel.

[cibernox]

I opened a PR with my english translation. I did find however another issue, IDK if you've found it too. If I set the fan speed to the very minimum (the moisture protection one) it automatically changes to the low setting (Reduced) after a few minutes, even with my wall control unplugged. Is this something you experience too?

[hanskenb]

Hi there, I am actually still struggling with this issue. I have a Brink Renovent Excellent, without any remote control attached to it. However, my ebusd controller keeps resetting to Reduziert when I control it trough ebusd

I read that a workaround would normally be to actually get a control panel to set the system to level 2 and then always change the value air quantity level2 at the different times.

However, I'm unable (or ignorant on how) to change these settings on the device itself.

Many thanks for any help.

[cibernox]

@hanskenb I solved it in a different way. Since I now I've integrated this into home assistant I have it available as a 'Fan' entity. I solved it with this node-red automation:

Every 60 seconds I run one automation that checks if the unit is "off" (I've defined "off" as being in the moisture-control speed) and if so, turn it off again. Since it's being turned "off" again and again, it does the same that the wall control unit did.

[hanskenb]

@cibernox , thank you for your reply.
Would it be possible to share the node-red code?
I'm new to node-red

[ceraz68]

Yes, so it is.

The master remote control is flooding the bus - as far as I know - every 5 seconds. Because I want to still use it, I've added a step switch to the CWL/Renovent device. The step switch has a higher priority than the master remote control.

If you examine the ebus traffic, you can see that there are different devices sending the "Ventilatorbetrieb".

I've changed the ebusd-configuration - for testing purpose - to:

w,,VentilatorbetriebWrite,,,,40a1,,,,ULR,0x0=Feuchteschutz;0x00010001=Reduziert;0x00020002=Normal;0x00030003=Intensiv,,,,,IGN:1

r,,VentilatorbetriebRead,40220101,,,4022,01,,,UIR,0=Feuchteschutz;1=Reduziert;2=Normal;3=Intensiv,,FanMode

If you are using a step switch it doesn't matter what the master remote says. It is talking much, but it will be ignored by the CWL device.

Thanks for posting this workaround ... but I don't understand which values you are changing to increase the priority of the commands sent on the ebus as the values you post are the same as in the existing csv file. Can you explain more ?

I have a renovent 400 at address 7c, an ebus adapter, brink emodule (waste of money), a wired WTW Control unit.

version: ebusd 23.1.23.1-9-g1895339e
update check: revision 23.1 available, device firmware 1[8419] available
device: 192.168.0.88:9999, enhanced, firmware 1.1[7e1d].2[73c8]
signal: acquired
(...)
masters: 4
(...)
address 01: master #6
address 31: master #8, ebusd
address 36: slave #8, ebusd
address 77: master #19
address 7c: slave #19, scanned "MF=ENCON;ID= ;SW=-;HW=-"
address 7f: master #24

[alexferrari88]

@hvorragend I disconnected the screen and indeed it is working!! I was able to create in home assistant an mqtt.fan entity that allows me to set the fan speed wither with levels (0 to 3) or with presets (Low, Medium, High), and it can also turn it off (which is not really off but the lowert lever for moisture control) and ON again (which I arbitrarily decided that it turns on in "Low" by default).

It's working great!

I am also in the process of adding the rest of the sensors, at least the ones I care about because since I'm disconnecting the wall control (which was in the garage anyway and I rarely used) I want to have every possible piece of information I may care about in home assistant, like warnings about filter cleaning and such.

One setting I'm particularly interested in playing with is the Pressure Imbalance. I have a fireplace that I use occasionally and when I do, obviously the fire is consuming air from within the home. Being my home fairly new and quite air-tight, I can feel that the pressure at home gets low and cool air tries to enter in the few spots that are not completely air tight, like below the entry door. The installer back in the day mentioned that double flow mechanical ventilations like this allow to push more air in then they take out. If that is the case, it would be more efficient to make the device increase fan speed when the fireplace is burning so air goes through the heat exchange instead of letting the chill air enter below the front door.

Would it be possible to share the code to have the same on my Home Assistant?

[tiotuba]

hi @cibernox, how did you manage to get all the variables from your config.CSV (ebusd) into home assistant?
I have my ebusd addon running on HomeAssistant OS and MQTT. Even though I can see already some entities like outside temp, intake temp etc. I cannot see other entities, like to set fan speed, reset filter, etc.
am I missing something?

I haven't changed anything in the mqtt-hassio.cfg file except the "filter-direction = r|u|^w".

thanks!

[Zwoet]

Hi Tiotuba, for me the only one I had to change was;

I changed it from FanSpeed to FanMode so it was the same as the end of the line, and then it worked.

The others all worked without any changes. I just # out a lot of lines to clean the log file while getting all this to work.

[tiotuba]

Hi Tiotuba, for me the only one I had to change was;

I changed it from FanSpeed to FanMode so it was the same as the end of the line, and then it worked.

The others all worked without any changes. I just # out a lot of lines to clean the log file while getting all this to work.

hi @Zwoet, you gave a great hint. I was using the Brink Renovent Sky config CSV from Paddyx and not this one.

Once I started using the CSV for Renovent Excellent 300 (which is the same) the entities and topics started showing up on my MQTT.

P.S. great hint with the FanMode/FanSpeed. It worked great. Thanks!

[pvyleta]

@Zwoet @tiotuba Just for clarity, changing the name from FanSpeed to FanMode is just a workaround. The root cause is, that FanSpeed is not matched by the "regex" in mqtt-hassio.cfg file. You can provide your local copy of that file through --mqttint commandline parameter, or, presumably if you are using the HA ebusd addon, there is a possibility to provide the filepath from the addon config.

[tiotuba]

@pvyleta I have the HA ebusd addon, and I've done just that. I entered the filepath to my local copy and it only worked after I changed FanSpeed and FanMode. I think both entities having the same name is causing maybe an issue during MQTT discovery? not sure.

[Zwoet]

Yeah same for me, I used ebusd addon, with the .csv as file loaded in. Thought was the only way to accomplish this ?

File:

Link here:

[pvyleta]

Hmm, I see, so the fact the comment name is different is not the problem, but the fact that the writable field is named the same as the readable might be. I will investigate it deeper if I have some time.

[cibernox]

It's weird that I didn't have to change the name of FanSpeed to fan Mode for this config to work.

I take the change to ask something unrelated. I don't want to use the built-in screen ever again, but I keep it around only to be able to reset the state of the filter when I put new ones. There's one entry for resetting the filter in the configuration that is commented. In uncommented but nothing shows on the UI. Has anyone been able to tell the unit that you've installed clean filters using HomeAssistant?

[pvyleta]

@cibernox I have not yet done that, but I am just now looking deeper into the Brink Configuration tool via decompiler, and I found a lot of possible settings that I am waiting to test - not only for Renovent Excelent, but there is tons of options for Flair and other units. But back to your question - if you make the necessary changes (allowing write parameters and adding 'reset' into the pattern of 'filter-name=') in mqtt-hassio.cfg you should be able to see that command.

[pvyleta]

@Zwoet Note that I am referring to the mqtt-hassio.cfg that you need to copy locally on top of the .csv file