FORUM PLAN UPDATE: Date revision: This forum will remain open to new posts and responses until December 1, 2018. (After that date, you will still be able to view and search the forum.) Also, we're taking a second look at the best place to host future conversation. For now, keep using this forum, and stay tuned for more news.
Stefan's issue (via PMR) appears to be related to the wrong HTTP password on the device and Companion not reporting back that the password is really wrong. We are still tracking that down, but if you are sure you user typed in the correct HTTP password, you should open a PMR (blame it on the server and collect HTTP thread logs too) and we'll debug it as well.
For LO66187, that is definitely in the 18.104.22.168 code. We would need logs to determine what went wrong in your case. But, I can tell you that if there are no devices that exist for the name as entered, it will do the lookup, find the new name, and use the new name; it will only use the as-entered name if it matches an existing device name. If that doesn't explain it, you need a PMR so that we can look at the logs as to what is going on.
Feedback response number RSSN8S4RPE created by Robert S Sielken on 03/05/2012