First scan of the documentation shows that there is primairy a difference in function codes.
To bad it does not show the correct value of the unit type for the Vento Expert units it holds value 2,3 or 4. So now it is going to be a “if not one of these, then use the wifi fan schema”.
It will take some time due to the share project in the basis, and its in typescript, not my most experienced code language. But ill do a fork of it and see if I can make it work. When I got a version ready I hope you are willing to test it for me
others if you have Vento Expert meter_power capability. Once that one is present it can show in the consumers list. And that should be an all time total.
Thx a lot Kaoh for trying to make it work. I mainly need the basic functions like on-off, fanspeed and after-running period. I defenitely want to test any new version.
Not yet, in my sparse free time I worked down a todo list with my Homey apps. The best I have right now is, it’s now at the top of my list. And hopefully this weekend isn’t that busy in my private time.
I worked some of my gaps on making sure I can alter the typescript module I am using as a base for the app, and compile the typescript into the same working nodejs module I got. Because my app is written in nodejs and not typescript. This meant I had to figure out from the source of the base module how to compile that in such a way the code remains working while using it in my nodejs code.
I did manage to get that working, and used that to alter and enhance a part of the discovery capabilities of the library.
So next is indeed altering it in such a way it allows for more blauberg device types with different package structures (the module maps the messages to a fixed message structure now, and your fan has a different one) so it becomes flexible. Based on that I plan to add the message structure definition of the wifi fan, and then send it to you for testing.
But time is a factor sorry. Life is busy. I am head of tech at a large ICT consulting firm, have a family with 2 kids (one handicapt) and am busy with supporting a very cool high tech health care startup.
So free time is sparse and I also need some true relax time. Bug fixes take an hour or two of my apps, that I can manage, but such a rewrite of a module, specially since its in a code language I dont use myself often, and its managed by someone else (who clearly holds high standards) it requires real time, and more than an hour once in a while because it takes time to get into it.
Hi Kaoh,
Thx for putting so much effort into the app. It is well appreciated! You don’t have to apologize for the limited time that you have to put into the app. It will be great if it works with the wifi fan, for now I can start it with my phone. I wish I could help you with the programming, but although I work in the IT too, my work is not technical.
Great app! I actually started creating an app myself for my Flexit Roomie Duo V2 and made it communicate with my ventilator. Then I found that it was a lot of white label / products branded differently which has a lot of similarities, that made me come across this app. I tested you app and it was much more feature complete than mine and it is also able to control the brand that I’m using.
Reach out if you need help with maintaining your app!
Also - the other brands I’ve come across is “Flexit Roomie”, “EcoVent”, “Oxxify”, “TwinFresh”, “Duka”. I suspect many of these will also work with this app.
Can you link me the device you actually purchased? I might order one myself for testing.
I am working on a version right now, I wont be able to test it myself, so I will release a Test version later today with the blind coded version to see if it actually works for you.
Great work, this really made my day! The app works out of the box except for “fan speed %” and “fan rpm”. However, setting speed mode [off, low, med and high] works smoothly. Setting manual speed mode in the app kicks it out of the native app-controlled schedule though and you can’t go back. I guess this a brand specific feature in Flexit’s app. But thats fine, I’m going to migrate the schedule to a Homey-Flow anyway.
The history log is spammed with disconnected/connected
Yeah the connection status is based on received timeouts or other errors. I also noticed it is spammy. I think I need to rethink that. So you can ignore it.
How did you add your Flexit to homey via Blauberg vent?
I have now the Blauberg home app (used previously the Flexit fans app) and we’re able to add my vents there and can control them, but homey can’t find the Flexit vents through the blauberg vent app.
For 2 months, I have been using your app with great success in my flows to control my 2 Vento A50 c3-1 S8 W v.2. Great app! Unfortunately the A50 became unreachable in Homey since yesterday while the Blauberg app still works as usual. In Homey, I have deleted the devise and your app, then I reinstalled the app and try adding the device one more. Your app is telling me there is no new device to install. Any idea how I should solve this?
Then your local discovery is disrupted. UDP discovery is a bit noisy so normally an app can spam the network while in use, but if we do the same with Homey it will the network constantly. So I reduced it. But that means that devices that only respond once in a while can be missed.
But it can also be linked to your network equipment. If you changed something, like a new WIFI AP or router they might block the discovery cross segemnts.
I had some intrusions on my network lately and intrusion detection added a bunch of firewall rules. I just deleted all internal to internal rules and everything is working again! Thanks a bunch! Do you have a donation link?
for the Vento Expert units it holds value 2,3 or 4. So now it is going to be a “if not one of these, then use the wifi fan schema”.
