Fix the naming so 2 will not fight with each other.

Max2Play Home › Forums › Max2Play Development (Ideas, Wishes) › Fix the naming so 2 will not fight with each other.

Tagged: 

Viewing 7 posts - 1 through 7 (of 7 total)
  • Back to forum
    Posted in: Max2Play Development (Ideas, Wishes)
  • Raymond Day premium
    22. Juli 2021 at 4:34 #51490

    Hi I got about 7 max2play setups and one of them on a NanoPi NEO-LTS and sound hat NanoHat PCM5102A installed Armbian buster (21.05.6) armv7l

    Have another one same setup all most the same and DD copied the Armbian setup on it and edit it /etc/host and /etc/fstab and it’s been working real good.

    Log on to it’s max2play and changed it’s name on there too.

    My LMS don’t see it some times it does but then switches back to the one I DD copied it from.

    Got 2 more maz2play setups and they get mixed up too even though the name is not the same and did not DD copy them installed both them separate so I just unplug one to have the other work.

    So I hope you can get this fix so the names don’t get mixed up. Maybe get them to know by the mac address. At least my DHCP server for my LAN don’t get them mixed up.

    Thank you love max2play.

    -Raymond Day

    • This topic was modified 2 years, 9 months ago by Raymond Day.
    • This topic was modified 2 years, 9 months ago by Raymond Day.
    Raymond Day premium
    22. Juli 2021 at 5:14 #51494

    Got a video that shows this on my Google drive.

    only 29 sec. long shows it good.

    -Raymond Day

    Raymond Day premium
    22. Juli 2021 at 5:45 #51495

    Here is the IP info on both of them just checking if the mac address is the same and it’s not.

    root@neo-doc2:~# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether 3e:34:f5:36:93:03 brd ff:ff:ff:ff:ff:ff
root@neo-doc2:~#

root@max2play-hat:~# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether 6e:08:f4:b6:e7:2c brd ff:ff:ff:ff:ff:ff
root@max2play-hat:~#

    -Raymond Day

    Raymond Day premium
    24. Juli 2021 at 0:20 #51496

    Stopped the player on my neo-doc2 but on LMS it still showed so I just clicked on to start playing then it showed 2 neo-doc2 but playing on the max2play-hat got this photo of it.

    Something is wrong were it don’t see it good. Can see in the video I link to how it auto switch back and forth from both.

    I guess there is some setting in the max2play-hat that looks that same as the neo-doc2. They do have the same CPU one is on a doc2 and one the original doc they made for them.

    -Raymond Day

    Raymond Day premium
    24. Juli 2021 at 9:36 #51497

    Because this was a DD copy of a SD card I did a find for the word like this:

    find -type f -exec grep -IH 'neo-doc2' {} \;

    Then I changed neo-doc2 to max2play-hat by hand and rebooted and looks like it fixed it.

    Guess it was in a dhcp file. Not sure were that was.

    All most sure it was in /var/lib/NetworkManager the dhclent* files.

    Now to plug in my other max2play server that is on a raspberry pi and see if it still gets mixed up with one.

    -Raymond Day

    Raymond Day premium
    24. Juli 2021 at 9:58 #51498

    Booted the max2play-justboom and it get mixed up with the one I just fixed max2play-hat. In the same way the neo-doc2 did with max2play-hat.

    There names all started with max2play. I don’t think that has any thing to do with it because LMS seen them both before I booted the max2play-justboom.

    -Raymond Day

    MarioM Moderator
    26. Juli 2021 at 12:34 #51508

    Hi Raymond,

    thank you for the detailed report. I saw at the beginning of your video that the MAC address of the player is 00:00:00:00:00. I think this is the problem! Something is wrong with the MAC address of one or both players. Please check again if they are overwritten somewhere (e.g. in the advanced settings of Squeezelite or Multisqueeze).

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.

Register here