Common Issues

Below are the most common issues encountered when deploying MKTI microservices.

• Port conflicts preventing containers from starting
• JSON formatting errors causing rule failures
• Home Assistant webhook misconfiguration
• Docker not running or daemon unavailable
• Firewall or network restrictions blocking requests
• Containers restarting due to invalid configuration

Port Conflicts

If a container fails to start due to a port conflict, update the port mapping in your Docker Compose file. A full guide will be added here soon.

JSON Errors

MKTI microservices require valid JSON input. If a service fails, check your JSON payload for missing commas, incorrect brackets, or invalid types.

Webhook Issues

Home Assistant webhooks must match the URL and port of your MKTI service. Incorrect webhook URLs are a common cause of automation failures.

Container Restart Loops

Restart loops usually indicate invalid configuration or missing environment variables. More detailed diagnostics will be added here as the documentation expands.