Closed heleon19 closed 3 years ago
Hi Heleon i'm fine, thanks. I'm busy with KNX Secure at the moment. I saw you're connecting via a KNX Interface in unicast. Please enable the checkbox "Ignore ACK requests", this one:
Then, please, at least on one of the two installations, upgrade to the latest version, because there are everytime little changes/iprovements involving the connection part as well.
Hi Massimo, We were able to recreate the problem by removing and plug back in the network cable at the IP interface a few times. After that, we set the "Ignore ACK requests" and updated to the latest KNX Ultimate Version (1.2.36) and we still get the same result, but now with a new error in the log: After a deploy it reconnected correctly again.
Si Simon, Every KNX Interface behaves differently, as far i have seen in these years. As soon as you unplug the cord, some interfaces will release the tunnel after a while, some other interfaces fail to do so and then you'll run out of free tunneling connections. For this reason, i ever suggest using a KNX Router. I tried to reproduce your issue, without success. For me to check and solve your particular issue, i need to know the make/model of your KNX interface on both the installation site.
It is a Weinzierl KNX IP Interface 731. But even if theres no free tunnels on the Interface, why does it works after a deploy?
Hi a Support's person at Weinzierl, was aware of an issue with Weinzierl 731. See here https://github.com/Supergiovane/node-red-contrib-knx-ultimate/issues/78
Are you able to perform a firmware upgrade on Weinzierl 731? If not, please leave me today to make other tests..
..and another question... do you have more than 1 ethernet/wifi interface on the PC running node-red?
Hi Simon Please unzip this file into your ./node-red/node_modules/node-red-contrib-knx-ultimate/nodes folder and restart node-red. Then try again unplugging the cable.
11 Aug 14:00:00 - [warn] ------------------------------------------------------ 11 Aug 14:00:00 - [warn] [node-red-contrib-knx-ultimate/knxUltimate-config] SyntaxError: Invalid left-hand side in assignment 11 Aug 14:00:00 - [warn] ------------------------------------------------------ 11 Aug 14:00:00 - [info] Waiting for missing types to be registered: 11 Aug 14:00:00 - [info] - knxUltimate-config
With this file I do get an error
Hi Heleon, you need to use the latest version of knx-ultimate, then replace the file.
You can revert to a previous version by issuing a command: npm install node-red-contrib-knx-ultimate@1.2.14
Then please use this zip (not the previous) :
EDIT: Please be aware, the destination folder is ./node-red/node_modules/node-red-contrib-knx-ultimate/nodes
This file for the lates version?
Yes. Please be aware of the destination folder ./node-red/node_modules/node-red-contrib-knx-ultimate/nodes
I was now able to load the file.
We can observe different scenarios when we disconnect the network cable at the interface for different lengths.
Please unzip this file into your folder: .node-red/node_modules/node-red-contrib-knx-ultimate/knxultimate-api2/src FSM.js.zip
I'm going forward in the blind, because i've tested several times with several disconnection intervals and knx-ultimate always regain the connection and the ability to write to the bus as well.
Hi Reto please unzip this file here ./node-red/node_modules/node-red-contrib-knx-ultimate/nodes as well:
Have loaded both files. Now the following behavior:
Partly the nodes become gray, then green, connection is interrupted.
If I disconnect the interface while the reading nodes are being read, the nodes also turn green. The connection is interrupted.
We have about 40 values that are read out in this project
Hi Please dont' care about the status colors. For me is important to know: does knx-ultimate reconnects and works ok in each case you mentioned here https://github.com/Supergiovane/node-red-contrib-knx-ultimate/issues/132#issuecomment-896822967 ?
On every reconnection, knx-ultimate should attempt to re-read the values of all nodes set as "read on connection/reconnection". Does this happen?
Thanks
Hi No in some cases after reconnection the values are not re-read. But after deploy it does. We use a switch to connect PC and KNX Interface. Do you have the same setup? Thank you Reto
Hi, yes. I physically disconnect the lan cable coming from the PC. Ok, let go step by step. I'll take a look at the "reading" after you confirm this: does does knx-ultimate reconnects and works ok in each case you mentioned here #132 (comment) ?
I do not understand the question.
Be aware of, we disconnect the lan cable from the switch to the interface. Not the lan from pc to the switch.
case 1 and 2 --> yes case 3 --> no case 4 --> disconnect while reading --> no
Hi, After disconnection/reconnection of the lan cable, does KNX-Ultimate send and receive telegrams from the KNX Bus? Is that point fixed?
Ah, ok. We must fix that before thinking to the "read" function.
My colleague who is on site has left. Should I go on site tomorrow to test further? Otherwise I will be back on site on Monday.
Could you make an option at the watchdog which does the reconnect. In combination with the TP test that would be pretty safe? If it can be done without, all the better.
Hi, i need some time to work on that. As i mentioned earlier, my 2 KNX Interfaces doesn't behave like yours. They work as expected.
About the watchdog, you can already force a reconnection. You can read about that in the wiki (https://github.com/Supergiovane/node-red-contrib-knx-ultimate/wiki/de-9.-WathDog-Messages-to-the-node) by using the msg.setGatewayConfig property.
Hi Massimo This file with the FSM.js? I can do one short test today. On monday I'm on side, then I can do more tests. Thank's for your support
Hi Heleon here another try. please unzip this file here ./node-red/node_modules/node-red-contrib-knx-ultimate/nodes knxUltimate-config.js.zip
The issue was very naggy, because it involves an old API part, that was bugged. I tested it at 360° degrees and it should work. Please use the attached zip on latest knx-ultimate version already installed (not the old 1.2.14).
Hi Massimo I'm not on side, so I'll test it at Monday.
Ok. The file contains some unwanted "banana" logs, but in the official release, i'll remove that.
Hi Reto, for Monday, the new Version 1.2.37 will be already out, so you can simply install that new version. All your trouble should be far away.
Hi Massimo Thank you for the new version, I've installed v1.2.38.
Unfortunately, not all problems have been solved. Sometimes when I disconnect the network connection, the nodes turn red "Disconnected", when I plug in again at that moment, the nodes turn green, but I can't switch anything, even the inputs are not read.
Further I noticed that the setting "On connect/reconnect read value" is always Unknown. Even after I have set this.
Hi Heleon there should be something wrong if the option "Bei Verbidung/.... der Wert lesen" doesn't remain selected. Are the node.js and node-red up to date? Node.js should be at least 12.x or better 14.x, while node-red at least 1.1.x
Node.js v12.16.1 and Node-RED 1.1.3
Just found out, if I select "Lesen den letzten ..." and then go back to "Nein" or "Lesen vom KNX-BUS" it works. So I'think we have to use an upgrade Script for old projects? Or you could parse the value in oneditoredit to 0 or 1?
But the issue with the connection is still our big problem ;-)
Hi If you leave that unselected, it behaves exactly as you set on the old version (There was only yes and no). This behaviour is for backward compatibility and it's the base logic of all changes in my nodes: not to change the setted behaviour. So you can leave it blank or select option 1 (Lesen vom KNX-BUS).
The issue with connection should be 100% solved, i tested many times with many disconnection attempts and speed (< 500ms, < 1 second, between 1 and 3, < 10 and > than 10 seconds) and it has ever regained the connection (the old version, instead, had the issue you mentioned in the first post). I suspect an issue with your KNX Interface, as i told you above in this discussion. If you can, you should upgrade it's firmware or try with another KNX Interface.
Are you eventuelly able to make a video (either record the screen or use your cell-phone to make a video of the screen) and send it here?
Just send you an mail with the video. I will not upload it here. Let me know when you get it.
Got it. What happens if you put an inject node here and send the value directly, istead of clicking on the big blue lamp on the right?
It makes no difference, just tested it.
I don't know how to help you more than that. I cannot reproduce your issue. I checked with 1 Enertex interface, 1 Enertex Router set as interface, and 1 Eibmarkt Interface, all without any issue. Tried the same as you, by detaching, reattaching the interface's RJ connector and all the time, it has regained the connection. The fact that when you restart node-red, it works again, can be related to some underlying thing happening in the "dgram" component of node.js. I strongly suggest you to try another KNX IP interface, or even better a KNX router. As i wrote, your interface had problem in the past.
how is your network setup? As I said, the PC is connected to the interface via a switch. I disconnect the interface, but the PC is still connected to the network. This certainly makes a difference than disconnecting the PC from the network, the detection is different.
I noticed that as long as I wait after an interruption until all values have been read initially, the connection is established correctly. However, if I disconnect again during the initial readout, as shown in the video, the connection is no longer established.
Hi Reto i tested by disconnecting the cable direcly at interrace level, connected by a switch, like your. Please unzip this and retry:
If unsuccessful, please unzip this: knxUltimate-config.js.zip
I tested without the modificated file with an Weinzierl IP Interface 732, still the same as with the 731. I'll do the test with the modificated file now.
Use the latest one, please
Still the same. I disconnect for one two seconds. While the values are then initially read out, I disconnect again, after which the connection never recovered. Can you put some Banana Log in your test files, so we know the file is correct loaded?
It definitely happens when an interrupt is during the initial readout function.
I'm focusing on that.
knxUltimate-config.js.zip Try this. You should see some BANANA logs
Now the connection is never restored even if I wait for the initial readout.
BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS [info] 8/16/2021, 2:06:44 PM KNXUltimate-config: Loaded saved GA values 37 [info] 8/16/2021, 2:06:44 PM KNXUltimate-config: Do DoInitialReadFromKNXBusOrFile [info] 8/16/2021, 2:07:03 PM KNXUltimate-config: wrote peristent values to the file /xyz-data/knxultimatestorage/knxpersistvalues/knxpersist6f05cdf2.6fd4bc.json [warn] 8/16/2021, 2:07:03 PM knxUltimate-config: Disconnected. [warn] 8/16/2021, 2:07:03 PM knxUltimate-config: knxConnection warning: timed out waiting for CONNECTIONSTATE_RESPONSE BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS [info] 8/16/2021, 2:07:08 PM KNXUltimate-config: Loaded saved GA values 37 [info] 8/16/2021, 2:07:08 PM KNXUltimate-config: Do DoInitialReadFromKNXBusOrFile [info] 8/16/2021, 2:07:32 PM KNXUltimate-config: wrote peristent values to the file /xyz-data/knxultimatestorage/knxpersistvalues/knxpersist6f05cdf2.6fd4bc.json [warn] 8/16/2021, 2:07:32 PM knxUltimate-config: Disconnected. [warn] 8/16/2021, 2:07:32 PM knxUltimate-config: knxConnection warning: timed out waiting for CONNECTIONSTATE_RESPONSE BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS [info] 8/16/2021, 2:07:37 PM KNXUltimate-config: Loaded saved GA values 37 [info] 8/16/2021, 2:07:37 PM KNXUltimate-config: Do DoInitialReadFromKNXBusOrFile [info] 8/16/2021, 2:07:51 PM KNXUltimate-config: wrote peristent values to the file /xyz-data/knxultimatestorage/knxpersistvalues/knxpersist6f05cdf2.6fd4bc.json [warn] 8/16/2021, 2:07:51 PM knxUltimate-config: Disconnected. [warn] 8/16/2021, 2:07:51 PM knxUltimate-config: knxConnection warning: timed out waiting for CONNECTIONSTATE_RESPONSE BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS [info] 8/16/2021, 2:07:57 PM KNXUltimate-config: Loaded saved GA values 37 [info] 8/16/2021, 2:07:57 PM KNXUltimate-config: Do DoInitialReadFromKNXBusOrFile [info] 8/16/2021, 2:08:25 PM KNXUltimate-config: wrote peristent values to the file /xyz-data/knxultimatestorage/knxpersistvalues/knxpersist6f05cdf2.6fd4bc.json [warn] 8/16/2021, 2:08:25 PM knxUltimate-config: Disconnected. [warn] 8/16/2021, 2:08:25 PM knxUltimate-config: knxConnection warning: timed out waiting for CONNECTIONSTATE_RESPONSE BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS BANANA STOP HANDLING TELEGRAMS [info] 8/16/2021, 2:08:31 PM KNXUltimate-config: Loaded saved GA values 37 [info] 8/16/2021, 2:08:31 PM KNXUltimate-config: Do DoInitialReadFromKNXBusOrFile 16 Aug 14:08:39 - [info] Stopping flows
The only thing not covered by a sudden disconnection, was the response sent from some node set to respond to read request. This is yet covered. Try this: knxUltimate-config.js.zip
How many nodes are set to "read on start"? 37 as i see in the log?
Hello Massimo How are you? Haven't heard from you for a long time.
We have the problem on two installations that very likely after a network interruption the connection is no longer established correctly. The nodes are all green, so they do not show any error. However, writing and reading does not work. The watchdog which writes to a group address recognizes the error. After a deploy, the connection works again.
Attached is the log from this morning, and the configuration of the interface.
We are using the KNX Ultimate 1.2.14, since then there seems to have been no releases that fix my problem.
Thanks for your help
watchdog_flows.txt 2021-08-11.log