SHELLY 1 GEN4 - ZIGBEE NOT WORK
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.7k
- Forks
- 2k
- Avg merge
- 18h 55m
- Merged PRs (30d)
- 35
Description
What happened?
Hì.
I bought some gen 4 Shelly1 and some Shelly1 Mini. I was disappointed and cheated!!
There's not much to say. I think it's a known fact that Shelly and Zigbee don't get along. I even wrote to the manufacturer...
The exposed functions are few, and for example, the toggle/momentary selection doesn't work.
Shelly1G4_0xccba97fffec87710
Indirizzo rete 0xB35B
Indirizzo rete decimale: 45915
Modello Zigbee 1 Shelly
Definizione (Zigbee2MQTT)
S4SW-001X16EU (v0.0.1)
1 Gen 4 Shelly
ID firmware 2.0.0 20260710
Versione firmware 33554687
App: 0.2 build 0 | Stack: 0.0 build 255
MQTT zigbee2mqtt/Shelly1G4_0xccba97fffec87710
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
2.13.0 (unknown)
Adapter firmware version
{"build":397,"ezsp":14,"major":8,"minor":0,"patch":2,"revision":"8.0.2 [GA]","special":0,"type":170}
Adapter
EmberZNet
Setup
os: #1 SMP PREEMPT_DYNAMIC Thu Jul 30 12:44:18 UTC 2026 - 6.18.39-haos - x64
node: v24.18.1
ha: true
Device database.db entry
No response
Debug log
No response
Notes
Device
definition: S4SW-001X16EU - Shelly (v0.0.1)
software_build_id: 2.0.0
date_code: 20260710
endpoints:
{"1":{"bindings":[{"cluster":"genOnOff","target":{"endpoint":1,"ieee_address":"0x7cc6b6fffec9d62b","type":"endpoint"}}],"clusters":{"input":["genBasic","genIdentify","genGroups","genScenes","genOnOff"],"output":["genOta"]},"configured_reportings":[{"attribute":"onOff","cluster":"genOnOff","maximum_report_interval":65000,"minimum_report_interval":0,"reportable_change":1}],"scenes":[]},"2":{"bindings":[{"cluster":"genOnOff","target":{"endpoint":1,"ieee_address":"0x7cc6b6fffec9d62b","type":"endpoint"}},{"cluster":"genScenes","target":{"endpoint":1,"ieee_address":"0x7cc6b6fffec9d62b","type":"endpoint"}}],"clusters":{"input":["genOnOffSwitchCfg"],"output":["genGroups","genOnOff","genIdentify","genScenes"]},"configured_reportings":[],"name":"sw1","scenes":[]},"239":{"bindings":[],"clusters":{"input":["shellyRPCCluster","shellyWiFiSetupCluster"],"output":[]},"configured_reportings":[],"scenes":[]},"242":{"bindings":[],"clusters":{"input":[],"output":["greenPower"]},"configured_reportings":[],"scenes":[]}}
Health
time: Tue Aug 18 2026 20:36:45 GMT+0200 (Ora legale dell’Europa centrale)
os.load_average: 1, 1, 1
os.memory_percent: 19.4412
process.memory_percent: 1.1545
process.uptime_sec: 1308611
{"leave_count":0,"messages":2061,"messages_per_sec":0.0016,"network_address_changes":0}
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 reported S4SW-001X16EU device definition and its endpoint data, then compare the exposed controls with the reported toggle/momentary behavior. Reproduce on Zigbee2MQTT 2.13.0 with the listed EmberZNet adapter and collect a debug log; done means the missing controls or incompatibility is clearly identified and verified.
Written by the indexing model from the issue text.
Assessment
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100