Yes I have taken the dive into Docker… Issues getting command “reboot” sent to player threw XMR. Any insite would be helpfull.
Container info below:
CMS XMR setting:
Display android XMR setting:
Android Com
Send Command Error:
:
Yes I have taken the dive into Docker… Issues getting command “reboot” sent to player threw XMR. Any insite would be helpfull.
Container info below:
CMS XMR setting:
Display android XMR setting:
Android Com
Send Command Error:
:
I’m not certain if that address in android display profile is correct, could try to leave it blank (as it is by default)?
When you do that it will use the XMR public address set in the CMS Settings, in most cases there is no need to have different addresses in display profiles.
Once you fix that, you might need to clear display cache and reconfigure XMR.
Of course I assume the player is 1.8R102?
OMG my client was 1.7 updated to 1.8
Display config address is ok and it works now.
Sorry for that LOL
Lesson for the day ( always double check you’re client version )
You definitely don’t want the containers internal IP (the 172.16) address in the XMR Public Address setting. What you have in the Display Profile Setting is correct, and you should move that in to the general settings, and leave the one in the display profile blank.
You only need to fill that field in the special case that you have clients that would address XMR differently from the others (eg where your CMS is multi-homed).