Read "ParameterBlocks"

[henfri]

Hi Mathias,

currently, xknxproj can read Channels, but not parameter-blocks. See:
https://knx-user-forum.de/forum/öffentlicher-bereich/knx-eib-forum/2043088-vorstellung-knx-lens?p=2065298#post2065298

You find an example here:
https://github.com/OpenKNX/OFM-AccessControl/blob/8714e1353ffa6af868ad4aa5f814661317b35f31/src/AccessControl.share.xml#L367

Would it be possible, to read those as well?

Best regards,
Hendrik

[farmio]

Hi 👋!
Well, I guess it would be possible.
Just a bit awkward to add another directory layer next to channels that's afaik only used for ETS display purposes. And it will probably be tricky to parse them with associated ComObjects without severe performance decreases as their Ids don't seem to correlate with anything and we don't have any ComObjectRefRef parsing implemented.

[henfri]

Hi,

thanks for your quick reply!
The reason for that additional directory layer is, that channels in channels are not supported and this grouping is indeed useful.
I need that for knx-lens, where I mimick the ETS Display in a Bus-Monitor (just to fill gaps that ETS has...).

It would be great if you could support it. Performance is not such a big issue: I am caching the parsing. And in order not to impact others, this feature could be activated with an (optional) parameter.

If you need an example knxproj or knxprod, just let me know.

Best regards,
Hendrik

[farmio]

Sorry, I didn't want to raise false expectations... when I say it is possible, I didn't mean that I am going to work on this myself.

Performance may not be an issue for your use case, but it is for HA. Many instances run on low powered - and especially low ram - machines like Raspberry Pis or NAS. Parsing the application programs the way it is done currently (iterparse) makes it a bit difficult to retain recursively nested items and their child element structure. Using parse instead - like used in the project parser - would work fine, but needs like ~40x the memory.
But tbh I have never tested to parse a project on a machine with insufficient memory... no idea what would happen 😬

[henfri]

Hi,

you did not raise false expectations.... Reading between the lines I was uncertain whether you would or would not work on it - and I still am ;-) But before it was 50/50 now it is probably not :-)

Performance may not be an issue for your use case, but it is for HA.
I know. That is why I suggested the parameter to activate/deactivate it.

I might have a look into it. Can you spent 5 minutes to tell me where to start?

Greetings,
Hendrik

[farmio]

I'm trying to avoid having to deal with that XML hell as far as possible 😬 (same for the Forum you linked in the initial post - sorry your mentions there were not seen).

Have a look here for the parsing logic: https://github.com/XKNX/xknxproject/blob/main/xknxproject/loader/application_program_loader.py#L58
This actually only yields single element tags and their attributes - without child elements. Association works via Id parsing then.

In comparison, this parses the whole tree so it can be searched and traversed: https://github.com/XKNX/xknxproject/blob/main/xknxproject/loader/project_loader.py#L63