For some reason my stage bomebox won’t display the port or routing pages on the web GUI. The other pages load and seem to work fine. I tried downgrading to firmware 1.5.3, but the problem still persists.
I noticed the behavior start once I updated to 1.6, so I downgraded one of my 2 bomeboxes to 1.5.3 and it works fine now. The other is not. It doesn’t seem to be passing midi data either.
The most common reason for this is that your browser cache is not cleared. Often, restarting the browser will fix that. Pressing F5 or Ctrl-F5 (or Command-F5) on the respective page sometimes clears it, too. If that does not fix that, most browsers allow you to clear the cache from the browser settings.
You can also test this by either going into private mode (which doesn’t use cache) or trying another browser.
I would recommend you go back to version 1.6.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Just wanted to add some further data in case it’s useful:
After updating to v1.6, the MIDI port page would load fine, but would show no available ports (not even the internal BomeBox DIN). No amount of browser cache clearing, browser restarting, running Incognito/private, BomeBox + computer restarting would cure it. This is on DuckDuckGo (Chromium-based) which has a ‘destroy everything by fire’ cache clear button
Moving to a completely different browser (Edge) and logging in from there allowed me to see the ports! …but still no luck in DuckDuckGo.
I realized I had saved the BomeBox IP address + password in DuckDuckGo, and tried deleting that…and then all started working! So beyond cache clear and basic state management, you might have to literally delete everything imaginable depending on your setup.
At least it’s working
OK, so you are saying it didn’t start working with DuckDuckGo until you deleted the IP and password, Or did you clear everything before it started working? We will look into it. Maybe it is just an issue with some browsers.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Hi Steve! I had cleared the cache, restarted etc - it’s only when I also deleted the bookmark/favorite and saved password that it started working. And yes this may very well be browser specific (DuckDuckGo is WebView / Chromium afaik), hence my reason for sharing
Gemini said this could cause it not to clear cache.
“DuckDuckGo allows you to ‘Fireproof’ specific websites so you stay logged into them even after hitting the fire button. If a site’s cache won’t clear, it may be whitelisted.”
You logins and passwords will still be preserved on non-fireproofed sites.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Hey guys, sorry for these continued issues with the web config after updating the firmware. We are working on a firmware update which will fix this cache problem. For all future updates to come.