Skip to content

App Simple HTTP Connector

Arie J. Godschalk edited this page Nov 12, 2026 · 3 revisions

Simple HTTP Connector for Flows

Supported apps · Variables · API

The public Simple HTTP Connector for Flows source documents actions that extract JSONPath values from HTTP responses or JSON tokens into Better Logic variables.

For example, given a JSON response {"temperature":21}, a documented JSONPath-to-Better-Logic action can select $.temperature and store the result in a suitable BLL number variable. Configure the HTTP request and select the variable in the connector's card. Verify the response and path before relying on the result.

The public source uses an older Homey SDK. Check whether a compatible version is available for your Homey and whether its cards are still present. This is a variable integration; a BLL permission or variable action does not establish that {[ ... ]} is decoded in the connector's text fields.

Poll a measurement into a variable

The original app topic announces Better Logic variable actions, including number-variable support. The source README calls the relevant action GET JSONpath Better Logic (A22).

A test-data adaptation is:

  1. Create a BLL number variable ApiTemperature.
  2. Trigger the Flow on a suitable polling schedule.
  3. Select GET JSONpath Better Logic and your endpoint.
  4. For a response {"temperature":21}, choose $.temperature.
  5. Select ApiTemperature as the destination.
  6. Check the actual variable value after running the card.

Paths depend on the response. For {"readings":[{"watts":125}]}, the corresponding adapted path is $.readings[0].watts. Confirm both the selected value and its type before using it in a calculation.

These are historical card names, not a guarantee of availability on current Homey models. The 2019 compatibility report specifically describes a green card result without a variable update. Verify the end result, not only the card's success indicator.

Community example: an authenticated DSMR request

The DSMR Reader discussion provides HTTP options with an X-AUTHKEY header, and the follow-up confirms the request works. The app allows a JSON options object in the URL field. A placeholder adaptation is:

{"method":"get","protocol":"https:","hostname":"YOUR-DSMR-HOST","path":"/api/v2/datalogger/dsmrreading","headers":{"X-AUTHKEY":"YOUR-PRIVATE-KEY"}}

Use the protocol and API path actually supported by your server. The original uses HTTP; prefer HTTPS when available, particularly outside a trusted local network. The request solution demonstrates header handling, not the response schema: inspect your own DSMR response before choosing the JSONPath and BLL destination.

Never publish the real key in screenshots, exported Flows or logs.

Receive JSON instead of polling

The source documents Incoming POST (T30) exposing a JSON token, and JSONpath Better Logic (A80) extracting a value from it. An adapted workflow is:

  1. Configure the connector's incoming event and access controls.
  2. Receive {"temperature":21} as the request body.
  3. Pass the JSON token to the JSONPath-to-Better-Logic action.
  4. Extract $.temperature into the BLL number variable.

Do not copy obsolete authorization-bypass or whitelist instructions from older versions. The README itself warns of whitelist limitations on Homey v2. For current setups, verify platform support and authentication first. If these old connector cards are unavailable, the MQTT/JSON extraction workflow illustrates the same extract-then-set pattern using explicit BLL actions.

Clone this wiki locally