Initial Setup Failing

[EJansenMSFT]

Hi Team,

Just found this project and thought i'd give it a go, but in trying to get up and running, I'm having an issue that I'm hoping someone can help me out with. After reading through everything, I just customized the sample docker-compose.yaml and vuegraf.json files.

After doing that, I just run:

docker-compose -f docker-compose.yaml build --pull && docker-compose -f docker-compose.yaml up -d

From there, it builds all of the containers, as seen here, except the vuegraf container just constantly restarts:

It doesn't really give an error, it just says the following:

I just used the default "influxDB" portion within the .json file, as I've never used InfluxDB before, so i'm not sure if that has something to do with it or not?

I found this in the vuegraf.py file:

What am I doing wrong?

Thanks ,
Eric

[jertel]

Try updating the vuegraf.json file with "host": "influxdb", instead of my.influxdb.hostname.

[EJansenMSFT]

For some reason it's still doing the same thing:

:/

[jertel]

Is your grafana instance able to connect to the influxdb?

[EJansenMSFT]

Well, I can see that the influxdb is listening on port 8086 on the server here:

I've never used either Grafana or InfluxDB before so it's a bit of a learning curve. I can see that if I log into the Graphana page though that i can add a data source. In plugging the info in that was in the .json file, it appears to be good:

[EJansenMSFT]

Ah yes, waay better logging now:

[jertel]

Ah. It's trying to hit api.emporiaenergy.com over https. Check your outbound firewall rules, or whatever else is blocking it. Should be good once you find that restriction.

[jertel]

Oops, I read that too quickly. It's still stuck on InfluxDB isn't it.. Try putting that back to influxdb and see if you get past that error.

[EJansenMSFT]

Sure enough:

Hmmmmm.. I'll maybe try to re-type it in there. It should be the same username / password that I use in the app, I would think. I don't know if there's separate creds on their site or not.

[EJansenMSFT]

HAH, nope, it was me - one character had the case off. That fixed it immediately:

Great support! Thanks a ton!

Now I just need to figure everything else out. ;)