I already found a few things, which I added to the Bug List.
We keep a separate thread for the Bug List, which is here:
http://forums.x10.com/index.php?topic=22373.0This is what I found so far:
1. Changing a module between "Lamps" and "Old Lamps" does not change the color of the bar at the top until you go out of the room (or AHP) and go back in. This is a new bug in 3.310 (at least I didn't notice it in 3.306). It is a cosmetic issue, but there is no reason not to fix it in the next version.
2. "Florescent Decorator Switch" sends extended commands if defined as a "New" lamp.This is also a new bug in 3.310. I had a number of SmartHome relay (non-dimming) switches that were defined in AHP as "Florescent Decorator" switches (WS13A-L). When 3.302 introduced SoftStart support, I noticed these didn't change their behavior, even if defined as "Lamps" instead of "Old Lamps - no SoftStart." However, in 3.310, I see that AHP now sends an Extended Dim command to turn them on. Do the newer (post 2008) WS13A-L switches turn on with an Extended command? If so, then I wonder why the change wasn't made earlier. If not, then it is a bug that needs to be corrected. When I changed them to the "Fluorescent Decorator Switch" from the "Old Lamps" list, they worked fine.
3. SDK sends extended commands for Unit codes defined as SoftStart modules in AHP.This is another one that is new in 3.310. I found it by accident, too. I was trying to control my "Florescent Decorator Switch" (see #2 above), but it wouldn't go on. Even using the AHCMD wouldn't do it. My PalmPad could turn it on, and I could turn it off in AHP (or with AHCMD), but I could not get it to go on. I checked the Activity Monitor, and sure enough I saw the Extended Dim commands. (I discovered this together with bug #2). Once I changed the module definition in AHP, AHCMD would send the correct "On" command. It looks like there is no longer a way to specifically send "on" commands for a module that is defined in AHP as SoftStart.
Edit: I did some more testing. interestingly enough, sending an "on" to a SoftStart module now instead sends it an Extended Dim command to the level it was last at (either the current level of it is on, or the last level if it is off). I'm sure this will mess up a lot of people who use the SDK. There is no mention of this behavior change in the release notes at all (unless it has something to do with them changing the SoftStart dim level status that had been broken before).
4. Changing a module between "Lamps" and "Old Lamps" should keep the current "module type" selection, instead of defaulting to the first item in the list.This started with 3.302, but I haven't bothered to report it. It is less of a "Bug," and more of an "Annoying feature."
Since those of us with older modules have to re-define them as "Old Lamps," It would be nice if we could do that by just changing the first drop-down, instead of having to change both. Again, it is a cosmetic thing, but still a nice thing to get fixed.
I also confirmed a few bugs were fixed. I don't have the ability to test them all, but I did mark the ones I could confirm as "fixed" in the list.
Hopefully, as more users install and test 3.310, we will get a better picture of how it is working, and get the developers working on ironing out the kinks.