Modbus: RTUOVERTCP > Splitting

Configuration
1

Hi everyone,
Just started today learning HA, i have experience in Industrial automatisation (Rockwell, GE) but i have noticed for HA i can throw that experience away.

Since that experience i like to work with Splitting up my YAML’s to make it more easy to read and backtrack.
But i am stuck with an issue, i have tried multiple ways, but i think i have lack of knowledge even i use the information pages.

I have ran into an issue while adding yaml files and modbus !include.
My POE Relay board works perfectly when on configuration.yaml

Relays integration

modbus:

  • name: har30_1
    type: rtuovertcp
    host: 192.168.1.203
    port: 4196
    timeout: 5
    switches:
    • name: “RL Vooraan beneden UP”
      address: 0
      write_type: coil
      slave: 1
    • name: “RL Vooraan beneden DOWN”
      address: 1
      write_type: coil
      slave: 1
    • name: “RL 3”
      address: 2
      write_type: coil
      slave: 1
    • name: “RL 4”
      address: 3
      write_type: coil
      slave: 1
    • name: “RL 5”
      address: 4
      write_type: coil
      slave: 1
    • name: “RL 5”
      address: 5
      write_type: coil
      slave: 1
    • name: “RL 6”
      address: 6
      write_type: coil
      slave: 1
    • name: “RL 7”
      address: 7
      write_type: coil
      slave: 1
    • name: “RL 8”
      address: 8
      write_type: coil
      slave: 1
    • name: “RL 9”
      address: 9
      write_type: coil
      slave: 1
    • name: “RL 10”
      address: 10
      write_type: coil
      slave: 1
    • name: “RL 11”
      address: 11
      write_type: coil
      slave: 1
    • name: “RL 12”
      address: 12
      write_type: coil
      slave: 1
    • name: “RL 13”
      address: 13
      write_type: coil
      slave: 1
    • name: “RL 14”
      address: 14
      write_type: coil
      slave: 1
    • name: “RM 15”
      address: 15
      write_type: coil
      slave: 1
    • name: “Light_1”
      address: 16
      write_type: coil
      slave: 1
    • name: “Light_2”
      address: 17
      write_type: coil
      slave: 1
    • name: “Light_3”
      address: 18
      write_type: coil
      slave: 1
    • name: “Light_4”
      address: 19
      write_type: coil
      slave: 1
    • name: “Light_5”
      address: 20
      write_type: coil
      slave: 1
    • name: “Light_6”
      address: 21
      write_type: coil
      slave: 1
    • name: “Light_7”
      address: 22
      write_type: coil
      slave: 1
    • name: “Light_8”
      address: 23
      write_type: coil
      slave: 1
    • name: “Light_9”
      address: 24
      write_type: coil
      slave: 1
    • name: “Light_10”
      address: 25
      write_type: coil
      slave: 1
    • name: “Light_11”
      address: 26
      write_type: coil
      slave: 1
    • name: “Light_12”
      address: 27
      write_type: coil
      slave: 1
    • name: “Light_13”
      address: 28
      write_type: coil
      slave: 1
    • name: “Light_14”
      address: 29
      slave: 1

But i tried different ways to implement this with a different yaml file.

FXP:
modbus: !include_dir_named relays
i set this up correctly, made folder relays, added har301.yaml, removed the modbus out of this file.

The moment i do this i get warnings of not adding Baudrate, Type, etc. Even it states “type: rutovertcp”
So it feels like the moment you Split yawl’s, it doesn’t read “type”.