Troubleshooting - Revision history

Bcmwiki: Consistency pass: multi-wavelength in-development, bcmeter-pi link, anchor/Flask/V2 fixes, airflow & ATN clarifications

2026-06-08T18:43:41Z

Consistency pass: multi-wavelength in-development, bcmeter-pi link, anchor/Flask/V2 fixes, airflow & ATN clarifications

← Older revision		Revision as of 18:43, 8 June 2026
Line 6:		Line 6:
	\| '''Negative data over a longer period''' \|\| '''Temperature or lighting changes.''' Ensure the bcMeter is not in direct or reflected sunlight (keep reflections from windows on other side of the road in mind). Do not place near radiators or heat sources. If issue persists, contact support.		\| '''Negative data over a longer period''' \|\| '''Temperature or lighting changes.''' Ensure the bcMeter is not in direct or reflected sunlight (keep reflections from windows on other side of the road in mind). Do not place near radiators or heat sources. If issue persists, contact support.
	\|-		\|-
	\| '''Device keeps restarting''' \|\| '''Power supply.''' Cable too long or thin — see power requirements in [[Setup#~~Power Supply is Critical~~\|Setup]].		\| '''Device keeps restarting''' \|\| '''Power supply.''' Cable too long or thin — see power requirements in [[Setup#Hardware Requirements\|Setup]].
	\|-		\|-
	\| '''WiFi unstable or disconnects''' \|\| Voltage instability (see power supply) or weak signal. The hotspot may temporarily disappear for 2–3 minutes during self-recovery — it returns automatically.		\| '''WiFi unstable or disconnects''' \|\| Voltage instability (see power supply) or weak signal. The hotspot may temporarily disappear for 2–3 minutes during self-recovery — it returns automatically.

Bcmwiki: Sync with updated manual: added window reflections note for negative data, updated power supply reference link, removed 502 Bad Gateway (V1 only)

2026-03-31T18:22:41Z

Sync with updated manual: added window reflections note for negative data, updated power supply reference link, removed 502 Bad Gateway (V1 only)

Bcmwiki: Error codes: backend/API/logs only, not in frontend

2026-03-08T18:06:10Z

Error codes: backend/API/logs only, not in frontend

← Older revision		Revision as of 18:06, 8 March 2026
Line 33:		Line 33:
	=== Error Codes ===		=== Error Codes ===

	~~Error~~ codes are shown in the interface ~~status bar when a measurement stops due to a hardware or sensor issue~~. They ~~also~~ appear in the [[API reference\|Status API]] response (<code>/api/status</code> → <code>error</code> and <code>error_msg</code> fields) and in the '''System Logs''' (accessible from Maintenance).		These numerical error codes are '''not''' shown in the frontend interface. They appear in the [[API reference\|Status API]] response (<code>/api/status</code> → <code>error</code> and <code>error_msg</code> fields) and in the '''System Logs''' (accessible from Maintenance). The interface displays a human-readable error message instead.

	{\| class="wikitable"		{\| class="wikitable"

Bcmwiki: Fix ERR_ADC_LOW/SATURATED descriptions, add error code visibility info

2026-03-08T17:50:39Z

Fix ERR_ADC_LOW/SATURATED descriptions, add error code visibility info

← Older revision		Revision as of 17:50, 8 March 2026
Line 32:		Line 32:

	=== Error Codes ===		=== Error Codes ===

			Error codes are shown in the interface status bar when a measurement stops due to a hardware or sensor issue. They also appear in the [[API reference\|Status API]] response (<code>/api/status</code> → <code>error</code> and <code>error_msg</code> fields) and in the '''System Logs''' (accessible from Maintenance).

	{\| class="wikitable"		{\| class="wikitable"
Line 38:		Line 40:
	\| 0 \|\| ERR_NONE \|\| No error		\| 0 \|\| ERR_NONE \|\| No error
	\|-		\|-
	\| 1 \|\| ERR_ADC_LOW \|\| Sensor reading ~~<0.5V~~ — ~~likely no~~ filter ~~installed~~		\| 1 \|\| ERR_ADC_LOW \|\| Sensor reading too low — filter extremely loaded
	\|-		\|-
	\| 2 \|\| ERR_ADC_SATURATED \|\| ~~Reading >3.8V~~ — LED too bright		\| 2 \|\| ERR_ADC_SATURATED \|\| Sensor reading saturated — LED too bright; at low duty this indicates no filter is present
	\|-		\|-
	\| 3 \|\| ERR_FLOW_ZERO \|\| Pump stall, airflow below minimum		\| 3 \|\| ERR_FLOW_ZERO \|\| Pump stall, airflow below minimum

Bcmwiki: Update: V1/V2 naming, remove ESP32/Pi distinction

2026-03-08T13:21:12Z

Update: V1/V2 naming, remove ESP32/Pi distinction

← Older revision		Revision as of 13:21, 8 March 2026
Line 10:		Line 10:
	\| '''WiFi unstable or disconnects''' \|\| Voltage instability (see power supply) or weak signal. The hotspot may temporarily disappear for 2–3 minutes during self-recovery — it returns automatically.		\| '''WiFi unstable or disconnects''' \|\| Voltage instability (see power supply) or weak signal. The hotspot may temporarily disappear for 2–3 minutes during self-recovery — it returns automatically.
	\|-		\|-
	\| '''No WiFi networks listed''' \|\| Reload the interface to re-initialize the network scan. ~~On ESP32, scanning~~ pauses during active measurement — wait for the next sample cycle.		\| '''No WiFi networks listed''' \|\| Reload the interface to re-initialize the network scan. Scanning pauses during active measurement — wait for the next sample cycle.
	\|-		\|-
	\| '''No data on graph''' \|\| '''Sampling interval.''' With the default 300s sample time, the first data point appears after ~15–20 minutes (3–4 samples needed, plus initialization). Be patient.		\| '''No data on graph''' \|\| '''Sampling interval.''' With the default 300s sample time, the first data point appears after ~15–20 minutes (3–4 samples needed, plus initialization). Be patient.
Line 22:		Line 22:
	\| '''Email notifications not working''' \|\| Verify the email service password (API key) is entered and validated in Email settings. Check that at least one valid recipient address is configured.		\| '''Email notifications not working''' \|\| Verify the email service password (API key) is entered and validated in Email settings. Check that at least one valid recipient address is configured.
	\|-		\|-
	\| '''502 Bad Gateway error''' \|\| ''(V1~~/Raspberry Pi~~ only)'' Check PHP-FPM version in <code>/etc/nginx/sites-enabled/default</code>. Correct the <code>fastcgi_pass</code> line to match your PHP version.		\| '''502 Bad Gateway error''' \|\| ''(V1 only)'' Check PHP-FPM version in <code>/etc/nginx/sites-enabled/default</code>. Correct the <code>fastcgi_pass</code> line to match your PHP version.
	\|-		\|-
	\| '''Sensor values very low, don't change''' \|\| Check voltages on LED and sensor connections. Verify 12V power is connected (the optical ADC requires it). Run calibration with a clean filter.		\| '''Sensor values very low, don't change''' \|\| Check voltages on LED and sensor connections. Verify 12V power is connected (the optical ADC requires it). Run calibration with a clean filter.
Line 31:		Line 31:
	\|}		\|}

	=== Error Codes ~~(ESP32)~~ ===		=== Error Codes ===

	{\| class="wikitable"		{\| class="wikitable"

Bcmwiki: Wiki update: sync with manual and dev docs (2026-03)

2026-03-08T13:10:46Z

Wiki update: sync with manual and dev docs (2026-03)

← Older revision		Revision as of 13:10, 8 March 2026
Line 1:		Line 1:
	== ~~Error "502 bad gateway" when accessing the bcMeter Interface~~ ==		== Troubleshooting ==
	~~if you get a 502 bad gateway error, check PHP-FPM version in /etc/nginx/sites-enabled/default :~~

	~~Correct line~~ "~~fastcgi_pass unix~~:/~~run~~/~~php~~/~~php7.4~~-~~fpm~~.~~sock;"~~ <- 7.~~4 to~~ the ~~version you see when entering~~		{\| class="wikitable"
	~~"ps aux~~ \| ~~grep php~~-~~fpm"~~		! Issue !! Likely Cause & Solution
	in ~~terminal~~.		\|-
			\| '''Negative data over a longer period''' \|\| '''Temperature or lighting changes.''' Ensure the bcMeter is not in direct or reflected sunlight. Do not place near radiators. If issue persists, contact support for advanced configuration.
			\|-
			\| '''Device keeps restarting''' \|\| '''Power supply.''' USB cable impedance too high (cable too long or thin). Use a high-quality cable (<40 cm) and a 2.5A supply.
			\|-
			\| '''WiFi unstable or disconnects''' \|\| Voltage instability (see power supply) or weak signal. The hotspot may temporarily disappear for 2–3 minutes during self-recovery — it returns automatically.
			\|-
			\| '''No WiFi networks listed''' \|\| Reload the interface to re-initialize the network scan. On ESP32, scanning pauses during active measurement — wait for the next sample cycle.
			\|-
			\| '''No data on graph''' \|\| '''Sampling interval.''' With the default 300s sample time, the first data point appears after ~15–20 minutes (3–4 samples needed, plus initialization). Be patient.
			\|-
			\| '''Pump noise when stopped''' \|\| Motor controller signal latch. Go to '''Maintenance > Reboot Device''' or start a new log and stop right after initialization.
			\|-
			\| '''Pump stall / no airflow''' \|\| The device has automatic stall protection. If flow drops below threshold for 3 seconds, recovery is attempted (up to 4 times). After 4 failures, measurement stops with pump error. Check for blocked tubing, saturated filter, or hardware issues.
			\|-
			\| '''"Time: not synced" warning''' \|\| Device clock not synchronized. Go to '''Maintenance''' and sync with your browser. Internet-connected devices sync automatically via NTP.
			\|-
			\| '''Email notifications not working''' \|\| Verify the email service password (API key) is entered and validated in Email settings. Check that at least one valid recipient address is configured.
			\|-
			\| '''502 Bad Gateway error''' \|\| ''(V1/Raspberry Pi only)'' Check PHP-FPM version in <code>/etc/nginx/sites-enabled/default</code>. Correct the <code>fastcgi_pass</code> line to match your PHP version.
			\|-
			\| '''Sensor values very low, don't change''' \|\| Check voltages on LED and sensor connections. Verify 12V power is connected (the optical ADC requires it). Run calibration with a clean filter.
			\|-
			\| '''ADC saturation error''' \|\| LED too bright or sensor oversaturated. The device attempts auto-recovery by reducing LED duty. If persistent, recalibrate with a fresh filter. Check in [[Developer mode]] if advanced LED settings need adjustment.
			\|-
			\| '''Overtemperature warning''' \|\| Internal temperature exceeded 65°C. Move the device to a cooler location. Measurement pauses automatically and resumes when temperature drops.
			\|}

			=== Error Codes (ESP32) ===

	=~~= The bcMeter does~~ not ~~connect to my WiFi ==~~		{\| class="wikitable"
			! Code !! Name !! Description
			\|-
			\| 0 \|\| ERR_NONE \|\| No error
			\|-
			\| 1 \|\| ERR_ADC_LOW \|\| Sensor reading <0.5V — likely no filter installed
			\|-
			\| 2 \|\| ERR_ADC_SATURATED \|\| Reading >3.8V — LED too bright
			\|-
			\| 3 \|\| ERR_FLOW_ZERO \|\| Pump stall, airflow below minimum
			\|-
			\| 4 \|\| ERR_OVERTEMP \|\| Temperature >65°C
			\|-
			\| 5 \|\| ERR_LED_FAILURE \|\| LED not functioning
			\|-
			\| 6 \|\| ERR_ATN_LIMIT \|\| Attenuation >120 — filter extremely clogged
			\|-
			\| 7 \|\| ERR_OUTLIER_EXCESS \|\| >80% of readings out-of-bounds
			\|}

	~~# Double check [[Software#Configure_the_microSD_Card_for_WiFi_access\|this procedure]] was done correctly and/or repeat it.~~		=== Getting Help ===
	# Look at your router interface if there is a new device "raspberrypi" or similar. If you ever had another raspberrypi connected to your wifi, the dns of your router might have assigned another hostname to the raspberry.

	~~== The sensor values are very low and do not change ==~~		If your issue isn't listed here, contact jd@bcmeter.org with:
	~~# Check voltages on LED and Sensor~~		* Description of the problem
			* Screenshot of the interface
	~~== Any other~~ issue ==		* System logs (download from '''Maintenance > Download Logs''')
	~~# Let me know, I~~'~~m glad to add it~~ here~~. Mail description and screenshot to~~ jd@bcmeter.org.

Bcmwiki at 14:33, 5 January 2022

2022-01-05T14:33:56Z

← Older revision		Revision as of 14:33, 5 January 2022
Line 1:		Line 1:
	== Error "502 bad gateway" when accessing the bcMeter Interface ==		== Error "502 bad gateway" when accessing the bcMeter Interface ==
	if you get a 502 bad gateway error, check PHP-FPM version in /etc/nginx/sites-enabled/default ~~is corresponding~~ to ~~installed php~~ version.		if you get a 502 bad gateway error, check PHP-FPM version in /etc/nginx/sites-enabled/default :
	~~Check version with running~~ "ps aux \| grep php-fpm" in terminal.
			Correct line "fastcgi_pass unix:/run/php/php7.4-fpm.sock;" <- 7.4 to the version you see when entering
			"ps aux \| grep php-fpm"
			in terminal.


	== The bcMeter does not connect to my WiFi ==		== The bcMeter does not connect to my WiFi ==

Bcmwiki at 14:31, 5 January 2022

2022-01-05T14:31:30Z

← Older revision		Revision as of 14:31, 5 January 2022
Line 2:		Line 2:
	if you get a 502 bad gateway error, check PHP-FPM version in /etc/nginx/sites-enabled/default is corresponding to installed php version.		if you get a 502 bad gateway error, check PHP-FPM version in /etc/nginx/sites-enabled/default is corresponding to installed php version.
	Check version with running "ps aux \| grep php-fpm" in terminal.		Check version with running "ps aux \| grep php-fpm" in terminal.


	~~== The bcMeter does not connect to my WiFi ==~~

	== The bcMeter does not connect to my WiFi ==		== The bcMeter does not connect to my WiFi ==

Bcmwiki at 14:31, 5 January 2022

2022-01-05T14:31:12Z

← Older revision		Revision as of 14:31, 5 January 2022
Line 1:		Line 1:
			== Error "502 bad gateway" when accessing the bcMeter Interface ==
			if you get a 502 bad gateway error, check PHP-FPM version in /etc/nginx/sites-enabled/default is corresponding to installed php version.
			Check version with running "ps aux \| grep php-fpm" in terminal.


			== The bcMeter does not connect to my WiFi ==

	== The bcMeter does not connect to my WiFi ==		== The bcMeter does not connect to my WiFi ==

Bcmwiki at 18:38, 7 July 2021

2021-07-07T18:38:53Z

← Older revision		Revision as of 18:38, 7 July 2021
Line 4:		Line 4:
	# Look at your router interface if there is a new device "raspberrypi" or similar. If you ever had another raspberrypi connected to your wifi, the dns of your router might have assigned another hostname to the raspberry.		# Look at your router interface if there is a new device "raspberrypi" or similar. If you ever had another raspberrypi connected to your wifi, the dns of your router might have assigned another hostname to the raspberry.

	== The sensor values are very and do not change ==		== The sensor values are very low and do not change ==
	# Check voltages on LED and Sensor		# Check voltages on LED and Sensor

	== Any other issue ==		== Any other issue ==
	# Let me know, I'm glad to add it here. Mail description and screenshot to jd@bcmeter.org.		# Let me know, I'm glad to add it here. Mail description and screenshot to jd@bcmeter.org.

← Older revision		Revision as of 18:22, 31 March 2026
Line 4:		Line 4:
	! Issue !! Likely Cause & Solution		! Issue !! Likely Cause & Solution
	\|-		\|-
	\| '''Negative data over a longer period''' \|\| '''Temperature or lighting changes.''' Ensure the bcMeter is not in direct or reflected sunlight. Do not place near radiators. If issue persists, contact support ~~for advanced configuration~~.		\| '''Negative data over a longer period''' \|\| '''Temperature or lighting changes.''' Ensure the bcMeter is not in direct or reflected sunlight (keep reflections from windows on other side of the road in mind). Do not place near radiators or heat sources. If issue persists, contact support.
	\|-		\|-
	\| '''Device keeps restarting''' \|\| '''Power supply.''' ~~USB cable impedance too high (cable~~ too long or thin~~). Use a high-quality cable (<40 cm) and a 2.5A supply~~.		\| '''Device keeps restarting''' \|\| '''Power supply.''' Cable too long or thin — see power requirements in [[Setup#Power Supply is Critical\|Setup]].
	\|-		\|-
	\| '''WiFi unstable or disconnects''' \|\| Voltage instability (see power supply) or weak signal. The hotspot may temporarily disappear for 2–3 minutes during self-recovery — it returns automatically.		\| '''WiFi unstable or disconnects''' \|\| Voltage instability (see power supply) or weak signal. The hotspot may temporarily disappear for 2–3 minutes during self-recovery — it returns automatically.
	\|-		\|-
	\| '''No WiFi networks listed''' \|\| Reload the interface to re-initialize the network scan~~. Scanning pauses during active measurement — wait for the next sample cycle~~.		\| '''No WiFi networks listed''' \|\| Reload the interface to re-initialize the network scan.
	\|-		\|-
	\| '''No data on graph''' \|\| '''Sampling interval.''' With the default 300s sample time, the first data point appears after ~15–20 minutes ~~(3–4~~ samples ~~needed, plus initialization). Be patient~~.		\| '''No data on graph''' \|\| '''Sampling interval.''' The chart needs 3–4 samples before it can render. With the default 300s sample time, the first data point appears after ~15–20 minutes. Check that a session is running and wait for the first samples to arrive.
	\|-		\|-
	\| '''Pump noise when stopped''' \|\| Motor controller signal latch. Go to '''Maintenance > Reboot Device''' or start a new log and stop right after initialization.		\| '''Pump noise when stopped''' \|\| Motor controller signal latch. Go to '''Maintenance > Reboot Device''' or start a new log and stop right after initialization.
Line 18:		Line 18:
	\| '''Pump stall / no airflow''' \|\| The device has automatic stall protection. If flow drops below threshold for 3 seconds, recovery is attempted (up to 4 times). After 4 failures, measurement stops with pump error. Check for blocked tubing, saturated filter, or hardware issues.		\| '''Pump stall / no airflow''' \|\| The device has automatic stall protection. If flow drops below threshold for 3 seconds, recovery is attempted (up to 4 times). After 4 failures, measurement stops with pump error. Check for blocked tubing, saturated filter, or hardware issues.
	\|-		\|-
	\| '''"Time: not synced" warning''' \|\| Device clock not synchronized~~. Go to '''Maintenance''' and sync with your browser~~. Internet-connected devices sync automatically ~~via NTP~~.		\| '''"Time: not synced" warning''' \|\| Device clock not synchronized. Internet-connected devices sync automatically; for offline devices, use Maintenance > Time Synchronization.
	\|-		\|-
	\| '''Email notifications not working''' \|\| Verify the email service password (API key) is entered and validated in Email settings. Check that at least one valid recipient address is configured.		\| '''Email notifications not working''' \|\| Verify the email service password (API key) is entered and validated in Email settings. Check that at least one valid recipient address is configured.
	\|-
	~~\| '''502 Bad Gateway error''' \|\| ''(V1 only)'' Check PHP-FPM version in <code>/etc/nginx/sites-enabled/default</code>. Correct the <code>fastcgi_pass</code> line to match your PHP version.~~
	\|-		\|-
	\| '''Sensor values very low, don't change''' \|\| Check voltages on LED and sensor connections. Verify 12V power is connected (the optical ADC requires it). Run calibration with a clean filter.		\| '''Sensor values very low, don't change''' \|\| Check voltages on LED and sensor connections. Verify 12V power is connected (the optical ADC requires it). Run calibration with a clean filter.