OK, I suggest if you want to connect BomeBox to Computer direct with Ethernet (with no router in between), you configure the ethernet side of the BomeBox as an ethernet master. Be sure you do not use Wi-Fi on your computer when doing so. BomeBox will then assign your computer an IP address. This is not my best recommendation.
If you have an existing router, it would be even better (best recomendatin) to connect both your computer and BomeBox to the LAN ports of the router and leave the BomeBox configured as an ethernet client. In this configuration, your computer will also still be able to access the internet (that is if your router is connected to the internet). In this case, your existing router assigns an IP address to both BomeBox and your computer. I wouldn’t recommend using WiFi either on your BomeBox or your computer in this configuration as they will be on different networks.
You should still be able to use WiFI from your phone to access the web config however since the WiFi and ethernet are on different networks, they will more than likely not be able to talk to each other unless you set up some advanced routing on the BomeBox.
As a HotSpot, the BomeBox defaults to IP addres 192.168.153.1
As a Ethernet master, your BomeBox will default to IP address 192.168.1.1
As you can see, they are on different networks.
For APIPA mode the address I get for my BomeBox is 169.254.6.211, but this might vary depending on the APIPA negotiation protocol.
I also noticed that in the APIPA mode the netmask is 255.255.0.0 instead of the default of 255.255.255.0 (for the other modes). What this means is that their broadcast address are also different and broadcast requires that the network portion of the IP address needs to be the same for all attached devices on that network. Bome Network uses broadcast packets (on the same network) to identify other hosts on the network.
If the netmask or network is different, they cannot find each other unless you set up special manual routing.
The only reason, I might see them not identifying each other when your project file is loaded is perhaps the way you defined the attached devices or routing in the project file. The project file settings generally override the BomeBox default settings on open devices and midi routes when you load it.
The BomeBox tries to “remember” the settings from the last time it was running so if you switched from WiFi to ethernet, the old settings might be remembered incorrectly, but they should still be able to connect.
Another thing that I’ve found as that you should always initiate the network connection from the same point. If you try an initiate a connection on BomeBox and initiate the same connection, Bome Network can get confused so you should delete all pending connections, then re-initiate them in the order you always want them. I anticipate over time, Bome Network will get smarter about this.
Bome Q and A Moderator and
Independent Bome Consultant/Specialist