Optimization of the initial read about node-red-contrib-knx-ultimate HOT 9 CLOSED

Hi Reto.
"Initialread" is triggered whenever node-red restarts. The case of a restarting node-red is very limited and, normally, this doesn't happen so often.
When it happens, i've users saying the exact contrary as you states. They need a visualization touchscreen updated as soon as possibile, to avoid pushing a button while the status of the button is unknown.
I can for sure add a delay (currently, it's fixed at 5 seconds after knx-ultimate initialisation), but thinking to add a new timer and queue array may be a bit overwhelming.
Let me know if a simple "customizable initialread delay" can be useful for you.
:-)

from node-red-contrib-knx-ultimate.

Hi Massimo

An adjustable delay would help a little bit, but it must also be ensured that this timer is cleared when deploying or disconnecting.

The initialread is not only used when restarting Node-RED, but also for deploy and reconnect.

In my opinion, a second queue would not be much more complex? By default the delays would be the same as before, but for larger projects you could set priorities accordingly.

from node-red-contrib-knx-ultimate.

Hi Reto
Yes, the redeploy triggers the initialread as well, but if you select "deploy only changed nodes" it should not be triggered.
I'll think about double queue. Maybe i can move a "read" request from the "initialread" queue, to the main telegram queue only if the main telegram queue is empty.
About clearing timers, i need to clear all timers everytime, most importantly, if i've a timer that pushes telegrams from "initialread" queue, into the main queue from time to time.
Let me do a gurumeditation about that.

from node-red-contrib-knx-ultimate.

Thanks for thinking about it ;-)

I would have a two more feature requests, are you open for it?

from node-red-contrib-knx-ultimate.

Yes, but please create a new issue for each.

from node-red-contrib-knx-ultimate.

Ok, solved in a very elegant way.
Out soon in v 1.1.40
If you wanna try, create a function node "Massive read request" and paste this code
for (let index = 0; index < 1000; index++) {
node.send({readstatus:true});
}

Then start the function and in the meantime, turn on/off any other knx-ultimate node.
The "write" and "response" does have the higher priority in the massive flooding "read" telegrams.

from node-red-contrib-knx-ultimate.

Thank you for optimizing this!

Could you create node setting parameters for the read delay time and the delay between telegerams can be read/write?

from node-red-contrib-knx-ultimate.

Hi Reto,
not now sorry, we've fighting with Coronavirus here.
We're very in trouble..
Hope in the next weeks...

from node-red-contrib-knx-ultimate.

In the meantime, you can disable the automatic read and use an inject node with delay you want, that sends a read request to knx-ultimate.
Please see here https://github.com/Supergiovane/node-red-contrib-knx-ultimate/wiki/-Sample---Read-value-from-Device

from node-red-contrib-knx-ultimate.