Use separate scale/graph for power/cost

[joneyes]

looking at the usage graphs, cost doens't seem to increment.
I'm assuming total should be a total costs - so this doesn't climb either.
Did i miss something in my settings?

[jneilliii]

I'll have to go back and review why this might be happening. My last tests with this those numbers were definitely updating live. In the meantime, could you enable debug logging in the plugin's settings, restart OctoPrint and then let it run for a few minutes so the polling gets some data. I never personally tried less than 1 minute polling, and that might have something to do with it, but need to see how your tasmota is reporting and see how that data comes across in the log.

[jneilliii]

It's definitely incrementing for me with every status poll (assuming the math increases). Dug out an old POW R2 and connected to it from the plugin.

[joneyes]

Hi,
Yes, i can see that now, looking back at mine. Apologies. Thanks for looking at it.
It appears not to increment, as it's sharing the same scale as the power, and as costing is set to 0.31/KWh, it looks like it's flatlined.

May be an option is to put cost / total on the other side of the graph on an auto ranging scale and make the items selectable?

[jneilliii]

I've recently done something similar with Plotly Temp Graph plugin, so I can definitely look at this possibility.

[joneyes]

Hi, just wondering if you got around to this yet?
If you haven't, no worries.

[jneilliii]

I have not had much time lately for plugin development because of work.

[joneyes]

I know how that feels.. I have a stack of stuff in a queue for spare time when I finish work testing.. Regards Jon Eyes Sent from my Galaxy

…

-------- Original message -------- From: jneilliii ***@***.***> Date: 31/10/2023 13:50 (GMT+00:00) To: jneilliii/OctoPrint-Tasmota ***@***.***> Cc: Jon Eyes ***@***.***>, Author ***@***.***> Subject: Re: [jneilliii/OctoPrint-Tasmota] Use separate scale/graph for power/cost (Issue #203) I have not had much time lately for plugin development because of work. — Reply to this email directly, view it on GitHub<#203 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AU2Y66CWPBXDEZ3VDW3P3VDYCD6ZRAVCNFSM6AAAAAA3VWDMQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBXGI2TSOBSGU>. You are receiving this because you authored the thread.Message ID: ***@***.***>