Hi all,
I'm afraid I've run into 2 new problems/bugs with the Dude 2.1.
Honoustly I've to admit I'm a little disaster with function-coding but with lots of help from others here I'll manage eventually..
So it might just be me that triggers these problems.. (hope not...
)
I've several functions that check whether or not a returned value is within a certain bandwidth (eg Humidity between 40 and 60 %). The returned value should be graphed. First I couldn't get the value graphed, with help from Winkelman I made it work in the end.. Second I couldn't configure the function so that it would actually check if the value is within parameters, Uldis came to help and after he fixed a bug within the Dude itself it all looked great.. I had graphs, and I had devices appearing as I hoped them to appear because of preset parameters.
But.... :'( The Dude v2.1 is giving me headaches at the time of writing..
It's displaying functions with 15 digits after the decimal point (a function dividing the returned value by 10 should display 1 digit huh?
) within the device labels (inconvenient since it makes your labels HUGE
). But the worst thing is that I seem to have lost my (until sofar) great graphing ability. Since the installation of Dude 2.1 I'm seeing lots (and I mean LOTS!) of gaps within my graphs and more than once the graphing stopped at some random time and the graph isn't updated anylonger..
I give an example of a function that is performing erraticly and frequently displays gaps ..
--
Name:
RV #1 (from Relative Humidity (in Dutch is RV) port #1
)
Type:
Function
Available:
if(oid("1.3.6.1.4.1.3854.1.2.2.1.17.1.3.0")>0,1,-1)
Error:
if(or(oid("1.3.6.1.4.1.3854.1.2.2.1.17.1.3.0")<40,oid("1.3.6.1.4.1.3854.1.2.2.1.17.1.3.0")>60),concatenate("Relative Humidity out of range. Value = ",oid("1.3.6.1.4.1.3854.1.2.2.1.17.1.3.0")),"")
Value:
oid("1.3.6.1.4.1.3854.1.2.2.1.17.1.3.0")
Unit:
# %
Rate:
None
--
The above function does it comparison of the returned value as exspected, values outside the bandwidth of 40-60 % RH are stated as incorrect, which changes the state of the device accordingly.
The graphing part isn't working as I hoped, occasionally it works and more frequently it doesn't..
, resulting in (huge) gaps.
As appeared just about 5 minutes ago, it also happens that the webinterface again refuses to display devices within the webinterface 'Maps' after a longer period of running.
Sadly enough, logging into the webinterface is either extremely slow or not working at all.
Please help!! I like the Dude for it possibilities and capabilities, but hope it will get more stable soon..
Regards,
Minollie