Anybody Using More Than 100 Zones On An Elk M1?

[123]

So I guess when picking the var(s) needed for a UI element, the list of available ELK-related vars includes all 208 zones (both active and disabled zones). I agree this adds no overhead because the M1 broadcasts its events (well, most of 'em anyway ... not Counters or Zone Voltages) and polling is not required. The only value to pre-defining the list of M1 zones would be to reduce visual clutter (i.e. no need to see stuff that's disabled and unused).

Anyway, not a big deal ... just a subtlety of interest to a small tiny audience of driver developers.

 

[IVB]

Also of interest to DIY'ers - The reason I like the CQC model of only selecting the fields you're interested in is that as i'm creating screens, I don't have to wade through 1000 (or more) fields to get to the one I want.

 

[123]

Also of interest to DIY'ers ... I don't have to wade through 1000 (or more) fields to get to the one I want.

It is encouraging to learn that people do appreciate subtle design decisions ... although, I'm not sure IVB represents the typical DIYer ... uber-DIYer, yes.