[quote=“Buxton, post:36, topic:199464”]I was just playing around with the software–trying to understand the capabilities based on your quote:
You don't need DataYours at all, and can link Grafana directly to openLuup.
[/quote]
Well, as usual, I have not explained things very well. It’s certainly time for an update to the documentation.
DataYours has its own Whisper database, location defined by the contents of DataYours variable LOCAL_DATA_DIR, usually ‘whisper/’. Data Historian has its data wherever you’ve set the system attribute openLuup.Historian.Directory, usually ‘history/’.
Pointing Grafana at openLuupIP:3480/, should allow its metric menus to find both databases, but I’ve just tried this, and it seems not to find the DataYours files. This is perhaps the issue you raised. I will look into it. [edit: it does work, I just didn’t have DataYours running when I tested it!]
However, what DOES work, is to add the following line to Lua Startup
luup. attr_set ("openLuup.Historian.DataYours", "whisper/") -- overriding DY finder
Assuming that your LOCAL_DATA_DIR points to ‘whisper/’, then after a restart, you should see all your original DataYours file under a metric tree called DataYours…
"DataYours.Vera-88800000.008.urn^micasaverde-com^serviceId^EnergyMetering1.EnergyUsage",
"DataYours.Vera-88800000.294.urn^micasaverde-com^serviceId^EnergyMetering1.EnergyUsage",
"DataYours.Vera-88800000.386.urn^micasaverde-com^serviceId^EnergyMetering1.EnergyUsage",
"DataYours.cpu.d",
"DataYours.memory.d",
"DataYours.unknown",
"DataYours.uptime.m",
…along with the other sub-trees generated by the historian (one for openLuup, and one for each bridged Vera.)
HTH, AK