Schneider Electric NH3516A (Wiser Odace) disconnects after interview (duplicate)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.7k
- Forks
- 2k
- Avg merge
- 18h 55m
- Merged PRs (30d)
- 35
Description
@Koenkk I posted this on behalf of another user (from Discord server). They created some issues, but they don't show up. Can you access them? I get 404:
- #32767
- #32793
- #32795
What happened?
Hi, I am experiencing a systematic disconnection of a Schneider Electric Rotary Dimmer (Wiser Odace S940513, detected as NH3516A) immediately after the interview phase. The device joins, interviews successfully, but fails during the configuration step and leaves the network.
What did you expect to happen?
For the device to stay on network and messages to be send/received as normal
How to reproduce it (minimal and precise)
Factory reset the Schneider NH3516A dimmer.
Allow join in Z2M.
Device interviews successfully.
Configuration fails with the above ZCL parsing error.
Device disconnects.
Zigbee2MQTT version
2.13.0
Adapter firmware version
EmberZNet 0x90395efffec80862 Revision: 7.4.2 [GA]
Adapter
SLZB-07
Setup
Add-on on HAOS: running on Pi5
Device database.db entry
{"id":47,"type":"Router","ieeeAddr":"0x70ac08fffe3862d2","nwkAddr":63205,"manufId":4190,"manufName":"Schneider Electric","powerSource":"Mains (single phase)","modelId":"NHROTARY/UNIDIM/1","epList":[3,21,242],"endpoints":{"3":{"profId":260,"epId":3,"devId":257,"inClusterList":[0,3,4,5,6,8,769,2821],"outClusterList":[25],"clusters":{"genBasic":{"attributes":{"modelId":"NHROTARY/UNIDIM/1","manufacturerName":"Schneider Electric","powerSource":1,"zclVersion":3,"appVersion":2,"stackVersion":6,"hwVersion":2,"dateCode":"","swBuildId":"002.011.015 R"}}},"binds":[{"cluster":6,"type":"endpoint","deviceIeeeAddress":"0x90395efffec80862","endpointID":1}],"configuredReportings":[{"cluster":6,"attrId":0,"minRepIntval":0,"maxRepIntval":65000,"repChange":1}],"meta":{}},"21":{"profId":260,"epId":21,"devId":260,"inClusterList":[0,3,2821,65303],"outClusterList":[3,4,5,6,8,258],"clusters":{},"binds":[],"configuredReportings":[],"meta":{}},"242":{"profId":41440,"epId":242,"devId":97,"inClusterList":[],"outClusterList":[33],"clusters":{},"binds":[],"configuredReportings":[],"meta":{}}},"appVersion":2,"stackVersion":6,"hwVersion":2,"dateCode":"","swBuildId":"002.011.015 R","zclVersion":3,"interviewCompleted":true,"interviewState":"SUCCESSFUL","meta":{},"lastSeen":1786034228095}
Debug log
Full log file attached, and a copy of the Z2m logs displayed, device is "0x70ac08fffe3862d2"
Notes
The device successfully completes the interview but fails during the configure phase. The error indicates a RangeError [ERR_OUT_OF_RANGE] when trying to read the manufacturer-specific attribute wiserControlMode from the lightingBallastCfg cluster. After 3 failed attempts (or immediately after the first critical error), the device leaves the network (device_leave).
Device Firmware 002.011.015 R
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached log.log and Z2m.log.log files, focusing on the configuration phase for device 0x70ac08fffe3862d2 and the wiserControlMode parsing error. Compare the failure with the referenced duplicate issues if accessible. Done means the NH3516A completes configuration, stays on the Zigbee network, and can send and receive messages normally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- embedded-iot, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100