We have an official thread for this plugin. HTTP_Control basically can be used as a structure to build custom plugins. If you have some device that is a one-off or otherwise no one wants to make a plugin for it, and it accepts get/post/put/delete requests and responds with plain text or json responses, then you can use http control to create IoX nodes. It is similar to network resources but adds the fact that it creates nodes so sending requests can be done directly from scenes and then the bigger thing is that responses go into nodes and again can be used directly in scenes. Of course you can still use programs to control it. The biggest advantage over network resources is that responses are accepted and usable. The simple example is a thermometer that you make into a thermostat. You can send a request from a node and get a response that then goes into a node. Within the plugin configuration you set certain values to be "on" or "off" allowing for the node to turn scenes on or off, or in the case of a thermostat, perhaps a heater or cooler. You might say above 38 is "on" below 35 is "off" for a fridge., Between 35 and 38 are left alone as hysteresis zone,.

Just updated the plugin to now be configurable from a nice html interface. No plugging in all kinds of parameters and values into the plugin config page. Also added xml to parsing.

@apostolakisl Thank you for building this. Installed it and setup API calls to a local computer we use for music and can now get status values back to the eISY. Works great.

@apostolakisl after upgrading to 1.5.3 (and later to 1.6.1) backups of eisy-ui fail with these messages in the eisy-ui log:

2026-11-01 08:12:40 [error] web: Backup failed: Error: EACCES: permission denied, open '/var/eisyui/ns/plugin_9/data/http_control_identity.json'

2026-11-01 08:12:40 [error] web: Error with API request to GET /api/system/backup/create: Error: EACCES: permission denied, open '/var/eisyui/ns/plugin_9/data/http_control_identity.json'

I have submitted a ticket to UD but didn't know if there's something you can do to fix this. Thanks!

HTTP_Control-log-2026-11-01T16-38-51.321Z.zip

Edited 23 hours ago23 hr by Mr B
Update: also getting a ton of errors in the 1.6.1 log (attached). None of my configured endpoints survived the upgrade. They still show up in the node list but they don't show up in the editor or in the plugin configution. Installing in PG3 allows BU.

To continue...

Moving HTTP_Control to PG3 allows the eisy to complete a backup. However the the endpoint configuration editor page doesn't work. Have to configure from the plugin page in PG3.

Maybe pm me your log. I currently have the most recent eisy firmware and installed http control locally from eisy developer plugins (not legacy ph3x) and it is all working. Ud mentioned that they were going to start blocking ports on eisy, perhaps they have with the latest firmware but for whatever reason a local install bypasses that. I assume you are running the latest version of http control. Exactly what happens when you open the html confirmation page? If it is port blocks, they said that they would then open ports for plugins after vetting it. So maybe I need to request that.

I see that you posted a log earlier and am looking at it. it appears the port isn't blocked and the html editor is starting, but something with the migration from the old way of storing all the configuration values to the new way where it is shared with the eisy ui config page.

Should all be fixed now.