Unfortunately I’ve been super busy - and still am, but update is upcoming, although I had to ask some 3rd party help for that - but I’ll make a update in 1-2 weeks, if not less (not wanting to give false hope..)
Okay, I’m done. A decent update to app has been pushed to GitHub repository. Shortlog of changes is:
- Added ventilation and temperature Flow controls
- manual CTS602 CO2/external-heat options
- configurable estimated power and energy monitoring
- Fixed Flow filters, direct ventilation control, settings refresh and pairing reliability
All changes can be seen here: GitHub - oskarirauta/homey-nilan-app: Homey Nilan TCP Modbus driver · GitHub
I see you’ve already deleted your post, but I had exactly the same issue recently with “Processing failed” when publishing one of my apps. Solution is to remove the .homeybuild folder. Might be a bug in the Homey CLI
@smarthomesven THANK YOU!
I am stuck btw., tried to reach out to support - but no assistance than to ask in forum 
GREAT HELP TY
New version available in the store.
Work by @osku
Still does not work with reading values from my unit. There is a flaw in the modbus_api.ts file, where it waits all (even adresses that cannot be read) and therefore fails.
Fix is at
I can’t find the fix, commit log shows that it’s file updated by me 8 months ago..
But this should now be fixed here: fix modbus_api not to fail on CTS700 · oskarirauta/homey-nilan-app@3456ba4 · GitHub
TEST updates. New version is in verification stage.
Version 1.4.1 is now live.
@osku @Kim_Kokholm
Thank you.
I can confirm it is working now. 
Excellent.
Actually I’ve run into a bunch of problems. The app seems to becom unresponsive. The filter alarm is way off (keeps showing alarm, even when it has been cleared) and a few other annoyances.
Is there any chance I can publish a branch to the repo with som optimizations i’ve made (with a lot of help from AI, but they do seem reasonable and to be working)
We can either make a PR out of it, or you could cherry pick whatever changes makes sense to you.
@osku what is your take on this?
I would prefer, you creating a new driver, for your needs. How does that sounds?
In the pairing, we can refer to your model.
I do not develop on this app anymore, I’m just the publisher.
@osku is the maintainer for now, so let’s have his take on this.
What board are you using? CTS-602 or CTS-700?
I can’t work much on CTS-700, since I only have CTS-602.
If none of the above, then you need a new driver, and we will accept participation to the project as we are not affiliated in manufacturer or homey in professional way, we have just brought our contribution and have our limitations.
I’m also on CTS-602. I have a Comfort 300LR unit.
The reason I am wanting to participate is that a lot of the features that some of the other units expose are also visible to me in the app, but I really don’t want to see anything related to water, extra heater and such. Also there is something wrong with the filter alarm on address 101, which keeps returning 1. The correct alarms are returned on 400+ and can be deducted to be filter alarms if the returned id is 19. Another thing is stability or maybe it’s just ability to recover properly after a lost connection. Mine runs for some hours, but will then just stop responding and need a restart. I haven’t a fix ready for that, but I would want to give it a shot to make it all more robust.
Venlig hilsen
Jon Hye-Knudsen
Yes, I only was able to of course make support for my Nilan EC9(vp18) - but system is already built so that you can make a model dedicated version. If model is “unsupported”, it shows pretty much everything. About those filter alarms.. Are you sure you are not running “outdated” firmware version, there was a point when Nilan changed some things. Protocol support provided is from latest Nilan’s doc.
Mine runs months with no issues of any kind. On Homey Pro 2023.
Hi,
You could very well be right. I have the old non-touch control panel and it might not be the latest firmware.
I have come to suspect that my Elfin EW11 has a tendency to disconnect from my WiFi. Sometimes it won’t reconnect for hours it seems when looking at my WiFi logs and that is of course a problem. Could be because of the “quality” of power from the Nilan unit, so I’ll have to look into that separately. It does seem to expose the apps inability to reconnect properly after such a WiFi disconnect I think. I have to restart the app for it to connect to the EW11 again and not just get timeout error for every command sent.
I’ll look into the model support. Mine shows up as Comfort (type 13) with bus version 4 and it seems pretty clear in the Nilan documentation what features are actually supported on it.
Anyway. I really appreciate the work you’ve done. I would not be anywhere with getting my unit into Homey without it.
I’m on a Homey Pro Mini by the way.
Venlig hilsen
Jon Hye-Knudsen
You probably got the same e-mail about new developer possibilities, where one was creation of “organization”, which gives you a chance to set rights for more than one developer to curate app.
You might (or might not) be interested in it.
Nilan’s documentation also is partial; it reports that VP18 supports features that it doesn’t and I have verified some of these features that should be supported: will never be supported for vp18. So documentation is about 80-85% accurate on supported features, usually in a way that it says that device supports something; that it doesn’t - but you have to be careful here; if there are models (revisions) that do support thing that is missing in your version even while being same Comfort (type 13); then you need to add that feature, even when it would always say 0 on your device.
I have added some of these questionable features as a per-detect base, means that they appear as a capability once value has even once been something else than 0. For other options, I have added a setting that is either enabled or disabled during pairing by user.
Happy hacking and good luck.
