Systemair SAVE

Share your Projects!
1

I’m working on API bindings for Systemair ventilation systems that are registered on their cloud platform.

Once done, it should make it easy to add a plugin for these ventilation systems in HA.

The project is available here:

Let me know if you have questions or want to help out.

2

Great that you’ve started this project! I won’t be able to help with programming, but I’ve used GitHub - perara/systemair-save-connect: Systemair SAVE Connect: custom integration for Home Assistant, which hasn’t been working for some time, and the author won’t continue the project. Maybe something can still be salvaged from it?

3

Any chance these APIs also work locally…?

4

SAVE CONNECT 2.0 module has web service running on it which has, in addition to UI, locally exposed API. So AFAIK there shouldn’t be need for a cloud access.

You can see API calls if you navigate to the web interface and inspect network calls in browser.

5

yup, I just checked, it’s actually quite easy, but very low-level.

The reads are a GET request with json (query url-encoded params) like: {“modbus_addr”: num_to_read, “modbus_addr2”: num_to_read2…}

to the endpoint http://address/mread?…

And returns

{'modbus_addr": val1, “modbus_addr+offest”: val2, etc…}

The writes are (also!) GET requests, query params with

{“modbus_addr”: val_to_write, “modbus_addr2”: val_to_write_2}

to

http://address/mwrite

6

Hi, is there any integration today that uses local access? Sadly my programming (even json) skills are very basic…
Thanks

7

There is, check out here: GitHub - tesharp/systemair: Home assistant integration for Systemair SAVE Connect 2 using modbus over http.

1 Like
8

Hi,
I have been trying to use the blueprint with an VSR500 - I had previously integrated the VSR500 over MODBUS TCP.
The IAM module is in “Modbus Gateway TCP-RTU/RS485” - did try with the “Homesolutions Cloud” as well.

image
image416×640 18.5 KB

I do get an error in HomeAssistant:
This error originated from a custom integration.

Logger: custom_components.systemair
Source: custom_components/systemair/config_flow.py:36
integration: systemair (documentation, issues)
First occurred: 6:20:49 PM (3 occurrences)
Last logged: 6:46:59 PM

Error fetching information - 404, message=‘Attempt to decode JSON with unexpected mimetype: text/html’, url=‘http://10.0.10.x/menu’
Error fetching information - Cannot connect to host http:80 ssl:default [Timeout while contacting DNS servers] (Getting a 404 on the /menu or the /mread pages on the IP address).

Is there something that I am missing?

10

Its because this integration based on new Save Connect 2 module. Old IAM didn’t has web api for modbus. You can try my fork based on vanilla ModBus protocol supported by both modules.

11

Thanks @AN3Orik I’ve switched from my previous Modbus direct with EW11 to the save connect 2.0 with your code. I have to say it’s very very impressive work, thank you so much for sharing. Will provide feedback and happy to do any testing etc.