Troubleshooting

Troubleshooting

First checks

1. Open OSPy → Diagnostics and find the plug-in health entry and latest error.
2. Confirm that the plug-in is installed, enabled and compatible with the current OSPy and Python versions.
3. Reopen the plug-in settings and verify required fields, addresses, files and credentials.
4. Confirm that every required dependency is installed, enabled, configured and healthy.
5. For hardware, verify power, wiring, bus address, GPIO or serial device and operating-system access.
6. Check the plug-in page for retry behavior, test mode, calibration and expected status indications.

Common causes

• A permission was added by an update but has not been approved.
• An I²C address, GPIO, serial port, station output or other resource is already used.
• A required Python or operating-system package is missing.
• A local service, Internet endpoint, e-mail server, database, MQTT broker or Shelly device is unavailable.
• The provider has not produced its first cached reading after startup.
• A safety plug-in is deliberately in test, monitor-only, bypass or locked-incident state.

Reporting a problem

Open an OSPy-plugins issue and include the OSPy version, plug-in version, Python version, operating system, exact steps, expected and actual behavior, and relevant Diagnostics output. Remove passwords, API tokens, e-mail addresses, private addresses and other secrets before posting.

Back to the documentation home