Repository navigation
App Simple HTTP Connector
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.
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:
- Create a BLL number variable
ApiTemperature. - Trigger the Flow on a suitable polling schedule.
- Select GET JSONpath Better Logic and your endpoint.
- For a response
{"temperature":21}, choose$.temperature. - Select
ApiTemperatureas the destination. - 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.
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.
The source documents Incoming POST (T30) exposing a JSON token, and
JSONpath Better Logic (A80) extracting a value from it.
An adapted workflow is:
- Configure the connector's incoming event and access controls.
- Receive
{"temperature":21}as the request body. - Pass the JSON token to the JSONPath-to-Better-Logic action.
- Extract
$.temperatureinto 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.
Support development - If Better Logic Library is useful to you, you can support its
continued development through GitHub Sponsors,
Patreon,
PayPal, or
bunq.
Thank you!