Possibility of GET requests on events

[deadphreaker]

It will be good addition, if there will be ability to send GET requests on events like button down or buton up with sending in GET request some variables (e.g. temperature setpoint) directly to different devices (like OpenBeken) supporting http requests or to PHP script running on Apache.

[fvanroie]

Hi, thanks for the suggestion. I don't own devices with HTTP endpoints only. That seems to be a job for a Home Automation system.
Just to get a better idea of your suggestion: can you please share exactly what the HTTP endpoints would look like?

[deadphreaker]

It may look like described there
https://www.elektroda.com/qa,openbeken-http-command-cm-cmnd-guide.html
The main idea is have access to objects and variables in openHASP (for example with names of control like in Object Oriented Programming - slider.value or something like that).

So the openHASP can manage devices directly through HTTP requests (for example writing setpoint in channels) or send GET request to PHP script with parameters in URL so that script can handle them and proceed with them to different devices.
The idea is about to make openHASP more flexible and applicable to different protocols/syntax to cover more devices and a lot of other systems.

[fvanroie]

Thanks for the clarification! The webpage describes a different HTTP-based approach. While event-driven HTTP hooks can be useful for some use cases, this is currently out of scope for the project.

GET requests would only serve very simple one-to-one scenarios and cannot respond to openHASP, e.g. with state updates.

or send GET request to PHP script with parameters in URL so that script can handle them and proceed with them to different devices

Translation is typically handled by a dedicated home automation system. As soon as you need a script to glue devices together, that system should also be able to monitor MQTT messages from openHASP and handle routing accordingly.

openHASP is primarily UI/event-driven, while orchestration (MQTT/HTTP requests, device logic) is usually handled by systems like Home Assistant, Node-RED or openHAB.

This would require some form of bidirectional HTTP communication, which in turn needs a proper API design to be useful across many different scenarios. While valid use cases exist, I would need more examples and broader user feedback to justify this shift in philosophy.