Post command to enable/disable device

I used to use a POST command to enable and disable devices on my hub using this POST command;

http://[hub ip]:8080/device/disable?id=xxxx&disable=true

Sometime in the past few hub updates this command stopped working. Was this option removed from the hub? And/Or is there another way of accomplishing the same thing another way?

What platform version are you running? Check Settings > Hub Details to see.

Another approach from Rule Machine o disable/enable a device:

I’m using webCoRE and NodeRED but thanks for the tip.

Running 2.5.0.153.

It used to work but don’t know when that option was removed because I don’t use the command that often

I thought that was addressed before then, but that could have been only for internal use by the hub. You could try a JSON body instead of URL parameters for your data, which I think worked even when this was temporarily broken for "official" usages before. (It's not really supported, so I'm still not saying it will, but that did work when the URL parameters didn't when this issue was first discovered...)

I wonder if this would be worth exposing over Maker API. :thinking:

In webCoRE I send is as JSON. Agree, It would be a nice feature to incorporate into Maker API

I'm confused, since your original posts shows URL parameters. If something still isn't working, can you explain how it's constructed?

This is the webCoRE piston that issues the POST command along with the logs.

6/7/2026, 4:59:32 PM +869ms
+2ms â•”Working queued event [Home - Hub1].wc_async_reply = httpRequest with a delay of 100ms, canQueue: false, calledMyself: true
+6ms â•‘Runtime (6269 bytes) initialized in 1ms (v0.3.114.20240115_HE)
+24ms â•‘â•”Execution stage started
+31ms ║╚Execution stage complete. (6ms)
+35ms ╚Event processed successfully (34ms)
6/7/2026, 4:59:32 PM +704ms
+7ms â•”Received event [Home - Hub1].test = 1780865972704 with a delay of 1ms, canQueue: true, calledMyself: false
+21ms â•‘Runtime (6227 bytes) initialized in 2ms (v0.3.114.20240115_HE)
+23ms â•‘â•”Execution stage started
+35ms â•‘â•‘Executed virtual command httpRequest (2ms)
+37ms â•‘â•‘Requesting wake up at Sun, Jun 7 2026 @ 4:59:56 PM EDT (in 23999ms) for 1 (st:2)
+40ms ║╚Execution stage complete. (18ms)
+84ms â•‘Setting up scheduled job for Sun, Jun 7 2026 @ 4:59:56 PM EDT (in 23990ms)
+86ms ╚Event processed successfully (82ms)
6/7/2026, 4:59:32 PM +769ms
+4ms â•”Received event [Home - Hub1].wc_async_reply = httpRequest with a delay of 0ms, canQueue: true, calledMyself: false
+6ms ╚Event queued (2ms)

Based on this post, it doesn't look like you're sending a JSON body (or any) at all:

Based on that, it also looks like, unless you're using variables, you'd need to manually construct a JSON string to use for a "CUSTOM" body type (and eliminate the URL parameters — with some digging, that's what changed recently and no longer works, but JSON body still should and does to me externally to the hub with curl, so webCoRE on the hub should, too, if you find the right way to make it actually send what you want; I don't use webCoRE myself so won't be much help beyond that).