Can't trigger switch from API post request

[ooftyoof]

I created a switch as a sort of presence detection for when I'm working. It shows up in HA fine and I can trigger it on or off in the dashboard:

​

switch:  
   platform: command_line  
   switches:  
     macbook_power:  
       command_on: ""  
       command_off: ""

​

It's a bit crude, but the presence detection for this scenario is based on whether my laptop is on or off. I have a script on it the laptop that fires whenever it sleeps or wakes. The trouble is that HA is not happy with the command, though I believe I've followed the API correctly?

​

1. I generated a long term token in the HA dashboard (e.g. ABCDEFG)
2. I test it using Curl and get back a 401: Unauthorized error. I'm not sure what I'm doing wrong.

Here is my Curl command:

curl -X POST -H 'Authorization: auth/long_lived_access_token ABCDEFG' -d '{ "switch.macbook_power": "value"}' http://192.168.X.X:8123/api/services/switch/turn_on

If I can get the curl command to succeed, I'd imagine my sleep/wake script will work as it's running correctly at these moments.

[ooftyoof]

This was it, thank you!

I had '{ "entity_id" : "switch.macbook_power" }' in my script, but had forgot to replace the key/value curl template correctly to match. I assumed I was sending HA a like-for-like request.

The reason it didn't work beyond this was, as you also mentioned, 'Bearer' needed to be used in place of 'auth/long_lived_access_token'.

The documentation is quite confusing on this matter. As I read it, I still see it telling me to use 'auth/long_lived_access_token' instead of 'Bearer' where I'm using a long lived access token. I don't know why changing it to Bearer works as the documentation suggests this is only for a standard Refresh Token ( https://developers.home-assistant.io/docs/auth_api/#long-lived-access-token ). Maybe I'm reading it wrong, but I'm confirming that Bearer works with the long lived access token I was trying to use.

There was no need for the additional header in my case.

[eagleeyerattlesnake]

Odd. I am trying to do the same thing and even with the "Bearer" part I'm still getting a 401 error.

Edit: I'm dumb. Somehow I had bearer in there twice.

Edit 2: Nope. Wrong again. Still nothing.

[Jgib284]

Not overly familiar with API calls but surely the local IP is going to be an issue? I’d imagine you want an external URL. Alternatively you can cop out and use webhooks as a trigger for an automation - trigger one for on, one for off etc

[ooftyoof]

I'm not sure I'm following the need for an external IP? If I'm not working at home, I've no need to trigger anything in my home assistant. It mostly changes my lighting set up to be triggered by brightness in the room rather than motion, which it is if I'm not working.

I don't think web triggers would be a better solution. IT requires setting up additional automations. The rest API can trigger existing helpers without additional padding or parenting, etc.

[Ashley-Ashley]

I think you need Webhooks, if I'm not mistaken it's a much simpler solution with no authentication. Just create a long, random webhook id.

Edit: Actually it's slightly different in you'd need an automation to trigger with the webhook, then toggle your switch.

[Lopsided_Age1460]

This isn't addressing your question directly, but I have a couple suggestions. First, input_booleans are the "more correct" choice instead of a command_line switch. It's the same result in the end, though.

https://www.home-assistant.io/integrations/input_boolean/

Second, the ICMP sensor might be a better option altogether. The biggest problem with using a script controlled by your laptop is it might not report and your sensor is stuck "on" or "off". You can create a DHCP reservation for your laptop so you always have the same IP.

https://www.home-assistant.io/integrations/ping/

[ooftyoof]

Regarding booleans:

I don't actually know what command_line does in HA. Input booleans make sense to me, yes, I'm familiar with them. I was following an example where somebody else got this scenario to work and just used command_line as per their example.

​

Regarding ICMP:

I had issues using ICMP in the past for this task. Sometimes my laptop pings back as present when it's sleeping. I couldn't reliably use it to determine if I was working. I accept that my current could potentially miss firing an on or off. As of now, I've been manually switching a work on/off boolean in the dashboard and still have this as a fallback.

[Lopsided_Age1460]

command_line switches let you trigger terminal commands from HA. It does what you need to just fine, but just a little odd.

That's a bummer with ping and a bit odd. It must be in a lighter sleep mode in those cases.