Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configuration issue for Aeotec ZWA023 Smart Switch 7 US #1756

Open
apella12 opened this issue Apr 12, 2022 · 1 comment
Open

Configuration issue for Aeotec ZWA023 Smart Switch 7 US #1756

apella12 opened this issue Apr 12, 2022 · 1 comment

Comments

@apella12
Copy link
Contributor

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.

  • OH2 Version: OH3.3M3
  • Binding Version : Base code from Feb 3
  • Device name: Aeotec ZWA023 Smart Switch 7 US
  • Link to database:
  • XML as text Node114.txt

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

@openhab-bot
Copy link
Collaborator

This issue has been mentioned on openHAB Community. There might be relevant details there:

https://community.openhab.org/t/associations-to-device-with-multiple-endpoints-not-working-correctly/138340/2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants