Supergiovane / node-red-contrib-knx-ultimate

Control your KNX intallation via Node-Red! A bunch of KNX nodes, with integrated Philips HUE control and ETS group address importer.
https://youtu.be/egRbR_KwP9I
MIT License
143 stars 34 forks source link

Tapperella #249

Closed gtnscebba closed 1 year ago

gtnscebba commented 1 year ago

Hello Supergiovane, I hope it's all okay.

I use the KNX Ultimate version 2.1.15 and Nodedred 3.0.2.

Attached, I inserted two images of a flow present in my Nodeded project that manages some objects of my home office. I could send you the JSON but I'm not able to do in Github.

As far as "Gestione Luce Studio" is concerned, I have no problem, everything works as I want. The reason for the presence of the two buttons "Luce Studio" and "Plafoniera Studio" is that these go in two different tab of the dashboard. However, by pressing them, their behavior is perfect, the light turns on off.

As you can see, a similar scheme was made for the management of the shutter. The scheme thus configured works because I was forced to remove the connection between the exit of "Tapp Studio" and input of node "Tapparella" because I have a problem that I describe.

The buttons "SU", "GIU' '" and "STOP" are inserted in a tab of the dashboard that sees all the objects of a room. All these three buttons work perfectly. (This shutter does not have an actuator who manages the absolute position)

The "Tapp Studio" button is inserted in the dashboard tab which is a synoptic of all the objects of the house. When I connect the exit of the "Tapp Studio" button at the input of KNX Ultimate node "Tapparella" (Group address 1/0/2) the shutter moves (in the opposite direction compared to the proceeding), but goes to "shots", not with a linear movement. This annoying behavior was introduced by one of the updates, before it worked perfectly.

Furthermore, on the KNX actuator of the shutter continues to feel an intermittent click until the end of the running time inserted on the real KNX device even if the roller shutter is completely high or completely at the bottom. To make the click stop before this time, I must press the "STOP" button or the physical button of the KNX system.

It would seems that the KNX Ultimate node "Tapparella Studio Status" is responsible for this annoying behavior.

In your opinion, is there a way to eliminate this annoying behavior or it is not possible?

I thank you as always for the excellent support that you gives everyone.

Ciao!

NR_LuceStudio NR_TapparellaStudio

gtnscebba commented 1 year ago

Please do not consider the isolated function "Tap Studio Stop", as it is not operative

Supergiovane commented 1 year ago

Hi Gaetano Tapparella studio status should be an absolute position status, like 0-100%, not a boolean value. What do you mean with

but goes to "shots", not with a linear
movement

The actuator is responsible for all movements. Knx-ultimate only sends a command to move up and down the rolling shutters. I think your rolling shutters have gone out of time sync with the actuator, for whatever reason, maybe a black out…

gtnscebba commented 1 year ago

Regarding your first question: I mean the shutter moves for 1 second, stop 1 second, moves for 1 second and so on, until it reaches the final destinaton (top or bottom).

Regarding the second question: I don't know the root cause, the behaviour of the shutter is "normal" if you use the "SU/GIU/STOP" buttons of nodered project or the real buttons in KNX system.

I assure you that before some uodates of KNX Ultimate, the behaviour of "Tapp Studio" button was correct, as "SU/GIU".

Supergiovane commented 1 year ago

Hi Gaetano I’m currently on holiday, so i cannot take a look at it, but you could debug the matter using ETS diagnostic tool. You could also install a previous version of knx-ultimate, the last from v1.xx. For that, please see the npmjs help on how to do so.

gtnscebba commented 1 year ago

It is not so urgent, take a quiet vacation. Ciao!

Supergiovane commented 1 year ago

Hi Have you then solved, or do you still need help? If by using the inject nodes, the behaviour of the tapparella is right, i suspect something wrong with the configuration of the SU and GIU dashboard nodes.