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)]

Can you double check that you are using the right hostname format in your prj.conf?

(Error -22 points to an issue with that: https://github.com/bifravst/bifravst/blob/saga/docs/devices/TroubleShooting.md#error-code--22)

Get your endpoint using: 

aws iot describe-endpoint --endpoint-type iot:Data-ATS | jq -r '.endpointAddress'

The ID for the certificate must match the IMEI of the device.

To verify can you generate a device certificate and send it to me via email ([email protected]) so I can try to connect from my end.

[Calin M]

Hi Markus,

I emailed you the keys and the endpoint.

Thanks!

[Markus Tacker (he/him)]

I have not received it, yet.

[Calin M]

Maybe the email was blocked because if the tgz attachment. I attached the keys as text and sent it again.

[Markus Tacker (he/him)]

Thanks, I got them.

Using those I cannot connect, so either

• this device already exists with a different certificate, so the Just-in-time provisioning will attach the certificates to the new device -> create a new set of certificates and send them to me again (node cli create-device-cert)
• there is something wrong in your account with regards to the just in time provisioning. If this is a blank / development account, could you set up an IAM user for me so I can poke around, what might have gone wrong?

[Markus Tacker (he/him)]

[Calin M]

At some point  i must have regenerated the certificate, because the cert on my box was different from what was on AWS. I dropped everything and started from scratch. Now it works.

Thank you so much for prompt help!

BTW, the application is very nicely written, I think it's a great example for using a bunch of technologies. I have something to play with for a while

Cheers,

Calin

[Calin M]

I will probably have more questions.. For instance, I seem to be getting a 404 on the geolocation api:

https://yoe7p62wj1.execute-api.us-east-1.amazonaws.com/v1/cellgeolocation.....

I did create a token and redeploy..

Also, the red circle that indicates the device hasn't synced the settings seems to stay on for quite some time. The device is sending data, but does not seem to read the new settings.

Thanks!

[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