Brokergateway only updates the NATS config on cluster changes initiated by a user, rather than SLNet trying to update NATS whenever it noticed a change, resulting in a lot of false positives. This does mean that when switching networks BGW will not update NATS of this change. Normally this can be fixed by following the procedure for changing IPs.

For people changing location a lot there is a sort of workaround: setting your NATS cluster to manual config and then updating all NATS & BGW configs to use hostnames instead of IPs.
However, from your logging it seems you have already done this?

Can you check if https://EdibSU.skyline.local/BrokerGateway/swagger/index.html is indeed reachable? If not, check if the DataMiner BrokerGateway service is running and if your hostname points to your new IP and isn't cached on the old one somewhere.

Also any errors found in the logging (C:\ProgramData\Skyline Communications\DataMiner BrokerGateway\Logs) might prove useful in figuring out the issue.

You mentioned "trying to startup NATS service". Note that with BGW the old NAS/NATS service is disabled and has been replaced with a new service called "nats-server". The old service still exists temporarily so you can easily switch back to the old NATS in case of a downgrade. The two services use the same port so can't run at the same time though. If the old NATS service is running, but you're using BGW, it will block the startup of nats-server and DataMiner won't be able to connect.