You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 28, 2022. It is now read-only.
what a promising work!
As it is in a 'work-in-progress' status I'd suggest a minor change, so the topic of the attReport event message to reflect full ZigBee characteristics, like this:
since now it is impossible to determine, which endpoint of my dual switch the report came from since the 'device' property of the message object holds the whole epList, not the source endpoint.
With complex devices, a good number of clusters with dozens of attributes could appear, so that's why I suggest the topic structure above.
Regards,
András
The text was updated successfully, but these errors were encountered:
Hi, hobbyquaker,
what a promising work!
As it is in a 'work-in-progress' status I'd suggest a minor change, so the topic of the attReport event message to reflect full ZigBee characteristics, like this:
ieeeAddr / attReport / endPoint / clusterId / attributeId
since now it is impossible to determine, which endpoint of my dual switch the report came from since the 'device' property of the message object holds the whole epList, not the source endpoint.
With complex devices, a good number of clusters with dozens of attributes could appear, so that's why I suggest the topic structure above.
Regards,
András
The text was updated successfully, but these errors were encountered: