Incompatible zigbee device?

sidjohn1 · April 21, 2026, 10:49pm

Just looking for a second set of eyes on this. C7 hub 2.4.4.156. I’m trying to add a SOMA Smart Shades 3 and it paired. i can see position and battery, but i can only control it intermittently. In previous comments someone recommended double pairing the device and that did improve things but every time is run a zigbee discover my hub rediscovers it. I’ve checked firmware and there are no firmware updates for this device.

I’ve never seen a zigbee device do this and it feels like a strong case for send it back.


sys:12026-04-21 05:30:19.366 PMinfoZigbee Discovery Stopped
sys:12026-04-21 05:30:14.440 PMinfoFound previously joined Zigbee device Master Curtain 2
sys:12026-04-21 05:30:05.213 PMinfoZigbee Discovery Running
sys:12026-04-21 05:30:00.983 PMinfoZigbee Discovery Stopped
sys:12026-04-21 05:29:50.469 PMinfoFound previously joined Zigbee device Master Curtain 2
sys:12026-04-21 05:29:27.459 PMinfoFound previously joined Zigbee device Master Curtain 2
sys:12026-04-21 05:29:20.849 PMinfoZigbee Discovery Running
sys:12026-04-21 05:27:19.272 PMinfoZigbee Discovery Stopped
sys:12026-04-21 05:27:05.706 PMinfoFound previously joined Zigbee device Master Curtain 2
sys:12026-04-21 05:26:34.838 PMinfoZigbee Discovery Running


dev:50122026-04-21 05:32:08.366 PMinfoMaster Curtain 2 shade was set to 45%
dev:50122026-04-21 05:32:08.363 PMinfoMaster Curtain 2 shade is partially open
dev:50122026-04-21 05:32:08.360 PMdebugdescMap:[raw:00120A01020808002037, dni:0012, endpoint:0A, cluster:0102, size:08, attrId:0008, encoding:20, command:0A, value:37, clusterInt:258, attrInt:8]
dev:50122026-04-21 05:32:08.354 PMinfoskipped global command cluster:0102, command:07, data:[00]
dev:50122026-04-21 05:32:08.351 PMdebugdescMap:[raw:catchall: 0104 0102 0A 01 0040 00 0012 00 00 0000 07 01 00, profileId:0104, clusterId:0102, clusterInt:258, sourceEndpoint:0A, destinationEndpoint:01, options:0040, messageType:00, dni:0012, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[00]]
dev:50122026-04-21 05:32:08.203 PMdebugdescMap:[raw:catchall: 0000 8021 00 00 0040 00 0012 00 00 0000 00 00 1900, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:0012, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[19, 00]]
dev:50122026-04-21 05:32:07.887 PMinfoaddress changed! new:0012, old:A4EB, checking group membership status...
dev:50122026-04-21 05:32:07.883 PMtracedevice announce...

rlithgow1 · April 22, 2026, 1:17pm

How close is your nearest mains device? This sounds like a weak signal issue.

sidjohn1 · April 22, 2026, 1:34pm

I have mains powered zigbee devices in every room of my house. In that room there are 3, so a few feet on multiple axis’s. 12ft max with line of sight. I also tried paring it a few feet from the hub. same logs.

The goal was to replace a preexisting zigbee device with this one because the motor was quieter.

Rxich · April 22, 2026, 1:35pm

Are you using a 3rd party driver? I've seen this where the device clusters aren't being intialized properly. You could try re-pairing very close to the hub

sidjohn1 · April 22, 2026, 1:38pm

Tried this and same behavior with the generic zigbee shade driver as with the SOMA Smart Shades 3 (Zigbee) — Hubitat driver and the super generic “device” driver

sidjohn1 · April 22, 2026, 1:54pm

just to clear up any weak signal concerns, the last hop RSSI of the device in its intended location is quite good. I dont think you can beat 255 for last hop LQI


dev:2026-04-22 08:52:05.040 AMinfoprofileId:0000, clusterId:0013, sourceEndpoint:00, destinationEndpoint:00 , groupId:0000, lastHopLqi:255, lastHopRssi:-64
dev:2026-04-22 08:51:47.603 AMinfoprofileId:0000, clusterId:0013, sourceEndpoint:00, destinationEndpoint:00 , groupId:0000, lastHopLqi:255, lastHopRssi:-67
dev:2026-04-22 08:51:29.847 AMinfoprofileId:0104, clusterId:0000, sourceEndpoint:0A, destinationEndpoint:01 , groupId:0000, lastHopLqi:255, lastHopRssi:-32
dev:2026-04-22 08:51:28.738 AMinfoprofileId:0000, clusterId:8004, sourceEndpoint:00, destinationEndpoint:00 , groupId:0000, lastHopLqi:255, lastHopRssi:-36
dev:2026-04-22 08:51:28.334 AMinfoprofileId:0000, clusterId:8005, sourceEndpoint:00, destinationEndpoint:00 , groupId:0000, lastHopLqi:255, lastHopRssi:-32
dev:2026-04-22 08:51:28.030 AMinfoprofileId:0000, clusterId:0013, sourceEndpoint:00, destinationEndpoint:00 , groupId:0000, lastHopLqi:255, lastHopRssi:-63

rlithgow1 · April 22, 2026, 2:01pm

Dumb question. During playing with drivers, did you click configure after save?

sidjohn1 · April 22, 2026, 2:10pm

Great question, 100% of the time.

sidjohn1 · April 22, 2026, 2:53pm

At this point im just documenting anything else i think is weird and i’m gonna send the link the this thread to Soma Support

The infoaddress changed! events when the zigbee radio is in pairing mode i think are odd, and this morning i realized the zigbee map does a good job visualizing why I think the events are odd.