@sowayan @securejangle we have a new beta firmware that supports group binding. You can download it from here:
http://inov.li/IRbxhx1646F/VTM31-SN_V1162.ota
One user did report: “the VTM31 update erases a user stored Node Label” so be aware of that if it will impact you.
Thanks @EricM_Inovelli. Sadly, all my switches are VTM-30 (on-off switch). I’ll gladly participate in a beta when there is a firmware for my switch.
Excellent. Thanks Eric.
I have a mix of dimmers and switches. I’ll give it a shot and reply with my results.
I deployed the beta firmware to my dimmers. I setup my group bindings using the HA Matter Binding Helper add-on.
Everything worked as expected. My lights are more responsive and reliable using group bindings. I didn’t notice any issues.
I’m looking forward to VTM30-SN firmware for my white series switches.
Please let me know if there’s anything I should test or check on the dimmers. I’ll continue to use the beta firmware until an official release is available. I’ll report back if I notice any issues.
Edit: If anyone would like to test the firmware with HA, be aware that you need to configure the matter-js server to import custom OTA firmware. The matter webserver will show the “Upload Firmware” button whether or not test-net DCL mode is enabled. This was a bit confusing.
I have tested myself too. I was able to use group binding for on/off, but not for level control. Were you able to test this on your side?
I didn’t really had time to troubleshoot if this is a firmware issue or something else. I am also using home assistant with the matter binding integration.
What is the “Dimming Speed (Simulated)” setting set to? If it is zero, set it to 2 or 3 and try again. That worked for me with direct binding.
I have tested myself too. I was able to use group binding for on/off, but not for level control. Were you able to test this on your side?
Ahhh, I didn’t actually test level control. It looks like this might be an ACL issue.
Edit: Matter Binding Helper creates ACL entries that look like this:
{
"1": 3,
"2": 3,
"3": [
9
],
"4": [
{
"0": null,
"1": 1,
"2": null
}
],
"254": 2
}
This appears to be valid, as per the Matter specification. But my Nanoleaf bulbs don’t seem to like it. I’m using the following ACL entry instead:
{
"1": 3,
"2": 3,
"3": [
9
],
"4": [
{
"0": 6,
"1": 1,
"2": null
},
{
"0": 8,
"1": 1,
"2": null
}
],
"254": 2
}
This is the AccessControlEntryStruct. Struct ID 3 is the ID of the group. ID 4 is the AccessControlTargetStruct.
For the AccessControlTargetStruct, ID 0 is the Cluster ID, ID 1 is the Endpoint number, and ID 2 is the device type.
@EricM_Inovelli is a beta with group binding capability planned for the VTM 30? I’d love to help with bringing this to the on/off switch.
@sowayan and @EricM_Inovelli - I have also downloaded the beta firmware and was able to successfully create a group binding from my dimmer to Nanoleaf downlights. Thank you so much! So happy to have this! Response is definitely a little bit snappier now.
One other quick report:
I have the Aux (add-on) Switch attached to the dimmer for my main staircase. Group bindings did not work reliably until I power cycled the dimmer using the pull tab. One of my two bulbs was responsive, the other was unreliable. That behavior shouldn’t be possible with multicast group bindings, but it’s what I observed.
@sowayan We should have it pretty soon. I’ll post here when we do.
@securejangle that is a little strange, but keep an eye on it and let us know if it acts up again. Doesn’t seem possible with how multicast works, but who knows.
My best guess is that it was still using the direct bindings for some reason. But I really have no idea.
We have added group binding support to the latest beta firmware:
Index of /firmware/VTM30-SN/Beta/1.0.6r1
The whole changelog is here: