Page 1 of 1

Problem with voltage display

Posted: Friday 27 May 2016 11:27
by hyla
Hi,

not quite sure if this is the right place for my question ...
I'm using Domoticz 3.5176 and MySensors 1.5.
In order to have a display of the voltages of my various sensors I am sending those values like this:
(heavily shortened:)

Code: Select all

    
    MyMessage battMsg(CHILD_ID_BATT, V_VOLTAGE);
   
    void setup()
    {
        (...)  
        gw.present(CHILD_ID_BATT, S_MULTIMETER);
        (...)
    }

    void loop()
    {
        gw.send(battMsg.set(batteryV, 1));
    }
    	
Doing that, I can have a look at the voltages under "Utility" and clicking "log" I get charts for "days, month, year"
Now, since a few versions ago (can't tell exactly, sorry) there are no values displayed in the "month" & "year" charts.

Any idea anyone why this should be so?

Apart from regular Domoticz updates there were no changes lately, especially in the sensor firmware.
voltage.jpg
voltage.jpg (41.98 KiB) Viewed 1775 times
Thanks,
Christoph

EDIT:
Gets weirder. It's got to do with the otherwise really fancy "min/max/avg" buttons. When I select "min" and "max" ONLY there is a display
again. Adding "avg" the chart is empty:
voltage_no_avg.jpg
voltage_no_avg.jpg (56.97 KiB) Viewed 1773 times

Re: Problem with voltage display

Posted: Saturday 28 May 2016 9:20
by gizmocuz
Send you a PM for a debug request

Re: Problem with voltage display

Posted: Saturday 28 May 2016 10:28
by gizmocuz
Solved in #5177

Re: Problem with voltage display

Posted: Monday 27 June 2016 17:09
by SweetPants
gizmocuz wrote:Solved in #5177
Not quite, i think it's back (avg) in at least 3.5271 maybe earlier
voltage.png

Re: Problem with voltage display

Posted: Monday 27 June 2016 18:01
by gizmocuz
Dont experience this issue here:
Voltage.PNG
Voltage.PNG (56.63 KiB) Viewed 1650 times

Re: Problem with voltage display

Posted: Tuesday 28 June 2016 15:15
by SweetPants
Yep, you are right, the fix was implemented earlier (may 28), but i updated the beta on a later date (june 24). Working fine now, sorry for the misunderstanding.