We’re discovering that devices cannot follow tagging rules for more than a single geofence profile.
Here is an example use case-
A router installed on a Ship regularly moves from the US Mainland to Alaska. On the mainland, they use a combination of Verizon and AT&T SIMs. In Alaska, the ship connects to a smaller local ISP whos SIMs are in slot B. The goal is to have an “Alaska” tag, and a “Mainland” tag. Each tag corresponds to a bulk configuration that sets cellular settings appropriately so that the Verizon and AT&T SIMs aren’t incurring roaming charges in Alaska and Vise Versa.
The logical seems to be built and the event logging shows appropriately, but for some reason, there is a limitation when applying the tags.
Please help take the next step in making geofence capabilities a more advanced feature.
I’ve got a couple use cases as well.
Use Case 1:
Customer has a fleet of routers and routinely sends routers to customer locations for events. Each location/event has their own WiFi SSID/PSK. Rather than having to reconfigure routers for each event/location, geofences could be used modify SSID/PSK for each location. Rather than constant configuration changes, routers could be shipped out and depending on their destination, they would get the correct configuration.
Use Case 2:
Router installed in a work truck roams between customer locations. Many customer locations do not have cellular internet. Allowing a single router to roam between multiple geofences means that router can have a tag for each customer location that corresponds to unique WiFi as WAN profiles ensuring constant internet access.
Hi, not sure Geofencing is the way to tackle this, if you put each location SSIDs and Passwords in the WiFi WAN, it will always look for them. If you have the SIM in priority 1 and WiFi WAN in 2, it will lt always look for mobile networks. If non are available kit will switch to the WiFi network that is available. Hope this helps
Hi, Not sure which device you are using, it sounds like a BR2 or similar if it has two SIMs. turning roaming off on the AT&T and Verizon Sims, will prevent the roaming charges in Alaska. if SIM A cant find a network in Alaska, it should step on to SIM B
I think Topher’s use case is a bit more complex. For example, a cruise ship might be near the coast of British Columbia where a carrier might have a partnership with local telcos. So… Roaming would be necessary in some parts of the cruise but should be turned off in other areas.
I think the Caribbean would be a better use case where a ship is going to multiple ports/countries each with their own local carrier/telco.
By combining geofencing and the SIM injector, each port could be tied to a different SIM ensuring the best service and no roaming.
Both good comments Logan have you explored using a geofencing app running on the Docker application on the router. Not something I am expert at but it may be a solution.