I’m using player version 2 R254.1 on Windows 10, and I’m trying to use the geolocation info, from a webpage and I only get a response that the geolocation is denied.
Is there a way to enable it ? If not, is there a way to get it from the latitude and longitude information present on the player configuration ? What about the other operational system Android and Linux, are these options available too ?
PS.: Using the Geo Schedule from CMS isn’t an option, because the webpage widget is already inside a playlist.
The browser api isn’t supported via cef in windows, or in our android player (because it isn’t implemented on our side).
I think I could add it here if the device knows its own location (via the Windows Location API). You could then call http://localhost:9696/info in your web page widget to get the lat/long.
I believe I could do the same in Android too and have made a note on that accordingly.
Have access to all information about the player in a centralized point sounds great!!!
I already tested the ‘/info’ on an Android player and works great.
Any ideas when it will be available for Windows players?
I’ve got it pegged for the next release and plan to implement it this week. If I can pull together a pre-release for testing I will come back on this issue and let you know.
Hi Dan,
thanks for your dedication.
Unhappilly, it didn’t work. When I tried to access ‘http://localhost:9696/info’ from the player, I got a 404 - Not Found page (Exception type: EmbedIO.HttpException).
I tried accessing the url from a webpage widget, directly in a layout and from a web browser (in the same machine) and got the same results.
I checked the version number in the About tab of player options and it still shows 2 R254.1. To make sure that I didn’t make any mistake, I desinstalled the version and installed the new one again.
The version number still the same and the error too.
I hope it helps,
I actually know exactly whats happening - I haven’t properly handled a case where GeoLocation is not available, and that is throwing out the whole request.
Unfortunately that most likely means you’re Player isn’t able to get its location from Windows via the Windows Location API. It may be something simple like this being turned off - worth checking that!
Now it is working perfectly!!! But, you were right, the localization in the player was turned off
I installed the new version and turned on the localization and now is getting the information correctly!!
Thanks a lot!!
Now, we’ll just wait to the release of this version to put it in production!!
PS.: Is there any application for the hardware key ? I don’t see why is there…
Requested by a user who has their Xibo Display’s synced to a 3rd party system, which they then call with our hardware key to return some data specific to that Display. Quite tidy!