Top 10 VSCP-Works Features You Should Know

Troubleshooting VSCP-Works: Common Issues and Fixes

1. VSCP-Works won’t start

• Symptom: Application fails to launch or crashes on startup.
• Likely causes: Corrupted installation, missing dependencies, incompatible Qt version, permission issues.
• Fixes:
  1. Reinstall latest VSCP-Works release for your OS.
  2. Ensure required Qt runtime is installed (match VSCP-Works build). On Linux, check ldd on binary for missing libs.
  3. Run as administrator/root once to rule out permission issues.
  4. Start from a terminal to capture error output and inspect logs (look in app data folder or console for stack traces).
  5. If crash persists, create a clean config (move ~/.vscpor %APPDATA%scp-works to backup) and restart.

2. Cannot connect to VSCP daemon or remote node

• Symptom: Connection refused, timeouts, or “no route” errors.
• Likely causes: Wrong host/port, firewall, daemon not running, TLS/auth mismatch.
• Fixes:
  1. Verify daemon is running on the server (systemd/service manager or process list).
  2. Confirm host, port, username/password, and protocol (TCP/UDP/SSL) match client settings.
  3. Test connectivity with telnet/nc (e.g., nc -vz host port) and check firewall rules on both ends.
  4. If using TLS, verify certificates and that both sides accept the chosen cipher/TLS version.
  5. Check daemon logs for rejected connections or auth failures.

3. Events not appearing in event monitor or UI

• Symptom: Sent events don’t show up; devices appear unresponsive.
• Likely causes: Filter settings, wrong network interface, event queue overflow, incorrect GUIDs/addresses.
• Fixes:
  1. Remove or widen filters in the event monitor (check class/type filters and source/destination).
  2. Ensure VSCP-Works is listening on the correct network interface (especially on multi-homed systems).
  3. Inspect event queue sizes and clear/restart if overflowed.
  4. Verify device GUIDs, node addresses, and that events are being generated (use packet capture e.g., Wireshark to confirm on the wire).
  5. Check for duplicate or conflicting plugins that may swallow events.

4. Rules or scripts not triggering

• Symptom: Automation rules, actions, or scripts don’t run when conditions are met.
• Likely causes: Incorrect rule conditions, script errors, disabled rules, or misordered rules.
• Fixes:
  1. Confirm the rule is enabled and saved.
  2. Validate the condition (class/type, data content, source) exactly matches incoming events.
  3. Check script logs or run scripts manually to catch syntax/runtime errors.
  4. Use logging actions (temporary) at rule start to verify condition matching.
  5. Ensure rule execution order and priorities aren’t preventing expected behavior.

5. Device/driver plugin problems

• Symptom: Plugins fail to load or behave unpredictably.
• Likely causes: Version incompatibility, missing dependencies, wrong configuration.
• Fixes:
  1. Confirm plugin is compatible with your VSCP-Works version.
  2. Check plugin-specific configuration (ports, baud rates, vendor IDs).
  3. Review plugin logs for load or runtime errors.
  4. Recompile/reinstall plugin if using locally built binaries.
  5. Disable other plugins to isolate conflicts.

6. Performance issues or high CPU/memory usage

• Symptom: UI sluggish, CPU spikes, memory growth.
• Likely causes: Large event flood, memory leak in plugin, excessive logging.
• Fixes:
  1. Reduce event rate (throttle sources) or apply stricter monitor filters.
  2. Disable verbose logging or rotate logs.
  3. Restart application to clear transient leaks; update to a release that fixes known leaks.
  4. Profile plugins by disabling them one at a time to find the culprit.

7. Persistence problems (config not saved)

• Symptom: Settings or rules lost after restart.
• Likely causes: Permission issues, config file corruption, wrong config paths.
• Fixes:
  1. Verify application has write access to config directories.
  2. Inspect and repair or delete corrupt config files (keep backups).
  3. Confirm you use the intended profile if VSCP-Works supports profiles.

8. Debugging checklist (quick steps)

1. Reproduce issue and capture exact error messages.
2. Check VSCP-Works logs and system logs.
3. Run app from terminal for console output.
4. Use network tools (ping, nc, Wireshark) for connectivity problems.
5. Temporarily simplify setup (single device, minimal rules/plugins).
6. Update VSCP-Works and plugins to latest stable versions.
7. If unresolved, collect logs, config files, and exact steps and consult project support channels or issue tracker.

If you want, I can produce a checklist tailored to your OS (Windows/macOS/Linux) or help interpret specific log excerpts—paste the error lines and I’ll analyze them.