Output Graphs?

mgent · 2017-12-30T20:46:01.675Z

Needed to change units. Solved.

First off, great device!!

Question: With the local iotawatt graph application I am unable to see any output feeds anymore. I can see the output values fine in the status screen and they update there no problem. However, none of these show up as selectable feeds for graphing. All the inputs do and they graph perfectly.

Any ideas, or did something change for outputs?

Thanks

overeasy · 2017-12-30T22:04:52.206Z

mgent:

Needed to change units. Solved.

Right. For anyone just tuning in, IoTaWatt outputs will only be selectable in graph if they have units = volts or watts. If it’s volts, it will appear under the voltage tab, if watts, it will appear under both power and energy tabs.

mgent:

did something change for outputs?

Yes, the API changed to use the names so that it can be used by other apps and to Support stored graphs (also relatively recent enhancement)

mgent · 2018-03-01T03:21:58.519Z

Wondering if you could help with a new problem. When I go to the local iotawatt graph now no feeds at all show up for selection. Inputs or outputs. Is there any common cause that could result in this?

Attached screen capture of what I get.

iota691×442 9.69 KB

overeasy · 2018-03-01T04:39:02.565Z

mgent:

Is there any common cause that could result in this?

I’m working a similar problem with another user, so there may be a common cause. It looks like a bug in a library that I use, but I cannot be sure yet. Could you please enter the following URL in your browser and post the result?

http://iotawatt.local/feed/list.json

overeasy · 2018-03-01T20:17:47.853Z

mgent:

Is there any common cause that could result in this?

Please see this issue:

Monitoring 13 circuits over three phases Getting Started

I found the problem. Long story short, when the feed list is too long, it doesn’t work. It’s not the number of feeds, but the total size of the list. In your case, the names are long, so it exceeds the limits. You got lucky removing that on output. The gap must have appeared in a non sensitive portion of the Json. In the short term, you could reduce the size of the names or wait a few more days and take the next ALPHA release which resolves the issue. I was able to recreate the problem and…

If you have long names on your inputs and some outputs defined, this may be your problem as well.

mgent · 2018-03-01T21:21:05.915Z

Thanks, I’ll see if that fixes it when released. Appreciate it!

jnoxon · 2018-07-09T17:43:32.474Z

For what it’s worth, I ran into this problem today. I was able to make it work again by shortening the names of a few inputs. I have 14 CT’s attached and a bunch of outputs defined.

When I fetched /feed/list.json, it was invalid json (truncated), so I assume a buffer somewhere needs to be larger.

I’m running 02_02_30.