Configuration of the "Beep" sound

[Styx85]

One annoying issue I have in general with the Blauberg devices is a conformation "beep" sound when changing states, etc.
Is there a, maybe hidden, option to disable the sound? I have not seen anything in the protocol so far.

[AndyNew2]

I have this device and integration as well. This is linked to the crazy BlauBerg or EcoVent interface. I fear even BlauBerg etc. do not develop the interface, all bought years ago from "India"? I fear no change is possible via API. The API is available from BlauBerg for free, you check yourself, if you want.
I might disable the sound generator on the device by removing the speaker. Not yet done the mod, but this is really annoying and prevents a useful integration and automatism for this device.

[NicoDeLarge]

The disassamlby of the android app ("Impruf" same as blauberg) shows, that the library (which is made for several brands and vents) in general supports a parameter like that:

But it is not listed as parameter for the Vento.

However maybe its worth trying. I guess the 1025 is the command/parameter id. Although the IDs is the disassembly to not 100% match the IDs in https://blaubergventilatoren.de/uploads/download/ventoexpertduowsmarthousev11en.pdf

[Styx85]

That looks promising. Best guess it is behind the four undocumented blauberg parameters: https://github.com/gody01/ecovent_v2/blob/main/protocol.md Do you have the full parameter List of the Impruf App and can add it to the table, maybe there is a more regular recognizable parameter shift. Am Mo., 7. Okt. 2024 um 09:34 Uhr schrieb NicoDeLarge < ***@***.***>:

…

The disassamlby of the android app ("Impruf" same as blauberg) shows, that the library (which is made for several brands and vents) in general supports a parameter like that: image.png (view on web) <https://github.com/user-attachments/assets/ea46629f-8df7-4ed2-9525-3313390c4e87> But it is not listed as parameter for the Vento. However maybe its worth trying. I guess the 1025 is the command/parameter id. Although the IDs is the disassembly to not 100% match the IDs in https://blaubergventilatoren.de/uploads/download/ventoexpertduowsmarthousev11en.pdf — Reply to this email directly, view it on GitHub <#19 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHU52EBO5PUS5JOTZXV77GLZ2I2RLAVCNFSM6AAAAABPPIVIBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJWGE2DKMRYGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[NicoDeLarge]

ParametrList.txt
Vento.txt

See the two C# files attached. Unfortunately, the undocumented are also not explained/used there.

[AndyNew2]

Anybody tried the Impruf App? It seems similar but not equal. Also a lot of codes are the same, but quite a lot as well are different.
Do the Impruf App work on "Blauberg" Vents? Anybody tried yet. I could load the Impruf App, but can insert the Vents into it...

[AndyNew2]

Further question, I would have a look to the code, if I would understand, how HA does the trick. I know this integration here is just an HA interface and the actual control code, sending and reading data via network is hidden in a other project. The project is not "ecovent_v2" as this one, but actually "ecoventv2" without the "_". However when I check the code in my HA custom_integration I can't find "ecoventv2". How does HA resolve that trick? However it still works...

[NicoDeLarge]

I tried the Impruf App, it works with my relabeled Blauberg (https://raumluft-shop.de/rl-50rvw-dezentrale-wohnraumlueftung-mit-waermerueckgewinnung-und-wlan-steuerung.html).

And the HA integration here also works with my "Impruf/Raumluft" vents. So I guess the API should be the basically the same.

The appears to be the same for numerous OEMs (see App.cs line 523:577), while Blauberg seems to be the major brand.

App.txt

[AndyNew2]

I noticed, this integration seems to always set additional commands causing more beeps as the original app.
E.g. when I just change the manual speed with the original "Blauberg" App, it do not beep. With this integration it beeps.
It seems this integration sends additionally a set manual mode command, even it do not work...

[NicoDeLarge]

Further question, I would have a look to the code, if I would understand, how HA does the trick. I know this integration here is just an HA interface and the actual control code, sending and reading data via network is hidden in a other project. The project is not "ecovent_v2" as this one, but actually "ecoventv2" without the "_". However when I check the code in my HA custom_integration I can't find "ecoventv2". How does HA resolve that trick? However it still works...

The manifest.json lists pyEcoventV2 as requirement, which HA fetches from PyPI. The package should be the same as https://github.com/gody01/pyEcoventV2 (although the homepage link in the PyPI lacks a "1" in the url)... there you can find the magic.

[AndyNew2]

I found it on the internet. However where does HA store the content locally in your HA installation. That is what I am searching and can't find. Makes me mad, how good in hiding the relevant information they are ... ;-)

[Styx85]

It seems sth. got triggered here :) but anyhow. back to the parameter in the disassembled app. Another best guess by me is that 1025 is actually correct. the document you linked before was about the blauberg v1 version of the api, so far i did not found any true mismatch according to v2 in your posted parameter list. https://blaubergventilatoren.de/uploads/download/b133_4_1en_02_preview.pdf maybe first try to read the parameter? As a classical PEBKAC I have no knowledge of doing it myself. Am Mo., 7. Okt. 2024 um 20:18 Uhr schrieb Andy ***@***.***>:

…

I found it on the internet. However where does HA store the content locally in your HA installation. That is what I am searching and can't find. Makes me mad, how good in hiding the relevant information they are ... ;-) — Reply to this email directly, view it on GitHub <#19 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHU52EGQFYR5YMUD374O2ILZ2LF57AVCNFSM6AAAAABPPIVIBOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJXGU4DQNRUGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>