No response to KNX telegramms after about 15 minutes. Status telegramms to KNX are still working #82
Comments
|
Hi, I tried to reproduce the issue but my devices are working for hours without that behaviour. So, we have to do some tests to find out what is going on with yours. Please, could you type on the console Do you have another sonoff device? So as to add also a device to device communication to see if the devices can continue with the communication when this happens? device to device could be: DEVICE 1: DEVICE 2: |
|
Hi,
|
|
ok, Up to now we know for sure that
So, the problem is in the communication wifi router <-> Tasmota. In your phone, please install a multicast tester app like this one:
And with this we can see the telegrams but over the wifi. Please, tell me, if when the "stop receiving" happens, if you can still see the KNX telegrams on the app. |
|
Hi, After disconnecting the mains from the Sonoff device its working again, you can see the response whats now? |
|
Hi, Thanks a lot for your patience and for all the tests. Please, let's try another firmware version. Now in releases there is the v5.13.1a with some bugs solved from Tasmota (not related to this issue). This is to test if the problem is related or not to lwIP 2.0. The last release is built with lwIP 1.4 due to better stability. |
|
Hi, |
|
Hi. Thanks again for the tests. I could not reproduce this issue with my devices, that's why all these tests to find out the root of the problem. The Tasmota's KNX driver uses the ESP-KNX-IP library. This library doesn't have a receive buffer/stack for the version compatible with the esp library 2.3. So there is no possible overflow. If it is processing a knx command and another arrives it will be in the multicast buffer. If another one arrives before the buffer is processed it will be ignored. A Tasmota device can process about 5 knx telegrams per second. I will build a firmware for you with esp library 2.4 and the esp-knx-ip optimized for this new library. This one has a reception stack. The problem with 2.4 esp library is that you can not use the sleep feature. It hungs the device. That's why the releases are being made with 2.3 until this bug on esp library is solved. The last 2.4.1 stills have problems. |
|
Hi, |
|
Hi, Now in releases there are the firmwares:
These have the latest libraries. please do not use sleep command. |
|
@ascillato |
|
Platform.io
El mié., 9 de may. de 2018 02:17, jeylites <notifications@github.com>
escribió:
… @ascillato <https://github.com/ascillato>
What compiler are you using?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#82 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ahw-h8Vo_wqLC-phxR2vW_VOOg0Wf2MFks5twnwBgaJpZM4TuP3N>
.
|
|
I’m starting to see a pattern. It seem very few people has got issues
compiling with Platform io
I going to try and to see it fixes the issue
On Wed, May 9, 2018 at 1:20 PM Adrian Scillato ***@***.***> wrote:
Platform.io
El mié., 9 de may. de 2018 02:17, jeylites ***@***.***>
escribió:
> @ascillato <https://github.com/ascillato>
> What compiler are you using?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <
#82 (comment)
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/Ahw-h8Vo_wqLC-phxR2vW_VOOg0Wf2MFks5twnwBgaJpZM4TuP3N
>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#82 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AIw6wDPmMrtLo8ARHcdup1NtwIGY56XNks5twnyXgaJpZM4TuP3N>
.
--
Sent from Iphone Mobile
|
|
I don't know. Here rocketscience is using the same firmware that I have on
my devices.
El mié., 9 de may. de 2018 02:23, jeylites <notifications@github.com>
escribió:
… I’m starting to see a pattern. It seem very few people has got issues
compiling with Platform io
I going to try and to see it fixes the issue
On Wed, May 9, 2018 at 1:20 PM Adrian Scillato ***@***.***>
wrote:
> Platform.io
>
> El mié., 9 de may. de 2018 02:17, jeylites ***@***.***>
> escribió:
>
> > @ascillato <https://github.com/ascillato>
> > What compiler are you using?
> >
> > —
> > You are receiving this because you were mentioned.
> > Reply to this email directly, view it on GitHub
> > <
>
#82 (comment)
> >,
> > or mute the thread
> > <
>
https://github.com/notifications/unsubscribe-auth/Ahw-h8Vo_wqLC-phxR2vW_VOOg0Wf2MFks5twnwBgaJpZM4TuP3N
> >
> > .
> >
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <
#82 (comment)
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AIw6wDPmMrtLo8ARHcdup1NtwIGY56XNks5twnyXgaJpZM4TuP3N
>
> .
>
--
Sent from Iphone Mobile
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#82 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ahw-h5SMhBYRWQDU2lSH7raWK2sfkFMhks5twn1CgaJpZM4TuP3N>
.
|
|
Sorry for the late feedback. |
|
if you type status 0 on the console, can you see: 19:13:20 RSL: STATUS2 = {"StatusFWR":{"Version":"5.13.1a","BuildDateTime":"2018-05-07T22:06:01","Boot":31,"Core":"2_4_1","SDK":"2.2.1(cfd48f3)"}} |
|
Hi, |
|
mmmm, this issue is hard. I can not reproduce it at home, and the new firmware you have is using a totally different multicast routines. do you have access to the serial connection of the device? because the esp-knx-ip library has a debug info that can be activated (on compilation time) that outputs to the serial interface. to see if the ESP8266 is seeing the KNX telegrams. If you dont have access, I will have to add those debug routines to tasmota to display on the console. |
|
i think i have accesss to ther serial connection, i would try this. |
|
Great!!! I have added to the releases page the firmware files:
These ones are the same than sonoff_KNX-EN and sonoff_KNX-DE but with Debug information over serial. Please, on the console, type the command Thanks |
|
Hi, LEN: 17 LEN: 17 LEN: 17 LEN: 19 ` |
ascillato
added
bug
|
Hi I think I found the problem ! 😄 I could reproduce this issue. If the sonoff device get disconnected from the wifi router, when reconnecting to the same router it loose the multicast connection for receiving packets. That's why a reboot solve the issue because on boot it opens again the UDP. I will release a patch for this. So, The issue was not related to esp lib versions, configurations nor compilation. For the disconnection tests, I just unplug my wifi router and plug it again. So, then with the patched version you should not have problems, but you should look why you have those micro-disconnections from your router ( may be too many wifi devices ? ) There is a very interesting and technical video about wifi routers installation by davidelang at https://www.usenix.org/conference/lisa12/technical-sessions/presentation/lang_david_wireless |
|
Thanks a lot again for all the tests you made. Thanks to all your help was possible to find the root of the problem. 👍 |
|
Hi, On releases page were updated all the firmwares with this bug fixed. Please, check it. Thanks! |
|
Hi,
|
|
ups... sorry. uploaded wrong file. Fixed and updated files on release page. Now, when there is a reconnection you will see KNX Start on the console. |
|
Hi, 10:59:05 KNX: Received from 7.5.70 Befehl Write: 1 zu Relay 1 |
|
The serial log disabled message is always there. Now you see it because you have Let's try this. I added the KNX_START routine that register on the router the multicast channel to receive, also on the SAVE KNX SETTINGS Button. Please, when the disconnection happens, go to KNX Menu and press save. After that try again to see if it receives telegrams. (everything without reboot) If this works, we just need to find a way to make tasmota realize of this micro-disconnections to re-establish the UDP channel. The new firmware for this testing is sonoff_KNX-DE_TEST.bin |
|
Hi, Do you have access to your wifi router configuration? The configuration that is working fine for me is:
Note the Multicast: IGMP v3 |
|
This multicast disconnection seems to be a problem on the ESP8266 Libraries as explained on esp8266/Arduino#1165. So, the ESP8266 library have problems with some routers if IGMP snoop is enabled. That explains why I can not reproduce this issue, and you can. We tested the v2.3.0 and also v2.4.1 with lwIP 1.4 and 2.0 and all the time the fail is the same. Let's try:
|
|
Hi, I optimized the settings in the Fritzbox according to this site https://avm.de/service/fritzbox/fritzbox-7390/wissensdatenbank/publication/show/592_Stoerungen-beim-Fernsehen-ueber-IPTV-Anschluss/ If i disable the optimizing for IPTV (witch is IGMP-Snoop ON i think) the sonoff responses get very slow and most of the KNX-Telegrams to the sonoff get lost. I think the esp should handle these disconnections, as they always can occour. Actualy i think i better use the mqtt- or http-way and not the direct way over multicast, since this is not working stable in my hardware-setup This is my network config: Now: |
mmm, very weird. The routine behind KNX: Start opens a new socket for multicast reception, meaning that it joins again the multicast group for the KNX IP:PORT Address. So, the repeater and the esp are not understanding each other. If you connects direct to the Fritzbox, the "stop receiving" still happens? Sometimes the WLAN Repeaters have problems with some devices only. In your case your phone did not loose the multicast channel but the ESP does. It is known that the ESP has some issues with some routers/repeaters but the libraries are still on development to solve those.
Agree, but we reach an issue beyond Tasmota KNX Driver and beyond Tasmota project. It is on ESP8266 Wifi Libraries. I think, you should post this issue on https://github.com/esp8266/Arduino because it is a problem with IGMP handshake between ESP and your Repeater in particular.
Using MQTT you have a direct TCP connection that it is more reliable than multicast, and you can add also a home automation system like Home Assistant. Future Ideas: |
|
Well, with all this, we found and fix a bug that when a reset to the wifi router occurs, the KNX needs to reconnect. Thanks 👍 But we could not solve the issue between your wifi repeater and the ESP IGMP handshake. Sorry. |
ascillato
added
Fixed
|
Closing the Issue. I'm willing to help if you want to come again to use KNX when the reliability improvement is finished. Again, Thanks a lot for your help! 👍 |
|
Hi. Please take a look to issue 2643 from arendst/Sonoff-Tasmota. That was a very similar issue than this and the problem was the device acting as repeater. Could you test if connecting Tasmota direct to your main router the issue resolves? Thanks |
I am using an Enertex KNX router.
It does not matter from witch source the telegramms to the sonoff are comming, i used also an USB-KNX Interface.
After resetting the sonoff, its working (receiving) again for about 15minutes, after that only one direction ist working (sonoff -> knx).
Update:
sometimes its receiving again (without reset) for some minutes.
Sonoff Basic, Enertex KNX router, EDOMI
status 018:25:37 CMD: status 0 18:25:37 RSL: STATUS = {"Status":{"Module":1,"FriendlyName":["Sonoff"],"Topic":"sonoff","ButtonTopic":"0","Power":1,"PowerOnState":3,"LedState":1,"SaveData":1,"SaveState":1,"ButtonRetain":0,"PowerRetain":0}} 18:25:37 RSL: STATUS1 = {"StatusPRM":{"Baudrate":115200,"GroupTopic":"sonoffs","OtaUrl":"http://sonoff.maddox.co.uk/tasmota/sonoff.ino.bin","RestartReason":"Software/System restart","Uptime":"0T00:53:51","StartupUTC":"2018-05-01T16:31:46","Sleep":0,"BootCount":6,"SaveCount":97,"SaveAddress":"FB000"}} 18:25:37 RSL: STATUS2 = {"StatusFWR":{"Version":"5.13.0","BuildDateTime":"2018.05.01 06:01:14","Boot":31,"Core":"2_3_0","SDK":"1.5.3(aec24ac9)"}} 18:25:37 RSL: STATUS3 = {"StatusLOG":{"SerialLog":2,"WebLog":2,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["xxxxx",""],"TelePeriod":300,"SetOption":["02008001","55818000"]}} 18:25:37 RSL: STATUS4 = {"StatusMEM":{"ProgramSize":521,"Free":480,"Heap":16,"ProgramFlashSize":1024,"FlashSize":1024,"FlashMode":3}} 18:25:37 RSL: STATUS5 = {"StatusNET":{"Hostname":"SONOFF_001","IPAddress":"192.168.0.33","Gateway":"192.168.0.253","Subnetmask":"255.255.255.0","DNSServer":"192.168.0.253","Mac":"EC:FA:BC:10:56:38","Webserver":2,"WifiConfig":3}} 18:25:37 RSL: STATUS7 = {"StatusTIM":{"UTC":"Tue May 01 17:25:37 2018","Local":"Tue May 01 18:25:37 2018","StartDST":"Sun Mar 25 02:00:00 2018","EndDST":"Sun Oct 28 03:00:00 2018","Timezone":1,"Sunrise":"05:29","Sunset":"20:05"}} 18:25:37 RSL: STATUS10 = {"StatusSNS":{"Time":"2018-05-01T18:25:37"}} 18:25:37 RSL: STATUS11 = {"StatusSTS":{"Time":"2018-05-01T18:25:37","Uptime":"0T00:53:51","Vcc":3.161,"POWER":"ON","Wifi":{"AP":1,"SSId":"xxxx","RSSI":68,"APMac":"9C:C7:A6:49:BB:31"}}} 18:27:55 RSL: STATE = {"Time":"2018-05-01T18:27:55","Uptime":"0T00:56:09","Vcc":3.162,"POWER":"ON","Wifi":{"AP":1,"SSId":"CyberdyneSystems","RSSI":62,"APMac":"9C:C7:A6:49:BB:31"}}`
The text was updated successfully, but these errors were encountered: