LCDProc package version 0.11.4_2

[jimp]

LCDProc package version 0.11.4 now available.

It contains the following changes:

• Fixed bug with gateway status LED on Crystalfontz panels
• Removed unnecessary "+ " from some screen titles
• Gateway status detail now indicates if monitoring is disabled for a gateway
• Added APC UPS status screen (available only when APCUPSD package is installed)
• Added NUT UPS status screen (available only when NUT package is installed)
• Added "Restart PHP+GUI" option to button control menu

LCDProc package version 0.11.4_1 contains a fix for errors observed in the logs when using some of the recently added screens, such as the UPS information screens.

LCDProc package version 0.11.4_2 contains a new setting to control the syslog behavior, allowing the user to turn it off completely or change the log level. #14629

[jimp]

For other recent changes in the package, see the older threads:

• Versions 0.11, 0.11.1, 0.11.2
• Version 0.11.3

[fireodo]

@jimp

Cool Work!

Thanks a lot! Now Lcdproc really covers all needed informations!

Kind regards,
fireodo

[fireodo]

@jimp

Sorry Jim:

Those 2 Screens are throwing errors:

APC UPS Info:

Jul 27 14:04:12	LCDd	8491	00% 12% 247 49%
Jul 27 14:04:12	LCDd	8491	4
Jul 27 14:04:12	LCDd	8491	1
Jul 27 14:04:12	LCDd	8491	text_summary
Jul 27 14:04:12	LCDd	8491	scr_apcupsd
Jul 27 14:04:12	LCDd	8491	widget_set
Jul 27 14:04:12	LCDd	8491	Unknown widget id (text_summary)
Jul 27 14:04:12	php	19611	". Executed ""
Jul 27 14:04:12	php	19611	lcdproc: LCDd output: "huh? Unknown widget id
Jul 27 14:04:09	LCDd	8491	00% 12% 243 62%
Jul 27 14:04:09	LCDd	8491	4
Jul 27 14:04:09	LCDd	8491	1
Jul 27 14:04:09	LCDd	8491	text_summary
Jul 27 14:04:09	LCDd	8491	scr_apcupsd
Jul 27 14:04:09	LCDd	8491	widget_set
Jul 27 14:04:09	LCDd	8491	Unknown widget id (text_summary)
Jul 27 14:04:09	LCDd	8491	Connect from host 127.0.0.1:3489 on socket 6
Jul 27 14:04:08	php	19611	lcdproc: Start client procedure. Error counter: (0)

Gateway Status:

Jul 27 14:33:37	php	91924	lcdproc: LCDd output: "huh? Unknown screen id
Jul 27 14:33:35	php	91924	". Executed ""
Jul 27 14:33:35	php	91924	lcdproc: LCDd output: "huh? Unknown screen id
Jul 27 14:33:32	php	91924	". Executed ""
Jul 27 14:33:32	php	91924	lcdproc: LCDd output: "huh? Unknown screen id
Jul 27 14:33:30	LCDd	87868	Connect from host 127.0.0.1:49885 on socket 6

but the displayed Info is correct ...

Regards,
fireodo

[jimp]

I see the problem. Not sure why it didn't show up in my logs yesterday. There was one place I used the wrong variable (and one recent screen was missing it entirely) to prevent the full-screen widgets from attempting to use the summary data that some of the half-screen widgets do.

I'll have a fix up shortly. Thanks!

[fireodo]

@jimp said in LCDProc package version 0.11.4:

I'll have a fix up shortly. Thanks!

Thank you too!

Edit: made your modifications in lcdproc_client.php by hand and confirm - its OK now.

[jimp]

I just pushed 0.11.4_2 with a setting for the syslog level since some users were seeing some log spam from the daemon. The new setting should allow users to either set a log level that has less messages, or disable logging entirely.

[fireodo]

@jimp said in LCDProc package version 0.11.4_2:

either set a log level that has less messages, or disable logging entirely

Perfect! Thanks! (now I dont have to do it each update by hand )

[elvisimprsntr]

@jimp was kind enough to update the LCDProc package to include a NTP server screen georou @ GitHub originally created and we updated. Current package is 0.11.5. There is a pending update to 0.11.5_1 (screens below) that improves the display of PPS, GPS, vs GPS+PPS in certain edge cases.

https://github.com/pfsense/FreeBSD-ports/commit/b3a3a4bf28ad8a50211b6775ed20011097ceeef9

1. If you have a PPS source, it will display either the number of satellites (GPS) or stability value (PPS).
2. Otherwise, it will display the Active Peer Server IP address.

Notes: I am by no means a NTPD algorithm expert, but I noticed if a source is marked as a valid PPS Peer "o", NTPD uses that to sync and serve time to clients regardless if there a separate Active Peer "*" used for time data. If a GPS is being used for both a PPS Peer "o"and source of time data, it will be marked as PPS Peer "o" and there will be no other Active Peers "*" marked (see screen cap below). The NTP Widget seems to display the Active Peer "*" even when the PPS Peer "o" is actually being used to sync and serve time to clients. Which source is actually served to clients can be confirmed with "ntpq -c sysinfo". If you want to see the stability value when using a GPS with PPS, you can simply set the Clock ID of the GPS source to "PPS". I intentionally did not include seconds on the display since even with the LCDProc Refresh Frequency set to 1 second, time will jump multiple seconds with each screen refresh. Not sure if there is another mechanism that would improve the refresh rate of the first row to eliminate increments of multiple seconds.

Feedback welcome, subject to the limitations noted above.

I happen to be using a Garmin 16X (PPS Only) and 18X (GPS+PPS). NTPD only supports one PPS source at a time, thus marks the second as False Ticker "x"

https://github.com/elvisimprsntr/pfsense-ntp-gps. (WIP)