What the fuck is this?

Got some fancy application that you would like to use as a trigger for something?
Does that fancy application only speak HTTP?
Would you rather have it speak to your already running MQTT Setup?
Classic.
The idea behind this microservice (Let the buzzwords flooow) is to let you fire a basic af HTTP request at our REST-Endpoint (Another one!) which in turn publishes a message on some definied MQTT broker

How does it work?

  • send

    Fire HTTP request

    You know, like opening a website, but automagically
    (Well, you could do it manually)

  • sync

    ???

    HTMS does it's thing, publishing your message on the MQTT broker

  • lightbulb_outline

    Profit

    Light turns on
    (Or flushes your IoT connected toilet)

Still don't know what's going on?

Publishing a message on some MQTT Broker could be as simple as calling this:

https://api.httptomqtt.net/v1/mqtt/publish?broker=broker.tld&topic=couch/backscratcher/active&payload=SI
OR
Use our ready-to-use IFTTT Action and integrate with thousands of exisiting triggers / assistents etc.

Pricing

It does cost a fortune, right?
absolutely [...] not, Albert Einstein, 1930

Free tier
0€/month. Crazy, right?

  • access_time 250ms Broker timeout
  • message 6 MSG/Min.
  • dns 2 Brokers
  • list 5 Topics
  • lock_outline Locked Topics & Brokers

The completly free tier specifies the following limitations:

  • Your broker has to respond in 250ms max., otherwise the request will be terminated.
  • You can publish up to 6 messages per minute. Distribution does not matter.
  • You can send to 2 different brokers, which need to be pre-defined.
  • You can publish on up to 5 topics. The topics need to be pre-defined and apply to both brokers.
  • The Rip-Off tier allows you to use topics and brokers defined in HTTP parameters, no pre-definition needed.

Rip-Off tier
1€/month. I plan on spending every penny on nuggets.

  • access_time 750ms Broker timeout
  • message 128 MSG/Min.
  • dns Unlimited Brokers
  • list Unlimited Topics
  • lock_open Unlocked Topics & Brokers

Limitations? Pfft.

  • Increased broker timeout to 750ms . After that requests will still be terminated.
  • You can publish up to 128 messages per minute. Plenty of toasts per second.
  • You can use as many brokers as you like, which can be, but don't need to be pre-defined.
  • You can publish on any topic you like. The topics don't need to be pre-defined. You can still do it anyway.
  • Since you're using the Ripp-Off tier, the endpoint accepts any broker and topic you throw at it, no further configuration needed.

Convinced?

That took longer than expected.