From what I gather the fact that the HA-Bridge loads to port 80 by default is what causes most of the issues.
There are a lot of things that want to use port 80 and not just servers, these can make setting up the HA-bridge a pain.
Unless you knew what is running for sure on port 80 one would have a lot of
Junk
to got threw.
With that in mind I'm improving the initial setup.
Alex10 will auto write a habridge.config file when you enter the Alex10 setup page.
It will use the address of the PC you have alex10 installed on and the default port of 80.
Both these values will appear in the HA-Bridge Address settings.
You will be able to change both these values, in Alex10, editing the text boxes and pressing the change button.
When you start HA-bridge it will read the configuration file and use those settings.
if you plan to view the HA-Bridge web page you just need to type the correct IP and port values as the url .
However you never need to view the HA-Bridge now unless you wish to add scripts which Alex10 doesn't create. You also can change the HA-Bridge IP or port at any time afterwards as well however you'll need to stop the bridge and restart it before it uses the new settings.
I thought about adding the option to run this as a service however that would cause issues when/if you wished to add more x10 devices latter.
Instead I added the option to load on windows boot so if you already have it setup with a shortcut in the start up folder you may wish to remove it and choose that option as it will load quicker.
These options will be in the next release which should be out by the end of the weekend unless someone has another suggestion to make setup simpler. Adding that may push back the next release.