Replies: 12 comments 1 reply
-
|
I feel your frustration. I've been in similar situations where nothing seems to work. As to Vue, I haven't had the app installed on my mobile phone in probably 1-2 years. All I really care about is whether something is failing, and so I just needed the alerting, which is why I wrote Vuegraf. As to your steps you took, I can see why things weren't working out as you expected, as you tried the various attempts. At this point, my primary concern is that you might actually have two Vuegraf processes running and inserting data into your InfluxDB:
The result of these commands would be that you have a running Vuegraf containiner that likely is fetching and storing new data. Next you ran: And now you have a second python process running Vuegraf, which fetched historical data, and is currently fetching new data. So at this point you likely have duplicate data being stored. I would CTRL+C that interactive docker shell, and then run As to why InfluxDB isn't showing anything, you might need to provide some screenshots of the InfluxDB GUI, and the non-sensitive pieces of your vuegraf.json config so I can see if things are lining up in the Influx dropdown lists. Also, check that the InfluxDB time range is not looking at the future or some point of history. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the super quick reply! Here is the json: {
"influxDb": {
"version": 2,
"url": "http://192.168.68.195:8086",
"org": "vuegraf",
"bucket": "vuegraf",
"token": "<redacted>"
},
"updateIntervalSecs": 60,
"detailedDataEnabled": true,
"detailedDataSecondsEnabled": true,
"detailedDataHoursEnabled": true,
"timezone": "America/New_York",
"accounts": [
{
"name": "7200",
"email": "<redacted>",
"password": "<redacted>",
"devices": [
{
"name": "Panel A",
"channels": [
"HotTub",
"Attic",
"1st Floor Lights",
"Existing",
"Well Pump",
"Hot Water Heater",
"Panel Surge Protection",
"EMPTY1",
"1st Floor AC",
"1st Floor AC Compressor",
"Oven",
"1st Floor Bathroom fan",
"Dishwasher",
"Garage Lights",
"Garage/Greenhouse",
"EMPTY2"
]
}
]
}
]
}
Now before I got this output I did a full restart of the machine running these two docker instances and let them come up on their own (and they have)
Now the only place these exist as "EMPTY" are in the mobile app itself so unless this name gets pulled directly from vue's cloud service I would have expected "EMPTY1" and "EMPTY2" but perhaps they are just coming over from how I have it labeled in the official app. 
The other interesting thing I am noticing is that if I set `DetailedDataEnabled = TRUE` I get the following:
Let me know if there is something else you would like to see and thanks again for the help |
Beta Was this translation helpful? Give feedback.
-
|
Yes, as you later found, it does pull the names from the Emporia Vue account (entered via the mobile app). While the logged names match the App account names, the custom names you put in the JSON file will override the App names on the InfluxDB dashboards. The screenshot shows that it is seeing data, that's a good sign. The reason for the blank panel in the second screenshot is because the detailed data is only pulled at hourly intervals. Your chart shows it only has data for 45 mins or so. Putting that aside, is there any other missing data on the dashboard? |
Beta Was this translation helpful? Give feedback.
-
|
Yea live data (from the time I turned on or reset) the vuegraf docker instance has always worked. now im just missing historical data. Since we got to this point what would you do at this point if you wanted that historical data? ive only been running vue on this panel for ~40 days. Formatting the command in the setup instructions to my needs it ends up being: You saw the output of me doing this interactively within the docker instance but perhaps that isnt being looked at because it was a secondary python instance that pushed it? no clue. I do know that if I do the following in this exact order it will run and then stop (the docker instance): The only way I have been able to get the docker run command to work is running the version with no history: So as I do that again just now this is the output: so alright... it needs another variable when running the --resetdatabase and/or --historydays switches? |
Beta Was this translation helpful? Give feedback.
-
|
Try: Wait for that to finish loading the history. Then kill it with CTRL+C. Now, run the container again, without the arguments, and in daemon mode That container should now remain running in the background. It will also make it automatically restart if it ever crashes or the server reboots. You'll want a similar restart policy set on the influxdb container if you haven't done that. |
Beta Was this translation helpful? Give feedback.
-
Ok so before I move on are you saying I should be able to view the dashboard and see all my history? because I don't. it's still running interactively but I only see data from a few seconds ago. EDIT: to be clear -- because I know this might sound confusing -- I have never seen historical data no matter what I have done in the past. the only indication that historical data exists is in the log where it shows one line of ~15000 points coming in ...instead of the normal 16 once per minute after that point. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, at that stage, before shutting down the history load but after you see it logging those data point writes, you should be able to see the data in InfluxDB by adjusting the timeframe. Here's a screenshot showing how you can explore the InfluxDB data. See if you can find anything via that method:
The red arrows show items I clicked on to get there. |
Beta Was this translation helpful? Give feedback.
-
|
ok i see. again, many thanks for all the support. perhaps i've always had the historical data but the dashboard isn't updating. is there something I should be doing in order to see this data in the dashboard that was created for the project? |
Beta Was this translation helpful? Give feedback.
-
|
It's hard to say without seeing the raw data and screenshots of the empty dashboard. You might be able to figure it out if you click that "View Raw Data" toggle to the left of the "Past 30d" box in the screenshot I posted. It will give you insight into names of devices, panel names, account name, etc. |
Beta Was this translation helpful? Give feedback.
-
|
So this is the combined usage chart and code from the dashboard I will continue to play around but the dashboard that was already created for the project is all ill ever need there is just a disconnect in my brain on why the dashboard wont use any of the historical data but has no problem using live data (as it comes in). |
Beta Was this translation helpful? Give feedback.
-
|
Try removing one of these two lines, one at a time to see if data starts to show up:
|
Beta Was this translation helpful? Give feedback.
-
|
yeah that broke something loose. ill have to step through the query logic when I can see straight 
Taking that filter out gives me the data but also these daily spikes (assuming the 1 day aggregate) so it'll still need a cleanup later on.
Regardless this is clearly out of scope as the project itself is working fine it's just trying to understand how the db is being built up with the data from vue and if there is anything that can be done to better interpret the historical datapoints specifically vs the once per min data that comes over. regardless thanks for helping keep me sane and have a good evening |
Beta Was this translation helpful? Give feedback.
-
|
If you go to the dashboard and click on these Detail options, does any data show up?
Those spikes are expected, that's the hourly and daily aggregations. Since you deleted the detail filter it's just showing all of those aggregations. From a test perspective, it's ok that those spikes are there. The dashboard handles them already. |
Beta Was this translation helpful? Give feedback.
-
I have reset / deleted / even removed images for the vuegraf docker and had it recreate.
If I try and recreate (brand new) with the following
It will run.
But then I cannot get my historical data. so when I stop the docker instance and try the command
it fails because the container already exists.
"Ok fine. I will just blow everything away so I can run the command above"
runs, pulls images, the docker container immediately stops (yes I changed the 'myuser' so the path works)
"ok...uhh let me just start the instance and bash into it"
only influxdb docker is running...
"ok lets blow everything away again"
"ok that works, the docker instance isn't crashing at least. so maybe ill just kick off the script interactively from the docker shell"
ok now its running interactively in front of my face and after 3 or 4 minutes the output looks something like this:
Go back to the influxdb gui and refresh. nothing. no historical data, only new data.
I have probably been staring at all this for two long and I am forgetting something somewhere. I even see in the log above that the historical data is coming in...but in terms of actually seeing any of that data, visually? nada.
I am also likely out of my depth just in terms of this project. if Vue had a halfway decent graphing service I wouldnt have even needed this project. its just too dogsh*t of an application. but the data capture / hardware is bar none.
Anyway thanks in advance I hope someone can spot the stupid thing that I did to get me to this point.
Beta Was this translation helpful? Give feedback.
All reactions