dasshio: HassOS, VMDK - Status Code 401, Bad Request

I am seeing the same thing here.

{
  "timeout": 5,
  "buttons": [
    {
      "name": "Bathroom",
      "address": "38:F7:3D:7B:91:99",
      "domain": "script",
      "service": "toggle",
      "service_data": "{\"entity_id\": \"script.toggle_bathroom\"}"
    },
    {
      "name": "KimsToggle",
      "address": "00:FC:8B:7C:A8:24",
      "domain": "light",
      "service": "toggle",
      "service_data": "{\"entity_id\": \"light.kims_light\"}"
    },
    {
      "name": "RJToggle",
      "address": "18:74:2E:89:54:BA",
      "domain": "light",
      "service": "toggle",
      "service_data": "{\"entity_id\": \"group.bedroom\"}"
    }
  ]
}

Log

2018-07-23 21:43:14,608 | INFO | Packet captured, waiting 5s ...
2018-07-23 21:43:19,612 | INFO | Starting sniffing...
2018-07-23 23:14:47,797 | INFO | Bathroom button pressed!
2018-07-23 23:14:47,798 | INFO | Request: http://hassio/homeassistant/api/services/script/toggle
2018-07-23 23:14:47,806 | INFO | Status Code: 401
2018-07-23 23:14:47,806 | ERROR | Bad request
2018-07-23 23:14:47,810 | INFO | Packet captured, waiting 5s ...
2018-07-23 23:14:52,815 | INFO | Starting sniffing...
2018-07-23 23:16:42,428 | INFO | RJToggle button pressed!
2018-07-23 23:16:42,428 | INFO | Request: http://hassio/homeassistant/api/services/light/toggle
2018-07-23 23:16:42,440 | INFO | Status Code: 401
2018-07-23 23:16:42,440 | ERROR | Bad request
2018-07-23 23:16:42,443 | INFO | Packet captured, waiting 5s ...
2018-07-23 23:16:47,448 | INFO | Starting sniffing...

I’m still able to manually make a service call to toggle the groups.

Edit: I saw the discussion going on in #40 and here, I’ve uninstalled and removed the repo, then rebooted HassIO, installed the repo and addon, saved the config, rebooted HassIO again, same problem unfortunately.

Edit 2: Seems like the internal API is rejecting the request for some reason. I’ve modified my buttons to make the request manually, by passing in the x-ha-access header, and calling the relevant API manually to temporarily fix this. My config now looks like this:

{
  "timeout": 5,
  "buttons": [
    {
      "name": "Bathroom",
      "address": "38:F7:3D:7B:91:99",
      "url": "http://localhost:8123/api/services/script/toggle",
      "headers": "{\"x-ha-access\": \"YOURPWHERE\"}",
      "body": "{\"entity_id\": \"script.toggle_bathroom\"}"
    },
    {
      "name": "KimsToggle",
      "address": "00:FC:8B:7C:A8:24",
      "url": "http://localhost:8123/api/services/light/toggle",
      "headers": "{\"x-ha-access\": \"YOURPWHERE\"}",
      "body": "{\"entity_id\": \"group.kimsroom\"}"
    },
    {
      "name": "RJToggle",
      "address": "18:74:2E:89:54:BA",
      "url": "http://localhost:8123/api/services/light/toggle",
      "headers": "{\"x-ha-access\": \"YOURPWHERE\"}",
      "body": "{\"entity_id\": \"group.bedroom\"}"
    }
  ]
}

Just merged. Sorry guys but I was on holiday. Just released 0.3.1 with the fix. You’ll tell how it goes!

@e2m32 The code is correct, you just used the wrong header key. x-hassio-key is for the Hass.io API. Use x-ha-access for Home Assistant API requests. I just tested and it worked for me.

, headers={'x-ha-access': os.environ.get('HASSIO_TOKEN')}

@maur54, @wwwebrat, @jmoery, @JesseWebDotCom here’s a work around until the internal api link is fixed.

Thank you @russjr08!

{
  "timeout": 20,
  "buttons": [
    {
      "name": "mybutton1",
      "address": "AB:CD:EF:GH:IJ:00",
      "url": "https://<myhasubdomain>.duckdns.org:8123/api/services/light/toggle",
      "headers": "{\"x-ha-access\": \"my_ha_api_paswd\",\"Content-Type\": \"application/json\"}",
      "body": "{\"entity_id\": \"light.bathroom\"}"
    }
   ]
}

@danimtb set this up so the button can also call external api’s, not just the internal one provided for Add-Ins. If you have your HA API exposed, you can utilize that functionality to call it this way. If you’re not using a domain name, just use your HA’s internal IP address and drop https (assuming your not using SSL). I tried using https://192.168.x.x (internal IP), but I got an error.

Note that if you add users with the new authentication method that is coming soon, this will likely break your buttons. You’d have to update your headers.

An update for hassio has been released in order to fix the api issue https://twitter.com/pvizeli/status/1021854007546073088?s=21

Thanks @shoejosh! All these names, Hassio, Hassos, Home Assistant. Thanks for the explanation.

Hrm… Mine’s not working. Just updated to Hass.io Supervisor 121 (thats the version that showed up in my UI) and HA 0.74.1. I tried restarting the Dashio Add-on and my rPi. Anyone have any ideas? Roll back to Supervisor 120?

Same. HA 0.73.1 and was working great till yesterday. I don’t recall performing and updates which is why it’s a head scratcher that it just flat out stopped.

Working again!

The 0.3.1 release didn’t appear on hassio panel, but a reinstallation did the trick. Hours later the new version showed up.

Confirmed working here as well, thanks a bunch!

Working for me. Thanks Daniel.

@grantalewis, I wanted to make sure I could fix it first. Didn’t want to make any promises. As you can see, I needed some help.

Shoejosh did open up a PR for this, so looks like it just needs to be merged 👍

With @e2m32 suggestion now goes!!! Thanks!!

{ “timeout”: 2, “buttons”: [ { “name”: “son_UNO”, “address”: “FC:XX:67:XX:32:60”, “url”: “http://192.168.1.XXX:8123/api/services/light/turn_on”, “headers”: “{"x-ha-access": "xxxxx my password","Content-Type": "application/json"}”, “body”: “{"entity_id": "light.son_uno"}” }, { “name”: “son_UNO1”, “address”: “FC:XX:67:9B:XX:50”, “url”: “http://192.168.1.XXX:8123/api/services/light/turn_off”, “headers”: “{"x-ha-access": "xxxxx my password","Content-Type": "application/json"}”, “body”: “{"entity_id": "light.son_uno"}” } ] }

Add-ons communicating via http://hassio/homeassistant/ need to send the environment variable HASSIO_TOKEN (docs) as authentication. Not the users password.

Please, update Hass.io supervisor to version 120 to solve this issue. No matter if you are running resinOS or hassOS. Thanks!