I am currently building an application that is pretty similar to digital signage, But I would like to get some UUID or serial number on the chromecast to identify them on the serverside. This UUID/Serialnumbner would be used to determine where the chromecast is located and display the data accordingly for what is set up.
Is this even at all possible? Because all earlier questions resulted in an no and were asked a few years ago.
Solutions where I generate an UUID myself with data that is consistent on the chromecast are also fine.
I have fixed this by using the localStorage on the chromecast and generating an token on my own.
I am currently running some tests how long that storage will persist
It is not affected by reboots
Related
I am working on a IoT Project, where I need to deploy 700 beacons in different parts of the country.
Whenever a user(assuming the required services are enabled on the user's phone), the user should get a silent notification of a link to a webapp and if there's an Android/iOS app(for registered users) it would display an update notification.
I have implemented this functionality, so that's already done.
My problem is I have to configure every single beacon manually, which I would like to get it done via a script or an API, because there's a possibility I may have to do the same for 1000+ beacons.
I am using RadBeacon Dot Beacons
Configuration Process Details:
Configuration Doc Of Beacons
Configuration through the Beacon App
Setup a Google Nearby Beacon
How can I automate the entire configuration process for both Android & iOS ?
Little guidance will be highly appreciated.
Thanks
I would email or call support at Radius Networks and ask if you can get access to a private SDK to configure your beacons for iOS, MacOS or Android.
If you can get your hands on such a SDK, you could build an iOS, MacOS or Android app that does all of these configuration steps. You will still, however, need to put each RadBeacon Dot into configuration mode one by one and wait for your custom configuration app to connect via bluetooth and configure the beacon. Since bluetooth connections can be a bit finicky, this might take 5 secs or more with retries. So best case scenario, you're talking 5 secs x 700 = one hour to get them all configured.
You'll also have to account for the time it takes you to write the config app and debug it until it is working reliably and as quickly as possible. I have lots of experience with these kinds of apps, and would expect it to take me at least 8 hours, probably much more. So the best case level of effort to get all beacons configured is 9 hours.
The alternative, of course, is to train an intern (or your little sister) to do this manually, and pay him or her for the trouble. If you can get all these manual steps done in 45 seconds, doing 700 of them will take a little less than 9 hours -- faster!
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I'm hoping to create some sort of attendance register by using iBeacons device. I was wondering if it's possible to hook it up to some kind of database to store which devices have passed it?
From what I have found there isn't a lot of documentation about how to store information in the iBeacon device.
Feel free to link anything interesting and thanks in advance.
Yes, this is possible and it is a very common part of building beacon applications. The typical approach is to do the following:
Make a mobile app that:
Generates a unique device identifier on first run, for later passing to a server. Send this to the server via a web service call along with name, email, and any other info you want to collect to identify the user.
Detects beacons, passing the beacon identifier on first detection to a web service along with the device identifier from (1)
Optionally store the detections in a debice-local persistent data store, in case connectivity is notvavailable at the time of detection so records can be sent to the server later.
Make a server side app that:
Has a database that stores beacon detevtions tied to a mobile device identifier, along with a timestamp.
Has a database table that assigns meaningful location info to unique beacon identifiers.
Exposes a web service to record detection records sent by the mobile app.
Exposes a web service to register a new device identifier and tie it to user info like name, email, etc.
Add additional logic and perhaps web UI to show the results of specific devices being in beacon-specific places at specific times.
Building an app that does this can vary quite a bit depending on the specific use case. This is why it does not lend itself to cookie cutter solutions easily linked to on the internet.
We have a number of TVs where we want to display dynamic content. This is very similar to the built in Chromecast application that displays photos and art from Google, the major difference is that we have a mixture of photos and videos, and want to display for instance a whole video clip, then a few photos for 30 sec. each, then another video, then more photos, and finally when all is done, cycle through the whole thing again. We want to do the setup once for each Chromecast/TV, then let it run for days or even weeks.
One option could be a web server displaying the whole sequence repetitively on a specific web page url, and then have the Chromecast display its assigned web page. I looked at the development docs. and I suspect that I will need to develop a Chrome Sender application and use the standard receiver application on the Chromecast. It is not clear for me if the sender (Chrome) needs to run all the time, or once the setup is done, the Chromecast knows which url to display and can then be left alone for days.
We hope to replace dedicated servers and software that connect to the various TVs, and the Chromecast offering customization could be a very inexpensive solution.
Maybe this does not make sense, let me know!
The sender can be a chrome sender or a native app on an Android or iOS device; as for the receiver, you would need to write a custom receiver; that receiver, which is basically an HTML5 page, can receive the whole schedule (urls, etc) at the very beginning, or it can fetch the schedule dynamically from a certain server, etc. Once the receiver starts, your sender doesn't need to stay connected but if for whatever reason your chromecast is rebooted, or loses connectivity, etc, your sender would need to start your application on the chromecast again; there is no magical way for chromecast to start your app automatically.
I am currently looking for the best way to test my receiver app code. I would like to know if there is a way to have a non-production version of the receiver app code running, which is not visible to my users, so that I can test new functionalities without possibly breaking others that are currently live and in production. So far I have been doing trial and error with small snippets, but this is far from optimal.
My final goal is to be able to create different GIT branches of my code, which I can test on my Chromecast that is not visible to the public.
Thanks
One approach is to create another app id to be used for testing/development; as long as you do not publish that app id, no other device but your registered devices can see that app.
I working on a project were mobile users can receive alerts based on diferent factors, the server side will be implemented using the MVC framework.
My question is regarding the client side; what would be the most efficient way to send the alerts to the clients? is there any way to broadcast the alerts to each device or do I have to set up some system where each device pulls the data from the server on an interval of mins/seconds? I am afraid pulling the data every X secs/mins would create an unnesesary overhead on the mobile devices.
One way would be using SMS but SMS gateway services are expensive and not on my budget right now.
I haven't personally tried it, but this service might work for you:
http://www.airgramapp.com/api
It is free for limited use. Downside is it appears to be a separate install on the mobile device. This might means less control of the content of the message or its look. Upside is it looks quick and easy if you just need a proof of concept at this point.