As far as I know nothing else is needed. The name of the file is not important, the startup procedure works through the .rules files in the directory. I think for testing you can run the starup manually with:
sudo udevadm control --reload-rules && udevadm trigger

Working with just one device plugged in at a time and just one of the two entries in the .rules file.

lsusb shows you the 2341:0043 identifying the Arduino?
ls -l /dev shows you the Arduino as /dev/ttyACM0?
There is no sign of /dev/roofCtrl?

If the one device does not show, remove it and try the other one and switch them in the rules file. You should be able to see one of the devices in the /dir and then be able to make some impact with the rules file. Once you can tell that the file is being seen and can make a difference it might be easier to figure out what is going wrong.

Read More...