You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have noticed that some people success with poweron command but failed to use all other commands (including poweroff, volumeup, select source, etc.). Let's make a new issue and gather information here.
To clarify again, this integration contains two completly different communication ways with the projector:
Bluetooth BLE advertisement: This is used for poweron only. It requires:
token: "12D7C7899B9F80FFFFFF3043524B544D"
UDP via LAN: This is used for all other commands like poweroff, volumeup, etc. It requires:
host: 192.168.0.115
Whether the BLE poweron function works can not provide any clues that other commands through UDP will work, and vice versa.
For BLE poweron issue, please read the README carefully, and you can also find more info in #5 and #13 .
For other commands through UDP, if it is not working for your device, consider the followings:
Make sure the IP address of your projector is correct, you can check this in the projector's setting or in your router.
Make sure your projector IP is accessible from your HA host machine.
If still not working, let's make some debugging: turn on the projector and use nmap to see if these three UDP port is open:
make sure to replace the IP address 192.168.0.115 to your projector's IP.
The port 16735 and 16750 are necessary to control the projector. The port 554 is used to check the projector's power status, it only works for some of the XGIMI devices.
If these UDP ports are not open, it is very like that your XGIMI projector uses another protocol, this could happen in the international versions of XGIMI projectors (compared to the China version). This is just my assumption as I only get China version XGIMI projectors at hand. If that is the case, try the official Android TV integration.
To help us understand it better, let's gather the information here:
1. Your XGIMI model?
XGIMI z6x
2. Does the BLE poweron command works for your?
Yes.
3. Do the UDP commands work for your?
Yes.
4. Your XGIMI OS versions and Android versions (or screenshot of the setting pages):
5. Are these UDP port open? check by nmap
Port 16735: Yes
Port 16750: Yes
Port 554: Yes
6. Does the [Android TV](https://www.home-assistant.io/integrations/androidtv_remote/) integration work for you?
The text was updated successfully, but these errors were encountered:
1. Your XGIMI model?
XGIMI HORIZON (XK03H)
2. Does the BLE poweron command works for your?
Yes.
3. Do the UDP commands work for your?
No.
4. Your XGIMI OS versions and Android versions (or screenshot of the setting pages):
OS: 0X.2.6.139 / Android: 10
5. Are these UDP port open? check by nmap
Port 16735: No
Port 16750: No
Port 554: No
6. Does the [Android TV](https://www.home-assistant.io/integrations/androidtv_remote/) integration work for you?
Yes
I investigated on the ports and it seems that only TCP port are opened in my projector:
I have noticed that some people success with poweron command but failed to use all other commands (including poweroff, volumeup, select source, etc.). Let's make a new issue and gather information here.
To clarify again, this integration contains two completly different communication ways with the projector:
Bluetooth BLE advertisement
: This is used for poweron only. It requires:UDP via LAN
: This is used for all other commands like poweroff, volumeup, etc. It requires:Whether the BLE poweron function works can not provide any clues that other commands through UDP will work, and vice versa.
For BLE poweron issue, please read the README carefully, and you can also find more info in #5 and #13 .
For other commands through UDP, if it is not working for your device, consider the followings:
192.168.0.115
to your projector's IP.The port 16735 and 16750 are necessary to control the projector. The port 554 is used to check the projector's power status, it only works for some of the XGIMI devices.
To help us understand it better, let's gather the information here:
The text was updated successfully, but these errors were encountered: