I'm a Johnny-come-lately with this, but I do feel I should mention that using ezBUS requires knowledge of a) what ezBUS is, b) how it works, and c) how to configure it.
All that info is given in the user manual, and also in pictographic/text and video form on the website.
If you connected multiple lights - or anything else - via the ezBUS circuit, you had to have known there was a chance they wouldn't work at all without going through the device recognition procedure (the ezBUS circuit identifies smart devices by reading individual device addresses). Why the trouble?
With all due repect
If you design and build a piece of software , hardware , you have intimate knowledge built up over years of development and testing
(at first it's not intuitive, seems awkward , if not back to front ), by the time the part / product its launched / introduced, your the guru's ,
you know the device/ product intimatly , and can rattle off settings , tweaks and chunks of specifications without going anywhere near the manuals or spec sheets
Imparting that knowlege (knack) to other people can be very difficult, what you think and see, is often litterally lost in translation
Just by reading your reply above , tells me your in a different world to the end user, both in terms of understanding of the product, and the demographic of who uses the product
For info,
the manual isn't very clear or intuitive, and i found the way to do it by accident / trial and error
There are also other areas where first / third party hardware changes parameters too which arnt documented , that makes for interesting times trying to sort that out
