Wiser for KNX (LSS100100). Error connecting via Wiser KNX app

[Andrii90x]

Hello. I use Wiser for KNX (LSS100100) and Wiser KNX app on iPhone. When i try to connect to Wiser for KNX thought  Wiser KNX app i have a warning "Something went wrong while initializing the appication. The controller seems to be offline." and there is also the ability to choose further action "Try again", "Ignore" or "Logout". The connection will not be successfully whatever i choose. This has been going on for a day already. The result is the same when I try to make connection through another iPhone. The internet connection is ok. Moreover I can connect to Wiser for KNX (LSS100100) using WEB interface and i see that it works normally and i can operate it. Of course i can restart the device and everything can be normal again, but in this case i will not actually know what was the problem and it can happen again. You can see the warning and some pictures from WEB interface in the attached pictures. Can someone help me?

[Erwin-vd-Zwart]

@Andrii90x 

Did it ever worked or is this a new setup?

Some first steps:

Check the DNS and default GW,

Make sure you have create a Touch Visu with (app compatible) control items that needs to be showed in the app.

Make sure that all apps are updated currently -> Automations v1.0.2, Cloud connector v1.12.2,  KNX IoT 3rd Party API v1.31.4 and Touch 3 v3.17.3

Check on those apps the "update automatically" flag to be sure they are always up to date in the future.

[Andrii90x]

It looks like you answered me in logic machine forum... now i will write you here 🙃

"Did it ever worked or is this a new setup?" - it has been working for a long period of time, but now it doesn't work.

"Make sure you have create a Touch Visu with (app compatible) control items that needs to be showed in the app." - i did it and it worked before.

I checked everything written above, but it still doesn't work.

[Andrii90x]

we restarted the controlled and now it works normally... but we still don't know what was the cause of this problem 

[Erwin-vd-Zwart]

@Andrii90x 

Yes i contribute to the forum as many W4K/SL users asking questions there, this is the place where you need to be for SE..

No idea what it could have been, never heared an issue like that, i use it myself privately for quite a while (as pre production tester) and works all the time..

Good that it's solved for now..

[FZetina]

Hi

This error is normally shown when there is a communication between the controller, cloud and app. In many cases, when the controller, for some reason, is performing some actions that overload the processor, it causes this. After rebooting the controller, the issue goes away. If the issue comes back again is good to check in more detail what could be causing this (loops in the telegrams, multiple scripts, etc.

[Andrii90x]

Thank you for the answer.

[geir_eas_no_bfo]

Hi,

I have the same problem regulary/ very often.

You need to restart the app, when this accoures. 

It happens almosty every time when you try to open Wiser for KNX and when it has been "a sleep" on the iphone. 

(Must put in a notice that my controller is in a "bad" condition regarding "overload" on KNX bus-->because of the wiser zigbee gateway)

BR 

GIA

[Erwin-vd-Zwart]

Don’t use normal objects for Zigbee mapping when there is nothing that acknowledges the updates (aka when only used for visu or script) , only use normal objects when there is a receiving KNX device on the same address, this way the acknowledgement is being sent by the KNX recipient device.

[geir_eas_no_bfo]

ohh, okay. Tanx! 

I did not know. 

Is that mensioned in the manual? 

BR

GIA

[Erwin-vd-Zwart]

@geir_eas_no_bfo 

No as it has nothing to do with the device itself, this is basic KNX behavior, when sending a telegram on the KNX bus that is not acknowledged by a device/object, the telegram is repeated 3 times (or less when acknowleged), so if you setup a KNX system you have to take this always into account, this counts for any value that is published on the bus regardless of the origin (KNX/Modbus/Bacnet/Zigbee/TCP-IP etc), what counts is the KNX telegram that is send on the bus MUST to be acknowledged by something, if ACK is not received it will always be repeated x times.. 

When for example you have a pushbutton sending to a GA that holds no receiving object, this telegram is also repeated 3 times as it won't be acknowledged by a actuator that normally receives this telegram.. 

Snippet from the KNX protocol document:

[geir_eas_no_bfo]

Okay, tanx Erwin!

It makes sense when you point out this😮

Now I know the different between normal vs virtual grup objects. Did not think of that! SO Virtual gruop objects is the way then👌

Unfortently selv learned in the WiserKNX world. 

BR

GIA

[Andrii90x]

Can the error in the picture below be a reason of the communication error which we are talking about (i see it when i power up (restart) the device)? And i don't know what this error mean, because i haven't got a script called "apit3".

[esteve_budia]

Take a look at traffic lights to be sure everything it's ok...