Same problem for me.
Hi,
Please bring to my attention If this has been asked and resolved before;
I got the new Save Connect module (2.0).
There is a different setup on the home screen of It and I can’t find out how to set the device in “Modbus TCP converter mode.” as you explain in the beginning of this post;
" Device: Systemair IAM Modbus
This device supports the Systemair Internet Access Module in “Modbus TCP” converter mode.
See the Systemair Internet Access Module (IAM) user manual for setting the IAM to Modbus TCP converter mode."
Hi,
Why did Systemair remove the solution they had with the 1.0 version?
On Systemair homepage, It says you can integrate this through other applications.
Maybe that could be the best solution instead of buying another unit converting Modbus RTU → IP?
Hi, I have the old IAM module connected thru modbus and it was working great for a couple of years but now it disconnects from Homey within a few days and only reconnects when I restart the IAM to then disconnect again after a few days.
The IAM unit responds to pings when disconnected from homey so I’m guessing the problem is on the app-side.
Any suggestions?
I am trying to switch to Modbus TCP converter mode but to do that I need to access the web interface but the pw on the back of the unit does not work. It says the pw is wrong. Anybody else run into this issue?
Hi,
Would it be possible to add two things:
-
Activate the vacuum cleaner function trough flow cards?
-
Add the option to turn off fan (not just slow, normal and high). I would like to turn the ventilation system off if there is a fire alarm.
Hi
I have the Save Connect 2.0 (IAM) device and suffer for quite the same problem, but I get the feeling it’s in the IAM unit software the problem occurs that it stop answering because I get the problem that i can’t even reach the systemair app eventuality even if I don’t request it from my Homey ![]()
I have been in contact with the Swedish systemair support and they only gave me some advice of try to change to other wi-fi channels but I haven’t got any luck on that.
I have the same problem as well. I have disconnect the IAM from Homey and it still hangs the entire machine after a few days so I have to disconnect the power cord. Therefore I think that the problem is on the IAM device because everything work like a charm without having IAM connected. Very bad.
I have the new module and an engineer from Systemair told me that the smarthouse function is disabled in the new module. It is not the same configuration as the old one.
So, I am not sure how to implement the new module into Homey, even if it is possible.
Hi everyone,
I’m running a Systemair SAVE VSR 300 with SaveConnect 2.0. After the latest update (Main board SW 1.23.0 / IAM 1.3.0) the local Modbus TCP/HTTP API no longer works – only Modbus RTU settings are available in the menu.
This has broken my Homey integration, even though the Systemair app via the cloud still works fine.
Question:
Does anyone have a copy of an older firmware (e.g. 1.21.x) where local Modbus TCP was still enabled, or any tips on how to roll back to such a version?
Any help would be greatly appreciated!
Hi
I have also updated to the latest firmware Main board SW 1.23.0 / IAM 1.3.0.
And I am using the Modbus RTU mode without problem to connect from my Homey Pro (2023)
Slave address: 0
Baud rate: 1200
Parity: none
Stop bits: 1
Any chance that you could add more functionality for the zwave adapter?
Or is there a restriction in the zwave adapter?
For example the measured values in the analog inputs.
No more support for this app?
