Indigo Domotics

I am using 4.08

Downloaded it today

The error shows using 4.08

Am I missing something obvious?

Mike

Busta999 wrote:

Am I missing something obvious?

No, I am. That's what I get for multitasking. I'll take a look at .08 and get that error out of there.

As always, Much appreciated.

Mike

Just a follow-up to this latest issue. An update is in the works, but there's a lot more change included that I had in the pipeline (changes already made) and I've found a few bugs moving that to production. I hope to be able to get everything buttoned up today.

Damn it!

I demand a refund!!!

Oh

Alright then, you efforts are appreciated

Mike

Help is on the way...


Sent from my iPhone using Tapatalk

Code: Select all

TypeError: _log() got an unexpected keyword argument 'isError'

The latest release (v0.4.13) should solve this issue.

A note about the changes to the way colors are now selected in the plugin. Thanks to Matt & Jay exposing the OS X color picker for plugins, it is no longer necessary to support the notion of 'custom colors'. SO, I've (hopefully) removed that option from all chart elements that supported custom colors and moved to the color picker tool. For those users that used the old custom colors feature, I tried to remember the custom color value used and migrate that to the new system. This may or may not work 100 percent of the time. If errors are encountered that look like this:

Code: Select all

2017-07-28 21:55:51.023   Matplotlib Critical Error   [Chart - Temperatures Indoor] [Chart - Temperatures Indoor] Error plotting chart (to_rgba: Invalid rgba arg "#custom"
to_rgb: Invalid rgb arg "#custom"
invalid hex color string "#custom")


The easiest way to clear the error is to open the device configuration dialog and select the appropriate colors using the color picker tool. Hopefully, this won't be necessary, but it's a quick and easy fix if needed.

Dave

Many thanks for 4.13 - it certainly stopped all the error messages - excellent!

On updating graphs I am finding it hard to find a way to get Matplotlib to make the graphs using changed parameters in the chart definition.

I have tried, after closing every window, Redraw Charts, reload plugin, and disable and restart plugin.

None of these seem to force Matplotlib to read the changes in the Chart definition.

Any possibility that it is not re-reading the definitions after an update.

I have seen updates reflected but randomly quite a while after I have done the update.

Busta999 wrote:

Any possibility that it is not re-reading the definitions after an update.

I have seen updates reflected but randomly quite a while after I have done the update.

Hmmm. Here's how that's supposed to work. After changing a chart definition, you could:

1. Wait for the charts to refresh on their own.
2. Select redraw charts from the plugin menu.
3. Reload the plugin.

I can confirm that this is working on my end. Of course, that doesn't mean that it's working for you. How do you have your charts set to refresh? There is an overall setting in the plugin configuration -- I have mine set to 15 minutes. If you have that set to "Manual Refresh Only", then you will have to invoke the refreshes yourself. That said, the redraw charts menu item should still work for you.

Are you changing colors using the new color picker? Make sure to click on the color button of the setting you want to change (even though the color picker remains visible as you move from device to device.)

I don't recall making any changes to that part of the code, but that doesn't mean that somethings not messed up when I moved the devices to the new processing method.

OK,

Not a big issue at all.

It is not a consistent issue.

I'm updating charts for the new house so will try to track down circumstances for consistent failure.

Thanks very much. If the charts aren't updating when they're supposed to, that's a big issue.

Please let me know what you discover.

Cheers,
Dave

I am trying to narrow down circumstances.

When I did the update I had just moved house.

I had deleted csvs from previous house and that generated MatPlotlib errors (unsurprisingly ) is it possible that when encountering an error, even though it shows processing and updated it does not actually process and update while an error condition exists?

It is stable now, so not an issue, but I had 3 of the 12 charts not updating that was when I was getting the issues.

Speculation at this stage, to track down I need to replicate the error states I was encountering.

If no one else is having issues and mine have gone away, probably not going to spend too much time on it

Once a QA guy always a QA guy I guess

Mike

It's extremely possible that one of my error traps mistakenly prints an "everything went fine" message -- I wouldn't rule that out at this point. When you see the condition return, please take a look at the plugin log located at:

/Library/Application Support/Perceptive Automation/Indigo 7/Logs/com.fogbert.indigoplugin.matplotlib/

and see if there's any clues.

Dave

This probably already exists ...

I am creating a load of little, tiny, trend graphs that plot the last 6hrs of temperature.

[img][/img]

The grey filled area is the temperature of the hallway, where the thermostat is located.

The red line is the temp of the Ensuite Bathroom.

What I would like to do is place a, dotted/dashed line showing the 'ideal' temp i.e. 20C then at a glance you can see the ideal, whether the heating is hitting target at thermostat (or if thermostat set too high/low) and a specific room is hitting target - along with a trending indicator - temp is going up or down.

I cannot see how to get a static line in there, except to set a variable Target Temp and get Matplotlib to track that static, Ok it looks like I have answered my own question.

Will go an try it

Mike