Me again. I’ve had some issues with another box of mine today. The box is very temperamental in terms of connecting to the Bome network. This is something we noticed a few shows ago when setting up that particular box that day. Tried multiple cables etc & sometimes the device connects, 90% it doesn’t. Because of this in the end we factory reset the box multiple times, updated firmware to the latest version & even downgraded to check in hopes of getting it connected. We can initially set the device up with a fixed IP over Wifi.
We are currently powering the box via POE from my managed switch with with all Energy saving modes turned off. We also tried a different POE switch and computer in hopes to see it and connect but nothing is working or ping tests. What is odd is that the Bome network can sometimes see the box but it doesn’t connect or ping tests not working on that IP.
Any suggestions would be a great help as we’ve had 3 of our audio team on it to no success.
Steve’s USB-power/PoE-Out test sounds like a useful way to isolate the power and data paths. I’d also try the box on a simple unmanaged switch or directly to the computer, with Wi‑Fi temporarily disabled, and check whether the router or switch shows a DHCP lease for the box’s MAC address. If it works there, compare VLAN or client-isolation settings, port security, and PoE negotiation on the managed switch. When the Bome Network can see the box but ping fails, confirm the computer is on the same subnet and that the fixed IP is not colliding with another device. I’d note which power/data combination works before changing firmware again. For checking an audio setup once the network path is stable, this frequency reference is useful.
So it seems the PoE IN port can serve as PoE power supply, but not for network data. I’m afraid that this cannot be fixed with a firmware update. This is really unfortunate, I think we need to inspect it to see what’s going on. Please contact us directly.