Since this relates to Sean's template, I thought it might be best to post into this thread.
Sean's Template is #2254, titled 3M50 by Radio Thermostat as the manufacturer. At some prior point in time, Aviator had also created a template, but it somehow got committed as an unfinished template #2243, manufacturer Filtrete, model 3M50. There was no code attached to that template. I bring this up for a couple of reasons. The first and obvious one is that it could cause confusion if someone were to select it manually, since it wouldn't work.
The second reason is that I'm currently working on a driver for the CT-80 thermostat from Radio Thermostat. It's the big brother to the CT-30/3M50, and uses the same API (but with extra features supported by the hardware). For my development work, I've re-purposed the broken template 2243 to avoid conflicting with Sean's template. My local copy has been renamed CT-30/CT-80 by Radio Thermostat. I'm getting close to finishing up what I want to get done at this point in time, so I'll be looking to commit my code soon, so I can return to doing my ISY driver. My eventual goal is to implement all of the Radio Thermostat API, but that'll likely take a few phases. So, I'm looking for some guidance from you gents as to how you'd like me to proceed in the near term...
Since you wrote the 3M driver (and I'm basing parts of mine on yours), I don't want to step on your toes. Do you want to claim custodianship over the 3M driver? I can commit my changes against #2243 in a non-conflicting way, and you can decide if you like what you see, and how you'd like to go forward. Or I can post code into this thread or Trac or ...
I'm presuming that two devices can't have the same range of MAC addresses for DHCP, correct? Would committing my code into the currently broken 2243 be a problem?
Thanks for your time, gents!