Group Monitor Export for ETS

[heleon19]

Group Monitor Export for ETS

[MGKQB]

Please use an extra node. Multiple nodes for special functions make more sense and they make everything a lot easier to use and understand IMHO.

[Supergiovane]

Yes, it could be a logger node, able not only to do what heleon asked, but able to prepare the data for every type of logging.

[Supergiovane]

Hi Reto,
i managed to extract the CEMI raw telegram.
Now i must raise it from api to the node.

[Supergiovane]

Hi Reto
sames as before, not now sorry. We're in very trouble with Coronavirus now.

[heleon19]

Hello Massimo

How are you doing? The Corona virus has also reached us, we now also have restrictions on freedom of movement.

I've seen that you've made some progress lately. Is developing the group monitor an option for you? If so, you could make me an offer, we would also pay something. However, we would have to negotiate this by e-mail.
If you don't want to spend time on it, I understand.

Regards Reto

[Supergiovane]

Hello Reto
here it's a disaster. Luckily, the number of death people is not growing anymore, it stays to about 600 peoples at day, with a major spike of ca. 800 in one day, last week.
You should be able to do this via a simple function node, attached to knx-ultimate.
Knx-ultimate already outputs a RAW value with type of telegram (read, write, response). You need to put these data in an XML and you're done.
Or i'm missing something?

[heleon19]

Hopefully this will soon be over!

I would need the raw data frame, not only the value. Therefor a change in knx.js would be necessary.

Here it's what I got:

But I would need like the RawData in the XML above.

I think this group monitor would be a very usefull thing.

[Supergiovane]

Hi Reto
I don't use knx.js anymore. At least until Ekarak has merged my pull request, because i need the changes go faster and i've made some important changes in the api.
Let me ditch into the raw data frame. I'll let you know.
Then we see if putting the raw dataframe in a knx-ultimate node output property is suitable for you, or if we must go for another way (maybe a separate monitor node, to keep the things simple for people not interested in that).

[Supergiovane]

Hello Reto.
Ok raised up to the node.
Now the simples things.
I'll output the XML every xx minutes to the flow (in this case, you could save it with the "file" node, or send it to an FTP server, for example).

Can you please try to read this with your ETS and tell me if it's readable?
Banana.xml.zip

[heleon19]

Hi Massimo
First of all, thank you for working on it!
I can open it with ETS. I think it's an good idea to output it every xx minutes. So you are creating an extra node for it with an definable output interval?

[Supergiovane]

Yup. A logger node.
Think to release it tomorrow, as well as the api.

[Supergiovane]

V.1.1.51 is out.
Config: https://github.com/Supergiovane/node-red-contrib-knx-ultimate/wiki/Logger-Configuration
Sample: https://github.com/Supergiovane/node-red-contrib-knx-ultimate/wiki/Logger-Sample

[Supergiovane]

Hi Reto.
Does it work?
Give me a feedback. I’m italian. We love feedbacks.

[heleon19]

Ciao Massimo

Grazie mille! I know, the Italians likes to talk a lot :-)

Works very well. I also like the settings!

Do you do this as a hobby or is it your profession?

Regards Reto

[Supergiovane]

Hi Reto
No this was my job, but now it’s my hobby!
Glad it works!
If you need something else, just ask.
Thank you and have a nice weekend!