httptomqtt.net

What it is

HTTP to MQTT is a microservice that converts HTTP REST requests into MQTT publishes. It targets a common scenario: an app, webhook, or automation platform can only send HTTP requests, while the user already has an MQTT broker and an IoT automation setup. By calling its API endpoint and passing parameters such as broker, topic, and payload, you can publish messages to MQTT.

Core capabilities and ecosystem

Based on the page, its core function is very focused: an HTTP request comes in, and an MQTT message goes out. The sample endpoint is https://api.httptomqtt.net/v1/mqtt/publish?..., making it suitable for quickly connecting web service events to MQTT topics for lights, sensors, home automation devices, and similar use cases. It also provides a ready-made IFTTT Action, which can be used with IFTTT’s large ecosystem of triggers, assistants, and automation integrations. The page does not specify supported languages or frameworks, but since it is called via a REST API, any language or platform capable of sending HTTP requests can use it. No SDK information was found.

Pricing and limits

Pricing is clear and the entry barrier is very low. The free tier costs 0€/month, but the limitations are fairly noticeable: the broker must respond within 250ms, messages are capped at 6 per minute, only up to 2 predefined brokers and 5 predefined topics are allowed, and both topic and broker are locked. The 1€/month Rip-Off tier increases the broker timeout to 750ms, allows 128 messages per minute, removes broker and topic limits, and lets them be passed dynamically via HTTP parameters, making it much more flexible.

Pros and cons

The advantages are simplicity, low cost, and quick setup, especially for connecting IFTTT or other HTTP-only services to MQTT. The downsides are also clear: the page does not disclose key details such as authentication, security mechanisms, MQTT authentication methods, TLS, error handling, or service availability commitments. It also does not say whether the project is open source or supports self-hosting. The free tier’s timeout and rate limits are tight, making it better suited for testing or low-frequency control rather than critical production workflows.

Who it is for and access from China

It is suitable for IoT hobbyists, Home Automation users, and developers who need a quick Webhook-to-MQTT bridge. It is not ideal for enterprise scenarios with strict compliance, security, or SLA requirements. The page does not provide information about access from mainland China, so real-world testing is needed; payment methods are also not specified. If access or reliability is limited, alternatives such as Node-RED, n8n, a self-hosted HTTP-to-MQTT bridge, or Home Assistant automations may be worth considering.