search

arendst / Tasmota

Alternative firmware for ESP8266 and ESP32 based devices with easy configuration using webUI, OTA updates, automation using timers or rules, expandability and entirely local control over MQTT, HTTP, Serial or KNX. Full documentation at
https://tasmota.github.io/docs
GNU General Public License v3.0
22.26k stars 4.81k forks source link

Rel. 14.3 KNX: scenes are no longer working #22405

Open clkempe opened 3 weeks ago

clkempe commented 3 weeks ago

Since Version 14.3 scenes are no longer processed by the device.

Here the protocol of a 14.3 device: 08:49:44.814 KNX: Received from 0/0/14 Command Write: 0.00 to KNX RX 6 08:49:44.820 RSL: RESULT = {"Event":"Done"} 08:50:10.258 KNX: Received from 0/0/14 Command Write: 0.00 to KNX RX 6 08:50:10.264 RSL: RESULT = {"Event":"Done"}

Here the protocol of a 14.2 device (same scene events): 08:49:45.473 KNX: Received from 0/0/14 Command Write: 31 to KNX SCENE RX 08:49:45.478 RSL: RESULT = {"Event":"Done"} 08:49:45.507 RUL: EVENT#KNX_SCENE=31 performs 'Power1 0' 08:49:45.513 KNX: Output 1 = 0 sent to 0/6/25 08:49:45.515 RSL: RESULT = {"POWER":"OFF"} 08:49:45.517 RSL: POWER = OFF 08:50:10.912 KNX: Received from 0/0/14 Command Write: 29 to KNX SCENE RX 08:50:10.917 RSL: RESULT = {"Event":"Done"} 08:50:10.938 RUL: EVENT#KNX_SCENE=29 performs 'Power1 1' 08:50:10.943 KNX: Output 1 = 1 sent to 0/6/25 08:50:10.946 RSL: RESULT = {"POWER":"ON"} 08:50:10.948 RSL: POWER = ON

After a downgrade to 14.2 it works again.

Edit: found the reason. Up to tasmota 14.2 these options can be chosen: grafik

in 14.3 these: grafik

So, the entry "KNX SCENE RX" has been moved; at the former position there is now "KNX RX6". Before changing the configuration of all my devices: is there any reason for this change? And if, isn´t it better to keep "KNX SCENE RX" at it´s former position to provde backwards compatibility?

Jason2866 commented 3 weeks ago

This PR added new features and added more Slots. https://github.com/arendst/Tasmota/pull/22071

clkempe commented 3 weeks ago

Ok, but why not adding them after KNX SCENE RX?

github-actions[bot] commented 2 days ago

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.

clkempe commented 2 days ago

This PR added new features and added more Slots. #22071

No reply? So poor!

Jason2866 commented 1 day ago

There is a reply, the reason for the changed behaviour is identified and mentioned. Tasmota is a Open Source project, it needs someone with the time and skills to look at wanted changes. You are invited to provide a PR to change the behaviour you like.

clkempe commented 1 day ago

There is a reply, the reason for the changed behaviour is identified and mentioned. Tasmota is a Open Source project, it needs someone with the time and skills to look at wanted changes. You are invited to provide a PR to change the behaviour you like.

The point is: what does that mean for the future? Whenever a new option is added to this list, "KNX Scene RX" will be the victim and moved down, meaning that all users using scenes need to reconfigure their devices? There should be an awareness to take care of having a backwards compatibility for the settings.

Jason2866 commented 1 day ago

Tasmota tries to avoid breaking changes whenever possible. That's why this is still open. Someone has to take the job ;-)