If you actually read what I keep saying, it is nothing to do with port forwarding solving your problem. You seem to be fixated with various devices having particular IP addresses. The point I am making is that UNLESS you need to forward ports, it doesn't matter what IP address devices have.
I am totally confused as to what you are actually doing as you keep contradicting yourself with regard to whether devices have static IP addresses (which can only be set on the device itself, not the hub) or have DHCP allocated addresses (either reserved or not).
If you have set static addresses on the devices they should be outside of the DHCP range of the hub.
Factory reset the hub and start again.
I believe the OP is using a virtual modem on the device, one of which requires specific addresses, unless you are willing to poke around in it's "less than perfect" configuration files.
Static IP addresses are those chosen by the device, and so they normally need to be outside the range allocated by the router (but within the same subnet). As I only have the SH2 plugged in as a LAN device (so I can see some of the settings, I cannot see if the SH2 has the ability to manually allocate an IP to the device. If the SH2 does not have that ability then our OP would need to change the SH2 DHCP range of addresses in:
192.168.1.254 > Advanced Settings > IPv4 Configuration >
Start Address: 192.168.1.100
End Address: 192.168.1.227
gives DHCP 128 addresses to play with.
*depending on the DHCP daemon used manual IP addresses can usually be set anywhere sensible within the local subnet (inside or outside of the DHCP range).
**The Pi should be keeping it's own address, and just working as a bridge for the virtual modem, it's own IP should not be changing back and forth!