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
Putting this issue here because I worked with Aeotec support to solve this for me, but do not know what (if anything) needs to be changed in the Device DB for this device or in the binding code to fix the problem for others who have (or may in the future buy) the device.
Summary: Initialization/inclusion of this device fixes endpoint 1 as the priority for reporting. ("Refresh" will prompt a report on all channels). For the Meter CC this can be worked around since there is only one plug and endpoint 0 and endpoint 1 have the same information. What I noticed was this device has Clock CC and that will not work from endpoint 1. The attached pdf file summarizes the email communication with Aeotec support and the ultimate fix to use the Silabs PC controller to unassign endpoint 1 from the multichannel group association zwa023-email-chain-aeotec.pdf
I also did a Debug level re-initialize of the device. There does appear to be extra bytes in the multichannel area. Perhaps the device uses a higher version? Node114.txt
I did look at the DB to see what I could change with no success. As to the binding, I think this section Node association.txt
in the ZwaveNode class is where this is happening, but don't know enough about it change anything.
Bob
The text was updated successfully, but these errors were encountered:
Putting this issue here because I worked with Aeotec support to solve this for me, but do not know what (if anything) needs to be changed in the Device DB for this device or in the binding code to fix the problem for others who have (or may in the future buy) the device.
Summary: Initialization/inclusion of this device fixes endpoint 1 as the priority for reporting. ("Refresh" will prompt a report on all channels). For the Meter CC this can be worked around since there is only one plug and endpoint 0 and endpoint 1 have the same information. What I noticed was this device has Clock CC and that will not work from endpoint 1. The attached pdf file summarizes the email communication with Aeotec support and the ultimate fix to use the Silabs PC controller to unassign endpoint 1 from the multichannel group association
zwa023-email-chain-aeotec.pdf
I also did a Debug level re-initialize of the device. There does appear to be extra bytes in the multichannel area. Perhaps the device uses a higher version?
Node114.txt
I did look at the DB to see what I could change with no success. As to the binding, I think this section
Node association.txt
in the ZwaveNode class is where this is happening, but don't know enough about it change anything.
Bob
The text was updated successfully, but these errors were encountered: