Hello André,
I have been busy writing a parsing algorithm that can take any telegram (as far as known to ETS) and convert it into a interpretable JavaScript object. You might have a look at it, maybe it's worth integrating.
https://github.com/snowdd1/knx-dpt-parser
I have tried to build a simple bus monitor on top of node-eibd and knx-dpt-parser, and had to replicate some of your code to change it, because I needed the raw payload of the telegrams, which was not emitted. Of course one must know the DPTs of the destination group addresses, otherwise the differentiation between a percentage DPT5.001 and a HVAC mode 20.102 is not possible. To facilitate that, I have written a small parser that bring an ETS GroupAddress XML export (ETS5+) into a JavaScript Object Notation JSON file.
Regards
Raoul
Hello André,
I have been busy writing a parsing algorithm that can take any telegram (as far as known to ETS) and convert it into a interpretable JavaScript object. You might have a look at it, maybe it's worth integrating.
https://github.com/snowdd1/knx-dpt-parser
I have tried to build a simple bus monitor on top of node-eibd and knx-dpt-parser, and had to replicate some of your code to change it, because I needed the raw payload of the telegrams, which was not emitted. Of course one must know the DPTs of the destination group addresses, otherwise the differentiation between a percentage DPT5.001 and a HVAC mode 20.102 is not possible. To facilitate that, I have written a small parser that bring an ETS GroupAddress XML export (ETS5+) into a JavaScript Object Notation JSON file.
Regards
Raoul