@SmartHomePrimer: Some of the "weirdness you are seeing above has to do with where the lines and labels are. You'll have to play with it for the best results.
Everyone else, Beta version 0.1 is available. I'll go write up the changes now.
1 Like
The Nulls are normal. It's the place in the log line where "units" reside. Unit of "volts" or "amps". Some attributes don't have a unit.. Contact for instance.. no such thing as "open degrees F"
You can clearly see in your logs where Volts and % are in some rows and where On is followed by Null.
@thomas.c.howard beta working well! You may want to tidy up the install instructions in your first post... Great effort!!
1 Like
Good point; I have cleaned up the 1st post and will work on an install guide when I get some time.
4 Likes
@thomas.c.howard, thanks this looks really interesting. I tried it out this morning and didn't get very far. From the comments it looks like you HAD some instructions up, and have plans to put up some updated ones. But I couldn't find any up now and was lost without them. I got the code downloaded, created a timeline instance but had no idea how to tell it where to get is data. I clearly missed something. I'm looking forward to trying it out when you get the new instructions up. Based on the feedback so far it looks really promising. I hope your wife uses it for many years (so you keep supporting it)!
I am trying to reinstall this app and I get
Endpoint creation failed
when I hit the enable API on the time line. When I hit it for the other graph it says it did it, but I do not get the configuration screen.
What did I do wrong?
@TechMedX - When you install the code, before you save, you need to push the button in upper left hand corner" OAuth". when the code is listed on the "Apps Code" page, the column "OAuth" should say "enabled"
1 Like
thank you @thomas.c.howard I had it on for the main app but not child apps.
FYI - for documentation, you need to paste each code, and click save for it to read/load the app code. Then click oAuth, enable, close and save again.
Great app!
Documentation is updated at the top of the page.
4 Likes
Thanks! I missed the oauth part. Got it working now and it is very nice! Much appreciated!
@thomas.c.howard I've created a CSS patch in smartly for use with iframe-based tiles, making the tile content occupy 100% of the tile, borderless. I'd like to have it automatically apply this patch when people use HubiGraph (and other iframe-based tiles) within smartly.
I noticed with your attribute tiles, templateExtra appears to be set to 'Graph'. Do you plan on this staying consistent or are there plans to change it? I'm hoping to use whatever it is to detect the actual tile type and apply whatever CSS is necessary for it to look as intended.
btw great work! you're making some waves with this thing 
6 Likes
Looks awesome. I am trying to stay consistent, but who knows.... I am hoping to release something new tonight....
6 Likes
Google Chart Gauges are added. Updated the first post. Enjoy!
8 Likes
Oh snap....you know I have to try this!
Yep. 
OMG, that is so so cool.
Thank you!
1 Like
@thomas.c.howard
Thank you for the gauge graphs, I really am enjoying these. What I wanted to ask was using the line graph on my plug power monitor I can graph a lot of attributes, but when I select the gauge graph I can only do voltage, power and power factor. The attributes I can use under line graph are below.
apparentPower
current
power
powerFactor
reactivePower
voltage
Why would I not be able to use the others?
Also under the "Gauge Title" could we not set the font size and colour as a option? As well as being able to choose the update interval, 1 second, 10 seconds or is this updating real-time already?
Thanks for all the efforts in bringing this to life.
@greglsh I was experimenting with some things and never got the device selection cleaned up. I have just submitted an update that is cleaner/faster but still filters the "supported attributes" by two requirements:
- The attribute must be defined as a NUMBER (this is a Google Gauge requirement)
- The attribute must have at least a current Value. I.e. I don't want people asking why nothing is happening for a selected attribute that NEVER updates.
Give it a try,
