Smart Automation Troubleshooting Guide

Issue 1: Device Shows "Offline"

This is the most common issue. The device appears in GrowVPD Pro but shows a gray "Offline" badge and does not respond to commands.

Step-by-Step Fix

1. Check physical power. Is the device plugged in and powered? LEDs lit? This sounds obvious, but power strips get bumped and circuit breakers trip.
2. Check WiFi connection. Open the device's native app (Tuya, AC Infinity, Mars Hydro) and see if it shows online there. If it is offline in its own app, the problem is between the device and your WiFi router, not GrowVPD Pro.
3. Restart the device. Unplug it, wait 10 seconds, plug it back in. Many WiFi devices need 30–60 seconds after power-on to reconnect to the cloud.
4. Check your router. Some routers have device limits or disconnect idle devices. Ensure your router supports the number of connected devices you have. Grow rooms with 5–10 smart devices can push consumer routers to their limits.
5. Verify WiFi band. Most smart grow devices only support 2.4 GHz WiFi, not 5 GHz. If your router combines both bands under one SSID, the device may have connected to 5 GHz during setup but cannot sustain it. Force the device to 2.4 GHz if possible.
6. Re-pair if needed. If the device remains offline in its native app after all the above, remove it from the native app and re-pair it. Then re-discover it in GrowVPD Pro.

Issue 2: Automation Rule Not Triggering

The rule is enabled, the sensor shows data, but the target device never turns on or changes state.

Step-by-Step Fix

1. Check the sensor reading. Open the tent dashboard and verify the sensor is reporting current data. If the last reading timestamp is stale (more than 30 minutes old), the sensor may be offline or the token may have expired.
2. Verify the condition is actually met. For a VPD rule, check the current VPD value against the rule threshold. Remember that GrowVPD Pro calculates VPD from leaf temperature (which is estimated from air temperature), so the displayed VPD may differ slightly from what you expect.
3. Check the rule schedule. If you set active time windows (e.g., only trigger between 8 AM and 8 PM), the rule will not fire outside those hours.
4. Check minimum off-time. If you set a minOffMinutes of 10 and the rule was restored (turned off) less than 10 minutes ago, it will not trigger again until the cooldown expires. This prevents compressor damage on dehumidifiers and AC units.
5. Check the target device. Is the target device online? Can you manually toggle it from the Automation tab? If manual control works but the rule does not trigger, the issue is in the rule configuration, not the device connection.
6. Check for conflicting rules. If two rules target the same device with opposite actions, the higher-priority rule wins. A "turn off" rule with priority 10 will override a "turn on" rule with priority 5.

Tip: GrowVPD Pro logs every automation action with a timestamp and reason. Check the device action history to see if the rule triggered in the past and what caused it to restore. This log is invaluable for debugging.

Issue 3: Sensor Readings Seem Wrong

The sensor reports temperature or humidity values that do not match your handheld meter or what you feel when you enter the tent.

Common Causes

• Sensor placement. A sensor mounted high on the tent wall near the exhaust will read differently from one at canopy level. Always place sensors at the height of the plant canopy, away from walls, lights, and fans.
• Sensor drift. Cheap WiFi sensors (especially Tuya-branded ones) can drift 1–3°C and 3–8% RH over time. This is normal for the price point.
• Direct light exposure. If the sensor is in direct light from your grow light, the enclosure absorbs radiant heat and reports temperatures 2–5°C higher than the actual air temperature. Shield the sensor or move it into the shade.
• Condensation on the sensor. High humidity can cause condensation on the sensor element, making it report 100% RH until it dries out.

Fix: Calibration Offsets

In GrowVPD Pro, each sensor has calibration offset settings. Compare your sensor against a known-accurate reference meter for 30–60 minutes at the same location. Then apply offsets:

• If the smart sensor reads 2°C high, set a temperature offset of -2.0
• If the smart sensor reads 5% RH low, set a humidity offset of +5.0

These offsets are applied to all readings from that sensor before VPD calculation and automation evaluation.

Issue 4: Connection Drops Repeatedly

Devices connect and work for a while, then randomly disconnect and reconnect throughout the day.

Likely Causes

• WiFi signal weakness. Grow tents made of reflective mylar material can partially shield WiFi signals. If the router is in another room, signal inside the tent may be marginal. Use a WiFi signal strength app to check. Below -70 dBm is unreliable.
• Router overloaded. Each smart device maintains a persistent connection to its cloud. 10+ devices on a basic consumer router can cause it to drop connections under load.
• IP address conflicts. If your router's DHCP pool is too small, devices may fail to renew their IP lease and temporarily go offline.
• Cloud service issues. Tuya, AC Infinity, and Mars Hydro all rely on cloud servers. Occasional outages on their end will cause all devices from that platform to appear offline temporarily.

Solutions

• Move the WiFi router closer to the grow area or add a WiFi extender/mesh node
• Assign static IP addresses to your smart devices through your router's DHCP reservation settings
• Use a dedicated 2.4 GHz network for IoT devices if your router supports multiple SSIDs
• Upgrade to a mesh WiFi system if you have more than 15 smart devices

Issue 5: Token Expired / Authentication Failed

GrowVPD Pro shows an authentication error for a platform, and all devices from that platform stop responding.

By Platform

Tuya

Tuya tokens expire every 2 hours but are automatically refreshed. If refresh fails (usually due to network issues during the refresh window), you need to:

1. Go to Settings > Connected Accounts > Tuya
2. Tap Disconnect, then re-enter your Access ID and Access Secret
3. Verify the region matches your Tuya IoT Platform data center

AC Infinity

AC Infinity tokens are long-lived but can be invalidated if you change your password or log in on too many devices. Re-authenticate with your email and password in Settings.

Mars Hydro / Spider Farmer

These platforms use cloud connections that can drop if the app is force-closed or the phone restarts. Open GrowVPD Pro and let it re-establish the cloud connections automatically. If it fails, re-authenticate in Settings.

Issue 6: Emergency Override Stuck "On"

The temp-spike or condensation override fires (fans go max, heater off, dehumidifier off) and never releases, even after temperature comes back to normal.

• Check the recovery window. The override holds for a 10-minute recovery window after conditions return inside the safe band. If the temperature is bouncing around the ceiling (e.g., 31.8°C, 32.1°C, 31.9°C, 32.2°C…), every spike re-arms the recovery timer. Solution: lower the override ceiling slightly (e.g., 31°C instead of 32°C) so you stop kissing the threshold.
• Check sensor placement. A sensor right next to a hot lamp will keep tripping the override even when ambient air temp is fine. Move it to canopy level, away from direct light.
• Manually clear. Open the device action history and tap the active override entry > Clear override. Normal rules resume immediately.

Issue 7: Auto Stage Proposal Dismissed Accidentally

You swiped away the "Looks like flowering — switch stage?" notification by mistake and the proposal does not come back.

• Open the grow in the Diary tab and tap the stage chip in the header. The Auto Stage Detector card shows the current proposal (if any) and lets you accept it, snooze for 24 hours, or disable auto-detection for this grow.
• If the proposal is gone entirely (the engine no longer thinks the stage changed), it likely went away because the day/night signal flipped back. Force a re-check from Settings > Smart Automation > Auto stage detector > Re-check now — the worker re-runs and you will get a fresh notification if the vote still favours a stage change.
• You can always set the stage manually in the diary entry — auto-detection is a convenience, not the source of truth.

Issue 8: Light Ramp Not Happening (Sunrise / Sunset)

Your lights snap on at 100% instead of fading in over 30 minutes.

• Check lightRampSec in stage targets. Open Automation > Tent > Stage targets > Edit. Look for the lightRampSec field — it is in seconds, not minutes. 1800 = 30 min, 3600 = 60 min. If it is 0 or unset, the light simply switches.
• Verify your light supports native ramp. Mars Hydro iConnect, Spider Farmer, SANlight, and Vivosun support native ramp. AC Infinity and Tuya plugs cannot dim — only on/off. For those, the ramp will fall back to step-dimming if the device exposes a brightness DP, or be ignored if not.
• Check the device action log. A successful native ramp shows a single dimming-ramp action with the duration. If the log shows a series of brightness step commands instead, the device fell back to step-dimming.
• Schedule conflict. If the time window of your light schedule is shorter than the ramp duration (e.g., 10-minute window with 30-minute ramp), the ramp gets clipped. Extend the window or shorten the ramp.

Issue 9: Cloud Bridge Not Syncing (Tuya)

Your Tuya devices were working, then suddenly went offline en masse, and the Cloud Bridge status row in Settings shows a red dot.

• Check token expiry. Tuya access tokens last 2 hours but auto-refresh. If your phone was offline during a refresh window or the project was paused, the bridge token may have expired. Open Settings > Tuya Cloud Bridge > Test connection. If it fails, tap Re-link — the wizard re-runs Steps 4–5 (paste credentials & validate) without forcing you through the whole flow again.
• Check trial saturation. Tuya developer trials cap at 50 devices and a daily API quota. If you cross either limit, the bridge stops accepting new device discoveries until the next quota cycle. The Cloud Bridge status section shows quota usage; bridges over 80% of cap show an amber warning.
• Pulsar disconnected, polling fallback. If the live cloud push channel is down but standard polling still works, you will see "Push events: disconnected, polling every 15 min" on the bridge status row. Sensor refresh slows but data still updates. Tap Reconnect Pulsar to re-establish the push subscription.
• Switch region. If you migrated your Smart Life account to a different country (or your VPN moved you), the bridge may now be calling the wrong datacenter. The Switch region action re-tests against the suggested region without you re-pasting credentials.

Issue 10: Automation Runs But Has No Effect

The action log shows the rule triggered and a command was sent, but the physical device did not change state.

• Device firmware update needed. Some devices stop responding to cloud commands after a firmware update changes the API. Update the device through its native app.
• Physical override active. Some devices (especially AC Infinity fans and Mars Hydro lights) have physical buttons that can override cloud commands. Check if the device is in "manual" mode.
• Command not supported. If a rule tries to set a fan to speed 10 but the device only supports speeds 1–8, the command may be silently rejected. Verify the command value is within the device's supported range.

Still Stuck?

If none of the above resolves your issue:

1. Take a screenshot of the Automation tab showing the problematic rule and device status
2. Note the exact error message (if any)
3. Check the Discord community — someone has likely encountered the same issue
4. Contact support through Settings > Support with a description and screenshots