Connect which communication objects for shutter

Configuration
1

I am trying to integrate my shutters into HA. All of the base setup is already working as I have already successfully connected more than 20 dimmable lights and they all work perfectly.

I have found the following example yaml config in the documentation:

These are the communication objects I see in ETS:

Kommunikationsobjekte
Kommunikationsobjekte1211Ă—216 57.4 KB

They are:

  • Move manually
  • Stop manually
  • Position height manually
  • Position response (Also known as state)
  • Movement response (Also known as state)
  • Last direction response (Also known as state)

I don’t recognize the connection between those objectsand the config.

I have already been able to make them move, but it feels quite inconsistent as if I haven’t connected all objects or some incorectly. The shutters become asynchronous sometimes and usually have the wrong state after an interation restart. In some tests I got the position to work, sometimes I didn’t.

I believe this could be an ETS configuration error as well as I kinda just tried a lot to somehow get them to work.

I appreciate any help, thank you!

2

Hi :wave:!
So lets see what you have so far - post your yaml!

move_long_address is “Bewegung Manuell” (your GA column in the picture is to small)

Be sure to configure the same travelling_time_down and -up as you did in your actuators application.

1 Like
3

Thank you for your positivity!

I made the GA small on purpose as to not make it seem like I have an exisiting configuration.

This is my current yaml:

    - name: "Erdgeschoss KĂĽche TerassentĂĽr"
      device_class: "shutter"
      stop_address: "12/6/0"
      move_long_address: "12/6/1"
      position_address: "12/6/2"
      position_state_address: "12/6/3"
      travelling_time_down: 27
      travelling_time_up: 27

My config:

image
image1139Ă—216 36.5 KB

So, I have connected 4 objects, but I feel like I am missing something as I am able to control the shutter, but it’s a bit bugged. The state is not always synchonous and out of sync after moving them manually using the buttons on the actuator. Do I even need all six objects connected? The lights for example only needed 4 out of the 5 objects.

Do you know how to position is retrieved? I think it’s simply a calculaton based on time. Maybe I need to configure something in the ETS software for the position to be somewhat correct and the state to not fel buggy.

Thanksagain for your help and great positivity!

4

The yaml looks perfectly fine. The other 2 group objects aren’t supported by HA anyway.

I do :wink:. It’s not only time based but also updated from the bus - if your actuator sends updates.

What actuator model is this?
Can you configure it to send position updates while/after movement?

What is HAs KNX address (see ETS group address monitor when switching something from HA)?
Do you have multiple KNX lines?

Well, yes - the time it takes to open/close. These actuators are also solely time based (except maybe for SMI).

You use the buttons on the actuator? I guess they don’t send telegrams but control the actuator directly… these are meant for construction time, not regular use, aren’t they?

1 Like
5

Well … They are in use until I got the config done. I don’t like it, but that’s what the other inhabitants are doing for now :smiley:

I did that. Seems less glitchy to me. I timed them irl and then put the results into ETS and HA.

I don’t really know what that is, I don’t think so though. It’s just one IP Interface with like 6 Dimmers and 2 Actuators.

I will search more, but I didn’t see anything regarding this yet.

Since I started using HA, the bus monitor in ETS stopped working. Maybe the same address? Maybe there is a way to change that.

Well, I hope it does :smiley:

Ok. The only one remaining that sounded useful to me was “Last direction response” anyways.

https://download.schneider-electric.com/files?p_enDocType=User+guide&p_File_Name=MTN6705_6805_6710_6810_HWadd_DE.pdf&p_Doc_Ref=MTN67_MTN68_HWadd_DE

I am pretty sure it is this one: MTN6705-0008

6

Your tunneling server (knx ip interface) may only support one concurrent connection. That was pretty common for oder models, now most support 4-8. If that is the case this is normal.

Except if you are really using “Bus monitor” in comparison to “Group address monitor” in ETS - Bus monitor sets the interface in a different mode where it may not be able to have tunneling clients at the same time. Not all interfaces support bus monitor mode (you probably don’t need it anyway).

Sounds like you don’t have multiple lines. Its a way to split bigger installations into smaller chunks.

Chances are that the actuator doesn’t send telegrams when you use the hardware buttons on it - you can check via ETS group address monitor. I guess these are meant to work even when there is no KNX bus at all…
Why are there no KNX switches installed?

1 Like
7

Ohhh, yeah I was using the Bus monitor. It worked, but not while HA is connected. Group Monitor it is.

There are some fancy ass touch multi screen buttons. I did not start with those yet. I just wanted something working as my family has been living in darkness for some days. :sweat_smile: That’s why I started with the lights.

If you are curious, there are:

  • ~ 25 Lights (Only the sections individually addressable)
  • ~ 15 Covers
  • ~ 15 Smoke Detectors
  • ~ 20 individually addressable sockets
  • ~ 10 Buttons with multiple screens each and a temperature sensor each
  • A weather station, alexa devices, solar production live data, individually addressable heating in every room, door bell, gate, etc.

Should I configure the button connections in KNX ETS or just give them group addresses and do that in HA? How much effort will all of this “connecting” be? I have heard about Node Red.

Btw. thank you sooo much for your help! I highly appreciate you as I really want this to be done, so I can focus on other projects again :smiley:

8

Well, that escalated quickly :rofl:

ETS, definitely. A KNX installation should be functional without any central server instance. It’s fully decentraliced by design. The “connecting” is the lesser task after you have defined your group addresses. In fact I think it goes along defining GAs.
HA, NR or what have you comes on top.

9

Do you want me to mark this as the solution or does this thread end as soon as I do so?

10

I don’t know :man_shrugging: Mark it if you like.

1 Like
11

Well, those actuators are like 24 channels each and the dimmers are 6 channels. That’s because they have all extensions.

I get that, but between us, I think the ETS software is absolute garbage. Not the software, but the UX. There is no reason for something this simple to need such a complicated software. I am actually a DEV myself and I really struggled with the software. My personal opinion is: YAML config or IFTTT. Anything between has no target audience in my view. I will get it done though and I will listen to you!

12

ETS is the IDE of KNX. It’s not targeted for end users. I think ETS is really ok, apart it’s price - once you get the hang of it.

Xcode isn’t simple nor user friendly. Resulting Apps should be. Same for your Knx installation - it should be user friendly - imho that means it should be possible to control lights from wall switches when your LAN has problems, the server disk is defect or something is just rebooting / updating.

You can’t replace ETS completely anyway.