mlgw.yaml file

Ok so I fixed bug #1, check out the repository for the new code. Not that some times it takes a little while for the source to update.

I could not reproduce #2.

are you sure you set up the MLN configuration correctly?

Giovanni

I confirm that with the new code bug # 1 has been solved, but now the last source recalled becomes the default_source. This behavior would be welcome but becomes a problem with Beovision 7 / Beosystem3. When these devices are turned off, they send various telegrams that interfere with the sources, the result is that the plug-in stores a video source as the last source-default_source, even if you were listening to the Radio or a CD. The next time any device is turned on, it will recall a video source with the consequence of turning on the TV.

I was able to understand and solve bug # 2. The plug-in to operate in a bidirectional way synchronizes the mln (masterlink node number) with the identifiers of the ml devices. The synchronization is carried out in a sequential manner, combining the mln with the responses to the commands packaged ad Hoc (I ask Giovanni for confirmation of this statement), the Beolink Converter nl/ml (blc) and the netlink devices connected to it, do not respond to these commands. In my first plug-in configuration I had inserted the blc in second place (mln 2) with the consequence that the mln - command response associations were wrong. Now I have ordered all netlink devices at the end and I have used the mln: number option. Now everything works as it should.
I attach the modified and working mlgw.yaml file.
Moral of the story: If you have a beolink converter nl/ml (blc) and nl devices, always place them at the end.


I further played with the plug-in and found that local sources are not showing on home assistant. Example: if I turn on beovision 7 (video master) by recalling a local source (TV), this is not signaled on lovelace, while everything works if I recall an audio source. If a client device has a local source (eg Beolink Active PC) equal to that of an audio/video master, home assistant will call up the local one. It would be nice to implement the LINK + source function and a different source list for each device as it is done on MasterLinkGateWay.

Thanks again for the great work Giovanni is doing.

Emanuele

Thanks for testing!

For #1, can you enable "debug" logging  and send me the log of the ml traffic with a simple interaction?  This is an interesting use case to support.

logger:

  default: warning

  logs:

    custom_components.mlgw: debug

For #2  I get the synchro issues; that's exactly what is happening. will try to see if there is a more robust way of doing the ML<>MLN matching

Here I am,

I am attaching the log you requested from me, I will try to help you by describing my Bang & Olufsen system and what I did during the log.

A. This is my ML/NL configuration:

Login to view image

B. Below are the various commands sent to Bang & olufsen devices

     18:00 With the system completely off, using the beo4 remote control, I turn on the BV7 by calling up the Radio source.

              A radio station is played but lovelace first displays the Radio source and after one minute the DTV source.

 Login to view image

 Login to view image

 Login to view image
   

 Login to view image

 Login to view image

 Login to view image
 Login to view image

 Login to view image

 Login to view image

Cool I think I found the issue. Fixing the code and releasing later in the weekend.

Ok, I uploaded new version of the code, let me know if it works!

Now the plug-in works fine for audio sources.

Lovelace still doesn't show when a device (eg Beovision7) plays a local source (eg TV). Seeing the logs maybe there is a trick, but I want to be sure. As for the Playload type 0X44 and its subtype 0X0B, I discovered some things that can help in reporting the info of the source in use on Home assistant. I am attaching a pdf with what I have discovered so far.

Listening to the ML protocol you discover new things every time ...🙂

Local sources are an issue because nothing is reported on the ML bus when you select a local source like A.MEM. For example, when I select A.MEM on the Audio Master no message is sent out.

So not sure there is a solution for this.

Please send the log from selecting TV on the Beovision and we can look for any traffic.

For the Status messages you put in the PDF for payload type, can you cut and paste the actual logs? I find it easier to read through that.

thank you!