Failed reconnection with KNX after reload

2 years ago in Devices / KNX • updated 2 years ago • 2

Hello everyone.

I know there are already posts about it, but I don't see a problem similar to the one I currently have in any of them.

I have a Jigsaw connected to KNX by bus cable.

The problem is that sometimes due to power outages the Jigsaw and the KNX bus go down and not always but on certain occasions when both systems are up. the Jigsaw is not capable of lifting the link with KNX indefinitely and the only solution that can be applied is to restart the Jigsaw and at that moment it raises the link between both systems again.

Is there any way through a program, task or function that allows forcing to deactivate and reactivate the knx connection when it detects that the link is down? Or failing that, to be able to send some kind of Jigsaw restart through some function that “wakes up” the connection with KNX?

Thank you

Vote

Replies 2
Oldest first
- Newest first
- Oldest first

2 years ago

Hello,

Never heard of any problems regarding Jigsaw not booting up the KNX connection.

- Do you you have your Jigasaw updated? And have you performed the System Update?

- Are you using the Jigsaw internal BUS connection, or using an external KNX IP device?

As for reactivating the KNX connection, I don't think that's possible at the moment, at least as far as I've searched.

What you can do, is create a task, to trigger an e-mail for example, every time the system goes up (Building > Started > Equals = True > Allow Retrigger), to notify you of the reboot. At least you would be notified. I'd probably would set a delay on the task, just to be sure that the Jigsaw settles down before sending the e-mail.

As for the BUS not starting after a reboot, I confess that I've installed some dozens of Jigsaws and Grinders, and never had this issue.

Please confirm what firmware you are using, and if you also updated the system (Building > System > System Update > Update).

Software version (stable) is currently on 4.9.14

System version is currently on v3.

Best regards

2 years ago

Thanks for your response Ricardo.

I can tell you that it is not usual and as I already told you, the workaround that we apply is the reset of the equipment itself since it usually raises the interface. But I can tell you that I have already seen it in two different Jigsaws connected through the internal bus, so it does not apply IP network problems.

In both I have seen the status KNX > Connected > False and the message in the log every time a change is sent to a group address is this.

Devices : 08/08/2022 9:40:11 : Error : Tasks\Escenarios\3-Apertura Estandar\3-Apertura Estandar N1 : Error setting value Devices\KNX\Alumbrado\LOC 2 On/Off SAS 1 Interior.Value. Exception has been thrown by the target of an invocation. at System.Reflection.RuntimeMethodInfo.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object parameters, System.Globalization.CultureInfo culture) 0x0009a in <12b418a7818c4ca0893feeaaf67f1e7f>:0

at System.Reflection.RuntimePropertyInfo.SetValue (System.Object obj, System.Object value, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object index, System.Globalization.CultureInfo culture) 0x0006a in <12b418a7818c4ca0893feeaaf67f1e7f>:0

at System.Reflection.PropertyInfo.SetValue (System.Object obj, System.Object value, System.Object index) 0x00000 in <12b418a7818c4ca0893feeaaf67f1e7f>:0

at System.Reflection.PropertyInfo.SetValue (System.Object obj, System.Object value) 0x00000 in <12b418a7818c4ca0893feeaaf67f1e7f>:0

at BOSCommon.Node.Attributes.NodeValueData.SetValue (System.Object value) 0x00025 in <ace73a5194a84c5f857a3df5586be704>:0

at BOSCommon.Node.Common.NodeHost.SetValue (System.String name, System.Object value) 0x00079 in <ace73a5194a84c5f857a3df5586be704>:0

at BOSCommon.References.ValueReference.set_Value (System.Object value) 0x00012 in <ace73a5194a84c5f857a3df5586be704>:0

I don't know if someone from the Comfortclick Team can tell you something

The only thing that remains to be seen is whether at startup the value in KNX > Connection Type has changed, leaving the connection down, but when resetting the client I have lost the possibility of checking this data. In the first one that I saw the problem was a residential installation and there was no problem, but in this second one it is a shopping center and the availability must be continuous.

The solution that you have proposed to me was already implemented by mail and push message. Thanks anyway for the idea.

Customer support service by UserEcho