metabase metacloud android problem
Hi, New Kickstarter 2 senosr guy, Bradshaw in Buzzards Bay, sensing everything in the speedy cold cape cod canal.
I have 2 sensors that work perfectly with metawear, fully charged, running, up to date, AMAZING, thank you.
I have 3 androids a LG34c rooted android 4.4 an LG15C not rooted android 4.4 and a neat Samsung Galaxy Express 3 android 6.0 all with Metawear and Metabase installed.
I watched the Metabase tutorial. Just once, on I don't know which android, I saw the two sensors appear, But I was brand new, and did the wrong things and got no data.
I have a paid up (for a month!) metacloud account.
Starting every thing (androids) from off, and powering up. I never see the two sensors in METABASE. Right afterwards I look and run them perfectly from metawear. The bluetooth on all three androids sees the two sensors. and I don't try to connect from there, however they are very visible at the android OS level as well.
I am certain that this is NEW GUY CUSTOMER error, It always is.
Thank you for the guidance I badly need!
p.s. I am a 36 year firmware device OS engineer from DARPANET and MULTICS days and currently a BLE and ham radio moonbounce stack engineer, and in awe of this stuff! mbientlab is the best stuff ever. (until 17 months from now!)
Thanks, Bradshaw
I have 2 sensors that work perfectly with metawear, fully charged, running, up to date, AMAZING, thank you.
I have 3 androids a LG34c rooted android 4.4 an LG15C not rooted android 4.4 and a neat Samsung Galaxy Express 3 android 6.0 all with Metawear and Metabase installed.
I watched the Metabase tutorial. Just once, on I don't know which android, I saw the two sensors appear, But I was brand new, and did the wrong things and got no data.
I have a paid up (for a month!) metacloud account.
Starting every thing (androids) from off, and powering up. I never see the two sensors in METABASE. Right afterwards I look and run them perfectly from metawear. The bluetooth on all three androids sees the two sensors. and I don't try to connect from there, however they are very visible at the android OS level as well.
I am certain that this is NEW GUY CUSTOMER error, It always is.
Thank you for the guidance I badly need!
p.s. I am a 36 year firmware device OS engineer from DARPANET and MULTICS days and currently a BLE and ham radio moonbounce stack engineer, and in awe of this stuff! mbientlab is the best stuff ever. (until 17 months from now!)
Thanks, Bradshaw
This discussion has been closed.
Comments
When I take a new android (I have too many to admit) In metabase, I can connect to the fob, config, select 3 sensors accel, barometer, and gyro, happily collect for three minutes, then stop, download, it has me login, which I successrully do.
It says it synced but my data doesnt show up on the web. (same login and password)
THEN, when I go back to metabase, I no longer can connect to the fob, it is not visible, the second fob is not fisible. I am stuck with s non functioning metabase.
HOWEVER, when I go into metawear I see both fobs, both work beautifully.
I am a pretty good retired firmward engineer, I have tried the normal shutdown restart, only erasing the android and reloading metabase gets me running, and again syncing, but no data appears on the dashboard on the web.
this has to be user misuse, but I just don't see it yet. Thanks, Bradshaw
Love the tools, gotta see metabase work with the dashboard before I jump both feet into the API.
tnx,
slow response on my part. I am working a project that WILL involve this sensor, underwater, in the Cape Cod Canal.
WILL DO and get back to you.
I just got charged $5 for my 2nd month of the service.
I know this is old engineer error. So the blame is already placed!!! Thanks, Bradshaw