Hubigraphs 4.8 (The Final Chapter)

[habitat]

I am new to HE and VERY new to Hubigraphs

When I try to graph Temperature for a built in Thermostat Controller - I have no issues with a New Line Graph (Deprecated).

However if I use New Time Line Hubigraph finds a lot more attributes for the Thermostat Controller including TWO Temperature attribs.

If you select either Temperature attribute and Update it Hubigraph automatically selects BOTH Temperature attributes and then gets stuck on 4/4.

Not sure what is going on here, but I am using the standard, built in Thermostat Controller App and resultant Devices.

[habitat]

Ok used a Time Graph and that was Ok and did not have the two Temperature Attributes

[habitat]

What is the best way to graph a switch state over time?

ie - I would like to create a graph that shows when and how long the central heating (zwave) switch was turned on over the last 24 hours.

More complicated is to Show both when The Radiators (Boiler zwave) switch is on and off and The Hot Water (2nd Boiler switch) is on and off

I have not been Able to get a good result yet.

I have been trying multiple ways but nothing that looks reasonable

The best is one I did to track two zwave switches - Scenters for Lounge and Kitchen

[thomas.c.howard]

I would suggest using a TimeLine

[habitat]

Thanks will try that!!

[sherwoodbiz]

Thanks again for the manual install instructions worked great. Really like your app and have used it for a number of items.

I ran into a problem building a Weather Tile 2. After initial setup and use, I slowly modified or added items to the default view. Got 95% done and then got the following log error:

2021-01-16 10:54:35.257 am errorjava.lang.NullPointerException: Cannot get property 'parse_func' on null object on line 1554 (getGraph)

At that point it looked like I lost all my work since the tile only showed an error message. It's nice to have source code! I worked around the issue by surrounding the offending code with a try / recover. The tile then showed two elements I had tried to create a while before this happened. They were "visibility" elements and nothing seemed to show up after each attempt to create them. With the fix they showed up over another tiles still with no data, but I was able to delete them and things have worked since.

I did not take the time to really understand your code, just did a quick workaround, I am sure you can do better. Here is my quick fix:

    unit_type = atomicState.tile_type."${tile.type}".type;
    try {
        parse_func = atomicState.unit_type."${unit_type}".parse_func;
    } catch (e) {
        log.debug(tile.name+": Unable to get data: "+unit_type); 
        parse_func = null;
    }

So I would like to add visibility, should it work?

[sherwoodbiz]

Another thing seemed strange when customizing the elements (sub tiles). When I tried to replace the icon on the existing tile with no icon "x", it showed the x in place of the icon in the finished tile. Is this a bug or am I doing something wrong?

[Jost]

Hi @thomas.c.howard,

any ideas regarding my "wishes"?

@Jost

1. How can I remove the padding (i.e. white gap) left and right from the diagram?
2. How can I force the lines to draw to the right edge? It would be nice to just use the actual value (even if the last refresh is some time ago).
3. Similar for the left edge (e.g. the ugly big gap of the red line): If there is no older value, just reuse the very first value.

This would result in something like this (=> more space for the diagram):

4. [Bonus] I would like to see a little more of the past, e.g. 25 hours for a day view (for comparing actual behavior with yesterday).

[thomas.c.howard]

@Jost, I have your requests on my backlog. It should be about a week to address them. (I am currently in learning mode and on the cusp of releasing a self-generating Denon AVR driver)...I believe #1 is doable, #2 I can look into (there is quite a bit of logic to try to "force fill", #3 - See #2. #4 is simple.

[Jost]

That are already good news, thank you very much!

[christian.busch]

Help me understand the limits.
When I configure my time chart, it gives me a warning above 2k points on a c7. So i configure it around 1400.

Does this only apply to the single graph or do they cumulate if multiple of these are in the same dashboard?

Whats the long term storage for?
How do I use it? How do I access it?

Great work!
Chris

[thomas.c.howard]

• Limits? There are none! Seriously though... see below.

• The warning you see is per device on that graph. It estimates the number of points to aid in display. For example, if your graph (displayed) is 200 pixels wide, it makes no sense to display 1000 points. Google Charts (the underlying API) just averages down. By lowering the number of points you can set the combine function (min, max, mean, mid, sum) and have it function correctly.

• LTS is a solution to help aid in some ... weaknesses Hubitat has. Since the early days, the have (needfully) reduced the number of stored events. This has drastically improved hub performance, but took away the ability to store up to 2000 points; by default. A user can still adjust the device to store more at the expense of performance.

• LTS allows the user to store off a vast number of events and support displaying a graph for weeks (if that is what you want). As an example, my temperature graph produces 2000 events (Hubitat max) in 2 days. If I want a week long graph, then I will need LTS.

• Finally, LTS strength is that it stores as much as you need WITHOUT affecting the database performance. It's weakness... if you reconfigure or reset, you loose all the stored data. (I am waiting with great anticipation for filesystem storage access).
  *Access LTS from the setup screen on Time Graphs.

[oliver9]

@thomas.c.howard

I’ll take a look; something about the dates changed in the latest releases....

The Heat map is still not working. Same error as before (Unparseable date).

[thomas.c.howard]

@oliver9, Added another fix for your specific issue. I am not sure why your date-timestamp is unique, but this fix should do it. Sorry it took a month.

[habitat]

Hubigraph 4.2 - minor bug in HeatMaps

Selecting Italic Annotation in the Heat Map config turns on BOLD Annotation not Italic, each time you select Italic it turns on off Bold

[thomas.c.howard]

@habitat: Fixed in 4.6
@Jost: 1-4 are now implemented.

1. Under Graph Options you can now set horizontal and vertical graph fill %
   

   

3. Under the section for each device/attribute there is now a section on how to handle missing values
   

   

4. Under the options, you can now select days, hours and minutes.
   

   

[thomas.c.howard]

@sherwoodbiz,

Thanks for taking a look. Yes; the issue that you are seeing is known (to me) and one of the weaknesses of the "Hubitat" way of saving preferences to the app. The long explanation is this:

1. The entire design is based on the design tool updating preferences after each change.
2. Anytime you make an update, the design tool "sends" text to the app that stores it.
3. Once the data is stored, the app refreshes.
4. Part of the refresh is to updates the design tool

If everything goes off well, no issues. If steps 1-4 take too long and the user starts to make another change, things can get out of sync. When things get out of sync, you see symptoms like you observed. I have a weather tile with over 60 elements. It took 1/2 hour to build since I had to wait up to a minute for the refresh...

I am looking at a way to manually "save" things. That way you can go crazy and not update until you are ready. The disadvantage here is that you won't see "actual" data (for sizing and other features) until updating....

Thoughts?

[Jost]

Wow, sounds great!
And so fast implemented, thanx a lot!

Mhhh, HPM still says, that there is no new version?

OK, I load the new file from Github...
And voila! Wow, that's looking fantastic!

A free beer for you:

[sherwoodbiz]

That sounds good to me. Perhaps you can solve two or three problems at once :). I suspect the following would be too much work but here goes. How about having a text interface sort of like you have with apps and drivers, or perhaps something like "Layout" in dashboard. Perhaps add an export feature that outputs a textual description of the current graph app. The user could mod, and then import it back. You would do syntax checking etc. on the import. This could be used for graph backup, and also an easy way to duplicate graphs.

Ok, I know that unless you are already headed that direction, that's a lot work.

Back to you idea, if you can put the app into a delayed accept mode that would be something I would likely use.

[thomas.c.howard]

@sherwoodbiz,

Okay, I took your ideas into account. In the end I was able to make thing easier than I thought. I have made the following changes

• Adding/Moving/Deleting Tiles will save immediately

• Formatting/Icons are still saved by clicking the green save icon

• The tiles no longer try to update the Weather Data/Decimals/Centering until either 1) the page is refreshed OR 2) You double click and choose a new icon I put in the menu.

• When you click the new "refresh cloud icon" I change the cursor to "wait" until it is done refreshing.

Give it a try and please let me know what you think.

Updates are in version 4.65