Airios ventilation integration

[breckler]

Hi,

we have a airios VMN-02LM11 device in our flat, and I would like to send the same commands somehow via home assistant.

it seems that the device send on 868.3 MHz
https://www.nibe.eu/assets/documents/25862/IHB_NL_RF%20zender%20instructie_EN.pdf

Interface for ventilation systems | VMN-02LM11 | Airios

Any idea?

[etrag (ricardo)]

Hello, did you had any progress with this?
I have a Siberzone system that seems to be a rebrand from Airios. I have a RF Bridge from Airios/Honeywell that enables me to use an app to control however I would also like to integrate it with home assistant.

[breckler]

Hi, unfortunately I did not find a solution, so I ended up soldering a zigbee 4 channel relay board to the device by removing the buttons

[sergiojsilva]

Hi breckler,
Can you please post some pictures about your zigbee implementation? I don’t know what to solder but I would like to do the same thing with an arduino Wemos D1.
Thank you!

[zxdavb (David Bonnes)]

See here: Honeywell CH/DHW via RF - evohome, sundial, hometronics, chronotherm - Share your Projects! - Home Assistant Community (home-assistant.io)

[franji (Francisco)]

I have the same situation with a SIBER EVO1 device. I would like to change also bypass operation as AUTO does no work really well.
I have bought this https://indalo-tech.onlineweb.shop/ device and install ramses_cc ramses_cc. It intercepts packages and depicts in a log but I still need to understand something more about it to be able to operate.

[siebenish]

Did you end up finding a solution for your SIBER VMC?

[franji (Francisco)]

Yes, it works very nicely.
The steps are the following:

1. Buy MANDO MULTICONTROL INALÁMBRICO and link to the system or maybe use https://www.siberzone.es/Media/Uploads/dlm_uploads/manual-siber-mando-pulsador-4-botones-inalambrico.pdf (the latest not tested). I strongly recomment to use mando-multicontrol as you can check that your system work by watching how states change in it.
2. Buy https://indalo-tech.onlineweb.shop/
3. Install ramses_cc ramses_cc
4. Using logs detect the remote (37:xxxxxxx where xxxxxxx depends on your remote number) and device ( 32:yyyyyy where yyyyyy depends on your device number)
5. Add this code in configuration.yaml (

ramses_cc:
serial_port: /dev/ttyACM0 # e.g. evofw3-based device
packet_log:
file_name: packet.log
rotate_bytes: null
rotate_backups: 7
known_list:
32:xxxxxx : { class: FAN, _note: SIBER EVO1 }
37:yyyyyy:
class: REM
faked: True
commands:
away: ’ I — 37:yyyyyy 32:xxxxxx --:------ 22F1 003 000107’
low: ’ I — 37:yyyyyy 32:xxxxxx --:------ 22F1 003 000207’
medium: ’ I — 37:yyyyyy 32:xxxxxx --:------ 22F1 003 000307’
high: ’ I — 37:yyyyyy 32:xxxxxx --:------ 22F1 003 000407’
boost: ’ I — 37:yyyyyy 32:xxxxxx --:------ 22F1 003 000707’
bypass_off: ’ W — 37:yyyyyy 32:xxxxxx --:------ 22F7 003 00C8EF’
bypass_on: ’ W — 37:yyyyyy 32:xxxxxx --:------ 22F7 003 0000EF’
bypass_auto: ’ W — 37:yyyyyy 32:xxxxxx --:------ 22F7 003 00FFEF’
calendar_off: ’ W — 37:yyyyyy 32:xxxxxx --:------ 22B0 002 0006’
calendar_on: ’ W — 37:yyyyyy 32:xxxxxx --:------ 22B0 002 0005’

  _note: based upon an Orcon 15RF 6-button remote (VMN-15LF01) adapted for SIBER EVO1

[zxdavb (David Bonnes)]

This is better formatted, removes some typos, and has other improvements.

@franji

ramses_cc:
  serial_port: /dev/ttyACM0
  packet_log:
    file_name: packet.log
    rotate_backups: 7
  config: enforce_known_list: true

known_list:
  32:xxxxxx: {class: FAN, _note: "SIBER EVO1"}
  37:yyyyyy: 
    class: REM 
    faked: true
    commands:
      away:         " I --- 37:yyyyyy 32:xxxxxx --:------ 22F1 003 000107"
      low:          " I --- 37:yyyyyy 32:xxxxxx --:------ 22F1 003 000207"
      medium:       " I --- 37:yyyyyy 32:xxxxxx --:------ 22F1 003 000307"
      high:         " I --- 37:yyyyyy 32:xxxxxx --:------ 22F1 003 000407"
      boost:        " I --- 37:yyyyyy 32:xxxxxx --:------ 22F1 003 000707"
      bypass_off:   " W --- 37:yyyyyy 32:xxxxxx --:------ 22F7 003 00C8EF"
      bypass_on:    " W --- 37:yyyyyy 32:xxxxxx --:------ 22F7 003 0000EF"
      bypass_auto:  " W --- 37:yyyyyy 32:xxxxxx --:------ 22F7 003 00FFEF"
      calendar_off: " W --- 37:yyyyyy 32:xxxxxx --:------ 22B0 002 0006"
      calendar_on:  " W --- 37:yyyyyy 32:xxxxxx --:------ 22B0 002 0005"

TIP: Don’t enforce the known list until after you know your device IDs.

[zxdavb (David Bonnes)]

As as aside, the next version of ramses_rf will provide support for the above functionality without the need to purchase the remote control.

That is, rather than impersonating an existing control (that is already bound to the ventilation unit), it will simulate a virtual control (after binding it to the fan).

Given that the USB dongle from Indalo-Tech is much cheaper than these wireless remotes, this should be of interest to many.

[siebenish]

Thanks for the info. I have been waiting for the device to be back in stock for some time now to try it out, but so far nothing.

[zxdavb (David Bonnes)]

@siebenish Keep an eye on your inbox!

[Gdales]

Hi, I have the same problem with my VMC using the same remote control.
Do you know where can I buy the USB dongle from Indalo-Tech?

[zxdavb (David Bonnes)]

@Gdales

where can I buy the USB dongle from Indalo-Tech?

From here: https://indalo-tech.onlineweb.shop/

[GabrielRR (Gabriel Ribeiro)]

The store is closed for some time. Where can I find that device?

[siebenish]

Following up on this, I’m only now setting up the SIBER DF EVO 2 with the indalo-tech SSM-D2 USB stick.

The USB stick is recognized just fine by HA.

I can’t say I have found any behavior with Ramses CC that is repeatable until now. I’ve done the exact same configuration to end up having some data in packet.log, and with other tries just errors trying to setup the integration.

I’ve tried YAML only versions and the config flow versions, but at the moment I just get errors or HASSOS lockups.

However I did have some luck today with the integration, where it actually received logs when I placed only this in the known_list and nothing else:

18:003599:

And then I got these logs:

2024-04-30T19:35:21.496069 # ramses_tx 0.31.19

2024-04-30T19:35:21.555956 000 I --- 18:003599 63:262142 --:------ 7FFF 016 0010018F304A381B76302E33312E3139

2024-04-30T19:35:21.586983 000 I --- 18:003599 63:262142 --:------ 7FFF 016 0010018F304A381B76302E33312E3139

2024-04-30T19:35:52.002414 065 RQ --- 37:145236 32:137185 --:------ 31DA 001 00

2024-04-30T19:35:52.038417 071 RP --- 32:137185 37:145236 --:------ 31DA 030 00EF007FFFEFEF06FE087908AC06F9F00200011A36000000EF7FFF7FFF00

2024-04-30T19:36:54.044324 071 I 246 32:137185 --:------ 32:137185 31D9 017 000A020020202020202020202020202008

2024-04-30T19:38:45.252619 060 I --- 37:145236 32:137185 --:------ 22F1 003 000307

2024-04-30T19:38:45.280572 071 I 247 32:137185 --:------ 32:137185 31D9 017 000A030020202020202020202020202008

2024-04-30T19:38:45.373521 071 I --- 32:137185 --:------ 32:137185 31DA 030 00EF007FFFEFEF06FE087808AD06F8F00200023440000000EF7FFF7FFF00

2024-04-30T19:38:51.002711 061 I --- 37:145236 32:137185 --:------ 22F1 003 000407

2024-04-30T19:38:51.025685 070 I 248 32:137185 --:------ 32:137185 31D9 017 000A040020202020202020202020202008

2024-04-30T19:38:51.119722 071 I --- 32:137185 --:------ 32:137185 31DA 030 00EF007FFFEFEF06FD087908AD06F6F00200035C6C000000EF7FFF7FFF00

2024-04-30T19:38:53.951780 071 I --- 32:137185 --:------ 32:137185 31DA 030 00EF007FFFEFEF06FE087608AD06F5F00200035C6C000000EF7FFF7FFF00

2024-04-30T19:38:58.377934 061 I --- 37:145236 32:137185 --:------ 22F1 003 000107

2024-04-30T19:38:58.409943 069 I 249 32:137185 --:------ 32:137185 31D9 017 000A010020202020202020202020202008

2024-04-30T19:38:58.513965 071 I --- 32:137185 --:------ 32:137185 31DA 030 00EF007FFFEFEF06FE087708AD06F4F00200150E1A000000EF7FFF7FFF00

2024-04-30T19:39:03.939062 070 I --- 32:137185 --:------ 32:137185 31DA 030 00EF007FFFEFEF0700087708AE06F1F00200150E1A000000EF7FFF7FFF00

2024-04-30T19:39:07.252143 069 I --- 37:145236 32:137185 --:------ 22F1 003 000207

2024-04-30T19:39:07.283142 070 I 250 32:137185 --:------ 32:137185 31D9 017 000A020020202020202020202020202008

2024-04-30T19:39:07.377196 071 I --- 32:137185 --:------ 32:137185 31DA 030 00EF007FFFEFEF0700087508AE06EEF00200011A36000000EF7FFF7FFF00

2024-04-30T19:39:13.941433 071 I --- 32:137185 --:------ 32:137185 31DA 030 00EF007FFFEFEF0701087608AD06EDF00200011A36000000EF7FFF7FFF00

2024-04-30T19:41:53.812073 071 I --- 32:137185 --:------ 32:137185 31DA 030 00EF007FFFEFEF06FB087908AD06EEF00200011A36000000EF7FFF7FFF00

2024-04-30T19:50:55.995136 067 RQ --- 37:145236 32:137185 --:------ 31DA 001 00

2024-04-30T19:50:56.032141 071 RP --- 32:137185 37:145236 --:------ 31DA 030 00EF007FFFEFEF06EF087608AF06E5F00200011A36000000EF7FFF7FFF00

2024-04-30T19:51:53.335799 071 I 251 32:137185 --:------ 32:137185 31D9 017 000A020020202020202020202020202008

2024-04-30T19:51:53.428768 071 I --- 32:137185 --:------ 32:137185 31DA 030 00EF007FFFEFEF06ED087408AF06E0F00200011A36000000EF7FFF7FFF00

2024-04-30T19:52:43.285130 071 I --- 32:137185 --:------ 32:137185 313F 009 007CA734331E0407E8

2024-04-30T20:01:52.874413 071 I --- 32:137185 --:------ 32:137185 31DA 030 00EF007FFFEFEF06DF087308AF06D5F00200011A36000000EF7FFF7FFF00

2024-04-30T20:03:59.989922 066 RQ --- 37:145236 32:137185 --:------ 313F 001 00

2024-04-30T20:04:00.008668 070 RP --- 32:137185 37:145236 --:------ 313F 009 007CB803341E0407E8

2024-04-30T20:04:00.157005 066 RQ --- 37:145236 32:137185 --:------ 1470 001 00

But if I try to do this now, home assistant just locks up and needs to be cold restarted.

I also tried many variations of the below in the known_list flow box, but I got either integration start errors, or HA lockups:

"18:003599": 
  class: REM
"32:137185":
  class: FAN
  _note: SIBER EVO2
"37:145236":
  class: REM
  faked: true
  commands:
    away: " I --- 37:145236 32:137185 --:------ 22F1 003 000107"
    low: " I --- 37:145236 32:137185 --:------ 22F1 003 000207"
    medium: " I --- 37:145236 32:137185 --:------ 22F1 003 000307"
    high: " I --- 37:145236 32:137185 --:------ 22F1 003 000407"
    boost: " I --- 37:145236 32:137185 --:------ 22F1 003 000707"
    bypass_off: " W --- 37:145236 32:137185 --:------ 22F7 003 00C8EF"
    bypass_on: " W --- 37:145236 32:137185 --:------ 22F7 003 0000EF"
    bypass_auto: " W --- 37:145236 32:137185 --:------ 22F7 003 00FFEF"
    calendar_off: " W --- 37:145236 32:137185 --:------ 22B0 002 0006"
    calendar_on: " W --- 37:145236 32:137185 --:------ 22B0 002 0005"

Can anyone help out with what I’m doing wrong here?

[GabrielRR (Gabriel Ribeiro)]

Hi,

I also have a Siber Evo2.
And have the same problems as you. I can’t even receive logs. I have the last version from ramses and I’m using config flow. Did you manage to fix this? Can you share it?
thanks

[siebenish]

I’m actually stuck with an issue that didn’t get me near finishing a config file.

There is a GitHub issue open on this but it’s been hard to fix. basically the USB is hanging my HA instance when the integration is active, which although pointing at the integration it may also can be related to proxmox USB passthrough.

Startup hangs with pyserial-asyncio-fast

[zxdavb (David Bonnes)]

@GabrielRR

I can’t even receive logs.

Have you had a look at the first steps in: 3.1 I'm stuck: Help me · zxdavb/ramses_cc Wiki · GitHub

If so, and you’re not getting a packet log, please provide infor about:

• what version of RAMSES RF you’re using (I see is config_flow)
• your serial port configuration
• your HA log | grep ramses

[GabrielRR (Gabriel Ribeiro)]

Hi,
I checked the logs as you described in your reply.
Since I’m using Home Assistant as a Docker installation, I had to connect the USB drive inside the container. I found that I couldn’t use the following mapping:
/dev/serial/by-id/:/dev/serial/by-id/.
After changing it to
/dev/ttyACM0:/dev/ttyACM0,
it started working as expected.

I made a minimal configuration in the config flow, and now it detects the USB device from
https://indalo-tech.onlineweb.shop/ perfectly and writes to the log.