Google cloud integration error

Cloud
1

My goal is to log some data from vibration sensors into a database (ideally SQL). (Fair warning: I have no idea what I’m doing).

So far I’ve been trying to follow the Google Cloud integration tutorial (https://github.com/spark/google-cloud-datastore-tutorial).

I’ve followed the tutorial but whenever I run the final node tutorial.js, it seems to authenticate successfully but then I get this error:

events.js:160
  throw er; // Unhandled 'error' event
  ^
Error: Resource not found (resource=testing).

I can’t figure out what is triggering this error. I also don’t know if there are easier ways to accomplish my goal.

Any advice would be much appreciated!

2

Hello,

Sorry for the delay in responding to your post! I’m going to ping someone that will hopefully be able to help you. @bryce are you able to figure out what is triggering this error?

Kyle

3

@jeiden wrote that tutorial so might have a better idea of what causes that error. I would make sure you have everything created in Google Cloud and the configuration in the example code updated to match.

1 Like
4

@bryce Thanks! I think I got everything in the tutorial created, but am a little out of my depth. Any other suggestions for storing basic data for analysis? Could it be as simple as using an IFTTT to add data to a Google sheet?

5

@lukem1 I’ve ran into this previously. you may need to update your npm packages…

6

@jeiden I am working on the same tutorial, but cannot get the integrations to talk to the GCP, nor manually publish events to GCP. My command
gcloud beta pubsub subscriptions pull electronMapperPUBSUBtopic --limit 100
generates 0 results on GCP.

Any suggestions?

7

@rickkas7 can you try and help @MikeP171 here?

8

I went through the tutorial step-by-step and aside from a few minor changes (–max-messages to --limit for example) it appeared to work for me.

Are the events showing up in your Google Cloud integration in the Particle console? Beyond that, I’m not sure what the problem could be.

You could try using the Google web shell to rule out any problem with your local gcloud tool.