Missing "do not use" category and room about node-red-contrib-loxone HOT 7 CLOSED

Hey @KingAndi,

sadly the loxone websocket does not show items which are in the both categories.
node-red-contrib-loxone has no way to see them.

See the readme und caveats: https://github.com/codmpm/node-red-contrib-loxone#caveats

Events can only be generated by control-in and the controls have to be visible to show up in the node. Well, this is not a caveat as it lays in the design of Loxone's websocket. We can only come around this if Loxone add's a "websocket" checkmark to the controls in Loxone-Config. Also controls will not be shown if you put them in room "unused" and category "unused", albeit they are marked "visible".

Cheers,
Patrik

from node-red-contrib-loxone.

Hey Patrik!

Thanks a lot for you very fast response!

But i tried it. If I first set an other category (e.g. "not assigned") and connect it with the node it works fine.

After this I change the "not assigned" in loxone config into "do not use" it continues working, but in the Properties dialog of node-red the room and category is empty and so the control is not visible any more....

I also had a look into the LoxApp3.json file. the elements are still there visible.

Maybe you could fix it this way, that after opening the editing dialog the content of the control should stay if the room and category is unknown: (maybe a 0 UUID should be visible for room and category -> zero UUID="do not use", i tried it)

Bye Andi

from node-red-contrib-loxone.

Oh, you are right. That should work. My last info was as I stated. We only display what's in the LoxApp3.json file.
Will have a look as soon as I have time.

from node-red-contrib-loxone.

Hallo Patrik!

Perfect, you are great!
Another question: Do you speak german? - I have another idea to discuss, but my english is not so good, so i want to talk in german...

from node-red-contrib-loxone.

Yes, I speak german. Hit me up on the node-red slack, the wled discord or [email protected].

from node-red-contrib-loxone.

Ok, @codmdu had a look into this. Sadly this is not solvable.

Internally the node saves the uuid of the element of loxone. So, if you can select it while it is in "not assigned" (or "Living Room", "Bedroom", etc.) it can see the uuid and register it's event.

When you change the element in loxone to "do not use", it is no longer represented in LoxApp3.json thus can not be seen in node-red-contrib-loxone.
As the uuid is still present, everything should work. But we don't have any, let's say metadata, for the uuid anymore...
Loxone simply does not show elements that are in "do not use" via the LoxApp3.json.

Cheers,
Patrik

We've just had an idea.... investigating.

from node-red-contrib-loxone.

We've added an info on what is happeing with control's that are in room and category "Do not use".
Hope that helps 👍🏻

from node-red-contrib-loxone.