Khimo Support wrote:

The MLGW protocol driver will allow the integration of MasterLink products on the BLI using a MLGW or BLGW as MasterLink interface.

Which means, that - if you are new to the BeoLivingIntelligence-stuff and you still have old ML devices and the NL/ML Converter - you would still have to use/get a MLGW or BLGW in addition to the BLI, right???

That’s a lot of boxes ;-(

MM

Khimo Support wrote:

beojeff wrote:

I think that this forum would be a great place for you to explain this new ML driver so that we could all understand it better. There is no information about it on either the BeoIntegration site or the Khimo site. I'm sure there are many on this forum like myself who have a lot of classic ML products and are uninterested in moving to the BLI if it means losing control of those classic products. 

Very good point. Please note that this driver requires version 2.1.0+ on the BLI, and an update on the BLI App (both under internal test by now).

 

The MLGW protocol driver will allow the integration of MasterLink products on the BLI using a MLGW or BLGW as MasterLink interface.

 

The MLGW/BLGW should have MasteLink Gateway protocol enabled, and all the MasterLink devices should have a MLN [1] assigned. This MLN will be the address of the resource on the BLI.

 

On the BLI side, the available resources are:

 

- MasterLink video product: will send all the commands to the MasterLink VIDEO destination.

- MasterLink audio product: will send all the commands to the MasterLink AUDIO destination.

- MasterLink room: allows to track IR light and control inputs in a room, and can be used to track IR events and fire macros on the BLI.

 

Once the configuration is ready on the BLI, the devices can be controlled using the BLI App in a way similar to any other B&O audio/video device.

Hope the info helps,

Best regards,

the Khimo team.-

 

1 - An MLN numer identifies each product on the MasterLink network, and is assigned during the setup of the MLGW/BLGW.

So all of the macros and systems other than the B&O ML system are programmed on the BLI and nothing is really programmed as far as macros and systems on the MLGW/BLGW? For example, if we want the command "CONTROL 12" to be used as a trigger to set the thermostat to 70 degrees, we program that macro just on the BLI and not on the MLGW/BLGW and then rooms with an NL product that receives CONTROL commands and rooms with an ML product that receives CONTROL commands both can forward those commands to the BLI for macro execution?

Is an MLGW just as capable as a BLGW in integrating ML devices with the BLI?

Hi Khimo Team,

does the new "MLGW protocol driver" bring any enhancements to the BeoSound5 experience? Will it be integrated in the same way like it is in the BLGW (and even MLGW) with covers and search? Or is it still implemented as  an "ordinary" MasterLink device that has no further functionalty?

Thanks for a short reply.

Best regards

Doc Leisure

Millemissen wrote:

Which means, that - if you are new to the BeoLivingIntelligence-stuff and you still have old ML devices and the NL/ML Converter - you would still have to use/get a MLGW or BLGW in addition to the BLI, right???

That’s a lot of boxes ;-(

MM

Hi MM,

If you have a NL/ML converter then you already have the ML sources shown on the apps as NL ones, so you won't need a MLGW/BLGW.

Best,

the Khimo team

beojeff wrote:

So all of the macros and systems other than the B&O ML system are programmed on the BLI and nothing is really programmed as far as macros and systems on the MLGW/BLGW? For example, if we want the command "CONTROL 12" to be used as a trigger to set the thermostat to 70 degrees, we program that macro just on the BLI and not on the MLGW/BLGW and then rooms with an NL product that receives CONTROL commands and rooms with an ML product that receives CONTROL commands both can forward those commands to the BLI for macro execution?

Is an MLGW just as capable as a BLGW in integrating ML devices with the BLI?

Hi beojeff,

Exactly, the BLI driver uses the BLGW/MLGW only as MasterLink interface, all the macro programming for your home can be made on the BLI.

Best,

the Khimo team.

DocLeisure wrote:

Hi Khimo Team,

does the new "MLGW protocol driver" bring any enhancements to the BeoSound5 experience? Will it be integrated in the same way like it is in the BLGW (and even MLGW) with covers and search? Or is it still implemented as  an "ordinary" MasterLink device that has no further functionalty?

Thanks for a short reply.

Best regards

Doc Leisure

Hi Doc,

On the first version the ML devices will be shown as "ordinary" ones, without covers and search.

Best regards,

the Khimo team.-

Khimo Support wrote:

Millemissen wrote:

Which means, that - if you are new to the BeoLivingIntelligence-stuff and you still have old ML devices and the NL/ML Converter - you would still have to use/get a MLGW or BLGW in addition to the BLI, right???

That’s a lot of boxes ;-(

MM

Hi MM,

If you have a NL/ML converter then you already have the ML sources shown on the apps as NL ones, so you won't need a MLGW/BLGW.

Best,

the Khimo team

Thanks - that indeed, makes the BLI a bit more interesting.

MM

Khimo Support wrote:

Hi Doc,

On the first version the ML devices will be shown as "ordinary" ones, without covers and search.

Best regards,

the Khimo team.-

Hello Khimo Team,

thanks for the answer and sorry for insisting ;-)

Does "on the first Version" mean that there are further versions in planning that would offer an extended experience for the BeoSound 5 - covers, search & PlayQue.

Really looking forward - please.make it possible!

Best regards

Doc Leisure

Khimo Support wrote:

Millemissen wrote:

Which means, that - if you are new to the BeoLivingIntelligence-stuff and you still have old ML devices and the NL/ML Converter - you would still have to use/get a MLGW or BLGW in addition to the BLI, right???

That’s a lot of boxes ;-(

MM

Hi MM,

If you have a NL/ML converter then you already have the ML sources shown on the apps as NL ones, so you won't need a MLGW/BLGW.

Best,

the Khimo team

Khimo-

That isn't quite correct. With the NL/ML converter, you see just audio master and video master sources ML products on the NL network. However, this is not integrating link-room ML devices. Previously, you had mentioned to me that using the converter with a BLI would not give full control of ML devices such as we had on the BLGW. Also, those link room devices would not be able to transmit LIGHT/CONTROL commands since they would not be nodes on the BLI. Could you elaborate more on this? I thought that the ML driver integrating an MLGW/BLGW would fill in the gaps of this loss of control. There is much that we really need to understand.

As MM commented, the BLI needs a lot of boxes to integrate ML products. It would have been far more elegant to have just kept an RJ45 ML connection with the BLI!

Khimo Support wrote:

beojeff wrote:

So all of the macros and systems other than the B&O ML system are programmed on the BLI and nothing is really programmed as far as macros and systems on the MLGW/BLGW? For example, if we want the command "CONTROL 12" to be used as a trigger to set the thermostat to 70 degrees, we program that macro just on the BLI and not on the MLGW/BLGW and then rooms with an NL product that receives CONTROL commands and rooms with an ML product that receives CONTROL commands both can forward those commands to the BLI for macro execution?

Is an MLGW just as capable as a BLGW in integrating ML devices with the BLI?

Hi beojeff,

Exactly, the BLI driver uses the BLGW/MLGW only as MasterLink interface, all the macro programming for your home can be made on the BLI.

Best,

the Khimo team.

You didn't answer the second part of my question. Is there any advantage to using a BLGW over an MLGW with the BLI?