Gauges

[seggins]

4.3.1 (4064) gauges still not working.
Using Instromet on Windows 11.
Back on 4043 which works perfectly.

[broadstairs]

Can you explain which way you are trying to view the gauges? CMX dashboard, the alternate dashboard or a website (CMX default or other)?

Can you update your profile as it says Windows 10 currently?

Stuart

[water01]

And any chance of an MXDiags log so we can see what is going on, otherwise we are just guessing.

[SamiS]

I wonder if this is related to the same issue, gauges not functioning on dashboard but website is fine…

viewtopic.php?p=187341#p187341

[seggins]

Gauges do not work on both forms of display.

[HansR]

Gauges do not work on both forms of display.

And any chance of an MXDiags log so we can see what is going on, otherwise we are just guessing.

Seriously, I think water01 has a point here.

[jokerboy]

I wonder if this is related to the same issue, gauges not functioning on dashboard but website is fine…

viewtopic.php?p=187341#p187341

It is the same issue.

[jokerboy]

And any chance of an MXDiags log so we can see what is going on, otherwise we are just guessing.

I don't think there's going to be anything in the logs to help with this.

I believe this is happening only on stations that don't have indoor measurements. (I have a Tempest station which has no indoor temp/humidity)

The problem is an exception being thrown in the javascript on the dashboard page.

For those technically inclined, you can see this error in the web browser javascript console (developer tools, press F12). The exception is occurring in the function 'convertJson', on line 287 of dashboard.js, there's the statement:

Code: Select all

            inhum: inp.IndoorHum.toString()

The value of inp.IndoorHum is NULL, so a reference to the toString() method throws a null pointer exception. I believe the reason this is null goes back to a change made in October which removed the default value (0) for stations that don't ever explicitly set the value for the Indoor Humidity, thus the null propagates to the current data being sent to the browser in the dashboard page.

I sent Mark a PM explaining this and I'm certain he will know the best way to fix the issue.

For those wanting to test my theory and who are technically capable, go to your CumulusMX installation and go inside the 'interface/js' folder and edit the file dashboard.js (please make a backup copy first!!). Simply go to line 287 and comment it out by adding 2 '/' characters to the start of the line like this:

Code: Select all

//            inhum: inp.IndoorHum.toString()

Save the file, clear your browser cache, and then reload the page. The gauges should start working again, they did on mine (the clearing of the browser cache is important).

Please note this is a temporary fix and will be overwritten the next time you update CumulusMX.

[HansR]

Please note that a similar issue arises with another station and other gauges:
viewtopic.php?t=22802

I have no idea if it is similar but it looks like it. And it may have something to do with the Instromet as @seggins and @Andy02 both use that station and both have a problem with the gauges in the interface.

[HansR]

I am having an idea: could @seggins please post realtimegauges.txt (I'll ask similar to @Andy02
Does not work for the interface

[mcrossley]

I have fixed this for the next build. It does not affect data recording, only the display of data in the gauges on the dashboard.

[AndyO2]

@mcrossley - is this issue fixed in 4070? the release notes are inconclusive on this point

[mcrossley]

Yes, it should be.