No reaction to KNX commands after x days #22242

rolandunterholzer · 2024-10-06T09:10:57Z

PROBLEM DESCRIPTION

When using Shelly Plus 1PM with Tasmota 14.2.0.6 (6fa38e4-solo1) there is no reaction to KNX command after some days. After restarting the device via Web-Interface everything is working again.

REQUESTED INFORMATION

Make sure your have performed every step and checked the applicable boxes before submitting your issue. Thank you!

  Configuration output here:
11:06:03.390 MQT: stat/TasmotaFlurNord/RESULT = {"NAME":"Shelly Plus 1PM","GPIO":[0,0,0,0,192,2720,0,0,0,0,0,0,0,0,2656,0,0,0,0,2624,0,32,224,0,0,0,0,0,4736,0,0,0,0,0,0,0],"FLAG":0,"BASE":1}
11:06:03.613 MQT: stat/TasmotaFlurNord/RESULT = {"Module":{"0":"Shelly Plus 1PM"}}
11:06:03.823 MQT: stat/TasmotaFlurNord/RESULT = {"GPIO0":{"0":"None"},"GPIO1":{"0":"None"},"GPIO2":{"0":"None"},"GPIO3":{"0":"None"},"GPIO4":{"192":"Switch_n1"},"GPIO5":{"2720":"BL0937 CF"},"GPIO6":{"0":"None"},"GPIO7":{"0":"None"},"GPIO8":{"0":"None"},"GPIO9":{"0":"None"},"GPIO10":{"0":"None"},"GPIO11":{"0":"None"},"GPIO12":{"0":"None"},"GPIO13":{"0":"None"},"GPIO14":{"0":"None"},"GPIO15":{"0":"None"},"GPIO16":{"0":"None"},"GPIO17":{"0":"None"},"GPIO18":{"2656":"HLWBL CF1"},"GPIO19":{"0":"None"},"GPIO20":{"0":"None"},"GPIO21":{"0":"None"},"GPIO22":{"0":"None"},"GPIO23":{"2624":"HLWBL SEL_i"},"GPIO24":{"0":"None"},"GPIO25":{"32":"Button1"},"GPIO26":{"224":"Relay1"},"GPIO27":{"0":"None"},"GPIO32":{"4736":"ADC Temp1"},"GPIO33":{"0":"None"},"GPIO34":{"0":"None"},"GPIO35":{"0":"None"},"GPIO36":{"0":"None"},"GPIO37":{"0":"None"},"GPIO38":{"0":"None"},"GPIO39":{"0":"None"}}

If using rules, provide the output of this command: Backlog Rule1; Rule2; Rule3:

  Rules output here:

Provide the output of this command: Status 0:

  STATUS 0 output here:
11:07:00.564 MQT: stat/TasmotaFlurNord/STATUS = {"Status":{"Module":0,"DeviceName":"TasmotaFlurNord","FriendlyName":["TasmotaFlurNord"],"Topic":"TasmotaFlurNord","ButtonTopic":"0","Power":"1","PowerLock":"0","PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":0,"SaveState":1,"SwitchTopic":"0","SwitchMode":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":0,"SensorRetain":0,"PowerRetain":0,"InfoRetain":0,"StateRetain":0,"StatusRetain":0}}
11:07:00.627 MQT: stat/TasmotaFlurNord/STATUS1 = {"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"https://ota.tasmota.com/tasmota32/tasmota32solo1.bin","RestartReason":"Software reset CPU","Uptime":"0T00:10:25","StartupUTC":"2024-10-06T08:56:35","Sleep":50,"CfgHolder":4617,"BootCount":18,"BCResetTime":"2024-09-15T09:12:05","SaveCount":79}}
11:07:00.676 MQT: stat/TasmotaFlurNord/STATUS2 = {"StatusFWR":{"Version":"14.2.0.6(6fa38e4-solo1)single-core","BuildDateTime":"2024-09-30T09:26:03","Core":"3_1_0","SDK":"5.3.1.240924","CpuFrequency":240,"Hardware":"ESP32-U4WDH-D v3.1","CR":"462/699"}}
11:07:00.710 MQT: stat/TasmotaFlurNord/STATUS3 = {"StatusLOG":{"SerialLog":2,"WebLog":2,"MqttLog":0,"SysLog":4,"LogHost":"10.0.0.125","LogPort":1517,"SSId":["UNTERHOLZER",""],"TelePeriod":300,"Resolution":"558580C0","SetOption":["02008009","2805C80001000600003C5A0A192800000000","00000088","00006000","00004000","00000000"]}}
11:07:00.757 MQT: stat/TasmotaFlurNord/STATUS4 = {"StatusMEM":{"ProgramSize":1960,"Free":791,"Heap":150,"StackLowMark":3,"PsrMax":0,"PsrFree":0,"ProgramFlashSize":4096,"FlashSize":4096,"FlashChipId":"164020","FlashFrequency":80,"FlashMode":"DIO","Features":["0809","9F9AD7DF","0015A001","B7F7BFCF","05DA9BC4","E0360DC7","480840D2","20200000","D4BC482D","810A80B1","00000014"],"Drivers":"1,2,3,!4,!5,7,!8,9,10,11,12,!14,!16,!17,!20,!21,!24,26,!27,29,!34,!35,38,50,52,!59,!60,62,!63,!66,!67,!68,!73,82,!86,!87,!88,!121","Sensors":"1,2,3,5,6,7,8,9,10,11,12,13,14,15,17,18,19,20,21,22,26,31,34,37,39,40,42,43,45,51,52,55,56,58,59,64,66,67,74,85,92,95,98,103,105,109,127","I2CDriver":"7,8,9,10,11,12,13,14,15,17,18,20,24,29,31,36,41,42,44,46,48,58,62,65,69,76,77,82,89"}}
11:07:00.842 MQT: stat/TasmotaFlurNord/STATUS5 = {"StatusNET":{"Hostname":"TasmotaFlurNord","IPAddress":"10.0.0.13","Gateway":"10.0.0.254","Subnetmask":"255.255.255.0","DNSServer1":"10.0.0.110","DNSServer2":"10.0.0.111","Mac":"FC:B4:67:27:94:74","IP6Global":"","IP6Local":"fe80::feb4:67ff:fe27:9474%st1","Ethernet":{"Hostname":"","IPAddress":"0.0.0.0","Gateway":"0.0.0.0","Subnetmask":"0.0.0.0","DNSServer1":"10.0.0.110","DNSServer2":"10.0.0.111","Mac":"00:00:00:00:00:00","IP6Global":"","IP6Local":""},"Webserver":2,"HTTP_API":1,"WifiConfig":4,"WifiPower":17.0}}
11:07:00.901 MQT: stat/TasmotaFlurNord/STATUS6 = {"StatusMQT":{"MqttHost":"10.0.0.124","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_279474","MqttUser":"DVES_USER","MqttCount":1,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30,"SOCKET_TIMEOUT":4}}
11:07:00.938 MQT: stat/TasmotaFlurNord/STATUS7 = {"StatusTIM":{"UTC":"2024-10-06T09:07:00Z","Local":"2024-10-06T11:07:00","StartDST":"2024-03-31T02:00:00","EndDST":"2024-10-27T03:00:00","Timezone":99,"Sunrise":"07:58","Sunset":"19:17"}}
11:07:00.963 MQT: stat/TasmotaFlurNord/STATUS9 = {"StatusPTH":{"PowerDelta":0,"PowerLow":0,"PowerHigh":0,"VoltageLow":0,"VoltageHigh":0,"CurrentLow":0,"CurrentHigh":0,"MaxPower":0,"MaxPowerHold":10,"MaxPowerWindow":30,"MaxEnergy":0,"MaxEnergyStart":0}}
11:07:01.005 MQT: stat/TasmotaFlurNord/STATUS10 = {"StatusSNS":{"Time":"2024-10-06T11:07:00","Switch1":"OFF","ANALOG":{"Temperature1":41.6},"ENERGY":{"TotalStartTime":"2024-09-15T09:18:09","Total":0.015,"Yesterday":0.000,"Today":0.000,"Power":0,"ApparentPower":0,"ReactivePower":0,"Factor":0.00,"Voltage":228.40,"Current":0.000},"TempUnit":"C"}}
11:07:01.044 MQT: stat/TasmotaFlurNord/STATUS11 = {"StatusSTS":{"Time":"2024-10-06T11:07:01","Uptime":"0T00:10:26","UptimeSec":626,"Heap":148,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Berry":{"HeapUsed":23,"Objects":306},"POWER":"ON","Wifi":{"AP":1,"SSId":"UNTERHOLZER","BSSId":"54:4A:00:BF:C8:50","Channel":13,"Mode":"HT40","RSSI":48,"Signal":-76,"LinkCount":1,"Downtime":"0T00:00:03"}}}

Set weblog to 4 and then, when you experience your issue, provide the output of the Console log:

  Console output here:

TO REPRODUCE

Steps to reproduce the behavior:

Restart device
Wait some days (3-7)
Send KNX write to the defined "Group Addresses to Receive Data from"
The device does not toggle the output

EXPECTED BEHAVIOUR

A clear and concise description of what you expected to happen.
After receiving KNX write on the defined "Group Addresses to Receive Data from" the output should toggle to ON/OFF regarding the KNX write command

SCREENSHOTS

If applicable, add screenshots to help explain your problem.

ADDITIONAL CONTEXT

Add any other context about the problem here.

(Please, remember to close the issue when the problem has been addressed)

The text was updated successfully, but these errors were encountered:

Noschvie · 2024-10-07T08:55:16Z

What does the KNX configuration look like?

rolandunterholzer · 2024-10-07T10:49:22Z

Is there a possibility to debug KNX in detail at the Tasmota Device? With logLevel 4 activated I can't see any info that a KNX packet was received when the device is in the state of not acting to the messages.
After a restart it looks fine:

barbudor · 2024-10-07T19:36:30Z

With logLevel 4 activated I can't see any info that a KNX packet was received

At 13:08:04.633 you have a sample log for a incoming KNX packet

when the device is in the state of not acting to the messages

I don't understand that part of your message

May be you could run Wireshark on a computer to track all KNX packets on the network

rolandunterholzer · 2024-10-10T08:37:16Z

With logLevel 4 activated I can't see any info that a KNX packet was received

At 13:08:04.633 you have a sample log for a incoming KNX packet

please read carefully:

when the device is in the state of not acting to the messages

I don't understand that part of your message

May be you could run Wireshark on a computer to track all KNX packets on the network

In other words: after some days the device stops toggling the output in regards of the KNX packets sent

I think Wireshark would not help here because:
a) I can see the KNX packets within ETS GroupMonitor
b) After a restart of the device, the KNX packets are handled as supposed => the only thing that changes in my environemt with a restart of device is the device/runstate itself

bmpalmeida · 2024-10-21T23:46:43Z

I'm having a very similar problem, same device but with matter, after one day working properly it become not responding in Apple Home App. Reboot via web interface fixes it temporarily.

Noschvie · 2024-10-27T11:02:54Z

I have now started a test with an "Athom LB017W" that visualizes the status of a KNX status address. This means that a KNX address was linked to “Output 1”. This KNX status address will be triggerd by an KNX actor (Light in the staircase).

Noschvie · 2024-11-01T19:27:04Z

My test with the "Athom LB017W" running Tasmota 14.3.0 (release-knx) is working and has Uptime 5T08:46:41

rolandunterholzer · 2024-11-02T08:14:14Z

If I'm not wrong your device has an ESP8266 chip whereas the Shelly has an ESP32. So the releases are different.
I have other devices with the ESP8266 release that work without any problems.
So wether it is the ESP32 release or the shelly device itself...

Noschvie · 2024-11-02T09:52:10Z

Can also use a Shelly Plus 1 or Shelly 1 Mini Gen3 for testing, which do you prefer?

rolandunterholzer · 2024-11-06T14:43:33Z

If Shelly Plus 1 is also based on ESP32? --> please test that on. Thank You

Noschvie · 2024-11-07T06:16:55Z

Started the test with an "Athom Plug V3" / ESP32-C3 v0.4 running v 14.3.0 on Tuesday.

Noschvie · 2024-11-08T17:45:54Z

This issue can be reproduced with the "Athom Plug V3" / ESP32-C3.
The KNX: Received from 1/4/47 Command Write: 1 to Output 1 message is missing in the log.

rolandunterholzer · 2024-11-11T14:22:55Z

Currently as a workaround I restart the Shelly Plus 1PM every day by rule on 03:00. Will this somehow harm the device?

{"Rule1":{"State":"ON","Once":"OFF","StopOnError":"OFF","Length":35,"Free":476,"Rules":"on clock#timer=1 do restart 1 endon"}}

github-actions · 2024-12-06T14:37:27Z

This issue has been automatically marked as stale because it hasn't any activity in last few weeks. It will be closed if no further activity occurs. Thank you for your contributions.

arendst · 2024-12-06T14:41:53Z

Revive.

arendst · 2024-12-06T14:50:37Z

I'm currently testing this. I had a lot of trouble to get KNX going in the first place.

Finally, after disabling AP IGMP Snooping I managed to receive some commands. Alas after ten minutes that stopped working. I just disabled Wireless Meshing hoping to fix the issue.

Continue testing.....

arendst · 2024-12-06T16:42:40Z

Haven't seen the issue yet but in the meantime I extended command Knx_Enabled with the option to restart UDP multicast if KNX is re-enabled.

So in case of not receiving KNX commands anymore, instead of a restart, try this:

knx_enabled 0
knx_enabled 1

If it solves the connection problem pls let me know.

Noschvie · 2024-12-07T09:45:50Z

@arendst Hello Theo
updated the "Athom Plug V3" / ESP32-C3 with latest dev version yesterday and it works in sync with the "Athom LB017W" running Tasmota 14.3.0 (release-knx) for a few hours.
This morning I used

knx_enabled 0
knx_enabled 1

and it solves the connection problem for the moment.

arendst · 2024-12-07T10:29:28Z

Thx for the feedback. Finding the cause will be difficult.

arendst · 2024-12-07T11:39:25Z

Pls try latest dev. This adds an udp.flush() fixing possible miscommunications.

Noschvie · 2024-12-07T21:16:24Z

same behavior as before,

knx_enabled 0
knx_enabled 1

is needed to retrigger the communication.

arendst · 2024-12-07T21:53:38Z

Bugger.

As I cannot reproduce (other than that my ubiquiti system refuses to perform multicast most of the time) I suggest you use a rule to regularly perfrom the above commands until someone finds the root cause of this.

BTW it would be great if we could rule out either ESP8266 or ESP32.

Noschvie · 2024-12-08T17:32:45Z

After

knx_enabled 0
knx_enabled 1

was executed once at the "Athom Plug V3" / ESP32-C3 yesterday, the communication seems to have been working since then.

arendst · 2024-12-09T14:19:23Z

@Noschvie pls keep me posted when it fails again.

Noschvie · 2024-12-12T06:16:12Z

the "Athom Plug V3" / ESP32-C3 was working just before update to 14.4.0
Executing

knx_enabled 0
knx_enabled 1

and it‘s working again.

github-actions bot added the stale Action - Issue left behind - Used by the BOT to call for attention label Dec 6, 2024

arendst self-assigned this Dec 6, 2024

arendst added Requires more research (devs) Action - Issue requires more research and removed stale Action - Issue left behind - Used by the BOT to call for attention labels Dec 6, 2024

arendst added a commit that referenced this issue Dec 6, 2024

Extent command Knx_Enabled with KNX restart functionality (#22242)

789bbb8

arendst added a commit that referenced this issue Dec 7, 2024

Add udp.flush() to KNX receiver (#22242)

3a62cc6

arendst removed the Requires more research (devs) Action - Issue requires more research label Dec 16, 2024

Noschvie mentioned this issue Dec 25, 2024

KNX reception of telegrams no longer works 14.4.x #22714

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

No reaction to KNX commands after x days #22242

No reaction to KNX commands after x days #22242

rolandunterholzer commented Oct 6, 2024 •

edited

Loading

Noschvie commented Oct 7, 2024

rolandunterholzer commented Oct 7, 2024 •

edited

Loading

barbudor commented Oct 7, 2024

rolandunterholzer commented Oct 10, 2024 •

edited

Loading

bmpalmeida commented Oct 21, 2024

Noschvie commented Oct 27, 2024

Noschvie commented Nov 1, 2024 •

edited

Loading

rolandunterholzer commented Nov 2, 2024

Noschvie commented Nov 2, 2024

rolandunterholzer commented Nov 6, 2024

Noschvie commented Nov 7, 2024

Noschvie commented Nov 8, 2024

rolandunterholzer commented Nov 11, 2024

github-actions bot commented Dec 6, 2024

arendst commented Dec 6, 2024

arendst commented Dec 6, 2024

arendst commented Dec 6, 2024

Noschvie commented Dec 7, 2024

arendst commented Dec 7, 2024

arendst commented Dec 7, 2024

Noschvie commented Dec 7, 2024 •

edited

Loading

arendst commented Dec 7, 2024

Noschvie commented Dec 8, 2024

arendst commented Dec 9, 2024

Noschvie commented Dec 12, 2024

No reaction to KNX commands after x days #22242

No reaction to KNX commands after x days #22242

Comments

rolandunterholzer commented Oct 6, 2024 • edited Loading

PROBLEM DESCRIPTION

REQUESTED INFORMATION

TO REPRODUCE

EXPECTED BEHAVIOUR

SCREENSHOTS

ADDITIONAL CONTEXT

Noschvie commented Oct 7, 2024

rolandunterholzer commented Oct 7, 2024 • edited Loading

barbudor commented Oct 7, 2024

rolandunterholzer commented Oct 10, 2024 • edited Loading

bmpalmeida commented Oct 21, 2024

Noschvie commented Oct 27, 2024

Noschvie commented Nov 1, 2024 • edited Loading

rolandunterholzer commented Nov 2, 2024

Noschvie commented Nov 2, 2024

rolandunterholzer commented Nov 6, 2024

Noschvie commented Nov 7, 2024

Noschvie commented Nov 8, 2024

rolandunterholzer commented Nov 11, 2024

github-actions bot commented Dec 6, 2024

arendst commented Dec 6, 2024

arendst commented Dec 6, 2024

arendst commented Dec 6, 2024

Noschvie commented Dec 7, 2024

arendst commented Dec 7, 2024

arendst commented Dec 7, 2024

Noschvie commented Dec 7, 2024 • edited Loading

arendst commented Dec 7, 2024

Noschvie commented Dec 8, 2024

arendst commented Dec 9, 2024

Noschvie commented Dec 12, 2024

rolandunterholzer commented Oct 6, 2024 •

edited

Loading

rolandunterholzer commented Oct 7, 2024 •

edited

Loading

rolandunterholzer commented Oct 10, 2024 •

edited

Loading

Noschvie commented Nov 1, 2024 •

edited

Loading

Noschvie commented Dec 7, 2024 •

edited

Loading