[RELEASE] Prototype for Graber, Bali, Somfy TDBU Driver

marcik4 · April 12, 2026, 4:29pm

I have Zwave TDBU Bali shades (new models, purchased this year), and only bottom rail is working with all available drivers.

Top rail is using custom and undocumented zwave commands.

I've been messing around with Claude to try to reverse engineer it. I got it to work, partially. It's good enough for my use, but sharing it with more people - it may also work for you, or maybe you want to continue reverse engineering to make it fully functional.

I'm only able to move top rail to 69% (nice, but no idea why this number) on 2 TDBU shades I have. And then close it.

With those limitations (I don't need granular control) driver just supports 4 states - fully open, fully closed, half open from top, half open from bottom. Given that top moves in weird way, it cannot transition smoothly between those states, so it may fully open/close shades before setting the right command. That's why it has travelTimeSec - it's how long driver needs to wait before issuing next commands - it's set by default to 40s, as my shades take about 35s to make full move.

github.com

marcik4/Graber_TDBU_Shade_Driver/blob/main/Graber_TDBU_Shade_Driver.groovy

/**
 * Graber / Bali / Somfy TDBU Shade Driver
 * Version: 1.2
 * Author: custom (reverse engineered via Hubitat probe drivers)
 *
 * ═══════════════════════════════════════════════════════════════════════════════
 * DEVICE IDENTIFICATION
 * ═══════════════════════════════════════════════════════════════════════════════
 * Manufacturer:    Springs Window Fashions (Somfy) — mfr code 622 (0x026E)
 * Brand names:     Bali, Graber, Somfy
 * Model:           CRZB — "PowerCore Z-Wave with BLE Shade"
 * deviceId:        23106 (0x5A42)
 * deviceType:      16980 (0x4254) — NOTE: some sources show 0x5252, both seen
 * firmwareVersion: 14.7
 * hardwareVersion: 255
 * protocolVersion: 6.8
 * inClusters:      0x5E,0x26,0x85,0x59,0x72,0x86,0x5A,0x73,0x7A,0x6C,0x55,0x80
 * zwNodeInfo:      53 BC 00 04 11 07 5E 26 85 5C 59 72 86 5A 73 7A 6C 55 80 68 23
 *
 * FCC ID: 2AAVX-CRZB

This file has been truncated. show original

This all vibecoded, and included outcome of the current state of research in the comments. No warranty, I have no intention in developing it further myself. But with the current state of vibecoding, you should be able to take it further/tune it for your needs if you want to support your TDBU shades.

calinatl · April 14, 2026, 4:49am

Another way to support TDBU shades is to pair each rail as a separate shade...

marcik4 · April 14, 2026, 10:53pm

Were you able to do that with bali shades? i've tried (and searched online about it) and there's no way to do that.

calinatl · April 20, 2026, 6:23am

No, not with a Bali. I did it with TDBU shades that I paired with a Bond Bridge and brought into Hubitat that way.

marktheknife · April 20, 2026, 10:36am

Bali is a brand name.

Who makes your top down-bottom up shade?

calinatl · April 20, 2026, 9:35pm

Comfortex. They are not zigbee or z-wave. They use RF frequency that I connect to the Bond Bridge, then connect Bond Bridge to Hubitat.

marktheknife · April 20, 2026, 10:27pm

Can’t use this driver, then.

calinatl · April 20, 2026, 11:28pm

Correct; never implied I could. I was sharing a strategy for pairing TDBU shades with the OP who was having trouble getting each to work...

marktheknife · April 20, 2026, 11:41pm

Probably possible to control further with the right changes to the z-wave driver code.

marcik4 · April 21, 2026, 4:09am

Ok, my previous attempt failed WAF tests, and while I was happy with it, I had to go back to the drawing board.

I ended up with much better working driver now. I was able to reverse engineer how to set presets - and they trigger movement of both motors. Great thing about it, is that internally shades understand current state and know how to move between presets in most optimal way - previous driver required some weird dance around it.

github.com

marcik4/Graber_TDBU_Shade_Driver/blob/main/Graber_TDBU_Shade_Driver_v2.groovy

/**
 * Graber / Bali / Somfy TDBU Shade Driver
 * Version: 2.1
 * Author: custom (reverse engineered via Hubitat probe drivers)
 *
 * ═══════════════════════════════════════════════════════════════════════════════
 * v2.1 — STOP COMMAND
 * ═══════════════════════════════════════════════════════════════════════════════
 * switchMultilevelStopLevelChange works mid-travel on this shade — it halts
 * whichever rail is currently moving. (v1 comments incorrectly claimed it was
 * ignored; we'd only tested it while idle, not during motion.)
 *
 * Every preset command now fires stop first, then the new setLevel, with a
 * delay between them (configurable via commandDelayMs, default 750ms). Without
 * the delay, the stop lands but the subsequent setLevel is dropped — the
 * firmware needs a moment to settle before it'll accept new motion. Without
 * the stop, a setLevel issued during active travel is ignored until the
 * in-progress move finishes.
 *
 * Explicit stop() command is also available.

This file has been truncated. show original

It's really simple. switchMultilevelSet, starting from 246 correspond to presets in the app. 1st one is 246, 2nd one is 247, etc. I've configured 6 for myself, and created explicit commands for those presets. If anyone is interested - it's easy to rename those/add/remove or figure out nicer interface for it.

Hopefully WAF test is now at 100% and I don't need to reverse engineer more.