dduff617 wrote:Also, scanning the Bali/Somfy docs for info, I noticed this (possibly nothing more than z-wave "boilerplate"):
The current product controls may establish two Association Groups. Association Group #1 is a dedicated lifeline for secondary controls, primarily used for battery status reports, central scene cc, local reset cc. Association Group #2 is dedicated to slave shades nodes, with a maximum of 12 slave nodes. Normal shade control command will use Association Group #2.
That's not "boilerplate" as such, it's specific to this product - though the same concept of a lifeline group for main commands, then other groups for other operations is used widely. I did read that earlier tonight and checked it; battery commands are all using AG #1 as it says, so nothing further to investigate in this regard.
dduff617 wrote:I set up a watcher device for one of the Somfy remote devices. For this type of device, unlike the shades, I can't just do a "send status request", so I had to wait a while to see the next status report message go by. Here it is:Z-Wave Watcher Debug Raw command sent (Node 59): 01 09 00 13 3B 02 84 08 24 32 46 (True)
Z-Wave Watcher Debug Raw command received (Node 59): 01 08 00 04 00 3B 02 84 07 49
Z-Wave received "059 - KIT Shades Remote" status update battery level 55%
Z-Wave Watcher Debug Raw command received (Node 59): 01 09 00 04 00 3B 03 80 03 37 7E
This may be completely irrelevant due to it being a different message type, but how a different model Somfy-brand device reports status/battery, for whatever that's worth.
That's exactly what we should see. 80 03 37 xx is a battery value of 37 (55%). Ignore the 7E. that's a checksum to make sure the command isn't corrupt.