Can't start container via rest template since HA 2023.6

[jschaeke]

More info on https://community.home-assistant.io/t/rest-switch-stopped-working/581188

[raulibi]

Same problem

[evoteknic]

I get the same error

[philhawthorne]

Thanks for reporting.

There might have been a change to the rest sensor in home assistant. I vaguely remember talking about it on a podcast episode recently, but could be mistaken.

I am using MQTT discovery via the dev branch. I'll see if I can replicate using a rest yaml switch to see what is up.

[mitchellross]

Log:

Logger: homeassistant.components.rest.switch
Source: components/rest/switch.py:180
Integration: RESTful (documentation, issues)
First occurred: 10:37:07 AM (1 occurrences)
Last logged: 10:37:07 AM

Error while switching off http://local.ip:8126/container/frigate

Not sure that's particularly helpful?

[philhawthorne]

Thanks @mitchellross

I can see the same for me at the moment.

The server I'm testing with doesn't seem to be working at all for me at the moment (even via Postman) so need to do a bit further digging.

I changed the command to use webhook.site. I suspect Home Assistant is posting the data raw, and not in the same way it used to (ie JSON or HTTP post fields)

The hunt continues for the moment

[mitchellross]

Thanks Phil. Luckily its still reporting state fine to HA, so we can use a workaround for the moment with rest_commands and a script that turns off when state is on and vice versa. Eg. rest_command: temp_frigate_on: url: http://local.ip:8126/container/frigate/start temp_frigate_off: url: http://local.ip:8126/container/frigate/stop and script: alias: Temp frigate switch sequence: - choose: - conditions: - condition: state entity_id: switch.frigate state: "on" sequence: - service: rest_command.temp_frigate_off data: {} - conditions: - condition: state entity_id: switch.frigate state: "off" sequence: - service: rest_command.temp_frigate_on data: {} mode: restart

[philhawthorne]

Have nailed this down to Home Assistant no longer sending the content-type header application/octet-stream.

2023.5

curl -X 'POST' 'http://192.168.1.x:8126/container/xxx' -H 'connection: close' -H 'content-type: application/octet-stream' -H 'content-length: 18' -H 'accept-encoding: gzip, deflate' -H 'accept: */*' -H 'user-agent: HomeAssistant/2023.5.4 aiohttp/3.8.4 Python/3.10' -H 'host: 192.168.1.x' -d $'{"state": "start"}'

2023.6

curl -X 'POST' 'http://192.168.1.x:8126/container/xxx' -H 'connection: close' -H 'content-length: 18' -H 'user-agent: HomeAssistant/2023.6.1 httpx/0.24.1 Python/3.11' -H 'accept-encoding: gzip, deflate, br' -H 'accept: */*' -H 'host: 192.168.1.x' -H 'content-type: ' -d $'{"state": "start"}'

This could be a bug introduced when moving from aiohttp to httpx, which was done in this PR: home-assistant/core#90768

Interestingly, as @jschaeke pointed out, adding the header back to the YAML doesn't seem to fix the switch, which sounds like this new library Home Assistant is using is removing that header.

I'll raise this as an issue in Home Assistant core and see what the Home Assistant devs think here. There might be other REST sensors/switches etc that are now broken/unsupported. If the devs decide on that side they won't put a change in, then I'll update HA-Dockermon to be compatible with 2023.6 moving forward.

[philhawthorne]

2023.6 Workaround

switch:
  - platform: rest
      resource: http://192.168.1.x:8126/container/xxx
      name: XXX Test
      body_on: '{"state": "start"}'
      body_off: '{"state": "stop"}'
      is_on_template: '{{ value_json is not none and value_json.state == "running" }}'
      headers:
        content-type: 'application/octet-stream'

Seems the content-type header is case sensitive, and in the case of HA-Dockermon expects it to be sent the same way 2023.5 would send it, lowercase.

[jschaeke]

Workaround works indeed, I tried it indeed like that before, but probably, like you said, it had wrong capitalized casing.

[hitesh-singh]

2023.6 Workaround

switch:
  - platform: rest
      resource: http://192.168.1.x:8126/container/xxx
      name: XXX Test
      body_on: '{"state": "start"}'
      body_off: '{"state": "stop"}'
      is_on_template: '{{ value_json is not none and value_json.state == "running" }}'
      headers:
        content-type: 'application/octet-stream'

Seems the content-type header is case sensitive, and in the case of HA-Dockermon expects it to be sent the same way 2023.5 would send it, lowercase.

Thanks much @philhawthorne, this works fine

[TomAutoHome]

2023.6 Workaround

switch:
  - platform: rest
      resource: http://192.168.1.x:8126/container/xxx
      name: XXX Test
      body_on: '{"state": "start"}'
      body_off: '{"state": "stop"}'
      is_on_template: '{{ value_json is not none and value_json.state == "running" }}'
      headers:
        content-type: 'application/octet-stream'

Seems the content-type header is case sensitive, and in the case of HA-Dockermon expects it to be sent the same way 2023.5 would send it, lowercase.

My automations using ha-dockermon and rest switch work back again, thx @philhawthorne
Since I was using these switches with my overnight automation only, I found issues about a week ago. Not know even on what version of HA it happened first time. I discovered it on 2023.6.3

[rdlvm]

Same problem and also error in the HomeAssistant log:

ERROR (MainThread) [homeassistant.helpers.template] Template variable error: 'value_json' is undefined when rendering '{{ value_json is not none and value_json.state == "running" }}'

Trying the previous solution and it is not effective, I get an error when deactivating or activating switch:

ERROR (MainThread) [homeassistant.components.rest.switch] Error while switching off http://192.168.1.15:8126/container/tasmoadmin

[vks007]

Is this issue resolved or not, I am not able to run the start/stop operation by following the workaround mentioned above.
I get an error Error while switching off http://192.XXX.XXX.XXX:8126/container/frigate
My configuration:

switch:
  - platform: rest
    resource: http://192.XXX.XXX.XXX:8126/container/frigate
    method: post
    name: Frigate
    username: redacted
    password: redacted
    body_on: '{"state": "start"}'
    body_off: '{"state": "stop"}'
    is_on_template: '{{ value_json is not none and value_json.state == "running" }}'
    headers:
      content-type: 'application/octet-stream'

I have tried with and without method:post
The switch gets the state of the container fine but fails to either start or stop the same. I am on HA Core version 2023.10.3

[rdlvm]

Is this issue resolved or not, I am not able to run the start/stop operation by following the workaround mentioned above. I get an error Error while switching off http://192.XXX.XXX.XXX:8126/container/frigate My configuration:

switch:
  - platform: rest
    resource: http://192.XXX.XXX.XXX:8126/container/frigate
    method: post
    name: Frigate
    username: redacted
    password: redacted
    body_on: '{"state": "start"}'
    body_off: '{"state": "stop"}'
    is_on_template: '{{ value_json is not none and value_json.state == "running" }}'
    headers:
      content-type: 'application/octet-stream'

I have tried with and without method:post The switch gets the state of the container fine but fails to either start or stop the same. I am on HA Core version 2023.10.3

same problem.