Commit Graph

10 Commits (728be6ad55f4bd020d90f9302ebc732eb85df052)

Author SHA1 Message Date
Michael Zanetti df0b7e9c63 Rafactor handling of TSNs in ZCL to allow the application using it.
This patch separates the transactionSequenceNumber used for sending from the
one received. According to the specification, the transactionSequenceNumber is
not meant to equally increase on both ends, but instead really just be a "random"
number which allows to match a reply to a request. Syncing them on both ends
has the outcome to increase the likelyhood of collisions if a device sends
a notification at the same time we send a request and thus even may wrongly
interpret that incoming command as a reply to the request. In fact, ideally TSNs for
outgoing messages would stay away as far as possible from incoming ones.

The old code additionally had the problem that it would re-use the last received
TSN for outgoing requests, given it used a post-increment when reading
m_transactionSequenceNumber after setting it to the last received TSN.

The new code will use a single static upcounting TSN for all outgoing requests
but will still allow overriding it with a custom TSN of for some reason a certain
device requires a specific TSN (apparently those exist).
It will not do anything with incoming TSNs but forward them now to the application
layer which may decide to use it match its own transactions or to deduplicate packets.

This allows fixing the issue in nymea that remote controls sometimes produce duplicate
pressed events (seen most often with the Tradfri Symfonisk) by discarding commands that
didn't increase the TSN.
2022-01-22 13:51:21 +01:00
Michael Zanetti 6afc214202 More work on OnOff, LevelControl and ScenesCluster
This alignes the OnOff cluster with the LevelControl cluster in terms
of signal behavior: Previously, the OnOff cluster would fire a generic
commandSent() signal for some commands and specific signals for others.
Effectively forcing the user to connect multiple signals even if only
the command would be of interest.

The LevelControl cluster instead always fired a generic commandSent()
signal and *additionally* more specific signals for parsed parameters.

This changes the OnOff cluster to be in line with the LevelCluster
as and making the API a bit simpler to use when parameters are not of
interest.

Also it completes the specific parsing for all 3 clusters.
2021-12-07 10:14:02 +01:00
Simon Stürz cc725a9533 Improve debug output and add level cluster signals 2020-11-26 18:32:07 +01:00
Simon Stürz 4eafe285b0 Clean up clusters and implement default get methods for now 2020-11-12 13:27:37 +01:00
Michael Zanetti 40512509ae Fix some typos 2020-11-11 14:43:26 +01:00
Simon Stürz 8f1043ba9f Implement lqi updating of nodes and finishe on/off and level cluster 2020-06-14 14:39:10 +02:00
Simon Stürz cdd7a1a1aa Implement power configuration cluster 2020-06-13 21:18:01 +02:00
Simon Stürz 0992028a8a Rework entire uart communication flow and prepare level cluster command execution signals 2020-06-06 14:09:11 +02:00
Simon Stürz 275e4c8b97 Implement color control cluster and improve uart communication 2020-06-05 18:58:11 +02:00
Simon Stürz 80d4b1416e Restructure the descriptor handling and implement level control cluster server side 2020-06-03 19:50:47 +02:00