Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ETS5 Project - YAML File contains only "--- {}" #27

Open
marko3122 opened this issue Jun 4, 2024 · 3 comments
Open

ETS5 Project - YAML File contains only "--- {}" #27

marko3122 opened this issue Jun 4, 2024 · 3 comments

Comments

@marko3122
Copy link

marko3122 commented Jun 4, 2024

Hello,

My project has all the neccessary building information , however I did notice that none of my group addresses have the Data point type set. I've set some manually for testing , in the terminal I can see that It didn't skip those adresses now but in the yaml file there is still nothing to see but the "--- {}" line.

Nevermind, I found the "WARN -- : xyz Group not in object: use ETS to create functions or use specific code" Error as well. With amounts of corrections I will have to do, it comes close to doing it manually anway :(

WohnhausBUG
testyaml

@laurent-martin
Copy link
Owner

Right,

As described in the README, the tool cannot guess how KNX group addresses are associated with H.A. objects.

This information needs to come from somewhere.

There are 2 possibilities:

  1. in ETS, in building, create "functions" : one per H.A. objects, and place group addresses in those functions, (for example a light).
  2. or, if the naming is processable, write some small ruby code that parses the group name and deduce an object type and name...

Personally, initially, I used 2. , but then I added 1, as it is more integrated with ETS.

I see you have building information: did you create the functions ?

image

There are still some pitfalls: ETS functions are limited to a few only, and do not provide complex ones.
In a future release of this tool, it will be possible to include metadata in the comment part.

@TheFelix93
Copy link

@marko3122 how does it come that the DPTs are not set by ETS? I think always when I associated a GA with a device, like an actor, that writes to the GA the DPT was mapped automatically.

@marko3122
Copy link
Author

@marko3122 how does it come that the DPTs are not set by ETS? I think always when I associated a GA with a device, like an actor, that writes to the GA the DPT was mapped automatically.

No idea honestly, the owner decided to go with the "Horizone" visualization route so I won't be banging my head too much about this one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants