trying to get bifravst working

[Calin M]

Hi Markus Tacker (he/him),

I am following the instructions here:

https://bifravst.gitbook.io/bifravst/bifravst-on-aws/simulator

to deploy the web application, and the web application says:

Connecting to http://localhost:1234 ...

Which is probably not right.

When I use node cli connect, and open the url in the browser, this one also tries to connect to localhost.

Any suggestions for getting it running in the cloud? I mostly want to get this working n the cloud, with a real device, but how would I run the application locally?

Thanks,

Calin

[Markus Tacker (he/him)]

Hei,

this

Calin M said:

[0m[00:05:43.845,214] [1;31m<err> aws_iot: mqtt_connect, error: -22
[0m[00:05:43.851,501] [1;31m<err> cat_tracker: cloud_connect failed: -7

and this

Calin M said:

node cli connect deviceID tries forever to connect, and never manages.

show that neither the real device nor the simulator can connect to your AWS IoT broker.

Did you follow the set-up guide for your AWS account? 
https://github.com/bifravst/bifravst/blob/saga/docs/aws/GettingStarted.md

[Calin M]

Yes, I did. The device ID did appear under AWS IOT  / Manage / Things and there is a recently updated shadow document..

[Markus Tacker (he/him)]

Calin M said:

For instance, I seem to be getting a 404 on the geolocation api:

The 404 is returned if a specific cell is not known (neither by your devices previous geolocations nor Unwiredlabs [if you have enabled it]), so this is expected.

Calin M said:

Also, the red circle that indicates the device hasn't synced the settings seems to stay on for quite some time.

It should propagate to the device quickly, so double check that your device is connected, the configuration change should show up on the logs. Note that it will only check for new settings after the next cycle (e.g. in passive mode once movement was detected). In order to save power the device does not listen to configuration changes all the time.

[Markus Tacker (he/him)]

I did some further testing and can confirm the when the device is running, it no longer reports back the configuration changes: https://github.com/bifravst/firmware/issues/39

[Calin M]

Thanks for letting me know. Also, regarding the geolocation API, I did follow the instructions for setting it up and I did check that unwired knows about my cell tower, I called the API directly. It was a 404, as if the web app didn't know where the rest service is.

Was I supposed to redeploy the web app after I enabled the unwired api, or just the aws stack?

[Markus Tacker (he/him)]

No, the web app already knows about the Geolocation API endpoint (REACT_APP_GEOLOCATION_API_URL).

Calin M said:

I called the API directly.

What was your query?

You can look at the Step Functions execution which resolves the cell geolocations to see what happens:

[Calin M]

I'll have a look at the step functions.

This is what I see in the browser log

https://yoe7p62wj1.execute-api.us-east-1.amazonaws.com/v1/cellgeolocation?area=11009&cell=28311820&mccmnc=302220

HTTP/2 404 Not Found
date: Wed, 01 Apr 2020 08:52:55 GMT
content-type: application/json
content-length: 2
access-control-allow-origin: *
cache-control: public, max-age=86400
expires: Thu, 02 Apr 2020 08:52:55 GMT
X-Firefox-Spdy: h2

[Markus Tacker (he/him)]

Yes, this happens if the cell is not resolvable.

Note that the resolution result (even the negative one) is cached in DynamoDB for 24, so look for an entry in the bifravst-cellGeolocationcellGeolocationCache... table and remove it to trigger the resolution step function again.

[Calin M]

Strange. I logged into the unwired API entered all the numbers manually and it resolved correctly. I'll try to purge the cache