Troubleshooting
Common issues and what to check, in order.
My logic does not run
The most common cause is not clicking RUN. Creating logic and running it are separate steps: click RUN at the top, and check that the device icon shows a connected (green) state.
RUN reports an incompatible configuration error
The device selected at project creation differs from the board of the connected controller. Change the project's device to the actual board, or use All Devices for projects that run on multiple boards (Part 3).
Connection works on the same network but not from outside
Connecting from a different network (external internet, cellular, etc.) uses remote connection traffic, which has a monthly free quota. Once the quota is used up, external connections are limited until the next reset date. Connections on the same network are unaffected by the quota.
Settings changes are not applied
Some items are locked for editing while running. Stop with STOP, make the change, and click RUN again.
A condition triggers too often, or almost never
Sensor readings can flip between true and false in a short time. If the condition triggers too often, stabilize it with the Hold Time option (Part 4). If it almost never triggers, check that the comparison operator and target value match the variable's type.
AI analysis results are not written to variables
AI Analysis is an action, so it runs only when the condition of its control is met. For continuous analysis, set the condition to Always or Once so the analysis keeps running.
No camera feed is shown
Check in Settings → Camera that the camera is registered correctly and that no other program is using it. For USB cameras a faulty cable or hub may be the cause; connect through a different cable or port and check whether the symptom persists.
Dashboard widgets show no values
Widgets show live values while the controller is connected and running. Showing only default values in the editing view (stopped state) is normal behavior.
Notifications (push, Telegram, email) do not arrive
First check whether the action actually executed; if its condition is not met, the action does not run. For Telegram and email, also verify the bot token and server settings registered in Settings.
Audio stutters or playback is delayed
This is common on older operating systems whose audio server is PulseAudio. On devices with limited resources, PulseAudio's buffering and scheduling readily cause dropouts. Upgrading to a version that uses PipeWire as the default audio server is the reliable fix: Raspberry Pi OS and Debian from Bookworm onward, and Ubuntu from 24.04 LTS onward.
The error "Failed to create new vlc instance." appears
Grablo uses VLC for media playback and audio recording. Installing from the .deb package pulls VLC in as a dependency, so nothing extra is needed there, but this error appears in environments without VLC. Install it from the controller's terminal.
sudo apt-get update sudo apt-get install -y vlc
Installation reports that the account is not in the sudoers file
The login account lacks administrator (sudo) rights. Connect to the controller,
switch to root with su, and add the account to
/etc/sudoers. See Appendix B
for how to connect.
su nano /etc/sudoers
Add one line in the following form, save, and install again.
username ALL=(ALL:ALL) ALL
Files cannot be uploaded
File uploads require a connected device. If uploads fail while connected, the free storage (1GB) may be full; remove unused files (Part 3).