Should plugins detect changes before calling `setAttribute`?

[AMoo-Miki]

I create a plugin for Wiz light bulbs and outlets. These devices send their status every 5 seconds to the plugin. Should the plugin maintain the state of the devices and only call setAttribute for changes or is this handled by Matterbridge or matter.js?

PS, while the plugin is maintaining the state now, I occasionally see out of sync states. If Matterbridge/matter.js doesn't mind hearing from devices with their same old status, I would rather not maintain the state in the plugin. However, if a broadcast is made for every setAttribute, I would rather improve the state management in the plugin.

Please share your thoughts or any tips you might have.

On a side note, I would be grateful for any critique of the plugin. I would like to improve this before starting on plugins for Tuya and Switchmate.

[Apollon77]

matter.js wise we will ignore "same value updates" because matter.-side does not care ... so no issue with setting the value

[Luligu]

Concerning the other plugins, I update the states when the devices send update.

Set the debug on matter.js side to understand what is going on the matter side.

Only in z2m I check the update and filter the changes cause there some devices just send too many updates in a sec.

[Luligu]

Hi,
I close the issues.
If you need let me know.
Thanks again for your interest.

When you are ready tell me if you want your plugin on the list.