I need help for problems of XMR. I’ve running CMS with Ubuntu Server 18.04 & Docker. CMS running well and all requirements are installed so I want to push communication to player with command;
So XMR already connected to my tcp but still doesn’t work. Make sure for Reconfigure XMR on Display Edit but yes, still doesn’t work and I got this error message;
Why error? I’ve installed ZeroMQ and XMR on my CMS and I already set to my tcp on Setting like this;
I’ve completed this step for true command shell and still not working. But this topic was solved by allow TCP 9505 from AWS Security Groups. So, the problem is need more to config network communicate on AWS.
Yes, I’m using AWS for CMS. Your answer is important for Developer who using another VPS or etc.
@frederic_Horcholle
Hello, I installed xibo on a web server and downloaded the android player and successfully connected it to my android device. The content I want to send is reflected on my android screen. As you can understand, everything works fine but there is one thing that is not working. Whatever I did, I couldn’t send a command to my Android screen, does anyone have any information? According to some forums, I need to open port 9505 as tcp. But I didn’t want to open it without getting information from you, can you help me? All the changes I made are in the screenshots below.
Close screen command in Screens > Commands
su -c “am start -a android.intent.action.ACTION_REQUEST_SHUTDOWN”
Hi Gorkem, according to me port 9505 is not mandatry, only used when you need to push on synchronize contents between displays at onse, that my compréhension of XMR port (9505).
I only use Windows players so I don’t really know how to use android command.
I understand that you want to send a command to ou android device to shut it down, right ?
Sending command to a windows player does’t need the 9505 port.
See you
Fred
@frederic_Horcholle
Hmm, I see, so it’s not the port. Can someone who knows what steps I should follow to send the shutdown command to my Android screen in a healthy way and make it work?
OK, if it can help you, on windows player,
I schedule a task to kill all xibo process then turn screen saver on to snooze screen after 5 minutes (20h30), then I reboot the player in the morning. (6h30)
This make the screen off (because of power management) and the reboot awakes the display.
The windows player is still alive but in power saving mode (~2/5w/h instead of 30w), the screen is in power saving mode aswell (2 w/h instead of 100W). If your goal is to save energy
, that the way I do , may be you can adapt this to android and share it here.
I understand, it’s really nice that you are trying to help. But this is not what I am asked to do, I am asked to turn off, turn on and restart the Android screen with commands. I have browsed a few forums and it is said to be caused by port 9505. Since xibo is installed on a domain, I think the firewall gets stuck when sending commands.
OK ok I understand.
I think it could be difficult to turn on a player off by a command line, as it is off. But I’m not an android expert. I thought you was just trying to save energy, I need to improve my android skill sorry.