I have both - unless you have a newer beovision capable of displaying the home control menu then there is little point IMHO. I understand you use a pc based home automation solution interfaced to your MLGW (from your previous posts). I use a similar approach. For advanced users merely using the MLGW or BLGW as a gateway to a more capable automation controller then the difference is minimal. On the other hand if you are making use of drivers hosted on the B&O hardware then the BLGW has the benefit that new drivers are available for a broader range of things like hue lighting etc.

The only reason I updated was so I could see my webcams on my Beoplay V1 (basically an expensive baby monitor). I’d save my money and put it towards something more exciting like some new beolabs!

Yes, I am using the ML gateway into Domoticz, so as you say, I’ll not gain anything in switching to the BL Gateway. Thanks for the clarification!

For anyone who is interested - in my view the mlgw is available so cheaply now I think it’s a great way to access home automation from the B&O ecosystem if you’re willing to use an “always on” pc or Mac as the automation controller. Domoticz or Indigo are very good solutions and far more capable than anything natively hosted on the BLGW or BLI. For completeness I should also mention the MLGW is compatible with NL devices as well as ML devices. Quite an underrated product. 

I connected the MLGW to a Raspberry Pi running Home Assistant and it works great. No need for an always on PC... the Raspberry is more than enough to run my entire home automation.

The software to integrate the Masterlink Gateway with Home Assistant is here:

https://github.com/simonkamronn/mlgw

I connected the MLGW to a Raspberry Pi running Home Assistant and it works great. No need for an always on PC... the Raspberry is more than enough to run my entire home automation.

The software to integrate the Masterlink Gateway with Home Assistant is here:

https://github.com/simonkamronn/mlgw