P.S fiveHellions - If your making changes and you come across the bit of code that sends the rest request to OSA and could make the update it would be much appreciated. I might be on the wrong track as I haven't looked at the problem.
I finally got around to installing your app. Thanks for developing it.
Installation seems to have completed without any problems. What is the Object Name specified in the setup wizard used for?
Also, if your Android device is configured for multiple accounts does the registration happen on all of them or just the default account?
That way if you have a phone and a tablet and your wife has a phone, you can send messages to one particular device instead of all of them. Same with triggering tasker tasks.
As far as multiple accounts, do you mean the multiple users that google implemented with 4.2 for tablets? (some custom phone roms implement it as well) Or do you mean one user of the phone with multiple google accounts tied to it?
To be honest the answer either way is I'm not sure. The registration is with Google Cloud Messaging, when you register a device it gives you back an unique id to be able to send messages to that device. If you mean the former, I can do some testing on my nexus 7 and see if it gives a different id if you register the device under a different user. My thought is that it will generate a different ID so you would need to have an separate object created in OSA for both user of the device. But I will test and let you know.
For some reason my Android device is not getting created in OSA. I see an Android Device Type but no object. I'm running OSA 0.4.2. Is this dependent upon the latest code from the OSA repository
Are there any messages in the Rest log file?
You can try to pull a logcat off of your phone, that may give more info about why it isn't working. First go into the settings in the app and click verbose logging. Then you can download a logcat reader from the google play store. Try the wizard again then go read the logcat.
I think having multiple google accounts should be fine, but I will test adding another google account to my phone and make sure.
Alternatively if you can't get it to create the object in OSA. you can create one manually (object type ANDROID DEVICE). Once you have it created then you will need to enter the GCMID in the property for the object. Go into the app settings and you will see the GCM Registration ID, if you click it it will give you the option to share it and you can email it to yourself so you can copy and paste and not have to type the whole thing.
I then tried to manually notify from the objects page, and got the same error in the android log.
Code: Select all
06/17/2013 09:46:13.607 PM - Found Command: NOTIFY | param1: Hello OSA | param2: default,5 06/17/2013 09:46:13.637 PM - Added AndroidDevice to list: JeremyPhone 06/17/2013 09:46:13.650 PM - NOTIFY event triggered (JeremyPhone), parameter_1=Hello OSA, parameter_2=default,5 06/17/2013 09:46:13.654 PM - address = 06/17/2013 09:46:13.657 PM - GCM response new version = [ERROR] Device Token or API Key has not been set 06/17/2013 09:57:15.620 PM - Found Command: NOTIFY | param1: not working still? | param2: default 06/17/2013 09:57:15.793 PM - NOTIFY event triggered (JeremyPhone), parameter_1=not working still?, parameter_2=default 06/17/2013 09:57:15.798 PM - address = 06/17/2013 09:57:15.803 PM - GCM response new version = [ERROR] Device Token or API Key has not been set
I probably should have not included the owner property since it isn't used yet.
The main interface shows the mobile Web ui. I think it is set up to show places and let you drill down from there to individual objects.
I remember when I first tried to use the mobile Web ui mine was blank because I hadn't set up any place objects.