Hi there,

More and more, I have to create a device in the NevoSL from scrap - new devices, manufactured by brands which are not listed in the NevoSL database, new series of codes for existing brands...

As a result, I choose whatever device in the database which is not too far from an the one I want to include in my NevoSL, and I learn all the codes manually (remote against remote).

My only concern with this method is I have a lot of native codes belonging to the device I selected, that are absolutely useless, and even confusing sometimes (instruction bearing the same name from the native database, and the learnt codes).

Is there any way to delete these native codes in order to avoid any confusion?

Thanks in advance for your help!

+1 I've wanted to do this as well. On a somewhat related note, is there a way to force the command list in the devices window into alphabetical order? Any that I add always stay at the bottom of the list, in the order that I added them.

Both pat17 and I are trying to do the same thing, I think: customize and clean up the command list so it reflects an accurate code set for a particular device. Removing redundant/inoperable commands and getting them into order would be a great help.

There is really no way to delete the native codes. However, you can learn your codes into the native codes so they represent the codes you want, instead of learning separate codes. It works a lot better when you learn into the native codes.

Dave

Dear all,

Thanks for these answers... It's a bit late now, but I should have thought of the possibility to replace the existing codes!

Unfortunately, I have now too many pages using these codes either as buttons or part of macros to think of editing all of them!

Thanks again!

Hey pat,

I did discover another way to approach this if you face a similar problem in the future. When you're creating a new device that just doesn't match the pre-configured ones very well and want to "start from scratch," as you put, start with a "Barthelmess Home Lighting" device. Seriously! It only has one native command (Dim), so you're not going end up with a bunch of null commands. You add only those learned commands and HEX codes you need, and end up with a very clean and accurate device command list.

As Dave said, it's best to use native code names whenever you can, as they'll work with SuperFast Device Swap, but there's no reason you can't use them wherever applicable as you add your own commands.

The only thing that would make this even better is if I could figure out how to create the command list as a .csv file and dump them in all at once, like I can with serial devices. This allows more efficient editing (because you have an overview of all the info), and you can order them exactly as you want.